Re: [Fwd: Re: GNOME 2.16 release notes]
Brent Smith skrev: The release notes can now be translated - they are in the gnomeweb-wml module, at www.gnome.org/start/2.16/notes/docbook They use gnome-doc-utils/xml2po for translation Not Found The requested URL /start/2.16/notes/docbook was not found on this server. smime.p7s Description: S/MIME Cryptographic Signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Pashto Translation Team of Gnome
(Please subscribe to the gnome-i18n list and keep the list cc:ed on this matter. We want to keep this discussion public.) On 9/3/06, Mohammad Khalid Ameery [EMAIL PROTECTED] wrote: On 8/31/06, Mohammad Khalid Ameery [EMAIL PROTECTED] wrote: Dear GTP members, I have noticed that you have a Pashto Translation Team for Gnome Translation Project. But I noticed that The name for that team is Pusto which is wrong. The right spelling for this is Pashto which is used every where and is also right according to Spelling rules. The ISO 639 registration authority uses the Pushto spelling for this English language name (see http://www.loc.gov/standards/iso639-2/englangn.html#op). In GNOME, we use the ISO 639 spellings of language names in English. So if you want to change this, please convince the ISO 639 authority. Then, when they have adopted their recommendations, we can change to use the other spelling in GNOME. I have already convinced the ISO 639 for the spelling. I wish they will accept it. Ok. Please let us know when they do. What do you think, is name of the team changeable or we should create another team for this. I have sent and email to Ismail Maskani who is the only coordinator at the Pushto Team to add me to this team, but I have no reply from him. I want to start translation immediately because nothing is done in Pashto translation yet. what should I do? Keep bugging him. If you get no reply, please let us know, and we'll halve to resolve this some other way. I have no reply from him yet, I will continue sending him messages until I have any reply from him. Till that I will download the translation files and do my work offline. I will upload the translated files back when I am added to team. Ok. I haven't found any recent communications or activity by him either, so I think we should proceed. What we usually do in these cases is officially give the current language team coordinator a full week's time to reply. In case the coordinator hasn't replied by a week, we will continue with appointing some other coordinator for the affected language team. So, Ismail, please respond in a week from now, and please let us know why you've been unable to respond earlier. Khalid, please remind us (publically and on-list) when a week has passed from now. Also, please let us know (publically and on-list) whether you are volunteering for the new Pashto language team coordinator position. Please read http://live.gnome.org/TranslationProject/TeamCoordinatorResponsibilities . Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Assamese translation for GNOME
On 8/28/06, Amitakhya Phukan [EMAIL PROTECTED] wrote: Hi all, I want to join the GNOME translation project and want to work on the Assamese translation. I have contacted the coordinator of this project, Mr. Sunaram Patir, and he has welcomed me to the project team and has directed me to this link: http://developer.gnome.org/projects/gtp/join.html I want to participate actively in this project. Great! Welcome! Please do tell me what more is required from my side so that I can contribute to the maximum and how do I obtain the CVS access to it? I have already subscribed to the list at this email address of mine. Your team coordinator should be able to tell you what needs to be done for Assamese. You should be able to translate without having a CVS account -- ask your team coordinator what needs to be translated, then download the necessary po/pot files from the web, and then send the finished files to someone in your team that can commit the files for you. Being granted a CVS account of one's own usually comes *after* having already contributed -- please see http://live.gnome.org/TranslationProject/RequestingAnAccount for details. Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [Fwd: Re: GNOME 2.16 release notes]
On 9/3/06, Brent Smith [EMAIL PROTECTED] wrote: The release notes can now be translated - they are in the gnomeweb-wml module, at www.gnome.org/start/2.16/notes/docbook They use gnome-doc-utils/xml2po for translation I've started Thai translation. However, I think I find some typos: #: ../C/rnbackend.xml:129(para) msgid Due to the lack of active maintainership, the themes emphasisRand-Canyon/ emphasis, emphasisOcean-Dream/emphasis, emphasisSimple-Blus/ emphasis, emphasisSmokey-Blue/emphasis, and emphasisTraditional/ emphasis were removed. Likewise, the emphasisLighthouseblue/emphasis and emphasisMetal/emphasis theme engines were removed as well. The theme name Rand-Canyon should be Grand Canyon, Simple-Blus be Simple. Cheers, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GnomeDocUtilsMigrationHowTo improvements
Hi Behdad; On Sun, 2006-09-03 at 04:36 -0400, Behdad Esfahbod wrote: There are also a couple of technical problems with that document. One is: quote Set your build system up: * If you don't have one yet, create a m4 directory in your toplevel source directory; and create a .cvsignore file in it containing at least gnome-doc-utils.m4. Add this directory and its .cvsignore to cvs. * Add the following to configure.ac (resp. configure.in): * AC_CONFIG_MACRO_DIR([m4]) * Add m4 to EXTRA_DIST in the top-level Makefile.am See below Note 2 /quote This is absolutely unnecessary, and it does create problems. A lot. I added that section as a result of what I did learn when porting gnome-utils to gnome-doc-utils; at the moment of the porting, if I did not include the macro directory in the EXTRA_DIST, make distcheck would fail (I did various checks and the only change that affected the outcome of distcheck was that). Lately, I was able to pass the distcheck phase even when the m4 directory was not inside the EXTRA_DIST variable - so I think that porting my build environment to automake = 1.7 did the trick. I think it's safe to assume that yes: that bit is wrong when using an automake 1.7; I'd like people with older versions of automake to test that bit and see if it was just a screw up in my build environment. Ciao, Emmanuele. -- Emmanuele Bassi, E: [EMAIL PROTECTED] W: http://www.emmanuelebassi.net B: http://log.emmanuelebassi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [Fwd: Re: GNOME 2.16 release notes]
Theppitak Karoonboonyanan wrote: On 9/3/06, Theppitak Karoonboonyanan [EMAIL PROTECTED] wrote: On 9/3/06, Brent Smith [EMAIL PROTECTED] wrote: The release notes can now be translated - they are in the gnomeweb-wml module, at www.gnome.org/start/2.16/notes/docbook They use gnome-doc-utils/xml2po for translation I've started Thai translation. However, I think I find some typos: Another one: #: ../C/rnbackend.xml:41(para) msgid This also marks also the start of deprecating the previously used libraries emphasislibgnomeprint/emphasis and emphasislibgnomeprintui/emphasis: External projects are encouraged to use the new functionality provided by GTK + 2.10. This also marks also ... should not repeat also. Both fixed in HEAD. Thanks for pointing these out! -- Brent Smith [EMAIL PROTECTED] IRC: smitten ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bundling all translations into release tarball
On 9/1/06, Wouter Bolsterlee [EMAIL PROTECTED] wrote: JFYI, a quick glace at my local Gnome sources gives me the following list of modules that do NOT use po/LINGUAS [list of cvs modules...] Yes, I forgot to say, I also added those not using po/LINGUAS but configure.in or configure.ac. However it's for platform and desktop release only. I don't have too much time to check all gnome cvs modules thoroughly right now. Abel mvrgr, Wouter -- :wq mail [EMAIL PROTECTED] web http://uwstopia.nl child's rhyme stuck in my head :: said that life is but a dream -- tool -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFE+CN8P7QTTiUKY+sRAhZvAJ9+4SqfNtX6ZMYMysNGyidCvrq5+wCfSvCT V1UDxmhxr9PYTCZMJ5SBl8I= =1cU2 -END PGP SIGNATURE- ___ 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: Bundling all translations into release tarball
On 9/1/06, Daniel Nylander [EMAIL PROTECTED] wrote: Can you please check help/DOC_LINGUAS too? There might be some translations done that is missing from the DOC_LINGUAS I guess my time is too tight to do doc checking as well, since everybody is rushing to get their translation into gnome, and I'm no different. Besides, since the tarball release time is too near, I wouldn't want to risk breaking the build of tarball at such a time. Perhaps it can be done after release. So far I only notice 3 docs not added into DOC_LINGUAS: uk in eog/help hu in gnome-power-manager/help uk in gnome-terminal/help Abel Daniel ___ 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: GnomeDocUtilsMigrationHowTo improvements
On Sun, 2006-09-03 at 09:57 -0400, Emmanuele Bassi wrote: Hi Behdad; On Sun, 2006-09-03 at 04:36 -0400, Behdad Esfahbod wrote: There are also a couple of technical problems with that document. One is: quote Set your build system up: * If you don't have one yet, create a m4 directory in your toplevel source directory; and create a .cvsignore file in it containing at least gnome-doc-utils.m4. Add this directory and its .cvsignore to cvs. * Add the following to configure.ac (resp. configure.in): * AC_CONFIG_MACRO_DIR([m4]) * Add m4 to EXTRA_DIST in the top-level Makefile.am See below Note 2 /quote This is absolutely unnecessary, and it does create problems. A lot. I added that section as a result of what I did learn when porting gnome-utils to gnome-doc-utils; at the moment of the porting, if I did not include the macro directory in the EXTRA_DIST, make distcheck would fail (I did various checks and the only change that affected the outcome of distcheck was that). Lately, I was able to pass the distcheck phase even when the m4 directory was not inside the EXTRA_DIST variable - so I think that porting my build environment to automake = 1.7 did the trick. I'm not referring to the EXTRA_DIST part in particular, but the entire idea of enabling a MACRO_DIR. AFAIU a MACRO_DIR should be used when you want to use and distribute home-made macro files that may not be available on the system. I don't see any reason that one should do that. If the intention to make sure packages can be autogen'ed without gnome-doc-utils? I don't think that's important enough to warrant adding a directory to all modules. I think it's safe to assume that yes: that bit is wrong when using an automake 1.7; I'd like people with older versions of automake to test that bit and see if it was just a screw up in my build environment. Ciao, Emmanuele. -- behdad http://behdad.org/ Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill -- Dan Bern, New American Language ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for UI break for Tomboy
On 9/2/06, Alex Graveley [EMAIL PROTECTED] wrote: Hi, This simple patch makes the gtkspell dependency optional, and removes the enable spell-checking checkbox in the Prefrences depending on gtkspell's availability. I could probably just commit this as it basically counts as a build fix, but I thought I'd take the safe route since I'm new to all this. Besides, it gives docs people a heads up. Yeah, sounds sane, and it does have a ui-change necessary to go with the build fix. So here's 1 of 2. I wonder if that should be 2 of 2, considering http://mail.gnome.org/archives/release-team/2006-August/msg00159.html, but it's at least 1. :-) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Epiphany branched for 2.16
Hi, Epiphany is now branched for Gnome 2.16; the branch name is gnome-2-16. Regards, Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Translation QA tool
Hello everyone, I would like to bring to your attention a simple l10n QA tool that makes it very easy to submit l10n suggestions and bug fixes: http://gintas.pov.lt/l10nsuggest (in the string search screen try rinkm for rinkmena which is Lithuanian for file) I am hoping this will make feedback from Lithuanian users rise at least a little above zero ;) but there's no reason it couldn't be used for translations in other languages. This is just a prototype and it currently contains only Lithuanian translations of GNOME programs (by scraping l10n-status.gnome.org). Currently it only forwards the notes to me by e-mail, but this could be easily extended. The tool is also localisable. If other people are interested, I could import some other languages, or provide the source code so that you can run your own server. Feedback is appreciated, -- Gintautas Miliauskas http://gintasm.blogspot.com signature.asc Description: PGP signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation QA tool
I do not see any Quality Assurance metric in this tool. Could you tell us if your tool can do a TQI at least or if it supports some natural language checking artifact? Thanks El dom, 03-09-2006 a las 23:22 +0300, Gintautas Miliauskas escribió: Hello everyone, I would like to bring to your attention a simple l10n QA tool that makes it very easy to submit l10n suggestions and bug fixes: http://gintas.pov.lt/l10nsuggest (in the string search screen try rinkm for rinkmena which is Lithuanian for file) I am hoping this will make feedback from Lithuanian users rise at least a little above zero ;) but there's no reason it couldn't be used for translations in other languages. This is just a prototype and it currently contains only Lithuanian translations of GNOME programs (by scraping l10n-status.gnome.org). Currently it only forwards the notes to me by e-mail, but this could be easily extended. The tool is also localisable. If other people are interested, I could import some other languages, or provide the source code so that you can run your own server. Feedback is appreciated, ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n !DSPAM:44fb4800290361156312072! ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: libgnomeui broke the string freeze
On 9/3/06, Christian Rose [EMAIL PROTECTED] wrote: On 9/2/06, Wouter Bolsterlee [EMAIL PROTECTED] wrote: The libgnomeui commit [1] by Kristian Rietveld introduced a new string [2], which is unacceptable in string freeze, 4 days before a release. There has not been any notification sent out to to gnome-i18n either... Please revert the patch or make sure you reuse an already existing string. thanks, Wouter [1] http://cvs.gnome.org/viewcvs/libgnomeui/file-chooser/gtkfilesystemgnomevfs.c?r1=1.80r2=1.81 [2] Error getting information for '%s' Indeed, this is not acceptable. Kris, could you please revert this string addition? Reverting the patch would give you a gnome release with a very broken filechooser. Do you really want that ? And removing the _() just for formal string freeze reasons would be a bit silly, since the end effect would be just the same, an untranslated error message... Matthias ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Time of submitting the final translation !
Hi AllCan anyone let me know the exact time (UTC) for submitting the final translated files and after which no more files can be updated.Looking forward to get the answer from someone.Regards,Subhransu BeheraContributor, Oriya Localization Team. Here's a new way to find what you're looking for - Yahoo! Answers Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation QA tool
Hello, I do not see any Quality Assurance metric in this tool. Could you tell us if your tool can do a TQI at least or if it supports some natural language checking artifact? OK, that 'QA' should not have been there. It's basically a bug report tool that can search strings. I would like to hear suggestions of potentially useful features though. Sorry for the misleading e-mail. Best regards, -- Gintautas Miliauskas http://gintasm.blogspot.com signature.asc Description: PGP signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
