Trust me, "look up" strategies using gettext() <https://docs.python.org/3/library/i18n.html> are worse. They require you to translate a bunch of labels without the context of where they are going to be used.
-tk On Sat, Mar 16, 2019 at 1:27 PM kobuki <[email protected]> wrote: > Alright, thanks for the answer. This is the current state - is it possible > that in the future this might change and we can use custom template > variables for i18n for centralized configuration? Changind each and every > template by hand is tedious. Though automation is possible... > > On Saturday, March 16, 2019 at 8:07:51 PM UTC+1, Thomas Keffer wrote: >> >> See the section *Localization >> <http://weewx.com/docs/customizing.htm#localization>* in the Customizing >> Guide. >> >> To answer your specific question, any label that does not use a tag will >> have to be changed in the template. Other labels that do use a tag, such as >> $obs.label.barometer, are changed in weewx.conf. >> >> -tk >> >> On Sat, Mar 16, 2019 at 10:34 AM kobuki <[email protected]> wrote: >> >>> I've just upgraded to WeeWx 3.9.1 from 3.7.1. No problems at all, it >>> picked up the old config and went on running without a hitch. The new >>> default skin is a bit better than the old one, though I'm not using it yet, >>> for reasons outlined below. >>> >>> So, I was happy to see that many labels and metrics are templated and >>> can be defined in weewx.conf, but unfortunately not all. I would still need >>> to edit the templates by hand to fully translate them to my own language. >>> What is the recommended method for that? Is it possible to just add new >>> labels and their translations and refer to them like the rest of them >>> available in the weewx.conf sample? Like $obs.label.barometer, >>> $obs.label.rain, etc. The section headers on the left side of the web page >>> or the Almanac, for instance, still need translation. What is the current >>> recommended way to translate them? Is it planned to allow a user to define >>> them, or even arbitrary labels for use in templates, inside weewx.conf? It >>> would be great to have something like $custom.label.xxx at least for a >>> centralized definition. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weewx-user" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
