# Translations for Single Select and Multi Select Widget Options **URL:** \ **Category:** Product Suggestions\ **Tags:** single-select, widget, multiselect, translation\ **Created:** [April 11, 2024, 2:23pm UTC](https://community.tulip.co/t/translations-for-single-select-and-multi-select-widget-options/11187 "2024-04-11T14:23:17Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![nicolettenaya](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/nicolettenaya/32/9105_2.png) [@nicolettenaya](https://community.tulip.co/u/nicolettenaya)\ **Post date:** [April 11, 2024, 2:23pm UTC](https://community.tulip.co/t/translations-for-single-select-and-multi-select-widget-options/11187/1 "2024-04-11T14:23:17Z")
We’re currently unable to translate the options in the single and multi-select widgets. As a workaround, we’re adding both the Spanish and English text to the options. However, this current workaround is not ideal for our operators and citizen developers. As we continue to add more languages, this solution becomes less practical. Is it possible to expand the translation feature to include single and multi-select widget options? Current State: ![Screenshot 2024-04-11 at 10.17.57 AM](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/8/8d3748bccc973017bc8f08597f8dadfb43af4553.png) Work Around: ![Screenshot 2024-04-11 at 10.17.14 AM](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/a/a27d7b318f66a3b10781fcff527092f3c33f964b.png) ---
**Author:** ![Jhondy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jhondy/32/9414_2.png) [@Jhondy](https://community.tulip.co/u/Jhondy)\ **Post date:** [April 11, 2024, 2:40pm UTC](https://community.tulip.co/t/translations-for-single-select-and-multi-select-widget-options/11187/2 "2024-04-11T14:40:12Z")
> [@nicolettenaya](#): > > We’re currently unable to translate the options in the single and multi-select widgets. As a workaround, we’re adding both the Spanish and English text to the options. However, this current workaround is not ideal for our operators and citizen developers. As we continue to add more languages, this solution becomes less practical. Is it possible to expand the translation feature to include single and multi-select widget options? > > Current State: Nice suggestion Nicolette! If the Tulip team eventually implements it, I hope they make sure it applies to both existing styles: ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/c/c528ea6275f3931539af71b3552a4a6ea6ebe7b2.png) ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/5/5bdf6e1820ff38aab787d530d0942336c93fa893.png) ---
**Author:** ![danielpomeranz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/danielpomeranz/32/9379_2.png) [@danielpomeranz](https://community.tulip.co/u/danielpomeranz)\ **Post date:** [April 12, 2024, 5:30pm UTC](https://community.tulip.co/t/translations-for-single-select-and-multi-select-widget-options/11187/3 "2024-04-12T17:30:29Z")
In the meantime, it is nice to know that applications have access to App Info → User Preferred Language which you could use to filter an aggregation for the list. Could make a table like this and then use a filtered unique values aggregation to get the options. ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/1/103faa2caec9fa7540210eb28b172fa694b3048e.png) ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/1/1882f58d3b7f67c8456fe215c4e9737b6c0809de.png) ---
**Author:** ![tokotu](https://avatars.discourse-cdn.com/v4/letter/t/5fc32e/32.png) [@tokotu](https://community.tulip.co/u/tokotu)\ **Post date:** [April 16, 2024, 5:47am UTC](https://community.tulip.co/t/translations-for-single-select-and-multi-select-widget-options/11187/4 "2024-04-16T05:47:43Z")
As a possible solution for non citizien developer… you can create a custom widget loading language by http request and set only the **displayed** value of the selects and not the internal value. So you have no issues regarding data integrity for example issue with triggers based on different language values… ---
**Author:** ![mellerbeck](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@mellerbeck](https://community.tulip.co/u/mellerbeck)\ **Post date:** [April 16, 2024, 6:56am UTC](https://community.tulip.co/t/translations-for-single-select-and-multi-select-widget-options/11187/5 "2024-04-16T06:56:36Z")
This is another way [Simple Langbox Widget](https://community.tulip.co/t/simple-langbox-widget/8162) ---
**Author:** ![pete](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete/32/5653_2.png) [@pete](https://community.tulip.co/u/pete)\ **Post date:** [April 16, 2024, 5:24pm UTC](https://community.tulip.co/t/translations-for-single-select-and-multi-select-widget-options/11187/6 "2024-04-16T17:24:00Z")
@nicolettenaya - great suggestion! This is something we would like to enable, but not something we are able to tackle right now for various reasons. The suggestion from @danielpomeranz is a good suggestion in the mean time.