[libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 rc2), bugs to fix
Hi, On Sunday I exported updated po files from Pootle and I pushed them to git to the translations module. LibreOffice 3.4 rc2 will contain these translation updates. According to the plan rc2 will be 3.4.0 final, if all go well. So the next translation update will be for 3.4.1. I'll do the push next time when a release (3.4.1 rc) is coming. Please note, however, that there are still bugs in your translations that need to be fixed ASAP. Locales with fatal errors: cs, is, tr, zh-TW I fixed fatal (build breaker) errors before commit, but you need to fixe them in Pootle, too. Locales with bugs: as, bg, bn, bo, brx, bs, ca, cs, de, dgo, el, eo, fa, gu, he, hi, hr, id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl, nn, nr, nso, oc, om, or, pl, ro, rw, sa-IN, sat, sd, sk, sq, st, sv, ta, tg, tn, tr, ts, ug, uk, uz, zh-TW Log files (from all tools) and error files (from gsicheck tool): http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/ 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 rc2), bugs to fix
Andras, Locales with bugs: id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl, I have fixed kn issues Cheers Shankar -- 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 rc2), bugs to fix
Þann þri 24.maí 2011 10:47, skrifaði Andras Timar: Please note, however, that there are still bugs in your translations that need to be fixed ASAP. Locales with fatal errors: cs, is, tr, zh-TW I fixed fatal (build breaker) errors before commit, but you need to fixe them in Pootle, too. Locales with bugs: as, bg, bn, bo, brx, bs, ca, cs, de, dgo, el, eo, fa, gu, he, hi, hr, id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl, nn, nr, nso, oc, om, or, pl, ro, rw, sa-IN, sat, sd, sk, sq, st, sv, ta, tg, tn, tr, ts, ug, uk, uz, zh-TW Log files (from all tools) and error files (from gsicheck tool): http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/ Best regards, Andras Hi Andras, Fixed (hopefully all) Icelandic (is) errors, those were missing XML characters ( and /) in helpcontent2. But, I can see that now there's a bunch of new inconsistencies between msgid and msgstr strings. Mostly XML markup like (in /swriter/guide.po); #: borders.xhp#par_id6129947.help.text #, fuzzy msgid Choose item type=\menuitem\Table - Table properties/item. msgstr Veldu emphSkrá - Flytja út/emph. Or; #: mailmerge03.xhp#par_idN10543.help.text link href=text/swriter/01/mailmerge03.xhpMail Merge Wizard - Addresses/link link href=text/swriter/01/mailmerge00.xhpLeiðarvísir fyrir póstsameiningu - Heimilisföng/link The texts are OK, but the markup is wrong. The former could possibly be a suggestion automatically added by Lokalize (I use that sparingly and never sitewide), but the latter smells of an (incomplete/nonfunctional) merging. Also, the sheer number of locales all of a sudden full of bugs is quite suspicious. What do you think ? Best regards, Sveinn í Felli -- 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 rc2), bugs to fix
zh-TW should be fixed. Andras, would you please check it again for me? -- Sincerely, by Cheng-Chia Tseng -- 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 rc2), bugs to fix
On 24.05.11 13:47, Andras Timar wrote: Hi, Hi! On Sunday I exported updated po files from Pootle and I pushed them to git to the translations module. LibreOffice 3.4 rc2 will contain these translation updates. According to the plan rc2 will be 3.4.0 final, if all go well. So the next translation update will be for 3.4.1. I'll do the push next time when a release (3.4.1 rc) is coming. Please note, however, that there are still bugs in your translations that need to be fixed ASAP. Locales with fatal errors: cs, is, tr, zh-TW I fixed fatal (build breaker) errors before commit, but you need to fixe them in Pootle, too. Locales with bugs: as, bg, bn, bo, brx, bs, ca, cs, de, dgo, el, eo, fa, gu, he, hi, hr, id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl, nn, nr, nso, oc, om, or, pl, ro, rw, sa-IN, sat, sd, sk, sq, st, sv, ta, tg, tn, tr, ts, ug, uk, uz, zh-TW Log files (from all tools) and error files (from gsicheck tool): http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/ In Pootle seems everything is ok for my locale. Maybe I didn't get the point for the bug. May You explain please? http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/uk.log -- 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 rc2), bugs to fix
Hi *, 2011/5/24 Коростіль Данило ted.korosti...@gmail.com: [...] In Pootle seems everything is ok for my locale. Maybe I didn't get the point for the bug. May You explain please? http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/uk.log The problem that you have the exact same string in the location for two items that can then be easily confused in the UI and might even break functionality (when you for example assign the same name to two different functions in Calc). Заголовок is used for both heading and title If you cannot find a different word for title, use something that then corresponds to main heading or something like that. 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 rc2), bugs to fix
Hi Andras, Thanks to Ayhan he fixed the fatal errors and other errors. On Sunday I exported updated po files from Pootle and I pushed them to git to the translations module. LibreOffice 3.4 rc2 will contain these translation updates. According to the plan rc2 will be 3.4.0 final, if all go well. So the next translation update will be for 3.4.1. I'll do the push next time when a release (3.4.1 rc) is coming. I understand that the this was the last push befor 3.4 stable relase, so rc2 translations will be in 3.4? However, we just managed to achieve %100 percent on 3.4 UI translations today :( . Is it possible to update Turkish UI files. It is very important for our campaign to present LibreOffice as it has a %100 Turkish User Interface. We gathered a good localization team and thing are getting quite well. Turkish translations in Help files are not very good and we have lots of work to do. We hope to achieve this ratios in Help files as soon as possible. Best regards, Zeki -- 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
