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
Hi Sophia, Olivier,
Le 25/04/2018 à 16:47, Sophia Schröder a écrit :
> 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
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,
Hi Sophia, Olivier, all
Le 25/04/2018 à 14:33, Sophia Schröder a écrit :
> I am going to correct them, so they would appear again. ;-)
>
> Example:
>
> https://translations.documentfoundation.org/de/libo_help/translate/#filter=incomplete=149686853=54
This should not arrive in Pootle, there is
I am going to correct them, so they would appear again. ;-)
Example:
https://translations.documentfoundation.org/de/libo_help/translate/#filter=incomplete=149686853=54
Am 25.04.2018 um 14:21 schrieb Martin Srebotnjak:
Why would we do that - leave them untranslated?
Could you please
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.schroe...@outlook.com> napisala:
> Hello all,
>
> please avoid translation of wrongly formatted strings, even their
> retranslations.
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.
--
To
