This is incidental to the topic about using XSL to generate tax codes. That other topic is about the repetitive patterns that appear in each VAT system. This topic is about the language of the text in
@dave gave the example how languages are implemented for Belgium. The problem with that solution is that each country will have to duplicate the strings. For example, the strings in the French language are much the same in all EU countries using French (France, Belgium and Luxembourg). Some of those strings are also the same for non-EU countries using French, e.g. Switzerland.
Therefore, I took a new approach:
tax.xmlthat has XML tags for each string. It can also use placeholder arguments
a simple shell script that runs the XSL for each language, notice how the language code is passed on the command line
Notice that only the
tax.xml is specific to
account_ch. The XSL and string list could be used for any countries. I feel this is most relevant for EU countries because they all have similar intracommunity VAT rules, only the language differs from one country to the next.