[pacman-dev] [translation] String freeze for pacman 3.1.1 release
We've weeded out a handful of bugs and issues since 3.1.0, so it is time to call for a string freeze for 3.1.1. I've CC-ed this to the Arch General list to see if we can get a helping hand with some of our currently neglected translations. As this list may not be quite as familiar with how everything works, PLEASE reply to the list or privately to me if you have questions or want to help out but are not sure how. Our pacman translation policy is outlined here. The important sections for translators are the introduction and up to (and including) pre-release updates. http://www.archlinux.org/pacman/translation-help.html As stated in the above document, PO files have been made available to translate: http://code.toofishes.net/pacman/po_files/ I would like to get the release out within the next 7 days, so the sooner the better for the translations. Languages we currently have: cs_CZ: Handled by Vojtěch Gondžala <vogo@seznam.cz> de: handled by Matthias Gorissen <matthias@archlinux.de> en_GB: Handled by Jeff Bailes <thepizzaking@gmail.com> es: status unknown, no current translator fr: Handled by Chantry Xavier <shiningxc@gmail.com> hu: Handled by Nagy Gabor <ngaba@bibl.u-szeged.hu> it: Handled by Giovanni Scafora <linuxmania@gmail.com> pl_PL: Work in progress by Mateusz Jedrasik <m.jedrasik@gmail.com> pt_BR: status unknown, no current translator ru_RU: status unknown, no current translator If you wish to help translate, but your language is already listed as handled by someone, please contact them at the above addresses. If the language is listed as "no current translator", then please reply to ALL on this message stating you are doing the translation so we do not have duplicated effort (although you are more than welcome to work in teams). Once you have updated or completed a translation, simply tar and gzip the files up and send them back to pacman-dev@archlinux.org with a [translation] prefix in the message. For those that are used to the old method of updating translations (GIT patches), those are still acceptable as well. Please prefix the patch with "translation:" so it can be picked out easily. HOWEVER, if at all possible, please do not needlessly update the line numbers in the code! It makes it much easier to see which translations have been changed and updated if line number changes are not 90% of the patch. The "translations" branch is located in my GIT repo; one of the following things will probably be of help. http://code.toofishes.net/gitweb.cgi?p=pacman.git;a=shortlog;h=translations git remote add dan http://code.toofishes.net/gitprojects/pacman.git git checkout -b translations dan/translations -Dan
The original es-translator still seemed available when I talked to him a week ago. He doesn't read the lists regularly, and he probably would not mind if I remind him again. In the meantime, I did some work on that on my own, but I focussed on simple syntax errors and fuzzy entries. The more substantial untranslated parts should be left to native speakers. To avoid duplicate efforts, new translators may wish to checkout directly from my own public repo: http://git.archlinux.de/~matthias/pacman.git Dan, can you pull that directly, or do you need/prefer a patch? Best regards, Matt
Dan McGee wrote:
We've weeded out a handful of bugs and issues since 3.1.0, so it is time to call for a string freeze for 3.1.1.
Obviously, I only notice string problems AFTER the string freeze, because I look at the french translation only now. There is a "--" string coming from makepkg.sh.in , line 1184. And in pacman/callback.c , line 288 : "Replacing %s with %s/%s\n ." There is a dot after the newline.
Xavier wrote:
Dan McGee wrote:
We've weeded out a handful of bugs and issues since 3.1.0, so it is time to call for a string freeze for 3.1.1.
Obviously, I only notice string problems AFTER the string freeze, because I look at the french translation only now.
There is a "--" string coming from makepkg.sh.in , line 1184. And in pacman/callback.c , line 288 : "Replacing %s with %s/%s\n ."
There is a dot after the newline.
Anyway, that shouldn't be a big problem. The -- string can be translated to --, and the second message should be pretty rare (a replacement needs to occur during a -Su --noconfirm operation).
On Jan 15, 2008 6:04 AM, Xavier <shiningxc@gmail.com> wrote:
Xavier wrote:
Dan McGee wrote:
We've weeded out a handful of bugs and issues since 3.1.0, so it is time to call for a string freeze for 3.1.1.
Obviously, I only notice string problems AFTER the string freeze, because I look at the french translation only now.
There is a "--" string coming from makepkg.sh.in , line 1184. And in pacman/callback.c , line 288 : "Replacing %s with %s/%s\n ."
There is a dot after the newline.
Anyway, that shouldn't be a big problem. The -- string can be translated to --, and the second message should be pretty rare (a replacement needs to occur during a -Su --noconfirm operation).
Cool. It looks like that -- is from a misinterpretation of the gettext msg* program, which is no big deal (but did the other message make it in there?). It doesn't look like it did, unfortunately. Keep that other message in mind and we can do one of two things- I'll sed all the translations right before we release (probably best) or I'll patch it immediately following 3.1.1. -Dan
Dan McGee wrote:
Cool. It looks like that -- is from a misinterpretation of the gettext msg* program, which is no big deal (but did the other message make it in there?). It doesn't look like it did, unfortunately.
It did make it, so everything is alright on this side.
Keep that other message in mind and we can do one of two things- I'll sed all the translations right before we release (probably best) or I'll patch it immediately following 3.1.1.
Since I believe this string is quite rare, I'm fine with either way.
I'm João Felipe Santos <jfsantos@archlinux-br.org>, and i'm translating pacman to pt_BR. -jfsantos
participants (4)
-
Dan McGee
-
João Felipe Santos
-
Matthias Gorissen
-
Xavier