Dear developers,
A reminder about dealing with help files and cosmetic changes: the l10n
team is again impacted with thousands of changes (57k fuzzy strings that
needs to be checked one by one) that doesn't concern them. Examples:
<swichinline><caseinline><emph></emph></caseinline></swichinline> has
been changed to
<emph><swichinline><caseinline></caseinline><swichinline></emph>.
or
attributes removal such as oldref
etc.
Please, please before doing such changes, have a thought about the
balance between the work you ask to the l10n team and the value of the
change. If it's really necessary (I can understand cleaning of oldref,
yes), write a script or ask for it and don't commit until you get it. In
any case, drop a line to the l10n list so we can help without being
under the impression that nobody cares :)
Thanks in advance for your understanding,
Cheers
Sophie
--
Sophie Gautier sophie.gautier@documentfoundation.org
GSM: +33683901545
IRC: sophi
Co-founder - Release coordinator
The Document Foundation
--
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
- [libreoffice-l10n] Cosmetic changes in help files · Sophie
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.