Good afternoon gentlemen :-), A question with regard to translations and result tags. I’d like to use t-tags, but from a separate file with the explicit aim of reusability. So in the separate file (with the handle ‘Parameters’), I typed: {% capture herwaardering %}{% t= “herwaardering” fr:“réeval…

Hi Bart You are using the equal sign wrongly in the translation tag. Adjusting it like will probably solve it: {% t=“herwaardering” fr:“réevaluation” en:“revaluation” %} {% capture herwaardering %}{% t “herwaardering” %}{% endcapture %} {% result ‘herwaardering’ herwaardering %} Kind regards S…

OK Sam, thanks! Now, have a different question: is it also possible to use these translations as options in a select as follows (for example): ´´´ {% comment %}Step: Bepaal de juiste naam voor de leidinggevende(n){% endcomment %} {% capture company_form %}{{ company.company_form | replace: ‘.’,’…

Funny thing here is that both options seem to work, but when you delete the first option, the second doesn’t work anymore! Any clues? Thanks!

[image] Bart_Verhaeghe: {% capture leidinggevende_termen %}{% t= ‘bestuurder|bestuurders’ fr:‘gérant|gérants’ en:‘manager|managers’ %}{% endcapture %} {{leidinggevende_termen}} {% capture leidinggevende_juisteterm %}{% t ‘bestuurder|bestuurders’ fr:‘gérant|gérants’ en:‘manager|managers’ %}{% e…

Hi Sam, OK I adapted this (see below), but I still get the same funny result: it ‘works’ like this, but when I omit the 3 lines around leidinggevende_juisteterm, menu2 doesn’t work anymore, which is really strange … any ideas? Thanks! {% comment %}Step: Bepaal de juiste naam voor de leidinggevende…

Hi Bart I’m wondering if this is what you are searching for? {% comment %}Step: Bepaal de juiste naam voor de leidinggevende(n){% endcomment %} {% capture company_form %}{{ company.company_form | replace: '.','' | replace: ' ','' | upcase }}{% endcapture %} {% case company_form %} {% when '…

Hi Sam, This works indeed. Great and many thanks! Just a small remark: it’s a pity that the select becomes empty again when you change the language. So switching from Dutch to French does not automatically change the selected option from ‘bestuurder’ to ‘gérant1’. But this is already very nice … …

You can solve this problem by adding the option_values attribute. As described in this post: [image] CASE: create dropdown with select options Workbook & Cases If you want to create a dropdown with select options, like this: [06] you’ll have to use the select-tag: {% in…

Once again thanks Sam, This already works nicely, but I’d like to put the options themselves in different languages in separate variables, so they can be referenced later on with a result tag (so the strings themselves can be used in different templates). However, this doesn’t work as expected. A h…

[image] SamVanEenoo: {% comment %}Step: Bepaal de juiste naam voor de leidinggevende(n){% endcomment %} {% capture company_form %}{{ company.company_form | replace: ‘.’,‘’ | replace: ’ ‘,’’ | upcase }}{% endcapture %} {% case company_form %} {% when ‘MAATSCHAP’ or ‘CVBA’ or ‘CVOA’ or ‘NV’ or ‘SE…

Translations in result tags

Templates

SamVanEenoo August 3, 2018, 7:25am 9

You can solve this problem by adding the option_values attribute. As described in this post:

Topic		Replies	Views
CASE: create dropdown with select options Cases input , as_attribute	2	835	December 18, 2018
Translate options of checkbox Templates translations , filter_array	6	756	February 14, 2019
CASE: variables in translation-tags Cases variables , translations , case	0	763	May 17, 2018
Problem font and text in a document Templates	13	754	March 24, 2021
CASE: how to translate templates for use in other language (fr, en)? Cases	1	702	May 14, 2017

Translations in result tags

Related topics