Hi Sérgio, *,

On Tue, Jul 23, 2013 at 4:02 PM, Sérgio Marques <smarque...@gmail.com> wrote:
> 2013/7/23 Martin Srebotnjak <mi...@filmsi.net>

Why was there no announcement when getting the changes from pootle?
→ because there was no check that triggered a warning. Also there was
no merge-conflict, as the problem is not with the translated strings,
but how they are used.

And yes, a comment in the po file is one way to avoid that. And yes,
not using the translated names as internal IDs of course is better. It
will confuse the heck out of users to have two styles with the same
name, with no way to distinguish them. But at least the document state
would stay consistent. So you would still need the additional
checks/hint for translators.

> Agreed but please notice that those strings came from OO and never was the
> need to change.

No need for change was always there - but probably nobody complained
for that language. This time round, large language communities were
affected that did spot the inconsistency. So call it luck that the
bigger groups did make that mistake to take this problem into focus.

>> 2013/7/23 Sérgio Marques <smarque...@gmail.com>:
>> > 2013/7/23 Krunoslav Šebetić <kruno0...@gmail.com>
>> >>  On 07/23/2013 01:45 PM, Sérgio Marques wrote:
>> > [...]
>> > But we do need to know when a conflict exist. If we don´t know it how can
>> > we fix?

I thought this was pretty clear: You must not use the same string for
those two IDs. The Heading style must have a different translation
than then Title style.

>> >> We also have problem with that - it's only our fault...

At least nobody did spot that problem in all the time where the
strings were the same for over 30 languages...

ciao
Christian

-- 
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to