Vladimir Prus wrote:
Since most Boost libraries are header only, it makes no sense to ship binary .mo files and the user has to care about Boost's message translation himself.
Well, before .mo file you need to have translated .po. Clearly, translated .po would be of value. Actually, .mo might be of use, too, assuming _("") expands to
dgettext("boost", ...)
as opposed to
gettext(...)
which is a good idea anyway. Of course, the main application will be responsible for install .mo files and hooking them in. And given that, .mo is indeed little advantage over translated .po.
In fact, scratch all the above -- it was written having "shrink-wrapped" applications grabbing all dependencies with them in mind. It's totally fine to have boost install boost.mo into /usr/share/locale/xxx/LC_MESSAGES. Assuming boost code uses: dgettext("boost", ...) to get translations, it will work transparently, without any work for application's developer. - Volodya