Re: Automated translation into en_GB
Hello everybody, I think an automated translation as an additional help for translators would definitely be useful. I'm not a big fan of automated translations in general, because the quality is usually really bad, but in the case of en_US to en_GB, it is mostly spelling. I can't think of any phrasal verbs that you would come across in software (which would pose a problem, because the differences are bigger), since they are usually lower register and thus not very appropriate for software. I talked to several native speakers here and they also agree that the automated translation should not be a problem as long as it's limited to software (documentation might be more difficult, but does not seem impossible either). This also does not mean the en_GB team would be replaced by a script, but that automatic translations are available if they are needed. I like the idea of marking them as automatic translations so that, if there is time, a translator can look through them and mark them as checked. Sincerely, Florian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Leonardo F. Fontenelle wrote: Em Ter, 2009-01-27 às 14:09 -0500, Willie Walker escreveu: In the past, I was slapped seriously by the l10n team for touching *.po files. So, I'm requesting permission here before I check in the *.po changes. Is this OK with you all? This might be more to the point: for file in po/*.po; do sed -i "s+msgid \"\([^|]*\)|+msgctxt \"\1\"\nmsgid \"+" $file done BTW, just a quick comment that this doesn't catch mistakes where the translator translated the entire Q_ string rather than translating just the stuff after the "|". Orca's ar.po file, for example, appears to have several cases of this. The second "sed" at http://bugzilla.gnome.org/show_bug.cgi?id=569118#c17 fixes those. Note that the scripts are also making an assumption that the "|" character only shows up in strings for the purposes of the Q_ form. So, if someone has put the "|" character in something other than the Q_ form, the scripts will catch those and split them. As a result, one should carefully examine the files to make sure the expected changes have been made. Will ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Evolution-MAPI - new strings added
Hi, I just added new strings to evolution-mapi trunk, within bug http://bugzilla.gnome.org/show_bug.cgi?id=564897 It shows also new dialogs after authentication process, thus I guess a new UI introduced as well. Though depends on your point of view on a UI. Bye, Milan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
wrong translations of gconf key values
Dear translators, Gconf key values should not be translated to your language only (by dropping the original english string) because it makes it impossible for users to set them manually, e.g. by using gconf-editor. That is what the literal quotes should imply, see http://live.gnome.org/TranslationProject/DevGuidelines/Enclose%20literal%20values%20in%20double%20quotes . Example: msgid "Possible values are \"always\", "\"bonded\"." bad msgstr "Los valores posibles son: «siempre», «vinculados». good msgstr "Los valores posibles son: «always» (siempre), «bonded» (vinculados)." I've grep'ed the evolution po files and found 37 wrong po files. Nautilus: 21 po files. Epiphany: 20 po files. While I'm going to file bug reports for the rest of the evening I ask you how to avoid this. :-) To me it's obvious by looking at the filename of the string (ending with ".schemas.in") that these values should not be translated, but to lots of other translators it's not. In http://bugzilla.gnome.org/show_bug.cgi?id=569457 aloriel proposes to add a comment to each of these strings. Other opinions/comments? andre -- mailto:ak...@gmx.net | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Hey Everyone: Thanks much for the conversation around this. Just to follow up, we accomplished this: 1) Came up with a good plan for Python and applied it to accerciser and orca: http://bugzilla.gnome.org/show_bug.cgi?id=569118 http://bugzilla.gnome.org/show_bug.cgi?id=569341 2) Added comments to http://live.gnome.org/GnomeGoals/MsgctxtMigration to help others in the same boat. Will ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Ανοιχτή συζήτηση περί των έρ γων μετάφρασης από την εταιρία Ε ΕΛΛΑΚ
Να υπενθυμίσω ότι αν θέλετε να ρωτήσετε κάτι σχετικά με το διαγωνισμό «Πρόσκληση εκδήλωσης ενδιαφέροντος για την Ελληνοποίηση ΕΛΛΑΚ Λογισμικών που είναι χρήσιμα για επιχειρήσεις και την εκπαιδευτική κοινότητα» http://www.ellak.gr/index.php?option=com_openwiki&Itemid=103&id=eellak:metafraseis θα είμαι διαθέσιμος σήμερα το βράδυ (10μμ) στο IRC, Δίκτυο Freenode, κανάλι #gnome-el. http://wiki.ubuntu-gr.org/Wiki/Community/IRC Σίμος ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of gconf key values
+1 for adding comments to the strings. Some translators may use poedit while doing their work and won't see the source code file name associated with the string. -- Og B. Maciel omac...@foresightlinux.org ogmac...@gnome.org ogmac...@ubuntu.com GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Ανοιχτή συζήτηση περί των έργων μετάφρασης από την εταιρία ΕΕΛΛΑΚ
Ἕλλωυ, > Να υπενθυμίσω ότι αν θέλετε να ρωτήσετε κάτι σχετικά με το διαγωνισμό > «Πρόσκληση εκδήλωσης ενδιαφέροντος για την Ελληνοποίηση ΕΛΛΑΚ Λογισμικών > που είναι χρήσιμα για επιχειρήσεις και την εκπαιδευτική κοινότητα» > http://www.ellak.gr/index.php?option=com_openwiki&Itemid=103&id=eellak:metafraseis > > θα είμαι διαθέσιμος σήμερα το βράδυ (10μμ) στο IRC, Δίκτυο Freenode, > κανάλι #gnome-el. > http://wiki.ubuntu-gr.org/Wiki/Community/IRC > > Σίμος Ἆι έμ σόρι βάτ ἀί δοῦ νότ ἀνδερστάνδ θίσ; -- Γίνταυτασ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of gconf key values
On Wed, Jan 28, 2009 at 9:31 PM, Og Maciel wrote: > +1 for adding comments to the strings. +1 for comments, but what is the idea of developers about always warning translators? Some translators may use poedit > while doing their work and won't see the source code file name > associated with the string. > -- You can do that by right clicking on the string? But who wants to do that for more than 1000 strings. People should be warned about the situations like that. This kind of rules are always problems for new translators (at least at the beginning for me). We have good documentation about this kind of stuff which we can promote more. Comments are wellcome and I think a review and control mechanism is necassary and also good. Because even experienced translators can do such mistakes. However we (translation teams, coordinators...) should direct people to these resources. Updated and centralized documentation (tips, warnings and etc.) is a solution when it is used efficiently. > Og B. Maciel > > omac...@foresightlinux.org > ogmac...@gnome.org > ogmac...@ubuntu.com > > GPG Keys: D5CFC202 > > http://www.ogmaciel.com (en_US) > http://blog.ogmaciel.com (pt_BR) > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
GParted 0.4.2 to be Released Feb. 5, 2009
Hello Translation Teams, GParted version 0.4.2 is planned for release on Thursday, February 5th, 2009. All language translations completed before midnight, Wednesday, February 4th, 2009 will be included in this release. Thank you for your language translation efforts. Sincerely, Curtis Gedak (Maintainer of GParted) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Ανοιχτή συζήτηση περί των έργων μετάφρασης από την εταιρία ΕΕΛΛΑΚ
2009/1/28 Gintautas Miliauskas : > Ἕλλωυ, > >> Να υπενθυμίσω ότι αν θέλετε να ρωτήσετε κάτι σχετικά με το διαγωνισμό >> «Πρόσκληση εκδήλωσης ενδιαφέροντος για την Ελληνοποίηση ΕΛΛΑΚ Λογισμικών >> που είναι χρήσιμα για επιχειρήσεις και την εκπαιδευτική κοινότητα» >> http://www.ellak.gr/index.php?option=com_openwiki&Itemid=103&id=eellak:metafraseis >> >> θα είμαι διαθέσιμος σήμερα το βράδυ (10μμ) στο IRC, Δίκτυο Freenode, >> κανάλι #gnome-el. >> http://wiki.ubuntu-gr.org/Wiki/Community/IRC >> >> Σίμος > > Ἆι έμ σόρι βάτ ἀί δοῦ νότ ἀνδερστάνδ θίσ; That's amazing! Phonetic Greek Polytonic that corresponds to «I am sorry but I do not understand this». I am stupid, instead of announcing at i18...@hellug.gr, GMail put the address for this gnome-i18n mailing list. Sorry for the mix-up, Simos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String change in Appearance capplet (gnome-control-center)
The "wallpaper" term is replaced by "desktop background" as per GDP glossary Details here: http://bugzilla.gnome.org/show_bug.cgi?id=569382 Cheers; Luca ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of gconf key values
El mié, 28-01-2009 a las 18:55 +0100, Andre Klapper escribió: > Dear translators, > > Gconf key values should not be translated to your language only (by > dropping the original english string) because it makes it impossible for > users to set them manually, e.g. by using gconf-editor. > That is what the literal quotes should imply, see > http://live.gnome.org/TranslationProject/DevGuidelines/Enclose%20literal%20values%20in%20double%20quotes > . > > Example: > msgid "Possible values are \"always\", "\"bonded\"." > bad msgstr "Los valores posibles son: «siempre», «vinculados». > good msgstr "Los valores posibles son: «always» (siempre), «bonded» > (vinculados)." > > > I've grep'ed the evolution po files and found 37 wrong po files. > Nautilus: 21 po files. Epiphany: 20 po files. > > While I'm going to file bug reports for the rest of the evening I ask > you how to avoid this. :-) > > To me it's obvious by looking at the filename of the string (ending with > ".schemas.in") that these values should not be translated, but to lots > of other translators it's not. > In http://bugzilla.gnome.org/show_bug.cgi?id=569457 aloriel proposes to > add a comment to each of these strings. It would be even nicer if the translation software gives you a hint about this, I know it makes this kind of software very dependant on GNOME, but we could have a plugin for it. I'm CCing Pablo and Nacho for this issue. > > Other opinions/comments? > > andre -- Jorge González González Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of gconf key values
On Wed, Jan 28, 2009 at 10:07 PM, Jorge González González wrote: > El mié, 28-01-2009 a las 18:55 +0100, Andre Klapper escribió: > > Dear translators, > > > > Gconf key values should not be translated to your language only (by > > dropping the original english string) because it makes it impossible for > > users to set them manually, e.g. by using gconf-editor. > > That is what the literal quotes should imply, see > > > http://live.gnome.org/TranslationProject/DevGuidelines/Enclose%20literal%20values%20in%20double%20quotes. > > > > Example: > > msgid "Possible values are \"always\", "\"bonded\"." > > bad msgstr "Los valores posibles son: «siempre», «vinculados». > > good msgstr "Los valores posibles son: «always» (siempre), «bonded» > (vinculados)." > > > > > > I've grep'ed the evolution po files and found 37 wrong po files. > > Nautilus: 21 po files. Epiphany: 20 po files. > > > > While I'm going to file bug reports for the rest of the evening I ask > > you how to avoid this. :-) > > > > To me it's obvious by looking at the filename of the string (ending with > > ".schemas.in") that these values should not be translated, but to lots > > of other translators it's not. > > In http://bugzilla.gnome.org/show_bug.cgi?id=569457 aloriel proposes to > > add a comment to each of these strings. > It would be even nicer if the translation software gives you a hint > about this, I know it makes this kind of software very dependant on > GNOME, but we could have a plugin for it. > > I'm CCing Pablo and Nacho for this issue. A plugin doing that in gtranslator would be really easy to do, > > > > > > Other opinions/comments? > > > > andre > -- > Jorge González González > Weblog: http://aloriel.no-ip.org > Fotolog: http://www.flickr.com/photos/aloriel > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of gconf key values
Em Qua, 2009-01-28 às 21:56 +0200, Deniz Koçak escreveu: > On Wed, Jan 28, 2009 at 9:31 PM, Og Maciel wrote: > > +1 for adding comments to the strings. > > +1 for comments, but what is the idea of developers about always > warning translators? > It would be great if somehow the comments were added automatically, but I don't know how to do it, and with which tool. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Ανοιχτή συζ ήτηση περί των έργων μετ άφρασης από την εταιρία ΕΕΛΛΑΚ
2009-01-28 klockan 20:54 skrev Gintautas Miliauskas: > Ἕλλωυ, > Ἆι έμ σόρι βάτ ἀί δοῦ νότ ἀνδερστάνδ θίσ; > Γίνταυτασ ίληρίους! — Ϝαυτηρ (yay, digamma put back to use!) signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of gconf key values
On Wed, 2009-01-28 at 18:55 +0100, Andre Klapper wrote: > Example: > msgid "Possible values are \"always\", "\"bonded\"." > bad msgstr "Los valores posibles son: «siempre», «vinculados». > good msgstr "Los valores posibles son: «always» (siempre), «bonded» > (vinculados)." > While I'm going to file bug reports for the rest of the evening I ask > you how to avoid this. :-) > > To me it's obvious by looking at the filename of the string (ending with > ".schemas.in") that these values should not be translated, but to lots > of other translators it's not. > In http://bugzilla.gnome.org/show_bug.cgi?id=569457 aloriel proposes to > add a comment to each of these strings. > > Other opinions/comments? Nothing is ever obvious, especially to a new translator. There are similar problems and some solutions that we found in the Mozilla localisation files. These allowed us to automate parts of the Translate Toolkit. I'd like to propose that we adopt the Mozilla idea and extend it. The idea is built around comments, but comments that are both human and machine readable. Just dealing with the issue you discovered: #. LOCALIZATION_NOTE: DONT_TRANSLATE_WORDS (always,bonded) msgid "Possible values are \"always\", "\"bonded\"." The notes all start with 'LOCALIZATION_NOTE' and the type of note is denoted next, 'DONT_TRANSLATE_WORDS'. Its verbose but it means that a person can read it but also a tool can be instructed to read it. Thus a tool would simply need to detect the presence of 'always' and 'bonded' in the translation and fail if they are missing. Adopting such a system required work by coders or maybe it should be localisers since we feel the pain. It could be easily expanded to include things that capture setting e.g. OPTION (list,of,values), etc. It would be easy to extend the Translate Toolkit to detect these and flag appropriate errors. And also relatively easy to extend Virtaal (the translation editor we've developed) to catch those while editing. But any automated tool requires some structured information to back it up. So we need to get some consensus on that first. -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * xclip - where have you been all of my life! http://www.translate.org.za/blogs/dwayne/en/content/xclip-where-have-you-been-all-my-life * Virtaal on Fedora * Translate Toolkit on Fedora. Status of Virtaal and Pootle Stop Digital Apartheid! - http://www.digitalapartheid.com Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
