CLDR
On 20 Mar 2009 Roozbeh has announced, that gnome will eventually use CLDR data in the future. Are there any news about that, or is the project dead? http://mail.gnome.org/archives/gnome-i18n/2009-March/msg00334.html It would be extremly helpful, if the big desktop enviroments (GNOME and KDE) would use the CLDR data provided by the unicode consortium. The biggest problem is, that the glibc maintainers are not very interessted in updating and handling localisation data. So most patches will never going to glibc, until some of the devs have a very good day. Glibc has also a problem with the review process. For most languages the developers can't peer review, because they simply don't understand the language. This leads to poor quality in locales. On contrary, unicode has set up a stunning development infrastructure. The development cycle goes always through data entry, peer review and a verification cycle, befor they release a new version of the data. Regards ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Adding information column to DL with proposed release dates and documentation state
On Fri, 2011-04-08 at 08:55 +0200, Gil Forcada wrote: El dj 07 de 04 de 2011 a les 17:01 +0200, en/na Johannes Schmid va escriure: Hi! At this point this it is just an idea and I am very much looking for feedback. Would this be helpful? Will developers play along? Will this be acceptable within the design goals of Damned Lies (Claude)? Should the information in this columns be what I wrote, or is there something else that would be more helpful? As there are still rules to be defined for the applications included, this is difficult to tell. However, I think at least a list of release dates would be helpful as long as it can be generated automatically from GNOME releases and only those modules that have other dates would need to update them accordingly (which could send a mail to gnome-i18n). The documentation part seems difficult to me because it is always hard to tell how up-to-date documentation is. But it would be nice to have a marker that says Don't translated, this is outdated/being updated. Quoting from Shaun McCance: I've just added the following to all the pages in gnome-help: revision pkgversion=3.0 version=3.0.1 date=2011-04-06 status=outdated/ So, no, if we put a Mallard parser on D-L we could know the outdated status of mallard documents. Maybe even the mallard2po (or whichever script transforms mallard to po files) could also add some metadata to the strings that are inside a document with that header. Shaun, could you explain it further? Right, at least for the gnome-help, the documentation team made extensive use of the revision element, and we'll use it even more (and probably refine our use of it) in the future. The info in the revision element is probably useful to you all, because it can help you prioritize. The thing is, the revision marker is per-page. So it's not an all-or-nothing on a single document kind of thing. That has its ups and its downs for translators, I think. But an up is that we could mark strings as stable or not in the PO files. By the way, much of this information is available on Blip: http://blip.blip-monitor.com/ So one of the projects I've been working on is a replacement for xml2po called ITS Tool. http://gitorious.org/itstool It's the same idea. Strings are extracted from XML files and put into PO files, then merged back. But it does everything according to rules from the W3C Internationalization Tag Set, plus some extension rules to support features we need. I can add a rule to put a comment or something on each string that says if that string is stable or not. I don't know if there's a standard PO marker for that. Actually, if any translators have a little free time (I know, who has free time?), I wouldn't mind people trying it out and giving some feedback. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Adding information column to DL with proposed release dates and documentation state
Hi Johannes 2011/4/7 Johannes Schmid j...@jsschmid.de: Hi! At this point this it is just an idea and I am very much looking for feedback. Would this be helpful? Will developers play along? Will this be acceptable within the design goals of Damned Lies (Claude)? Should the information in this columns be what I wrote, or is there something else that would be more helpful? As there are still rules to be defined for the applications included, this is difficult to tell. However, I think at least a list of release dates would be helpful as long as it can be generated automatically from GNOME releases and only those modules that have other dates would need to update them accordingly (which could send a mail to gnome-i18n). Yes, that is the idea. The assumption is that all modules on one page in damned lies has to adhere to the same set of rules (whatever they may be). So either they are required to follow GNOME release schedule or they are not. If they are not _required_ then they inform DL (in one way or another) whether they still intend on following the GNOME release schedule (in which case the information can be autogenerated), and if they don't, they provide a date, when they have one. It was never the idea that all modules in DL had to have this information, if there is no release planned, then they don't set the date and we will know that it is lower priority. Then when they decide to plan a release, they set the date and we start translating. About the list, I think it is crucial that it is in DL since, as a translator, that is the center of my whole world ;). The information needs to be right there next to the number of strings needing to be updated. Concerning how to change the release date for your module, I think it is important that it is something that developers and documenters can do without any middle men. I'm a low tech kind of guy, so I would just ask them to put this information in a file somewhere in the source tree and have DL parse it, maybe there is a better way, but it has to be easy and direct. The documentation part seems difficult to me because it is always hard to tell how up-to-date documentation is. But it would be nice to have a marker that says Don't translated, this is outdated/being updated. The documenters know how up to date their documentation is. So the only things that is required is, that when they bring the documentation up to par with a certain release of to the state of current trunk, then they write down that release of the date in a file, that DL then parses. Same thing for marking it as DO NOT TRANSLATE, when you start rewriting the documentation from scratch, write it in that magical file and the information will be on DL. Regards Kenneth ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Adding information column to DL with proposed release dates and documentation state
Right, at least for the gnome-help, the documentation team made extensive use of the revision element, and we'll use it even more (and probably refine our use of it) in the future. The info in the revision element is probably useful to you all, because it can help you prioritize. The thing is, the revision marker is per-page. So it's not an all-or-nothing on a single document kind of thing. That has its ups and its downs for translators, I think. But an up is that we could mark strings as stable or not in the PO files. Well that depends. If you update the revision tags in the other files also, when you update one, then it could simply be defined as the oldest date. But if we cannot come up with an algorithm for this, there is still also the possibility of the documenters providing the information manually. Regards Kenneth ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-games, chess: Strings accidentally not marked for translation
2011/4/8 Robert Ancell robert.anc...@gmail.com: Hi, I just enabled some strings [1] for translation in Chess (gnome-games) that were accidentally unmarked for translation. These strings are: Save Chess Game Load Chess Game PGN files All files These strings are the same as they were in 2.32 and most .po files still have the translations there. Some po files have the translations commented out and will need to be re-enabled for 3.0.1. Well not exactly. If up to this point the strings were not there, then they will become obsolete (commented out) in all po-files that have been generated since they were commented out in the code, so if this happened say a month ago then pretty much all active translation teams will have to re-enable these strings. Not that it really matters since, no matter what, this is technically not a string freeze. Regards Kenneth ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String freeze break requests for gnome-control-center
Here are the 2 bugs: https://bugzilla.gnome.org/show_bug.cgi?id=647123 (with translations snatched from glib) https://bugzilla.gnome.org/show_bug.cgi?id=647125 (adds one string) Let me know if those are OK to commit. Cheers ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gnome-control-center.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-control-center.master': + Show help options Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze break requests for gnome-control-center
2011-04-08 16:52 keltezéssel, Bastien Nocera írta: Here are the 2 bugs: https://bugzilla.gnome.org/show_bug.cgi?id=647123 (with translations snatched from glib) This seems to be already committed, but no objections. Crashers are important. https://bugzilla.gnome.org/show_bug.cgi?id=647125 (adds one string) This replaces a not translatable string with a translatable one, so 1/2. Regards Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-control-center new string?
2011-04-06 21:35 keltezéssel, Kenneth Nielsen írta: 2011/4/6 Andre Klapperak...@gmx.net: On Wed, 2011-04-06 at 15:48 +0100, Richard Hughes wrote: I'm trying to fix https://bugzilla.gnome.org/show_bug.cgi?id=645002 which has just become a release blocker for Fedora 15. I'm proposing we add the following patch to gnome-control-center so that we can fix the issue properly for 3.0.1 I know we don't normally allow string additions in stable branches, but I thought I'd ask anyway. Ideas welcome. + /* TRANSLATORS: this is when the access point is not listed + * in the dropdown (or hidden) and the user has to select + * another entry manually */ + PANEL_WIRELESS_COLUMN_TITLE, _(Other...), The string already exists in g-c-c so technically speaking it is not a string freeze break: #: ../panels/user-accounts/um-language-dialog.c:180 msgid Other... However I don't know if some languages require a translation context (msgctxt) here which would make this a new separate string, in case the two translations differ (gender of strings that each of them refers to). See https://live.gnome.org/TranslationProject/DevGuidelines/Translation%20contexts It _is_ context/gender dependent, at least in Danish. So you cannot reuse an existing Other... translation from another project, _unless_ it there also refers to an access point (and the context is made clear in the translation you want to copy from). Regards Kenneth I'd say it's important enough to go. If this context gets added, then 1/2 from i18n. Regards Gabor Kelemen andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper | http://www.openismus.com ___ 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[Fwd: Re: Testing translated documentation]
Forwarding to gnome-i18n just to let everyone know this trick to test documentation translations. Btw thanks for all your work on Mallard and everything Shuan!! Cheers, -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net ---BeginMessage--- On Thu, 2011-04-07 at 20:03 +0300, Krasimir Chonov wrote: Hi there, I`m translating GNOME on Bulgarian language and now I want to start translating the documentation for GNOME 3 written on Mallard. Unfortenately I can`t find any information how to test the translated documentation. Can you give me a link with information what I should to? I don't think there is a page anywhere. The build process normally takes care of creating the translated page files. The problem with that for you is that you need the right dependencies and such to even run configure. Although at least for gnome-user-docs, that's not hard. You can call xml2po yourself though. This should work: for page in ../bg/*.page; do xml2po -m mallard -p xxx.po $page `basename $page`; done Run that inside the bg directory. Then run Yelp like so: yelp . You can also hand it the file name of a page file to look at that page immediately without navigation through things. -- Shaun ___ gnome-doc-list mailing list gnome-doc-l...@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-doc-list ---End Message--- ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Change of Telugu team coordinator
The bounce from Sunil's registered address is enclosed for your information. I have known Sunil for couple of years and he expressed interest to hand it off coordinatorship to others. Cheers Arjun fromMail Delivery Subsystem mailer-dae...@googlemail.comto arjunar...@gmail.com (Yes, this is you.) Learn morehttp://mail.google.com/support/bin/answer.py?hl=enctx=mailanswer=10313 dateSat, Apr 9, 2011 at 10:02 AMsubjectDelivery Status Notification (Failure) hide details 10:02 AM (2 minutes ago) Delivery to the following recipient failed permanently: su...@tcs.co.in Technical details of permanent failure: DNS Error: DNS server returned answer with no data - Original message - MIME-Version: 1.0 Received: by 10.204.168.66 with SMTP id t2mr2526944bky.53. 1302323549728; Fri, 08 Apr 2011 21:32:29 -0700 (PDT) Received: by 10.204.6.82 with HTTP; Fri, 8 Apr 2011 21:32:29 -0700 (PDT) Date: Sat, 9 Apr 2011 10:02:29 +0530 Message-ID: banlktingaqart+re7ozqdr_0nv9zauj...@mail.gmail.com Subject: Change of Telugu team coordinator From: Arjuna Rao Chavala arjunar...@googlemail.com To: gnome-i18n@gnome.org Cc: Sunil Mohan sunilmo...@gmail.com, su...@tcs.co.in Content-Type: multipart/alternative; boundary=bcaec52c666b90715d04a074d407 - Hide quoted text - Hi, Sunil, Telugu coordinator has become inactive. I would like to become the new coordinator to help continue the localisation work. Kindly approve at the earliest. Cheers Arjuna Rao Chavala Independent software technologist and Telugu localisation contributor On Sat, Apr 9, 2011 at 10:02 AM, Arjuna Rao Chavala arjunar...@googlemail.com wrote: Hi, Sunil, Telugu coordinator has become inactive. I would like to become the new coordinator to help continue the localisation work. Kindly approve at the earliest. Cheers Arjuna Rao Chavala Independent software technologist and Telugu localisation contributor ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
