On Thu, Dec 12, 2013 at 10:00 AM, Stanislav Horáček
<stanislav.horacek@gmail.com> wrote:
- but that doesn't solve the several typos that already exist and that
are overlooked by the l10n team (e.g in the Character > Font Effect
dialog, there is Overline _c_olor and Underline _C_olor and this is the
same for several dialogs)
It would be worth to create a wiki page that summarizes all these rules - LO
should use the Gnome rules (AFAIK), but there is a lot of specific issues:
for example, descriptions of Calc functions in UI are quite messy because of
different wording ("Returns...", "Calculates...", "Value of...") or
parameter names (capitalization etc.).
Of course the UX team should be also involved.
It is OK to fix new strings, also it is OK to fix obvious typos
anywhere. But we should refrain from re-phrasing old messages. It
would make a lot of unnecessary work for translators, and loss of
translation for unmaintaned languages. IMHO we have more important
things to do, than unify ("Returns...", "Calculates...", "Value
of...") or ("cannot", "couldn't", "could not") or whatever.
Best 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.