# Translations in result tags **URL:** \ **Category:** Templates\ **Tags:** variables, translations, result, capture\ **Created:** [August 2, 2018, 12:38pm UTC](https://community.silverfin.com/t/translations-in-result-tags/1084 "2018-08-02T12:38:46Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![SamVanEenoo](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/samvaneenoo/32/134_2.png) [@SamVanEenoo](https://community.silverfin.com/u/SamVanEenoo)\ **Post date:** [August 3, 2018, 7:25am UTC](https://community.silverfin.com/t/translations-in-result-tags/1084/9 "2018-08-03T07:25:59Z")
You can solve this problem by adding the option\_values attribute. As described in this post: > [@CASE: create dropdown with select options](https://community.silverfin.com/t/case-create-dropdown-with-select-options/893): > > If you want to create a dropdown with select options, like this: [06] you’ll have to use the select-tag: {% input period.custom.vat.imported as:select options:"Yes|No" %} However, you might wanna make sure the select-options present themselves in the right language. In order to do so, we’ll need to put those select-options within a translation-tag, and capture that into a new variable we’ll use for the select-tag: {% t= "Yes|No" nl:"Ja|Neen" fr:"Qui|Non" %} {% capture vat\_options %}{% t "… --- _[View the full topic](https://community.silverfin.com/t/translations-in-result-tags/1084)._