Dňa 31.12.2011 13:56, Andras Timar wrote / napísal(a):
2011/12/31 Martin Srebotnjak <miles@filmsi.net>:
I guess the conservatism of OOo team when designing UI with those UI spec
documents was a good thing and this should be in a way incorporated in the
LO development process, even if with a lower administration impact on
developers - but there should be some l10n representative checking ALL the
proposed changes of UI strings - that they are logical and that they are
localizable in all 100+ languages. Only then they could be checked in.
No, that would effectively kill productivity. It is better to catch
issues in beta phase. Not to mention that the UI approved by a
comittee in the Sun era still resulted crap. See the history of
http://opengrok.libreoffice.org/history/core/cui/source/dialogs/insrc.src,
it is Mihkels example. This file has not been touched by LibreOffice
developers.
So, Andras, will you take care of these two string-formations in the code
for 3.5, the one reported by Milos and the one by Mihkel? Or do we have to
adapt our translations according to "what the author of code wanted to
say"? Time for 3.5 is running out I guess.
I don't understand why anyone needs to adapt translations for Milos' example.
We have "Delete $1" and "Format $1" where $1 can be "Header" or
"Footer". Those are STR_HEADER and STR_FOOTER from
sw/source/ui/docvw/docvw.src and are not used anywhere else, so you
can translate them as you need to fit into the "Delete $1" context. I
hope the translation for "Header" or "Footer" is not different
depending on if you delete it or if format it.
No, it is not different.
So, I corrected the translation to the accusative case without the
capital letter. I could have done that also earlier (thanks to KeyId),
but I was not sure if these string were used elsewhere in a different
context (say, in nominative) or not. Now I know :)
Thanks
Milos
As for the Insert Rows/Columns modal dialog, it was a good catch that
needs to be fixed. But if it have been good enough for the last couple
of years, then I don't think we need to urgently fix it in 3.5 and
break the string freeze. Let's fix it in master. What do you think?
Best regards,
Andras
--
email & jabber: sramek.milos@gmail.com
--
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
Context
- Re: [libreoffice-l10n] compound strings · Milos Sramek
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.