![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Hello all,
please avoid translation of wrongly formatted strings, even their
retranslations.
I am in a bigger process to correct them and improve formatting like
emphasises in help text sentences themself.
The only one I leave untouched for now are the malformed bookmark tags.
Why would we do that - leave them untranslated?
Could you please elaborate with an example?
Lp, m.
V sre., 25. apr. 2018 14:07 je oseba Sophia Schröder <
sophia.schroeder@outlook.com> napisala:
I am going to correct them, so they would appear again. 
Example:
Hi Sophia, Olivier, all
I am going to correct them, so they would appear again.
Example:
This should not arrive in Pootle, there is no translation work here, so
why should we care about it? Again, the commit introducing spaces should
not have been pushed. Why hundreds of languages should work on that 2 or
3 times afterwards?
Cheers
Sophie
Hi Sophie, *,
this is what I meant:
If new strings arrive in pootle, and there are wrong / malformatted,
leave them out of translation for now and do it *after* they are corrected.
Unhappily I cannot test them beforehand locally
(and I am not responsible for most of them beeing malformatted, but of course a few. ;-))
Suggestions for improvements even of wording and text formatting are always welcome, of course.
Hi Sophia, Olivier,
Hi Sophie, *,
this is what I meant:
If new strings arrive in pootle, and there are wrong / malformatted,
leave them out of translation for now and do it *after* they are corrected.
This is not how our workflow is going, if it's in Pootle then we have to
review it and work on it and it will double our work. More, it's even
not a translation work.
Unhappily I cannot test them beforehand locally
(and I am not responsible for most of them beeing malformatted, but of
course a few. ;-))
I don't say it's because of you of course 
what I mean is that these
space typos introduce a lot of work for l10n for a very little gain for
documentation.
Suggestions for improvements even of wording and text formatting are
always welcome, of course.
There are a lot of suggestions done through Pootle already where commits
should not have gone through but should have been reviewed before
impacting all of us.
But if you want to work on typos, corrections and enhancements that will
serve both documentation and l10n, I would be very happy to work with
you on this, I triage all the suggestions for Olivier already, and I can
forward to you what needs to be corrected. Would you be interested on
working on this with me?
Cheers
Sophie
Hi, Sophia, *,
that is why I suggested a simple extension of gerrit interface with a flag
whether that particular issue changes UI or help strings/affects l10n
process.
That way it would be much easier for interested documentation and l10n team
members to check on those entries before they get pushed or report errors
just as they get pushed. And not after a few months when they land in the
updated Pootle and first translators recognize them as errors ...
Lp, m.
Hi Martin, *,
yes, this or another approach... . But sadly, we still haven't one. At least I am not aware of such.
I am a translator, mostly fixing stuff in our own translation or silence false positives, when they occur for better overview.
So I stumbled over the failures in our help text sources, and since I am able to contribute there myself, thank to:
https://wiki.documentfoundation.org/Documentation/GerritEditing .
I do not longer waste my and others time to report them.
In opposite, I asked to forward such reports to me, so I can look into the correspondending file and correct,
what I find there.
But for now, I know I have to be a bit reluctant for the reason already mentioned.