El sáb, 27-04-2002 a las 21:54, Isam Bayazidi escribió: > On Saturday 27 April 2002 18:51, Christian Rose wrote: > > > - Translated PO files are inconsistent places in the module tree, > > > checking in changes is not an easy job. > > > > How is this? I'm not aware of any module that doesn't use > > module_name/po/ for storing po files, except gnome-i18n but that's a > > very special case anyway. > > > Well in KDE we put all the PO files for our language in one place in the CVS > tree .. that is in the kde-i18n/ar/messages .. that really ease the life of > the traslation team maintainer .. all I have to do to check the files in is > to do a 'cvs commit' while I am in the kde-i18n/ar .. while with Gnome > approch, I have to either commit each file in seperate, or to have a tree > structure that is semilar to the Gnome CVS tree structure, that would sparce > the PO files :-) take note that we have our own CVS .. and we commit our > changes to the Gnome CVS priodly .. > > > > > everyones effort, it seems that KDE did a great job i18n wise and that > > > lead to have around 50 languages shiped with the latest KDE 3 release.. > > > > If I count the locales listed on the current GNOME unstable status > > pages, I get the number 61 if I counted correctly. > > > > Well the languages that got translated enough to be shiped is 50+ languages .. > while I doubt that this number of langauges will be with Gnome .. I think > that the translation in Gnome is taken care by developers :-) developers like > it the best way and that is not the easy way :-) I think that it can be > simplified .. > > Think about what I have to do every commit to Gnome: > 1) grab the latest POT files by wget > 2) msgmerge with our current PO files > 3) check them in to the different module/po one by one .. > > I can not use the module.ar.po ( that I can get my wget too) which is the > translation file for the module in Arabic becuase it will be outdated as all > the translation occure in our CVS rather than Gnome CVS .. You are wrong here. The module.ar.po files are updated all days against latest cvs version (well, they should be updated all days. It's my fault if they are not updated). > > now the latest POT for each module have different names each time .. > module.HEAD.pot today could be module.NEW_TAG.pot tomorrow .. I guess that > discluding the TAG from the file name would be better, as it will be known > that the "status" will always include the latest, without the need to > refering to which tag it is from .. The idea with the name.TAG.pot pattern is that you, the translator, will know the branch where you should commit the file. Some time ago we didn't use this information and the translators were asking me for this feature. > but again I am not from this world (Gnome World) so I may not know the reasons > why things are this way .. but I am trying to overcome these difficulties .. Please, feel free to ask anything you need. Also, the status scripts are beeing modified now so If you have any suggestion/improvement about them, please feel free to send me it. Cheers. P.S.: This thread is really big and I don't have time today to answer all your questions, please be pacient I should finish some changes to generate today status pages, tomorrow I will answer more mails (or perhaps tonight, but only after status update ;-). And yes THE SOLUTION is at gnome-i18n/status/translation-status.xml Cheers. > > -- > Yours, > Isam Bayazidi > Amman - Jordan > ==================================================== > Think Linux + Think Arabic = Think www.arabeyes.org > ==================================================== > _______________________________________________ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Carlos Perelló Marín mailto:carlos@gnome-db.org mailto:carlos.perello@hispalinux.es http://www.gnome-db.org http://www.Hispalinux.es Valencia - Spain
Esta parte del mensaje esta firmada digitalmente