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


On Tue, May 28, 2013 at 1:28 PM, Mihovil Stanic
<mihovil.stanic@gmail.com> wrote:

I feel your pain. :)
I'm coming from Mozilla L10n in which you have access keys as a separate
strings to LO in which there is 3 different ways to mark access keys. I'm
not against marking access keys inside strings, but PLEASE decide how you
want to do it.

It is not possible, different technologies use different hotkey markers.
~ is for old VCL
_ is for new .ui
& is for native Windows widgets

Also, I'm having problems with knowing which of one word strings are free to
translate and which are variables (place holders or whatever it's called,
which I shouldn't translate). Not really sure why you are even offering
those strings in Pootle translation if they shouldn't be translated.

Please give us examples. If a string is not for translation, I'll take
it out from the pool. It may help, if you check other localizations in
Pootle, and see, if the string in question is translated there.

Regards,
Andras

-- 
To unsubscribe e-mail to: l10n+unsubscribe@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

Context


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.