charset=ISO-8859-15
Hi All, We've got a Spanish translation of the Planner user guide, and it seems to use ISO-8859-15 as its character set rather then UTF-8 (i.e. it needs charset=ISO-8859-15 in its header in order to transform correctly. Is there any rule or guideline against this? ...or maybe more importantly, any rule that we must use UTF-8? Yelp at least doesn't choke on ISO-8859-15. tnx! -- Kurt Maute [EMAIL PROTECTED] ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gnome glossary
On 6/27/06, TG [EMAIL PROTECTED] wrote: Can any one answer this question. Does the claime at http://developer.gnome.org/projects/gtp/glossary/ still hols true?? It has not been actively maintained for several years, in the sense that no new terms have been added. Still, the glossary is probably useful for many translation teams as a starting point for GNOME translation to some extent, and many teams do use it for that purpose. That's why we still keep it around in the GNOME Translation Project translation status pages. Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME Marathi L01n team details
On 6/23/06, Christian Rose [EMAIL PROTECTED] wrote: Fortunately, Jitendra has now clarified the situation publically onthe list, and has also given his opinion on the candidates. If there'sanything you would like to add to that, please do it now. As mentioned in following mail,http://mail.gnome.org/archives/gnome-i18n/2006-May/msg00128.htmlthe prospective coordinator Swapnil has lost his CVS account and I don't have an account for myself. In such a situation, as suggested in fewof the mails earlier, is it a valid option to submit through someone else like Karunakar who is coordinator for Hindi? Or should I apply for a cvs account? Rahul. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[Fwd: Re: Malayalam GNOME Translation]
Hi, I have not yet received any response from the current Malayalam co-ordinator. Had already informed that the mail sent to his email id ([EMAIL PROTECTED]) had bounced. I am awaiting for a reply. Please advise what is to done. Thanking you Best regards Ani Original Message Subject:Re: Malayalam GNOME Translation Date: Wed, 21 Jun 2006 09:09:12 +0530 From: Ani Peter [EMAIL PROTECTED] To: Christian Rose [EMAIL PROTECTED], gnome-i18n@gnome.org References: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi, The mail sent to Mr.Sajith V K([EMAIL PROTECTED]) has bounced back. It looks like the registered email address provided in the website is not valid. Regards Ani Christian Rose wrote: On 6/20/06, Ani Peter [EMAIL PROTECTED] wrote: I would like to let you know my interest to work with the Malayalam GNOME translation project. I have found out from the website for GNOME Translation Project that Mr.Sajith V K (CC-ing him) is the co-ordinator of the project. A cursory glance through the project pages revealed that there have not been much updations since 2004. I would like to know if the project led by Mr. Sajith is still active. In that case I would like to join in to further the project. Otherwise I would like to continue the project from where it has been left. Kindly advice how I should proceed. You are doing the right thing by contacting the current Malayalam coordinator. If you do not manage to get any response from him, then please let us know (publically on the list). Christian ___ 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
Re: charset=ISO-8859-15
On 6/28/06, Kurt Maute [EMAIL PROTECTED] wrote: We've got a Spanish translation of the Planner user guide, and it seems to use ISO-8859-15 as its character set rather then UTF-8 (i.e. it needs charset=ISO-8859-15 in its header in order to transform correctly. Is there any rule or guideline against this? ...or maybe more importantly, any rule that we must use UTF-8? For application translations (regular po files), we do require them to be encoded in UTF-8. I'm not sure of whether we have any similar formal requirement for docs translations, but I think it would not make sense not to have it, given the above. I think you're pretty safe to give the offending translator a slap and tell him or her to start using UTF-8. ;-) Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME Marathi L01n team details
On 6/28/06, Christian Rose [EMAIL PROTECTED] wrote: Swapnil and Rahul, do you have accounts in http://bugzilla.gnome.org/? In that case, please let me know your account name (the e-mailaddress used when you registered the Bugzilla account). Yes, I have a bugzilla account and its registered with the same e-mail address i.e.[EMAIL PROTECTED]Rahul. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Translation quality control and quality assurance
Hi I have been searching information about quality assurance and control in the localization processes, mostly reading about LISA QA and QA Matrix at Sun. I would like to know if there are more GNOME translators and developers interested about how to improve our different translation teams, from the point of view of applications and organization. Now I'm writing a guide for Spanish team, but some parts of this guide could be useful for other teams, so I'm planning to rewrite that parts in English. I am using some Sun and LISA documents as starting point, but I would like to have more information about procedures at Novell about localization. People interested about this research for GNOME and libre software in general, please mail me. Cheers! ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation quality control and quality assurance
Hi Francisco, I am glad to hear about this initiative. I will be happy to collaborate with you in any way possible. I work in the L10n team at Novell and we have localization processes for close and open source products, we use QA matrix (a customized version of the LISA QA model) to rate translations work, etc. So just let me know what exactly do you want to know about Novell's procedures. Are you interested in knowing everything from development, UA, file handling, vendor and volunteer work, our QA model? I have looked and exchanged information with Sun about their QA process in the past, and we recently have updated our QA matrix to be in line with some of the most recent LISA QA model recommendations. We also use language style guides. Regards, Arturo Francisco Javier F. Serrador [EMAIL PROTECTED] 06/28/06 4:19 PM Hi I have been searching information about quality assurance and control in the localization processes, mostly reading about LISA QA and QA Matrix at Sun. I would like to know if there are more GNOME translators and developers interested about how to improve our different translation teams, from the point of view of applications and organization. Now I'm writing a guide for Spanish team, but some parts of this guide could be useful for other teams, so I'm planning to rewrite that parts in English. I am using some Sun and LISA documents as starting point, but I would like to have more information about procedures at Novell about localization. People interested about this research for GNOME and libre software in general, please mail me. Cheers! ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Question regarding fuzzy messages in po files
Hi, I have a quick question about fuzzy translations in po files. When po files are compiled to mo files, are the fuzzy translations included or is the source string included instead? regards Shane Wims Localisation Engineer [EMAIL PROTECTED] +35316058293 Novell, Inc. Software for the Open Enterprise http://www.novell.com/open ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Question regarding fuzzy messages in po files
Op Wed, 28 Jun 2006 17:35:36 +0200 schreef Shane Wims [EMAIL PROTECTED]: Hi, I have a quick question about fuzzy translations in po files. When po files are compiled to mo files, are the fuzzy translations included or is the source string included instead? regards Shane Wims The source strings are included. This is because fuzzy matching is not good enought to provide a meaningful translation. Kind regards, Vincent van Adrighem ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Question regarding fuzzy messages in po files
On 5:35:36 pm 06/28/06 Shane Wims [EMAIL PROTECTED] wrote: Hi, I have a quick question about fuzzy translations in po files. When po files are compiled to mo files, are the fuzzy translations included or is the source string included instead? Fuzzies are ignored in the conversion, i.e., the original source string will show up in the interface. Regards, Gora ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gnome glossary
Thanks Christian I don't really know how much effort needed to update the glossary but it is importance can not be stressed more. For the languages that already established this might not be an immediate concern but for those languages yet or still developing their computer terminology it would save a lot of pain and precious resources. I hope the gnome team would consider updating the glossary on regular bases. cheers tefera On 6/28/06, Christian Rose [EMAIL PROTECTED] wrote: On 6/27/06, TG [EMAIL PROTECTED] wrote: Can any one answer this question. Does the claime at http://developer.gnome.org/projects/gtp/glossary/ still hols true?? It has not been actively maintained for several years, in the sense that no new terms have been added. Still, the glossary is probably useful for many translation teams as a starting point for GNOME translation to some extent, and many teams do use it for that purpose. That's why we still keep it around in the GNOME Translation Project translation status pages. Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Fwd: Gnome glossary
The problem I see with the glosary is that there is not a tool that we can use to check without human intervention if all translations in a languaje project are according to the glosary. Also, the is a lack of metadata in the po format that makes this glossay very inefficient. We can reuse gnome-i18n-tools mailist to talk about implementing better tools for i18n and l10n. El mar, 27-06-2006 a las 20:00 +0200, [EMAIL PROTECTED] escribió: On 6:47:01 pm 06/27/06 TG [EMAIL PROTECTED] wrote: Can any one answer this question. Does the claime at http://developer.gnome.org/projects/gtp/glossary/ still hols true?? Don't know about other folk, but we in the Oriya team (as well as at least some of the other Indian language teams) do use the GNOME glossary, along with additions to it, as a basis for uniformity in translation. Regards, Gora ___ 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
Re: Question regarding fuzzy messages in po files
When po files are compiled to mo files, are the fuzzy translations included or is the source string included instead? The source string is included (unless you manually override this setting at mo compile time). Jakub Friedl ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: charset=ISO-8859-15
You should send it to the Spanish translation coordinator or the Spanish list so we can have a look about it and make the appropiate suggestions to the translator. Often documents submitted by people not involved in the translation process are not translated according with our standards. El mié, 28-06-2006 a las 15:04 +0200, Christian Rose escribió: On 6/28/06, Kurt Maute [EMAIL PROTECTED] wrote: We've got a Spanish translation of the Planner user guide, and it seems to use ISO-8859-15 as its character set rather then UTF-8 (i.e. it needs charset=ISO-8859-15 in its header in order to transform correctly. Is there any rule or guideline against this? ...or maybe more importantly, any rule that we must use UTF-8? For application translations (regular po files), we do require them to be encoded in UTF-8. I'm not sure of whether we have any similar formal requirement for docs translations, but I think it would not make sense not to have it, given the above. I think you're pretty safe to give the offending translator a slap and tell him or her to start using UTF-8. ;-) Christian ___ 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
Re: Translation quality control and quality assurance
Hi As you know, currenly I have started to play with Sun QA Matrix. I really would like to have a tool similar to LISA QA model that fits well with OLT, kbabel and the rest of the tools. One of the problems I see is that industry is progresively using xliff format, and all our i18n technology still is peacefully stuck with po file format, even for documentation. I'd would like to know if from the tech point of view it would be more convenient to start using xliff, and how difficult could be to support that technology. I have seen screenshots of LISA QA model, but no idea about how it works. I have some ideas about how to implement some tests specifically for Spanish language. El mié, 28-06-2006 a las 16:57 +0200, Arturo Aguilar escribió: Hi Francisco, I am glad to hear about this initiative. I will be happy to collaborate with you in any way possible. I work in the L10n team at Novell and we have localization processes for close and open source products, we use QA matrix (a customized version of the LISA QA model) to rate translations work, etc. So just let me know what exactly do you want to know about Novell's procedures. Are you interested in knowing everything from development, UA, file handling, vendor and volunteer work, our QA model? I have looked and exchanged information with Sun about their QA process in the past, and we recently have updated our QA matrix to be in line with some of the most recent LISA QA model recommendations. We also use language style guides. Regards, Arturo Francisco Javier F. Serrador [EMAIL PROTECTED] 06/28/06 4:19 PM Hi I have been searching information about quality assurance and control in the localization processes, mostly reading about LISA QA and QA Matrix at Sun. I would like to know if there are more GNOME translators and developers interested about how to improve our different translation teams, from the point of view of applications and organization. Now I'm writing a guide for Spanish team, but some parts of this guide could be useful for other teams, so I'm planning to rewrite that parts in English. I am using some Sun and LISA documents as starting point, but I would like to have more information about procedures at Novell about localization. People interested about this research for GNOME and libre software in general, please mail me. Cheers! ___ 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
Re: Question regarding fuzzy messages in po files
Hi Shane, On 6/28/06, Shane Wims [EMAIL PROTECTED] wrote: I have a quick question about fuzzy translations in po files. When po files are compiled to mo files, are the fuzzy translations included or is the source string included instead? IIRC it depends on the OS. For Linux, the string in source code is used, as other say. But for some other gettext implementation, say in Solaris, I have the impression that the fuzzy string is STILL used. Abel regards Shane Wims Localisation Engineer [EMAIL PROTECTED] +35316058293 Novell, Inc. Software for the Open Enterprise http://www.novell.com/open ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Abel Cheung (GPG Key: 0xC67186FF) Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF * GNOME Hong Kong - http://www.gnome.hk/ * Opensource Application Knowledge Assoc. - http://oaka.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Question regarding fuzzy messages in po files
Op Thu, 29 Jun 2006 02:54:58 +0800 schreef Abel Cheung [EMAIL PROTECTED]: Hi Shane, On 6/28/06, Shane Wims [EMAIL PROTECTED] wrote: I have a quick question about fuzzy translations in po files. When po files are compiled to mo files, are the fuzzy translations included or is the source string included instead? IIRC it depends on the OS. For Linux, the string in source code is used, as other say. But for some other gettext implementation, say in Solaris, I have the impression that the fuzzy string is STILL used. Abel Ouch! That would be extremely bad. Fuzzy translations are often completely wrong. It would be better to have an English string which nobody can understand than a translated string meaning something else. Kind regards, Vincent pgplVkwysC5iC.pgp Description: PGP signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Announcing new team for bn_IN
On 6/27/06, Christian Rose [EMAIL PROTECTED] wrote: ..snipped Thanks Taneem for your reply. I would also like to thank you very much for your past involvement. It seems you were not entirely convinced that there was a real need for a seperate bn_IN. Could you please enlighten us why? In a similar manner, could you Sayamindu please enlighten us why you are convinced there is a need for a seperate bn_IN translation? We usually require rather solid motivations why translation efforts for a language should be split, so could you please explain and summarize the significant differences in written Bengali and/or terminology that you think warrants the split efforts. Hi, Sorry for the late reply - I have been travelling lately: Bangla/Bengali already has split locales as bn and bn_IN in most of the major distros like Fedora [http://i18n.redhat.com/cgi-bin/i18n-status], Debian [http://www.debian.org/international/l10n/po/bn_IN], Ubuntu [https://launchpad.net/people/ubuntu-l10n-bn-in and https://launchpad.net/people/ubuntu-bd]. Mozilla [https://bugzilla.mozilla.org/show_bug.cgi?id=267132] and XFCE [http://i18n.xfce.org/stats/index.php?mode=2] also have bn_IN translations. bn_IN and bn_BD have different locale definitions due to differences in currency, time etc. From the viewpoint of translations, translators based out of India follow the revised spelling and grammatical recommendations as mandated by the Govt. of West Bengal's [Indian State] Language Body -Pashcim Banga Bangla Akademi [http://timesofindia.indiatimes.com/articleshow/20704765.cms]. While translators based in Bangladesh follow the specifications of the local language body. Due to dialectical differences in the spoken language and a major shift from the traditional written form by the Indian body it is becoming difficult to maintain consistency in common bn interfaces. Currently, gnome is the major desktop where a common bn interface is maintained with not so satisfactory results both as a stand-alone desktop as well as in conjunction with the distros. Please let me know if you require any more information/clarification. Thanks, Sayamindu ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
