nirenjan
5fecdd3929
In order to improve security around the command processing, I plan to upgrade the communication protocol to use a fixed structure with an optional payload. As a first pass on this, I added a script to generate the IDs automatically from the configuration, as well as a script to map the module names and log levels to integer IDs. This also replaces the manual lmap_* and array_get_index lookup tables, so I don't have to always deal with creating an entry in constants.h and command.c and making sure they are in sync. |
||
|---|---|---|
| .. | ||
| LINGUAS | ||
| Makevars | ||
| POTFILES.in | ||
| README.md | ||
| libx52.pot | ||
| meson.build | ||
| xx_PL.po | ||
README.md
Notes for translators
libx52 is slowly being migrated to use the GNU gettext library to support
internationalization (i18n). Contributions are welcome to both update the
existing code to use gettext, and to add new translations.
xx_PL
xx_PL is a translation of English strings into Pig Latin that is used in lieu of any real translations. This file is used to test that the translation functionality is working as expected.
Adding new code to i18n (maintainers)
Most code should be using the _("...") format to refer to a translatable
string. Some strings can be left untranslated, but these are mostly just
whitespace, such as line breaks.
Once you add new strings to be translated, update po/POTFILES.in to include
any new files that have to be translated. The file path is relative to the root
of the project.
The next step is to rebuild the translation template libx52.pot. From the
repository root, run meson compile -C build libx52-update-po (adjust build
to your build directory), or ninja -C build libx52-update-po. This also
updates any translation files (with .po extension) to include the new source
strings.
Adding new languages (translators)
Run msginit -l <language-code> libx52.pot to generate a new .po file
for that language. Language code is a 2 letter
ISO-639-1 code with an
optional ISO-3166-1 region
suffix. Edit this file to add your translation, and add the new language to
po/LINGUAS.
po/LINGUAS must be in alphabetical order.
Testing the i18n functionality
TODO