Op 28-1-2020 om 12:16 schreef Stehmann:
That will be great help
Mechtilde
Am 28. Januar 2020 12:04:45 MEZ schrieb Dick Groskamp
<th.grosk...@quicknet.nl.INVALID>:
Op 27-1-2020 om 19:33 schreef Mechtilde:
Hello Dick,
if you double check it, then it is ok to disable the warning and hope
that it also works in the conversion.
And hope the translation works in the build.
I know there isn't an easy solution I'm now working on the "critical
errors" for German.
Kind regards
Mechtilde
Am 27.01.20 um 19:06 schrieb Dick Groskamp:
Op 27-1-2020 om 18:21 schreef Mechtilde:
Hello,
no that isn't a problem of the pootle server
It prevents to have problems to convert from po-files to sdf-files
in
the gsicheck.
Please try to solve most of the message.
otherwise it needs much manual works to get the translation into
the
code.
Kind regards
Mechtilde
Am 27.01.20 um 14:59 schrieb Dick Groskamp:
Op 27-1-2020 om 13:52 schreef Taavi Kaevats:
My original question was about strings within double quotes
within
angle brackets. Those that were already translated in many
languages,
but did generate critical error.
I can do one way or another, but the feedback i have received so
far
is rather contradictional. Strange.
Yep I know :-)
The Critical error is a Pootle thing. It mostly is a false
positive that
you don't need to concern much about.
It reacts on all XML-tags within a segment, even the non-link
tags, and
even on things that look like a XML-tag
It will probably work anyway in OpenOffice.
It is a bit hard to explain what to translate always and what not.
It is
not always black/white.
It depends a lot on the way the segment is used within OpenOffice.
Most times, when you look at it, you probably right away will see
if
something should be translated or not.
I think you can rely on the already translated strings that you
use as a
reference.
If that is translated you can translate also, if not don't ( or
ask so
we can check together)
If it is alreayd translated in several other languages, it
probably
should also be translated into your language :-D
OK, I'm lost now.
Are we talking about the XML-tags Critical errors in Pootle ?
I know I fixed number of them and most were false positives.
I checked the string several times and there was nothing wrong with
the
string, but the Critical error remained.
After I doublechecked the string I disabled the warning.
Can you point out where I'm going the wrong way ??
OK, thanks it should be OK for Dutch then.
Had a quick look at the Critical XML-tags for German.
Found that about 1500 tags seem to have somehow had the excessive
string
"visibility="visible"" added in links in the translated German string,
whilst it is not (or no longer) in the original string in EN.
I think it should be removed from the German string to make the
Critical
error go away.
If you would I could help you out there. I do have some spare time.
--
DiGro
___________________________
Apache OpenOffice 4.1.7 (Dutch) and scanned with Ziggo Safe Online
(F-Secure)
---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org
OK, I'll concentrate on the " visibility="visible" " then
--
DiGro
___________________________
Apache OpenOffice 4.1.7 (Dutch) and scanned with Ziggo Safe Online (F-Secure)
