2012/8/22 Stephan Bergmann <sbergman@redhat.com>:
On 08/22/2012 05:55 PM, khagaroth wrote:
How much work would it be to make this directly use gettext? I thought
the long term goal was to switch from custom translation formats to
gettext, so using yet another custom translation format for something
like this seems a bit odd.
Seeing gettext mentioned here: What always bothered me about (what little,
really, I know about) gettext, is that AFAIU it is based on the assumption
that a single string S in input language A can always be mapped to the same
string in output language B, even if S appears in multiple places in the
source, with potentially different semantics (that just happen to all be
representable by the same phrase S in language A, but not necessarily so in
language B).
This is why msgctx (message context) was invented, it solved this
problem. In my opinion gettext has other disadvantages in LibreOffice,
such as we cannot use it for all localizable content easily (e.g.
help, Windows installer, etc.).
Andras
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.