Cosmetic changes in help files

l10n
#1

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 :slight_smile:
Thanks in advance for your understanding,
Cheers
Sophie

#2

Hi Christian,

Hi Sophie, *,

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.

Well, you're right, sorry for the wrong word, but it has been there for
so many years...

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.

The request is to not have all at the same time, and at least have the
l10n team informed about how that will impact them.
If it has been there for years, then the changes could be spanned over
several versions. The same way, we don't organize our time the same if
we know that we will have a large amount of strings to review. If you
tell us "ignore this file", we won't spend time to work on it.
It's just about communication among groups, not to reproach anybody the
work he has done and how legitimate it is, on the contrary each
enhancement is welcome, but evaluating and leverage the impact on others
work is also part of it.
Cheers
Sophie

#3

Hi Sophie, *,

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

#4

Hi Sophie, *,

Hi Christian,
[...] The same way, we don't organize our time the same if
we know that we will have a large amount of strings to review. If you
tell us "ignore this file", we won't spend time to work on it.

Told already: ignore sbasic for now. most of the context-changes are there.

Use pootle's own filters to not translate fuzzy strings, but only
tackle untranslated ones.

Just ignore help after you're done with UI.

There's enough ways to translate without having to deal with those
strings at the moment.

Or just do as it was before introducing the master projects: Wait
until branch is created.
That translators are able to translate right now is a possibility that
they're free to ignore.

There's 4 month time to sort this out.

It's just about communication among groups

Yeah, I lack patience with translators, since I just hate writing the
same thing over and over again.

If they're too impatient to wait for the auto-translation, then they
should not look at helpcontent.

ciao
Christian