The code supports localized templates of page labels and file names. However, the app currently stores the templates only in their localized versions. That means that the configured templates are "lost" if the user chooses another language for the user interface.
To overcome this templates should be stored untranslated and always translated to the currently active language setting after retrieving the untranslated variant from the user preferences. Likewise, if the user configures a template the substitution keys should be "reverse translated" to the default language before writing them back to the user preferences.
rotdrop
commented
1 year ago
The code supports localized templates of page labels and file names. However, the app currently stores the templates only in their localized versions. That means that the configured templates are "lost" if the user chooses another language for the user interface.
To overcome this templates should be stored untranslated and always translated to the currently active language setting after retrieving the untranslated variant from the user preferences. Likewise, if the user configures a template the substitution keys should be "reverse translated" to the default language before writing them back to the user preferences.