This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a re-do for localization and closes #419
The solution is still based on GNU gettext (which is the underlying translation format for
boost::locale
) however this is a simpler integration directly with that tooling.In addition, the translation for
en_US
is embedded in the binary itself leaving no need to produce any translation files for a standard build. Instead, optional translations can be downloaded/packaged separately and installed in the standard location for the given OS/distro (eg{installation prefix}/share/locale
). There is a.pot
file that will need to be updated as new translatable strings are added, and sent to translators to process.