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

21.06.2015 u 14:17, Mikhail Balabanov je napisao/la:
Hello again with some more questions :)

I have worked on the Bulgarian l10n of and then LibreOffice
for quite some time and I have always assumed some things but in the light
of the new warning system I decided to ask. :)

* Is it OK to rearrange named placeholders because of different word order
in the translation language, for example (like '$type$ library "$name$"' ->
'library "$name$" of type $type$')?

Is it always safe to mute the
corresponding warnings?
* Is it OK to skip tag pairs and placeholders? In Bulgarian, repeating the
name of something in several sequential sentences is often considered
awkward style so I sometimes replace it with pronouns, skipping things like
%PRODUCTNAME and <emph>(control name)</emph>.
Probably yes
* Is it OK to add tag pairs? In some contexts, it appears that the original
misses a tag pair, for example the names of three of the four parameters of
a function are boldfaced in the explanation but the last one is not. I have
sometimes added <emph> tags for them, now I find these units due to the
warnings and wander whether to mute or to remove the tags and wait until
someone fixes the original.
Don't know

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.