Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index

2017-06-04 22:23 GMT+03:00 <>:


Yes, Bulgarian is also one of those inflected languages that require
different translations to the same English phrase depending on the context.
If we lose msgctxt, we must have another way to separate different
instances of the same English phrase. Years ago at my workplace, we had
this problem with an in-house l10n system and AFAIR we circumvented it by
including the context in the original translatable string where necessary
and then removing it in a small English ‘translation’, something like this:

Original: Number|noun
English translation: Number
Bulgarian translation: Номер

Original: Number|menu_item
English translation: Number
Bulgarian translation: Номериране

Original: Settings
English translation: <same as the original, so not included in the l10n
Bulgarian translation: Настройки

So this could be a fallback if the new system does not support a
context/instance id separate aside from the translatable text itself. UI
code can also automatically strip the part after the escaping character,
thus eliminating the need for an English ‘translation’.


While I appreciate the ingenuity of this approach, it would be utter
stupidity to replace a well-working implementation with msgctxt with such a
system in a l10n project the size of LibO :)

Best, Mihkel

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.