Raymond Hettinger wrote: > I'm curious whether there were thoughts about how to keep the > translations in sync with their English counterparts. Using standard gettext procedures. You extract all new docstrings, and merge the old translations with the new docstrings. Some translations become fuzzy, and the translators have to review them. Likewise, some docstrings will become new. As a result, some of the translations are always outdated, and the standard gettext procedure is to ignore them and fall back to a different language (e.g. if you had both pt_BR and pt translations, and pt_BR is outdated, you might fall back to the pt translation, before falling back to en_US). However, this is all way ahead in the future. Translating all doc strings is very time consuming, and hasn't been completely done for any language so far. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4