--- khaled ghetas <[EMAIL PROTECTED]> wrote: > > It would be best to convert all the manpages to .PO[T] format if > > possible and then simply follow the well-known procedure that > > everyone is using within Arabeyes for translations. > > Why don't translate them directly? > Man pages are simple text files and all what we need is translating > all words that don't start with "dot" and of course the command > itself and it's options.
The point is that we already have a well documented and established method (did I mention that 'gettext' is the defacto standard out there with regard to translations) and it would be best if we could follow it. One major advantage is that a workforce doesn't need to do anything elaborate for each project, they simply upload the file, launch Kbabel and translate away. Having different projects follow different standards would render various volunteers specialists in that application and that application only. As it stands now, if someone opted to translate one file from each of our projects he/she's more than welcome to do so in a standard method. >From the limited google'ing that I've just done it looks like there are various man2XYZ and XYZ2man translators and there are XYZ2po and po2XYZ, so in principle with a bit more reading and testing it should be possible. What about 'po4a' [1] ? I wonder what other projects/languages do... Could the various project maintainers (KDE/Gnome/Debian) comment on if said projects have a view on this and/or if they have the necessary scripts and procedure. Worse come to worse we could create these scripts if need be. [1] http://lists.debian.org/debian-i18n/2004/02/msg00026.html Salam. - Nadim __________________________________ Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html
_______________________________________________ Doc mailing list [email protected] http://lists.arabeyes.org/mailman/listinfo/doc
