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


Hi Sophie, *,

On Tue, Mar 22, 2016 at 11:44 AM, Sophie <gautier.sophie@gmail.com> wrote:
Dear developers,

A reminder about dealing with help files and cosmetic changes:

Despite what translators think and how they voice their opinion,
fixing syntax errors is not doing cosmetic changes.

Validation errors have been ignored for too long, time to weed that
out, whether translators like it or not.
We have validation checks in pootle for a reason. While some are less
useful than others, at least the xml-validility ones should be
respected.  And if people don't know why a error is triggered, they
should use feedback functionality/ask on the list.

attributes removal such as oldref

and this has been discussed already. (that's the cause for msg-context
changes and will be auto-fixed)

Adding up already-told-to-be-autofixed with other occurences of fuzzy
strings won't make that double the amount of strings to fix.

/me already deleted a reply to Martin because of my tone, so  I'll
keep that one short...

ciao
Christian

-- 
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.