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

On Fri, Jan 17, 2014 at 7:21 AM, Fridrich Strba
<> wrote:

On 16/01/14 21:18, Andras Timar wrote:
Content of <value xml:lang="x-default"> tag is not extracted for
translation, you need to use xml:lang="en-US". Same applies to all of
your exotic filters. So actually you did not add a new string for
translation. But you may want to enable translation for all of these
"FooBar Document" strings which exist under

Could you check in whether that is
what we want? Not sure what to do with ui strings that only say
"Microsoft Visio", how localizable that should be. OTOH, I would not be
surprised if for some languages it would be "Микрософт Визио".

Please, advise

Yes, I think we can allow localization/transliteration for all filter
names. It is up to the translators to keep the proper names. I trust
the community. :)

To translators: From the technical point of view, 42 new strings will
appear for translation. 41 of them have been in the source code for
ages, but were not localizable. Nothing will change, if you leave them
alone, they will be in English as before. The +1 new string is
"AbiWord Document".

Best regards,

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.