Feature Request: Separate document language from UI language. Optionally: Add the option of changing the documentment language for a single printout. #165
Right now the language of the label.* variables in a print template depends on the UI language and thus on the current environment. This makes multi-language usage (I need to be able to generate documents in English or German depending on the customer; a Belgian company should be able write in French, Dutch and German (and Neusser Platt) as required). Changing the shell environment to get that done feels like ripping out the cogs to change gears. The cleanest way to to it would be adding a language indicator to the documents (with the option of overriding it for printing).
If you want to support billing of foreign customers according to current European tax regulation it would also be required to add a link to the relevant taxes (just order food from an online shop in the Netherlands and you'll see the immediate massive drop in VAT). This might require moving to the database-less XML document structure...
Right now the language of the label.* variables in a print template depends on the UI language and thus on the current environment. This makes multi-language usage (I need to be able to generate documents in English or German depending on the customer; a Belgian company should be able write in French, Dutch and German (and Neusser Platt) as required). Changing the shell environment to get that done feels like ripping out the cogs to change gears. The cleanest way to to it would be adding a language indicator to the documents (with the option of overriding it for printing).
Another reason for this is more efficient use of text snippets and catalog entries (see also https://github.com/dragotin/kraft/issues/164).
If you want to support billing of foreign customers according to current European tax regulation it would also be required to add a link to the relevant taxes (just order food from an online shop in the Netherlands and you'll see the immediate massive drop in VAT). This might require moving to the database-less XML document structure...