[pacman-dev] pacman translations
Hi, I just saw that pacman3 supports internalization. Nice! :-) I want to complete the German translation; but before I start doing this: Does anybody else work on this? Do you want a patch or the whole file? -- http://www.archlinux.de
I just saw that pacman3 supports internalization. Nice! :-) I want to complete the German translation; but before I start doing this: Does anybody else work on this? Do you want a patch or the whole file?
I am very interested to the translation of pacman in Italian language. One year ago, I translated the previous version. -- Giovanni Scafora Arch Linux Trusted User & Package Maintainer (voidnull) http://www.archlinux.org linuxmania@gmail.com
I'll help Giovanni with the Italian translation, if anyone wants to contribute, please contact us. -- Alessio 'mOLOk' Bolognino
P.s. I put gtranslator in [community], GNOME users may like it. -- Alessio 'mOLOk' Bolognino.
Em Terça 06 Fevereiro 2007, Pierre Schmitz escreveu:
Hi,
I just saw that pacman3 supports internalization. Nice! :-) I want to complete the German translation; but before I start doing this: Does anybody else work on this? Do you want a patch or the whole file?
Hi, I want to translate it to brazilian portuguese. Is it already possible ? Thanks and keep the good work guys :)
On 2/6/07, Douglas Soares de Andrade <dsandrade@gmail.com> wrote:
Em Terça 06 Fevereiro 2007, Pierre Schmitz escreveu:
Hi,
I just saw that pacman3 supports internalization. Nice! :-) I want to complete the German translation; but before I start doing this: Does anybody else work on this? Do you want a patch or the whole file?
Hi,
I want to translate it to brazilian portuguese. Is it already possible ?
Thanks and keep the good work guys :)
WOW! Thanks guys for all stepping up to the plate for something like this. We'll (Aaron and I) try to make it a priority to figure out our plan of action for this and let you know exactly what we need from you guys. I know the PO and POT files need updating/merging before they should be updated, because some of the messages have changed. We'll definitely take any translations that people want to offer, as our current ones are a bit outdated. -Dan
On 2/6/07, Dan McGee <dpmcgee@gmail.com> wrote:
WOW! Thanks guys for all stepping up to the plate for something like this. We'll (Aaron and I) try to make it a priority to figure out our plan of action for this and let you know exactly what we need from you guys. I know the PO and POT files need updating/merging before they should be updated, because some of the messages have changed. We'll definitely take any translations that people want to offer, as our current ones are a bit outdated.
Yeah, I definitely agree with Dan here, you guys rock! I think the first thing would be to take a look at the POT files in libalpm and pacman directories on CVS and see if you can translate those into your target language (they're all probably severely out of date now). As a side note, I know very little about translating, but I am trying to figure out how useful po4a is for translating man pages. Wouldn't it make more sense just to translate the whole man page? I know little about this sort of thing, so feel free to slap some sense into me if I have this wrong. I just feel that po4a might be overkill for the translation of 3 man pages.
Am Dienstag, 6. Februar 2007 17:55:27 schrieb Aaron Griffin:
Yeah, I definitely agree with Dan here, you guys rock! I think the first thing would be to take a look at the POT files in libalpm and pacman directories on CVS and see if you can translate those into your target language (they're all probably severely out of date now).
OK, this seams to be quite easy when using KBabel. -- http://www.archlinux.de
OK. We have progress. I had to wrap my head around the whole gettext thing, but I did some tweaking and tinkering and got it to work nice and (kind of) smooth now. Here is the commit I made tonight, and it is pending on showing up on the list because it is some 400K in patches: * Update of all the *.po files and *.pot template files. * Makefile targets to rebuild po files now work - use 'make update-po' in the po directories. * Added two new translation templates as requested on the ML- 'it' and 'pt_BR'. As I said above, all of the po files are now updated. So those that started and made early replies on this thread, it is go time if you want to start the translations. I don't know much about it as I've never had to do it, but Alessio replied below about putting the gtranslator tool in community, and I believe the KDE equivalent kbabel may be useful as well. If not, just go straight to a text editor and do it that way. If there was previously translated material available, it should still be in your respecive po files. I know Giovanni said that he had previously translated pacman to Italian, however, this seems to be nowhere that I can find. If you still have something sitting around, we can try and incorporate it in, let me know on that. I would say your best bet is translate as much as you want/can, and then just inline include that file in an email back to this list. One of us will then place it back in the repository. So short summary: the po (translation) files are located in lib/libalpm/po/ and src/pacman/po/ at the moment. Currently I would not recommend starting on the manpages, as they are not complete yet. Any other questions, feel free to contact me or the list. -Dan
On 2/6/07, Dan McGee <dpmcgee@gmail.com> wrote:
Here is the commit I made tonight, and it is pending on showing up on the list because it is some 400K in patches:
Original Commit messages: =========================================================== Date: Tuesday, February 6, 2007 @ 21:22:53 Author: dan Path: /home/cvs-pacman/pacman-lib Modified: lib/libalpm/po/LINGUAS (1.2 -> 1.3) lib/libalpm/po/Makevars (1.2 -> 1.3) lib/libalpm/po/POTFILES.in (1.3 -> 1.4) lib/libalpm/po/de.po (1.1 -> 1.2) lib/libalpm/po/fr.po (1.1 -> 1.2) lib/libalpm/po/hu.po (1.1 -> 1.2) lib/libalpm/po/libalpm.pot (1.2 -> 1.3) src/pacman/po/LINGUAS (1.2 -> 1.3) src/pacman/po/Makevars (1.1 -> 1.2) src/pacman/po/POTFILES.in (1.2 -> 1.3) src/pacman/po/de.po (1.1 -> 1.2) src/pacman/po/fr.po (1.1 -> 1.2) src/pacman/po/hu.po (1.1 -> 1.2) src/pacman/po/pacman.pot (1.2 -> 1.3) * Update of all the *.po files and *.pot template files. * Makefile targets to rebuild po files now work - use 'make update-po' in the po directories. * Added two new translation templates as requested on the ML- 'it' and 'pt_BR'. This commit might be a bit big for the mailing list to like on the commit message. :) =========================================================== Date: Tuesday, February 6, 2007 @ 21:24:13 Author: dan Path: /home/cvs-pacman/pacman-lib Added: lib/libalpm/po/it.po (1.1) lib/libalpm/po/pt_BR.po (1.1) src/pacman/po/it.po (1.1) src/pacman/po/pt_BR.po (1.1) Oops. Actually add two new translation templates as requested on the ML- 'it' and 'pt_BR'. ===========================================================
Am Mittwoch, 7. Februar 2007 03:48:11 schrieb Dan McGee:
As I said above, all of the po files are now updated. So those that started and made early replies on this thread, it is go time if you want to start the translations. I don't know much about it as I've never had to do it, but Alessio replied below about putting the gtranslator tool in community, and I believe the KDE equivalent kbabel may be useful as well. If not, just go straight to a text editor and do it that way.
OK, we started our translation. Which character-encoding do you want? I think utf8 should be best choice because we could use it for every language. Pierre -- http://www.archlinux.de
2007/2/7, Pierre Schmitz <pierre@archlinux.de>:
Am Mittwoch, 7. Februar 2007 03:48:11 schrieb Dan McGee:
As I said above, all of the po files are now updated. So those that started and made early replies on this thread, it is go time if you want to start the translations. I don't know much about it as I've never had to do it, but Alessio replied below about putting the gtranslator tool in community, and I believe the KDE equivalent kbabel may be useful as well. If not, just go straight to a text editor and do it that way.
OK, we started our translation. Which character-encoding do you want? I think utf8 should be best choice because we could use it for every language.
Hm, is there a possibility to have two choices? For example, Ukrainians, Russians and other people with Cyrillic alphabet still prefer KOI8-U / KOI8-R often, because UTF-8 is still buggy in plain text console (there is a big bug-collector for these issues, but most of them are not fixed yet). -- Roman Kyrylych (Роман Кирилич)
On 2/7/07, Pierre Schmitz <pierre@archlinux.de> wrote:
OK, we started our translation. Which character-encoding do you want? I think utf8 should be best choice because we could use it for every language.
I agree, let's go with utf8
2007/2/7, Aaron Griffin <aaronmgriffin@gmail.com>:
On 2/7/07, Pierre Schmitz <pierre@archlinux.de> wrote:
OK, we started our translation. Which character-encoding do you want? I think utf8 should be best choice because we could use it for every language.
I agree, let's go with utf8
Then, can any dev take a look at problems with UTF-8 in console (most X issues are fixed)? I would like make a full switch to UTF-8, but I can't due to bugs. :( -- Roman Kyrylych (Роман Кирилич)
RK> Then, can any dev take a look at problems with UTF-8 in console (most RK> X issues are fixed)? I would like make a full switch to UTF-8, but I RK> can't due to bugs. :( Hm... which console programs have bugs in utf8? I do not spend too much time in console, but at least shell environment, mc-utf8, man works fine...
2007/2/7, Sergej Pupykin <ps@lx-ltd.ru>:
RK> Then, can any dev take a look at problems with UTF-8 in console (most RK> X issues are fixed)? I would like make a full switch to UTF-8, but I RK> can't due to bugs. :(
Hm... which console programs have bugs in utf8?
I do not spend too much time in console, but at least shell environment, mc-utf8, man works fine...
See http://bugs.archlinux.org/task/4418. UTF-8 should be fixed in all official packages, without the need to get community packages to work with UTF-8. -- Roman Kyrylych (Роман Кирилич)
2007/2/7, Pierre Schmitz <pierre@archlinux.de>:
[...] OK, we started our translation. Which character-encoding do you want? I think utf8 should be best choice because we could use it for every language.
Just FYI, we ( Arch Linux Italia ) are using utf8. We are pretty close to finish the libalpm and pacman translations. -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User
On 2/7/07, Pierre Schmitz <pierre@archlinux.de> wrote:
OK, we started our translation. Which character-encoding do you want? I think utf8 should be best choice because we could use it for every language.
Yes, I'd prefer UTF-8. In situations such as the one Roman mentions, perhaps UTF-8 is not the best then, and we can convert later. Note to all translators or future translators: I put a "translation-help" file in the pacman root directory to help you guys out, take a look at it if you want. In addition, if you see any changes that should be made there, then let me know. -Dan
2007/2/7, Dan McGee <dpmcgee@gmail.com>:
On 2/7/07, Pierre Schmitz <pierre@archlinux.de> wrote:
OK, we started our translation. Which character-encoding do you want? I think utf8 should be best choice because we could use it for every language.
Yes, I'd prefer UTF-8. In situations such as the one Roman mentions, perhaps UTF-8 is not the best then, and we can convert later.
UTF-8 is OK. I only asked if there is a possibility to have two man and po versions for some languages - UTF-8 and non-UTF-8. I think for man pages it is possible by putting them in corresponding /usr/man dirs (for example there are ru, ru.KOI8-R and ru.UTF-8 in /usr/man), the same can be done for .mo files, I think. Of course all this is quite odd. I would like all other encodings to disappear ASAP. -- Roman Kyrylych (Роман Кирилич)
RK> UTF-8 is OK. I only asked if there is a possibility to have two man RK> and po versions for some languages - UTF-8 and non-UTF-8. I think for RK> man pages it is possible by putting them in corresponding /usr/man RK> dirs (for example there are ru, ru.KOI8-R and ru.UTF-8 in /usr/man), RK> the same can be done for .mo files, I think. RK> Of course all this is quite odd. I would like all other encodings to RK> disappear ASAP. For man it is simplier to edit man.conf and put "iconv -f utf8 -t <locale-cp>" call into it. So I think man in utf8 is enough. Don't know about po...
On 2/7/07, Sergej Pupykin <ps@lx-ltd.ru> wrote:
RK> UTF-8 is OK. I only asked if there is a possibility to have two man RK> and po versions for some languages - UTF-8 and non-UTF-8. I think for RK> man pages it is possible by putting them in corresponding /usr/man RK> dirs (for example there are ru, ru.KOI8-R and ru.UTF-8 in /usr/man), RK> the same can be done for .mo files, I think. RK> Of course all this is quite odd. I would like all other encodings to RK> disappear ASAP.
For man it is simplier to edit man.conf and put "iconv -f utf8 -t <locale-cp>" call into it. So I think man in utf8 is enough. Don't know about po...
I believe the .po files are pretty good at working with different character sets, as long as you do 2 things: save the file in the correct character set, and correctly fill out the PO header where it asks for the charset used. After that, gettext does the hard work of converting between locales and charsets. -Dan
2007/2/7, Dan McGee <dpmcgee@gmail.com>:
On 2/7/07, Sergej Pupykin <ps@lx-ltd.ru> wrote:
RK> UTF-8 is OK. I only asked if there is a possibility to have two man RK> and po versions for some languages - UTF-8 and non-UTF-8. I think for RK> man pages it is possible by putting them in corresponding /usr/man RK> dirs (for example there are ru, ru.KOI8-R and ru.UTF-8 in /usr/man), RK> the same can be done for .mo files, I think. RK> Of course all this is quite odd. I would like all other encodings to RK> disappear ASAP.
For man it is simplier to edit man.conf and put "iconv -f utf8 -t <locale-cp>" call into it. So I think man in utf8 is enough. Don't know about po...
I believe the .po files are pretty good at working with different character sets, as long as you do 2 things: save the file in the correct character set, and correctly fill out the PO header where it asks for the charset used.
After that, gettext does the hard work of converting between locales and charsets.
OK, then I think there is no translation issues with UTF-8. :-) -- Roman Kyrylych (Роман Кирилич)
2007/2/7, Sergej Pupykin <ps@lx-ltd.ru>:
RK> UTF-8 is OK. I only asked if there is a possibility to have two man RK> and po versions for some languages - UTF-8 and non-UTF-8. I think for RK> man pages it is possible by putting them in corresponding /usr/man RK> dirs (for example there are ru, ru.KOI8-R and ru.UTF-8 in /usr/man), RK> the same can be done for .mo files, I think. RK> Of course all this is quite odd. I would like all other encodings to RK> disappear ASAP.
For man it is simplier to edit man.conf and put "iconv -f utf8 -t <locale-cp>" call into it. So I think man in utf8 is enough. Don't know about po...
Thanks for the tip! So, man issue is solved. :-) BTW, can you please comment on this bug: http://bugs.archlinux.org/task/4664 ? I think it can be closed with your tip, right? -- Roman Kyrylych (Роман Кирилич)
On 2/7/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/2/7, Sergej Pupykin <ps@lx-ltd.ru>:
RK> UTF-8 is OK. I only asked if there is a possibility to have two man RK> and po versions for some languages - UTF-8 and non-UTF-8. I think for RK> man pages it is possible by putting them in corresponding /usr/man RK> dirs (for example there are ru, ru.KOI8-R and ru.UTF-8 in /usr/man), RK> the same can be done for .mo files, I think. RK> Of course all this is quite odd. I would like all other encodings to RK> disappear ASAP.
For man it is simplier to edit man.conf and put "iconv -f utf8 -t <locale-cp>" call into it. So I think man in utf8 is enough. Don't know about po...
Thanks for the tip! So, man issue is solved. :-) BTW, can you please comment on this bug: http://bugs.archlinux.org/task/4664 ? I think it can be closed with your tip, right?
Very nice. Could someone with the know-how of this writeup a wiki page (or add to an existing one) related to locales and utf8?
On 2/7/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 2/7/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/2/7, Sergej Pupykin <ps@lx-ltd.ru>:
RK> UTF-8 is OK. I only asked if there is a possibility to have two man RK> and po versions for some languages - UTF-8 and non-UTF-8. I think for RK> man pages it is possible by putting them in corresponding /usr/man RK> dirs (for example there are ru, ru.KOI8-R and ru.UTF-8 in /usr/man), RK> the same can be done for .mo files, I think. RK> Of course all this is quite odd. I would like all other encodings to RK> disappear ASAP.
For man it is simplier to edit man.conf and put "iconv -f utf8 -t <locale-cp>" call into it. So I think man in utf8 is enough. Don't know about po...
Thanks for the tip! So, man issue is solved. :-) BTW, can you please comment on this bug: http://bugs.archlinux.org/task/4664 ? I think it can be closed with your tip, right?
Very nice. Could someone with the know-how of this writeup a wiki page (or add to an existing one) related to locales and utf8?
The other thing is to perhaps bring this over to the arch ML and see if you can get anything rebuilt as necessary for full UTF-8 compatibility. -Dan
2007/2/7, Dan McGee <dpmcgee@gmail.com>:
Thanks for the tip! So, man issue is solved. :-) BTW, can you please comment on this bug: http://bugs.archlinux.org/task/4664 ? I think it can be closed with your tip, right?
Very nice. Could someone with the know-how of this writeup a wiki page (or add to an existing one) related to locales and utf8?
The other thing is to perhaps bring this over to the arch ML and see if you can get anything rebuilt as necessary for full UTF-8 compatibility.
I think I get confused about what you exactly are talking about here. Are you talking about rebuilding of software or manpages? http://bugs.archlinux.org/task/4418 describes issues with UTF-8 in different software and lists patches and fixed packages in community. Are you talking about setting wiki page for listing UTF-8 support status for different packages? -- Roman Kyrylych (Роман Кирилич)
RK> Thanks for the tip! So, man issue is solved. :-) RK> BTW, can you please comment on this bug: RK> http://bugs.archlinux.org/task/4664 ? I think it can be closed with RK> your tip, right? iconv can be used if all manpages have the same charset. All of my pages are in koi8-r or ascii. So "iconv -f koi8-r -t utf8" always works. May be simple script can solve many charsets issue too.
2007/2/7, Dan McGee <dpmcgee@gmail.com>:
If there was previously translated material available, it should still be in your respecive po files. I know Giovanni said that he had previously translated pacman to Italian, however, this seems to be nowhere that I can find. If you still have something sitting around, we can try and incorporate it in, let me know on that.
There are not available previous files translated to italian language, because one year ago when I translated pacman, it did not still have support to gettext. It was my local test only. We (me and Alessio) will send you the translated files very soon. -- Giovanni Scafora Arch Linux Trusted User & Package Maintainer (voidnull) http://www.archlinux.org linuxmania@gmail.com
participants (8)
-
Aaron Griffin
-
Alessio 'mOLOk' Bolognino
-
Dan McGee
-
Douglas Soares de Andrade
-
Giovanni Scafora
-
Pierre Schmitz
-
Roman Kyrylych
-
Sergej Pupykin