Pootle disallows to translate [Runtime]

jbfaure · June 14, 2017, 6:03am

Hi,

For example in each string like bnHLi or u3nsA (Option VBASupport Statement [Runtime]), Pootle does not accept I translate [Runtime] ([Exécution] in French).
If I translate this file sbasic/shared.po offline, I guess I will have a lot of false positive errors in Pootle.

What can I do to fix that ?

Best regards.
JBF

ohallot · June 14, 2017, 9:42am

Hi Jean-Baptiste

Hi,

For example in each string like bnHLi or u3nsA (Option VBASupport
Statement [Runtime]), Pootle does not accept I translate [Runtime]
([Exécution] in French).
If I translate this file sbasic/shared.po offline, I guess I will have a
lot of false positive errors in Pootle.

What can I do to fix that ?

Best regards.
JBF

Is it because "[Runtime]" is seen as a placeholder? If affirmative, you
may silence it by clicking on the red (-) sign in the top right of the
string area. False positives are very frequent in pootle+LibreOffice.

Regards

Dwayne_Bailey · June 15, 2017, 2:41pm

We really do like eliminating false positives, specifically the critical
(red) ones. Too many false positives and people ignore tests.

It might be worth reviewing this data
https://github.com/translate/translate/blob/master/translate/filters/checks.py#L1992-L1995
as I'm not familiar anymore as to which variable styles are relevant now
that LibreOffice uses PO files. Eliminating `("[", "]")` might eliminate a
whole class of false positive variable warnings.

Also please let us know if checks don't apply to your language, e.g.
accelerators. Or if they ned to behave differently, quoting. And we have
some examples of Romanian checks so you are able to create custom language
specific checks (if you can code in Python).

sophi · June 15, 2017, 2:56pm

Hi Dwayne,

Hi Jean-Baptiste

Hi,

For example in each string like bnHLi or u3nsA (Option VBASupport
Statement [Runtime]), Pootle does not accept I translate [Runtime]
([Exécution] in French).
If I translate this file sbasic/shared.po offline, I guess I will have a
lot of false positive errors in Pootle.

What can I do to fix that ?

Best regards.
JBF

Is it because "[Runtime]" is seen as a placeholder? If affirmative, you
may silence it by clicking on the red (-) sign in the top right of the
string area. False positives are very frequent in pootle+LibreOffice.

We really do like eliminating false positives, specifically the critical
(red) ones. Too many false positives and people ignore tests.

It might be worth reviewing this data
https://github.com/translate/translate/blob/master/translate/filters/checks.py#L1992-L1995
as I'm not familiar anymore as to which variable styles are relevant now
that LibreOffice uses PO files. Eliminating `("[", "]")` might eliminate a
whole class of false positive variable warnings.

Also please let us know if checks don't apply to your language, e.g.
accelerators. Or if they ned to behave differently, quoting. And we have
some examples of Romanian checks so you are able to create custom language
specific checks (if you can code in Python).

Thanks a lot Dwayne, I'll have a look to the data during next week and
give you my feedback.
Cheers
Sophie

jbfaure · June 15, 2017, 8:14pm

Hi,

Hi Jean-Baptiste

Hi,

For example in each string like bnHLi or u3nsA (Option VBASupport
Statement [Runtime]), Pootle does not accept I translate [Runtime]
([Exécution] in French).
If I translate this file sbasic/shared.po offline, I guess I will have a
lot of false positive errors in Pootle.

What can I do to fix that ?

Best regards.
JBF

Is it because "[Runtime]" is seen as a placeholder? If affirmative, you
may silence it by clicking on the red (-) sign in the top right of the
string area. False positives are very frequent in pootle+LibreOffice.

Thank you Olivier. In fact when I validate my translation by ctrl+Enter, Pootle change the background color of the text area to orange (instead of blue when Pootle is happy with my translation or red when it find an syntax error) and stay there instead of jumping to the next string. It does not show the error icon (red (-)). I discovered that Pootle has however accepted my translation and that I can force it to jump to the next string.

If I go back to the problematic string, now I see the error icon and I can desactivate the placeholder check.

Best regards
JBF

mbalabanov · June 16, 2017, 7:25pm

Hello,

We really do like eliminating false positives, specifically the critical
(red) ones. Too many false positives and people ignore tests.

+1 After clicking through several hundreds of these just to see them
reemerge a couple of week later (regardless that there were no changes in
the original strings or the translations themselves), I just gave up and
can’t blame anyone who did the same. Can we at least have a keyboard
shortcut, or a way to disable the warnings when translating offline?
Currently the only way of switching them off is ‘ctrl+down, *wait for page
reload*, target tiny button with mouse, click, *wait for page reload*,
repeat ~750 times’, not the most effective use of one’s volunteering time.

that LibreOffice uses PO files. Eliminating `("[", "]")` might eliminate a
whole class of false positive variable warnings.

+1 Especially for the case in question, I don’t see any reason not to
replace all these [Runtime] with (Runtime) or even (Runtime library) which
further clarifies the intended meaning.
Also, all examples in the Help that look like (but are not) XML tags should
probably be changed from <non-tag> to something like <non-tag>,
eliminating another class of false positives.

Cheers,
Mihail