Re: XML tags
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 : 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)
Re: XML tags
That will be great help Mechtilde Am 28. Januar 2020 12:04:45 MEZ schrieb Dick Groskamp : >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
Re: XML tags
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
Re: XML tags
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 ?? > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: XML tags
Op 27-1-2020 om 16:44 schreef Dick Groskamp: Op 27-1-2020 om 15:54 schreef Taavi Kaevats: /offlist Hi, DiGro i see you've taken it offlist at one point? you don't preferre public discussion to reach a common understanding for everyone? anyway, i see your point and it is what i actually expected. I am not sure tho, why Mechtilde told to not change anything. PS! i also read your instructions to disable the warning. I have checked in the online environment and it seems to me there is much faster way for the same result: - Click the icon next to the warning XML tags ( it will turn grey) - Switch to the next or previous string using up/down arrow there are now 1 critical error less at the overview pane without editing/saving the string itself Do you confirm or override? Regards, tav Taavi, no problem to discuss it openly, but I thought the mail was sent to me personally, so I left out the mailinglist. So back to the list Tried your solution for the warnings. On an existing translated string it throws me an error NOT FOUND if I click the icon and won't turn grey. That's why I first have to edit the string. Then it works for me. "Do you confirm or override?" - I don't get such an option Greetings Maybe this link helps a bit : https://wiki.openoffice.org/wiki/Pootle_User_Guide/Translation_Built-in_Help -- 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
Re: XML tags
Op 27-1-2020 om 15:54 schreef Taavi Kaevats: /offlist Hi, DiGro i see you've taken it offlist at one point? you don't preferre public discussion to reach a common understanding for everyone? anyway, i see your point and it is what i actually expected. I am not sure tho, why Mechtilde told to not change anything. PS! i also read your instructions to disable the warning. I have checked in the online environment and it seems to me there is much faster way for the same result: - Click the icon next to the warning XML tags ( it will turn grey) - Switch to the next or previous string using up/down arrow there are now 1 critical error less at the overview pane without editing/saving the string itself Do you confirm or override? Regards, tav Taavi, no problem to discuss it openly, but I thought the mail was sent to me personally, so I left out the mailinglist. So back to the list Tried your solution for the warnings. On an existing translated string it throws me an error NOT FOUND if I click the icon and won't turn grey. That's why I first have to edit the string. Then it works for me. "Do you confirm or override?" - I don't get such an option Greetings -- 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
Re: XML tags
Hello I gues that the links etc doesn't work after building. Many of them are name anchor for links. Or that are name of variables. So you can test it in your translated version. Kind regards Mechtilde Am 26.01.20 um 19:36 schrieb Taavi Kaevats: > Hi > >>> Please don't translate the words between "<" and ">" > > This is confusing. > >> Project instructions >> Please don't add more spaces between "<" and ">" than in the English version. > > It doesnt say there cannot be less spaces or that the letters cannot > be changed between the symbols. > > Also, the words i spoke about ARE WIDELY TRANSLATED all over the languages. > > Take a look at the (random) screenshot for example: > https://pasteboard.co/IRN13yi.png > > So the work should be reversed in all languages? > > Looking for your reply, > Taavi > > conversation history: > 2020-01-26 19:25 GMT +02:00, Mechtilde : >> Hello, >> >> Am 23.01.20 um 11:17 schrieb Taavi Kaevats: >>> Hi, >>> >>> I am experiencing difficulties to decide whether to translate >>> translatable attributes (descriptions, titles etc) within "<" and ">". >>> (in help files) >>> I am working with 4 alternative language (including english and >>> german) to compare the source and there are portion of strings (more >>> than 100) where all 4 alternatives are translated into native >>> languages. However when i submit the translated version to my work, i >>> receive an "Critical errors: XML tags ". >>> >>> How exactly should i proceed? >> >> Please don't translate the words between "<" and ">" >> >>> >>> Regards, >>> Taavi >> >> Kind regards >> >> -- >> Mechtilde Stehmann >> ## Apache OpenOffice >> ## Freie Office Suite für Linux, MacOSX, Windows >> ## Debian Developer >> ## PGP encryption welcome >> ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F >> >> > > - > To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org > For additional commands, e-mail: l10n-h...@openoffice.apache.org > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: XML tags
Hi > > Please don't translate the words between "<" and ">" This is confusing. > Project instructions > Please don't add more spaces between "<" and ">" than in the English version. It doesnt say there cannot be less spaces or that the letters cannot be changed between the symbols. Also, the words i spoke about ARE WIDELY TRANSLATED all over the languages. Take a look at the (random) screenshot for example: https://pasteboard.co/IRN13yi.png So the work should be reversed in all languages? Looking for your reply, Taavi conversation history: 2020-01-26 19:25 GMT +02:00, Mechtilde : > Hello, > > Am 23.01.20 um 11:17 schrieb Taavi Kaevats: >> Hi, >> >> I am experiencing difficulties to decide whether to translate >> translatable attributes (descriptions, titles etc) within "<" and ">". >> (in help files) >> I am working with 4 alternative language (including english and >> german) to compare the source and there are portion of strings (more >> than 100) where all 4 alternatives are translated into native >> languages. However when i submit the translated version to my work, i >> receive an "Critical errors: XML tags ". >> >> How exactly should i proceed? > > Please don't translate the words between "<" and ">" > >> >> Regards, >> Taavi > > Kind regards > > -- > Mechtilde Stehmann > ## Apache OpenOffice > ## Freie Office Suite für Linux, MacOSX, Windows > ## Debian Developer > ## PGP encryption welcome > ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F > > - To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org For additional commands, e-mail: l10n-h...@openoffice.apache.org
Re: XML tags
Hello, Am 23.01.20 um 11:17 schrieb Taavi Kaevats: > Hi, > > I am experiencing difficulties to decide whether to translate > translatable attributes (descriptions, titles etc) within "<" and ">". > (in help files) > I am working with 4 alternative language (including english and > german) to compare the source and there are portion of strings (more > than 100) where all 4 alternatives are translated into native > languages. However when i submit the translated version to my work, i > receive an "Critical errors: XML tags ". > > How exactly should i proceed? Please don't translate the words between "<" and ">" > > Regards, > Taavi Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: XML tags
Taavi, These "Critical errors : XML tags" are thrown by Pootle. From my experience it seems that there are a lot of false positives. I check the translated string for errors and if everything is alright I disable the warning. Disabling the warning: First edit the string ( remove random 1 character (I mostly pick the last one)) Save the string Open the string again Click the icon next to the warning XML tags ( it will turn grey) Add the character back that you first removed. Save the string again. The critical error should now no longer appear -- 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
Re: XML tags
Hi, unfortunately I do not understand your answer at all. I use Google Translate. Try to use it too. In essence, I have only one question as to whether a cheaper alternative to transport would be possible. Best regards wenna59 - - Původní e-mail -- Od: Taavi Kaevats Komu: l10n@openoffice.apache.org Datum: 23. 1. 2020 11:17:40 Předmět: XML tags "Hi, I am experiencing difficulties to decide whether to translate translatable attributes (descriptions, titles etc) within "<" and ">". (in help files) I am working with 4 alternative language (including english and german) to compare the source and there are portion of strings (more than 100) where all 4 alternatives are translated into native languages. However when i submit the translated version to my work, i receive an "Critical errors: XML tags ". How exactly should i proceed? Regards, Taavi - To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org For additional commands, e-mail: l10n-h...@openoffice.apache.org "
