On Wed, Jul 16, 2008 at 11:45 AM, 甘露(Lu Gan) wrote:

I can't access you page right now, may use tor for it later, but it's a great news, Is there a i18n/l10n team to discuss/review Arch's under hood i18n/l10n infrastructure, not only the translation?

Not yet, but it is one of the project's goals. We want to improve Arch applications and utilities to support and process different languages. There are some Arch projects that does not support translations yet (the installer, for example) and we want to change this sittuation. -- Hugo

Hi, What I want is to have a central place where anyone interested in i18n can have the necessary information to help with this. IMHO this means, for example, have all the POT files of Arch's tools (not only pacman) in one place. I do not want to make pacman more or less dependent of Arch. What I want is that when people think "I want to help translate Arch and its tools" they can find everything they need in one place. Dan can still host the POT files and I can only put a link to them at the i18n project page. I think that have a translators list on the page is important. This facilitates communication and can prevent someone translate something that is already being translated. I think that a good communication between the i18n project and pacman is also essential. A notice of future dates of string freeze, for example. Things will be easier now that I am a member of this ML. As I spoke, the i18n project has several goals and help with pacman translations is only part of this (an important one). I just want to make life easier for translators. I do not want, in any way, hinder, obstruct or cause any change in pacman's development. Well, i am open to suggestions on how this integration can work or whether we should forget this idea. -- Hugo Doria

On Wed, Jul 16, 2008 at 2:10 PM, Matthias Gorissen wrote:

While I do not think that pacman's current translation process should be changed, I welcome any other approach towards i18n/l10n. If you can come up with a POT file for the installer, just count me in for the German version. Of course, this means that several small files must be added to the images, so nothing could be done without the consent of Simo or others.

I made a patch for the installer. It *probably* will be translatable soon. Please, take a look here: http://archlinux.org/pipermail/arch-dev-public/2008-July/006898.html http://bugs.archlinux.org/task/10425 Simo need to do some clean on the code. I am just waiting him to patch the installer again. There will be no radical change in the pacman's translating process. Dan can still host the files and voinull stays with his part, for example. It's just a question of integration and this involves news, information and instructions for the translation process. These are just ideas and I am open to suggestions. BTW, i liked the idea of translate the man-pages. I will take a look at this later. -- Hugo

On Wed, Jul 16, 2008 at 5:58 PM, Hugo Doria wrote:

Dan can still host the POT files and I can only put a link to them at the i18n project page. I think that have a translators list on the page is important. This facilitates communication and can prevent someone translate something that is already being translated.

Dan already host all pot and po files, he already gave a link to them and to translation instructions in the string freeze announcement : http://archlinux.org/pipermail/arch-general/2008-July/018245.html While I am perfectly sure you only have good intentions, and the page looks pretty cool, the content is currently not so nice. It provides different pot files and different instructions than the pacman project. I am worried someone could fall on that and start translating from scratch a file that is already translated. It also shows an incomplete and different list of translators for pacman and libalpm. For a project like the installer which has currently no translations, that is all good. For a project like pacman which already has translations and a way to deal with them, you should either simply give links, or integrate the same contents, information and instructions. Starting something in parallel for this kind of stuff does not do any good in my opinion. Though don't believe I am angry or anything, I am simply trying to explain why I think the current page should be changed.

On Fri, Jul 18, 2008 at 6:13 AM, Xavier wrote:

While I am perfectly sure you only have good intentions, and the page looks pretty cool, the content is currently not so nice. It provides different pot files and different instructions than the pacman project. I am worried someone could fall on that and start translating from scratch a file that is already translated. It also shows an incomplete and different list of translators for pacman and libalpm.

The list was incomplete because I'm still finishing the page. Now i already added almost all translators, including those who were in the PO headers, but not in Dan's mail. I agree that the links should point to the Dan's host. I already updated them. As I spoke before I do not want to change any translation process in pacman and, even less, do something parallel. I just want to concentrate the necessary information for it in one single place. I've updated the page and I think now things are going the right way. Please, take a second look: http://dev.archlinux.org/~hugo/arch-i18n/ I am open to more suggestions. Thanks. -- Hugo