[libreoffice-l10n] The Document Foundation is open for members
Dear contributors, within the last months the community around LibreOffice and The Document Foundation worked hard to establish policies, processes, infrastructure and all the things you need to deliver a high quality software. One of our basic principles is that we will acknowledge this merit and allow all the contributors to become official members of our community [2]. All members will have the right to run for a seat in the Foundation's board of directors, elect the board and drive the future of our projects. From now on all of you can apply for membership via our webform [1] . The membership committee [3] is eager to receive your applications. Please help us to process your request quickly. Read and follow the form's introduction carefully, provide a good description of your contributions and list at least two contacts who can confirm your contributions. The TDF Membership Committee, Sophie Gautier, Fridrich Strba, André Schnabel, Cor Nouws Links: [1] application form: http://www.documentfoundation.org/application-for-tdf-community-membership/ [2] community bylaws: http://wiki.documentfoundation.org/CommunityBylaws [3] more about the Membership Committee: http://wiki.documentfoundation.org/TDF/Membership_Committee -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi, Sunday night I exported updated po files from Pootle and pushed them to git to the translations module. LibreOffice 3.4 beta 2 will contain these translation updates. Please note, however, that there are still bugs in your translations that need to be fixed ASAP. Our friends at OOo project developed a new script that checks for duplicated translations. There are parts of the code where translations should be unique. For example in Calc function names, SEARCH and FIND must not be translated into the same term. These translation errors lead to mysterious bugs. For more explanation see http://openoffice.org/bugzilla/show_bug.cgi?id=112478 So now there are 3 checks in place for translations: gsicheck - standard check for tags etc. readmecheck - same as gsicheck but for the readme doublecheck - check if different English strings were translated into the same at critical parts of the code Locales with bugs: as, ast, be, bg, bn, bo, br, brx, bs, ca-XV, ca, cy, dgo, el, en-ZA, eo, et, fa, fr, gl, gu, he, hi, hr, id, it, ja, ka, kk, kn, kok, ks, ku, lt, lv, mai, mk, ml, mn, mni, mr, my, nb, ne, nn, nr, nso, oc, om, or, pl, pt-BR, pt, ro, ru, rw, sa-IN, sat, sd, sh, sk, sl, sq, sr, st, sv, ta, te, tg, tn, tr, ts, ug, uk, uz, vi Log files (from all tools) and error files (from gsicheck tool): http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/ Pootle also contains checks for many potential translation bugs. There are many false positives but it finds many real bugs. Please go through them, especially 'variables' and 'escapes', because these can be fatal (Review tab). Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Removing older versions of strings from pootle
2011.04.18. 11:54 keltezéssel, Dwayne Bailey írta: > > On 2011-04-17 23:33, André Schnabel wrote: >> Hi, >> >> Am 17.04.2011 20:59, schrieb Andras Timar: >>> >>> I also suggest removing version number from the name of the projects, because it has several benefits. One of them is preserving contribution statistics of the project. >>> That's a good point. Statistics are important. I wonder what others >>> think. >> >> I wonder why it should be important for the statistics if we have >> Version numbers in the project or not. If someone is actually doing a >> translation this is counted - and that is what matters (regardless of >> the version she contributed to). > By using project names such as "libo-current-ui" and "libo-next-ui" you > could achieve this statistics stability, if required. The descriptive > name of the project could then communicate that this is 3.3.x vs 3.4.x > But at some point I need to move libo-next-ui to libo-current-ui and create a new libo-next-ui. IMHO it's not a rename operation. Or is it? Anyway, André is right, statistics per language should be enough. It would be the best, if I didn't have to change anything in our current setup. :) Thanks, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
On 2011-04-19 09:13, Andras Timar wrote: So now there are 3 checks in place for translations: gsicheck - standard check for tags etc. readmecheck - same as gsicheck but for the readme doublecheck - check if different English strings were translated into the same at critical parts of the code In an ideal world I'd love those tools to inject the found errors back into Pootle so that you have one place to find and fix errors and no cryptic strings we need to search for. If anyone would want to try code that please give me a shout and we can work out what needs to be done. Pootle also contains checks for many potential translation bugs. There are many false positives but it finds many real bugs. Please go through them, especially 'variables' and 'escapes', because these can be fatal (Review tab). We need your help with these false positives: 1) If a test makes no sense in your language, e.g. startcaps in languages with no capitals, then please report that to the Pootle developers as we can switch these off for your language. 2) Please report false positives that affect your language and that you think could/should be fixed in the code. Please also try to mark your false positives. This allows you to reduce your error count to zero and will then show real errors clearly. You can do that by clicking on the cross next to the check when you are in review mode. We haven't had much testing of what happens to false positives when the files are upgraded, you would help us test and find bugs here. -- regards Dwayne -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hello Andras I finished pt-BR yesterday, so one last piece of my 3.4 help files will miss 3.4 sigh will get it on RC's... :-) About the check indicated, and looking into other translations, pt-BR has just one (ONE !!!) little false positive. So either I am a genius and extremely carefull guy at my work, or the script failed to pick other errors, as it did for other languages... :-) Can you double check? http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt-BR.log Thank you Olivier Em 19-04-2011 04:13, Andras Timar escreveu: Hi, Sunday night I exported updated po files from Pootle and pushed them to git to the translations module. LibreOffice 3.4 beta 2 will contain these translation updates. Please note, however, that there are still bugs in your translations that need to be fixed ASAP. Our friends at OOo project developed a new script that checks for duplicated translations. There are parts of the code where translations should be unique. For example in Calc function names, SEARCH and FIND must not be translated into the same term. These translation errors lead to mysterious bugs. For more explanation see http://openoffice.org/bugzilla/show_bug.cgi?id=112478 So now there are 3 checks in place for translations: gsicheck - standard check for tags etc. readmecheck - same as gsicheck but for the readme doublecheck - check if different English strings were translated into the same at critical parts of the code Locales with bugs: as, ast, be, bg, bn, bo, br, brx, bs, ca-XV, ca, cy, dgo, el, en-ZA, eo, et, fa, fr, gl, gu, he, hi, hr, id, it, ja, ka, kk, kn, kok, ks, ku, lt, lv, mai, mk, ml, mn, mni, mr, my, nb, ne, nn, nr, nso, oc, om, or, pl, pt-BR, pt, ro, ru, rw, sa-IN, sat, sd, sh, sk, sl, sq, sr, st, sv, ta, te, tg, tn, tr, ts, ug, uk, uz, vi Log files (from all tools) and error files (from gsicheck tool): http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/ Pootle also contains checks for many potential translation bugs. There are many false positives but it finds many real bugs. Please go through them, especially 'variables' and 'escapes', because these can be fatal (Review tab). Best regards, Andras -- Olivier Hallot Founder, Steering Commitee Member - The Document Foundation Voicing the enterprise needs LibreOffice translation leader for Brazilian Portuguese -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hello Olivier, 2011/4/19 Olivier Hallot : > About the check indicated, and looking into other translations, pt-BR has > just one (ONE !!!) little false positive. So either I am a genius and > extremely carefull guy at my work, or the script failed to pick other > errors, as it did for other languages... :-) > > Can you double check? > > http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt-BR.log > This is not a false positive. You need to translate Heading and Title to different words, otherwise you'll have troubles with default styles in the localized product. See for example http://openoffice.org/bugzilla/show_bug.cgi?id=113296 Anyway, congratulations for your almost error-free translation. :) Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hello Dwayne, 2011.04.19. 10:17 keltezéssel, Dwayne Bailey írta: > > We need your help with these false positives: > 1) If a test makes no sense in your language, e.g. startcaps in > languages with no capitals, then please report that to the Pootle > developers as we can switch these off for your language. > 2) Please report false positives that affect your language and that you > think could/should be fixed in the code. > For example: 'XX' cannot be replaced. - „XX” nem cserélhető le. This Hungarian translation is perfectly valid but it fails 'singlequoting', 'doublequoting', and 'startpunc' check. There are hundreds of string like this. There might be real errors among them, but... Anyway, I'll report if a check be dropped for my language. > Please also try to mark your false positives. This allows you to reduce > your error count to zero and will then show real errors clearly. You > can do that by clicking on the cross next to the check when you are in > review mode. Thanks for the hint, I did not know this. :) Unfortunately it will take a while to click through several thousand strings. > > We haven't had much testing of what happens to false positives when the > files are upgraded, you would help us test and find bugs here. > OK, maybe I should test it on a smaller test module... Fixing all failing Pootle checks would definitely increase the quality of translation. However, some teams will not find time to fix them all. The bugs I reported in my previous mail are severe bugs which can cause loss of functionality so I wish that everybody corrects at least those. Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Removing older versions of strings from pootle
Hi, I have to remind that we're in a situation that we only have one legacy branch. Sooner or later, we will have multiple versions of LibO strings available on pootle, that not only make the workspace crowded, but downloading zip folders and operations like this on them, make pootle slow. When pootle can't do things in parallel, we can partition the job logically and put it on multiple servers to gain speed up. So, Why not setup a pootle instance for legacy strings? All the previous versions can go there so everyone that needs them can still use it without switching to a new traslating interface. Migeration would also be easy. MySQL tables and files are copied to the server that holds legacy files. On the other hand, an upgrade on the current version, keeps everything in place. Anyway, someday in near future we'll have to remove older versions, so why not create a guideline for the lifecycle of those old strings and keep them in a good place? Hossein On 4/19/11, Andras Timar wrote: > 2011.04.18. 11:54 keltezéssel, Dwayne Bailey írta: >> >> On 2011-04-17 23:33, André Schnabel wrote: >>> Hi, >>> >>> Am 17.04.2011 20:59, schrieb Andras Timar: > I also suggest removing version number from the name of the projects, > because it has several benefits. One of them is preserving > contribution statistics of the project. That's a good point. Statistics are important. I wonder what others think. >>> >>> I wonder why it should be important for the statistics if we have >>> Version numbers in the project or not. If someone is actually doing a >>> translation this is counted - and that is what matters (regardless of >>> the version she contributed to). >> By using project names such as "libo-current-ui" and "libo-next-ui" you >> could achieve this statistics stability, if required. The descriptive >> name of the project could then communicate that this is 3.3.x vs 3.4.x >> > But at some point I need to move libo-next-ui to libo-current-ui and > create a new libo-next-ui. IMHO it's not a rename operation. Or is it? > > Anyway, André is right, statistics per language should be enough. It > would be the best, if I didn't have to change anything in our current > setup. :) > > Thanks, > Andras > > -- > Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/www/l10n/ > All messages sent to this list will be publicly archived and cannot be > deleted > -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi, Why some languages has a .err and .log files? other as galician not. Is for different checks? I have arrange it at galician. @Olivier, about problem with styles. We also had this problem (in spanish translation, there is too). I send a link, in hope give a hand. http://blog.openoffice.gl/coordinacion/article/un-problema-cos-estilos Otherwise, In galician translation, rest now a lot of job for coherence as the imported trasnlation from OOo.org (from versión 3.2) is deficient and ignores hundreds improvements we was doing. Antón 2011/4/19 Andras Timar : > Hello Olivier, > > 2011/4/19 Olivier Hallot : >> About the check indicated, and looking into other translations, pt-BR has >> just one (ONE !!!) little false positive. So either I am a genius and >> extremely carefull guy at my work, or the script failed to pick other >> errors, as it did for other languages... :-) >> >> Can you double check? >> >> http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt-BR.log >> > > This is not a false positive. You need to translate Heading and Title > to different words, otherwise you'll have troubles with default styles > in the localized product. See for example > http://openoffice.org/bugzilla/show_bug.cgi?id=113296 > > Anyway, congratulations for your almost error-free translation. :) > > Best regards, > Andras > > -- > Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/www/l10n/ > All messages sent to this list will be publicly archived and cannot be deleted > -- Antón Méixome - Blog about Galician Office Suite Galician community OOo.org & LibO http://blog.openoffice.gl // http://blog.libreoffice.gl -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
2011.04.19. 15:09 keltezéssel, Anton Meixome írta: > Hi, > > Why some languages has a .err and .log files? other as galician not. > Is for different checks? > .err files come from gsicheck. The other two checks (readmecheck and doublecheck) do not produce .err files. Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Andras, On 19/04/2011 10:13, Andras Timar wrote: Hi, Sunday night I exported updated po files from Pootle and pushed them to git to the translations module. LibreOffice 3.4 beta 2 will contain these translation updates. Please note, however, that there are still bugs in your translations that need to be fixed ASAP. I didn't finished the translation yet, I still need to proof read some files, so I didn't make any check for the moment, as I will still upload files on Pootle. When do you want us to have the files corrected? Kind regards Sophie Our friends at OOo project developed a new script that checks for duplicated translations. There are parts of the code where translations should be unique. For example in Calc function names, SEARCH and FIND must not be translated into the same term. These translation errors lead to mysterious bugs. For more explanation see http://openoffice.org/bugzilla/show_bug.cgi?id=112478 So now there are 3 checks in place for translations: gsicheck - standard check for tags etc. readmecheck - same as gsicheck but for the readme doublecheck - check if different English strings were translated into the same at critical parts of the code Locales with bugs: as, ast, be, bg, bn, bo, br, brx, bs, ca-XV, ca, cy, dgo, el, en-ZA, eo, et, fa, fr, gl, gu, he, hi, hr, id, it, ja, ka, kk, kn, kok, ks, ku, lt, lv, mai, mk, ml, mn, mni, mr, my, nb, ne, nn, nr, nso, oc, om, or, pl, pt-BR, pt, ro, ru, rw, sa-IN, sat, sd, sh, sk, sl, sq, sr, st, sv, ta, te, tg, tn, tr, ts, ug, uk, uz, vi Log files (from all tools) and error files (from gsicheck tool): http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/ Pootle also contains checks for many potential translation bugs. There are many false positives but it finds many real bugs. Please go through them, especially 'variables' and 'escapes', because these can be fatal (Review tab). Best regards, Andras -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
On 2011-04-19 15:06, Andras Timar wrote: Hello Dwayne, 2011.04.19. 10:17 keltezéssel, Dwayne Bailey írta: We need your help with these false positives: 1) If a test makes no sense in your language, e.g. startcaps in languages with no capitals, then please report that to the Pootle developers as we can switch these off for your language. 2) Please report false positives that affect your language and that you think could/should be fixed in the code. For example: 'XX' cannot be replaced. - „XX” nem cserélhető le. This Hungarian translation is perfectly valid but it fails 'singlequoting', 'doublequoting', and 'startpunc' check. There are hundreds of string like this. There might be real errors among them, but... We already do this kind of adaptation for French guillemets so we could probably easily adapt it for Hungarian. So yes that is the type of false positive I'm interested in hearing about and fixing. If you can give more examples of those strings so that I can build tests that would be helpful, Anyway, I'll report if a check be dropped for my language. Please also try to mark your false positives. This allows you to reduce your error count to zero and will then show real errors clearly. You can do that by clicking on the cross next to the check when you are in review mode. Thanks for the hint, I did not know this. :) Unfortunately it will take a while to click through several thousand strings. Yes, maybe focus on ones that are less error prone then the quotes. We haven't had much testing of what happens to false positives when the files are upgraded, you would help us test and find bugs here. OK, maybe I should test it on a smaller test module... Fixing all failing Pootle checks would definitely increase the quality of translation. However, some teams will not find time to fix them all. The bugs I reported in my previous mail are severe bugs which can cause loss of functionality so I wish that everybody corrects at least those. Yes, those few should be a priority and should be at zero. -- regards Dwayne -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Removing older versions of strings from pootle
Hi Hossein, 2011.04.19 16:08, Hossein Noorikhah rašė: I have to remind that we're in a situation that we only have one legacy branch. Sooner or later, we will have multiple versions of LibO strings available on pootle, that not only make the workspace crowded, but downloading zip folders and operations like this on them, make pootle slow. When pootle can't do things in parallel, we can partition the job logically and put it on multiple servers to gain speed up. So, Why not setup a pootle instance for legacy strings? All the previous versions can go there so everyone that needs them can still use it without switching to a new traslating interface. Disclaimer: the following is my personal impression. I don't (yet) think this makes much sense for one simple reason: as far as I remember from OOo, and looking at what we have now, it simply doesn't seem like LibO would be releasing from two or more branches simultaniously often and for long times. Unlike Mozilla. This makes excessive server load from working on old strings quite unlikely in my eyes. I think such load would be more occasional than usual, so in my opinion, it simply doesn't justify maintaining two totally independent installations of Pootle and keeping them in sync with each other. On the other hand, an upgrade on the current version, keeps everything in place. Anyway, someday in near future we'll have to remove older versions, so why not create a guideline for the lifecycle of those old strings and keep them in a good place? I think the policy here is quite simple: when there is a decision that there will be no more releases from a certain branch, then that branch should be dropped from Pootle. Rimas -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Sophie, 2011/4/19 Sophie Gautier : > I didn't finished the translation yet, I still need to proof read some > files, so I didn't make any check for the moment, as I will still upload > files on Pootle. > When do you want us to have the files corrected? I'll update translations in git every week, just before tagging betas/rc's/etc. There is no final deadline, really. The sooner you fix them, the sooner you'll have an error free localized build. I'll send the updated error list every week to this mailing list. Thanks, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] HSQLDB localization
Hi everyone, a long time ago, I stumbled upon this page: http://wiki.services.openoffice.org/wiki/HSQLDB_Localization . I'm wondering: would anybody want to see a HSQLDB module set up in Pootle? Would this encourage anyone to localize it or would it just be a waste of server's resources? Rimas -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] HSQLDB localization
Hi Rimas, 2011.04.19. 16:19 keltezéssel, Rimas Kudelis írta: > a long time ago, I stumbled upon this page: > http://wiki.services.openoffice.org/wiki/HSQLDB_Localization . > > I'm wondering: would anybody want to see a HSQLDB module set up in > Pootle? Would this encourage anyone to localize it or would it just be a > waste of server's resources? > Well, it's not a resource hog. :) It contains 255 messages only. I forgot that I translated it in 2005. Unfortunately the link to translations does not work on this wiki page. I found my translation on my hard drive. It would be nice, if could find those old translations somewhere... Interestingly, Italian translation is already part of the hsqldb package, others are not. Although the future of hsqldb in LibreOffice is not granted (hsqldb was written in Java), it will be with us for a while. So localizing its error messages in not a waste of time. If anybody else is interested, I can adjust the project files in git just like I did with NLPSolver. Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Andras, On Tue, 19 Apr 2011 09:13:18 +0200, Andras Timar wrote: > Our friends at OOo project developed a new script that checks for > duplicated translations. There are parts of the code where translations > should be unique. For example in Calc function names, SEARCH and FIND > must not be translated into the same term. These translation errors lead > to mysterious bugs. For more explanation see > http://openoffice.org/bugzilla/show_bug.cgi?id=112478 (snip) > Log files (from all tools) and error files (from gsicheck tool): > http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/ Thanks for sharing logs, in which Japanese (ja) locale had only one bug reported. I admit it is *not* false positive and fixed now. Good tools :) Cheers, -- Takeshi Abe > > Pootle also contains checks for many potential translation bugs. There > are many false positives but it finds many real bugs. Please go through > them, especially 'variables' and 'escapes', because these can be fatal > (Review tab). -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Andras, On 19/04/2011 17:09, Andras Timar wrote: Hi Sophie, 2011/4/19 Sophie Gautier: I didn't finished the translation yet, I still need to proof read some files, so I didn't make any check for the moment, as I will still upload files on Pootle. When do you want us to have the files corrected? I'll update translations in git every week, just before tagging betas/rc's/etc. There is no final deadline, really. The sooner you fix them, the sooner you'll have an error free localized build. I'll send the updated error list every week to this mailing list. Ok, thanks a lot Andras. Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Indeed I missed this since the very begining of OpenOffice 1.0, back in 2002 Makes a lot of sense and thanks Anton for the precise analysis of this error. Corrected. Regards Olivier Em 19-04-2011 10:09, Anton Meixome escreveu: Hi, Why some languages has a .err and .log files? other as galician not. Is for different checks? I have arrange it at galician. @Olivier, about problem with styles. We also had this problem (in spanish translation, there is too). I send a link, in hope give a hand. http://blog.openoffice.gl/coordinacion/article/un-problema-cos-estilos Otherwise, In galician translation, rest now a lot of job for coherence as the imported trasnlation from OOo.org (from versión 3.2) is deficient and ignores hundreds improvements we was doing. Antón 2011/4/19 Andras Timar: Hello Olivier, 2011/4/19 Olivier Hallot: About the check indicated, and looking into other translations, pt-BR has just one (ONE !!!) little false positive. So either I am a genius and extremely carefull guy at my work, or the script failed to pick other errors, as it did for other languages... :-) Can you double check? http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt-BR.log This is not a false positive. You need to translate Heading and Title to different words, otherwise you'll have troubles with default styles in the localized product. See for example http://openoffice.org/bugzilla/show_bug.cgi?id=113296 Anyway, congratulations for your almost error-free translation. :) Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted -- Olivier Hallot Founder, Steering Commitee Member - The Document Foundation Voicing the enterprise needs LibreOffice translation leader for Brazilian Portuguese -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
2011/4/19 Andras Timar > > This is not a false positive. You need to translate Heading and Title > to different words, otherwise you'll have troubles with default styles > in the localized product. See for example > http://openoffice.org/bugzilla/show_bug.cgi?id=113296 > > This same string is also a problem for Slovenian, but I cannot make up another word if both English words are localized into the same Slovenian word. I don't care what your script says but for Slovenian this is not an error - it would be an error if those strings had a different translation. Lp, m. -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Martin, On Tue, Apr 19, 2011 at 11:34 PM, Martin Srebotnjak wrote: > 2011/4/19 Andras Timar > >> This is not a false positive. You need to translate Heading and Title >> to different words, [...] >> > This same string is also a problem for Slovenian, but I cannot make up > another word if both English words are localized into the same Slovenian > word. > I don't care what your script says but for Slovenian this is not an error - That's a very strange attitude. So you're telling Slovenian users to screw themselves because the translator cannot come up with a way to use two different strings? > it would be an error if those strings had a different translation. I really doubt the Slovenian language doesn't have something that distinguishes a main title, from a simple heading, but be it. If you lack a word, then just add another. Make Title "Main Heading" or something similar. ciao Christian -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Martin Srebotnjak wrote: > 2011/4/19 Andras Timar > > This is not a false positive. You need to translate Heading and Title > > to different words, otherwise you'll have troubles with default styles > ... I don't care what your script says but for Slovenian this is not an error > - > it would be an error if those strings had a different translation. OK, but using the same word (which, by mistake, we did in Italian too) will break styles, as already explained, and anyway lead to unforeseen behaviour, since the code seems to assume that style names are all distinct. A very similar issue was fixed as a blocker for OpenOffice.org 3.3.0 Italian http://openoffice.org/bugzilla/show_bug.cgi?id=115232 and indeed, as Christian suggests in your case too, we decided to use a periphrasis. Regards, Andrea. -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Sophie, Andras, *, On Tue, Apr 19, 2011 at 4:01 PM, Sophie Gautier wrote: > Hi Andras, > On 19/04/2011 10:13, Andras Timar wrote: > >> Sunday night I exported updated po files from Pootle and pushed them to >> git to the translations module. LibreOffice 3.4 beta 2 will contain >> these translation updates. >> >> Please note, however, that there are still bugs in your translations >> that need to be fixed ASAP. Yes, as some of then even cause the build to break. http://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=libreoffice-3-4&brief-log=1303228818.4722#err44 > I didn't finished the translation yet, I still need to proof read some > files, so I didn't make any check for the moment, as I will still upload > files on Pootle. > When do you want us to have the files corrected? ASAP, so that the build can continue and maybe reveil breakers in other languages French (fr/text/shared/00/0200.xhp) and Welsh/Cymraeg (mediawiki/help/cy/com.sun.wiki-publisher/wiki.xhp) are causing the break, but that might just be because they are first to break and thus others won't even be tried. So please fix those "Expected Symbol: Close tag for " ones as fast as possible, and have Andras upload them, otherwise chances are that your language will just be skipped. (as beta2 is planned for this week-end, you really need to hurry, or either beta2 will not come at all or your language will probably be skipped (or reverted to the old translationi) - I'm speculating on this, as I am not involved in doing the release builds, but those are the only options I could think of, and my guess is that keeping on schedule is more important than to have the current status of all translations) ciao Christian -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi *,
On Wed, Apr 20, 2011 at 2:15 AM, Christian Lohmaier
wrote:
>
> [broken translations that break the build]
> So please fix those "Expected Symbol: Close tag for " ones as
> fast as possible, and have Andras upload them, otherwise chances are
> that your language will just be skipped.
For your convenience, I wrote a awk one-liner to turn the error-log
into clickable URLs that will take you to the translation unit in
question:
all in one single line - example for the fr.err log:
awk -F'\t' '$10!="en-US" { n=split($2, fp, /\\/); up=""; for (i=3;
ihttps://translations.documentfoundation.org/"; $10
"/libo34x_" $4 up ".po/translate/?sfields=locations&search=" $5 su}'
< fr.err
would result in
https://translations.documentfoundation.org/fr/libo34x_help/schart/01.po/translate/?sfields=locations&search=par_id7272255
https://translations.documentfoundation.org/fr/libo34x_help/schart/01.po/translate/?sfields=locations&search=par_id2259225
https://translations.documentfoundation.org/fr/libo34x_help/shared/01.po/translate/?sfields=locations&search=par_id31323250502
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id355152952
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id993155271
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id993159201.14
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id3149902.25
https://translations.documentfoundation.org/fr/libo34x_help/scalc/guide.po/translate/?sfields=locations&search=par_id3148576.19
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id3159084.88
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id3146806.89
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id3146130.90
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id31455974
the one-liner explained:
awk -F'\t'
tab is field seperator (I used awk, but of course you could do the
same with perl, sed,)
'$10!="en-US"
we're not interested in the english original strings when creating the
URL, as the original string is displayed in pootle anyway (and the
10th field in the error-log is the language tag)
{ n=split($2, fp, /\\/); up=""; for (i=3; i., also use it.
print "https://translations.documentfoundation.org/"; $10 "/libo34x_"
$4 up ".po/translate/?sfields=locations&search=" $5 su}'
assemble & print the URL
https://translations.documentfoundation.orgtranslate/?sfields=location&search=[]
< fr.err
read the file "fr.err" as input
ciao
Christian
--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Dwayne, *, 2011/4/19 Dwayne Bailey : > On 2011-04-19 09:13, Andras Timar wrote: >> >> So now there are 3 checks in place for translations: >> gsicheck - standard check for tags etc. This should be integrated into pootle somehow - and errors in there should "block" the exporting (syncing to on-disk-files) to avoid checking in invalid files (that then break the build) >> readmecheck - same as gsicheck but for the readme >> doublecheck - check if different English strings were translated into >> the same at critical parts of the code > > In an ideal world I'd love those tools to inject the found errors back into > Pootle so that you have one place to find and fix errors and no cryptic > strings we need to search for. Yes, indeed. But pootle should be more strict than gsicheck (but of course it should cover everything that gsicheck finds) While pootle already catches some of the errors, it doesn't flag this one for example: https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id3149902.25 (in case sophie is too fast and fixes it in the meantime: Dans une fenêtre de fichier de base de données, cliquez sur l'icône Requêtes, puis choisissez Éditer - Éditer. Lorsque les champs de référence n'existent plus, vous voyez cette boîte de dialogue i.e. non-matching - missing "h" - pootle doesn't flag it It's always better to have some false positives than to miss stuff. And may I suggest to change the theme to give a bigger font for the translation-box? I guess that's one of the reasons of missing quotes or writing an *opening* tag as and not noticing it. But even better would be a "commit-hook" that instead of letting you advance to the next translation unit points you back at the just-changed string with a message "You very likely introduce an error here - you mistyped the tag's name or something" :-) ciao Christian -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Christian, On 20/04/2011 04:20, Christian Lohmaier wrote: Hi *, On Wed, Apr 20, 2011 at 2:15 AM, Christian Lohmaier wrote: [broken translations that break the build] So please fix those "Expected Symbol: Close tag for" ones as fast as possible, and have Andras upload them, otherwise chances are that your language will just be skipped. For your convenience, I wrote a awk one-liner to turn the error-log into clickable URLs that will take you to the translation unit in question: thanks a lot, it's very kind :) but my issue here is more about my own organization than fixing the errors. I'm translating off line using wordorge of gedit, so I need to get my local files and Pootle files in sync. The process po2sdf -> gsicheck -> correcting po then upload on pootle is quite long and I tend to make it only when I'm over with the most important part of localization. It seems I don't have no more the time to wait for the end of my translation to gischeck the files, so I need to organize myself differently. But thanks a lot again really, that will help me to correct the files quickly later today. Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
2011.04.20. 5:34 keltezéssel, Sophie Gautier írta: > > But thanks a lot again really, that will help me to correct the files > quickly later today. > I fixed all build build breakers in cy, fr, ja and pt in git. Next time I'll check them before I commit. Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
