[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] Wrong efect at LibO 4.0 beta2 help

Hi Joan,

On Wed, Dec 26, 2012 at 10:26 AM, Joan Montané <joan@montane.cat> wrote:
> Hi,
> we (the Catalan l10n team) are testing currently l10n using LibO beta2 and
> we have found a weird effect at help.
> Some index entries look weird (see attached screenshot). Looking this
> problematic string at Pootle [1], We guess the cause. 2 different
> <bookmark_value> English string fields have been translated to the same
> Catalan strings. These aren't bad translations, because booth English
> strings translate to the same Catalan strings.
> So, the question is:
> What is the best approach to avoid the current behaviour?
> Can we delete the second <bookmark_value> at translated string?

Yes, you can add or remove <bookmark_value> as you wish. It is
designed so, that it does not have to match 1:1 with the English

Best regards,

Unsubscribe instructions: E-mail to l10n+help@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

Re: [libreoffice-l10n] Wrong efect at LibO 4.0 beta2 helpJoan Montané <joan@montane.cat>
[libreoffice-l10n] Wrong efect at LibO 4.0 beta2 helpJoan Montané <joan@montane.cat>
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.