Re: Manpages in language-specific packages
Felipe Augusto van de Wiel (faw) dijo [Thu, Sep 14, 2006 at 12:31:35AM -0300]: - I18N in manpages? Sorry, haven't been there, haven't done that It's not that difficult, just put the (english) manpage in /usr/share/man/ and the i18n manpage in /usr/share/man/XX. Man takes care of the rest. You could use po4a, it is an amazing tool to work with different formats and convert them into PO files, than you could easily request for translator on -i18n. ;) http://po4a.alioth.debian.org/ Hmh... Looks noble, but in the case of a very simple and quite unmaintained Perl module, I don't really think it's worth it to go so far away from the original author's way - I will follow Javier's advice... Of course, once I have time and finish adopting the modules I told I would :) Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Manpages in language-specific packages
Hi, I'm adopting liblingua-es-numeros-perl, a Perl module for translating numbers into their Spanish string representation. One of the first things I noticed is that the manpage is completely (and only) written in Spanish. So, besides sending any changes I do to the upstream author (although the module looks unmaintained, with only version 0.01 existing since 2001), what would be wisest? - Leaving it as it is - Translating only the manpage description, perhaps first section - Don't think it would be the best, as it might have non-ES users (although the whole module API is in Spanish) - Translating the whole manpage, and providing the Spanish translation as a separate file in /usr/share/doc (pointing at it from the manpage) - Going the inverse way, leaving the package as close as possible to its current status, and pointing to an English translation from /usr/share/doc - I18N in manpages? Sorry, haven't been there, haven't done that Personally, I don't feel it natural having a Spanish-only manpage. But then again, I'm among the nasty minority who does not like his computer to use his mother tongue ;-) Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Manpages in language-specific packages
On Wed, Sep 13, 2006 at 12:46:19PM -0500, Gunnar Wolf wrote: Hi, I'm adopting liblingua-es-numeros-perl, a Perl module for translating numbers into their Spanish string representation. One of the first things I noticed is that the manpage is completely (and only) written in Spanish. So, besides sending any changes I do to the upstream author (although the module looks unmaintained, with only version 0.01 existing since 2001), what would be wisest? Translate the manpage to English, distribute that in /usr/share/man/man[1-9] and put the Spanish manpage at /usr/share/man/es/man[1-9] (where it should be). That way non-Spanish users installing the program will have a manual page and Spanish users will be able to read it properly (if their locale is configured properly) - I18N in manpages? Sorry, haven't been there, haven't done that It's not that difficult, just put the (english) manpage in /usr/share/man/ and the i18n manpage in /usr/share/man/XX. Man takes care of the rest. Regards Javier signature.asc Description: Digital signature
Re: Manpages in language-specific packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/13/2006 08:21 PM, Javier Fernández-Sanguino Peña wrote: On Wed, Sep 13, 2006 at 12:46:19PM -0500, Gunnar Wolf wrote: Hi, I'm adopting liblingua-es-numeros-perl, a Perl module for translating numbers into their Spanish string representation. One of the first things I noticed is that the manpage is completely (and only) written in Spanish. So, besides sending any changes I do to the upstream author (although the module looks unmaintained, with only version 0.01 existing since 2001), what would be wisest? Translate the manpage to English, distribute that in /usr/share/man/man[1-9] and put the Spanish manpage at /usr/share/man/es/man[1-9] (where it should be). That way non-Spanish users installing the program will have a manual page and Spanish users will be able to read it properly (if their locale is configured properly) - I18N in manpages? Sorry, haven't been there, haven't done that It's not that difficult, just put the (english) manpage in /usr/share/man/ and the i18n manpage in /usr/share/man/XX. Man takes care of the rest. You could use po4a, it is an amazing tool to work with different formats and convert them into PO files, than you could easily request for translator on -i18n. ;) http://po4a.alioth.debian.org/ Regards Javier Kind regards, - -- Felipe Augusto van de Wiel (faw) Debian. Freedom to code. Code to freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFFCM0XCjAO0JDlykYRAh8dAJ0YTSRClqmuztq9kcX+JrOa5MS/6wCg0RN5 51RL76Gdu8xCOT+NGHk4NkY= =hEBH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
