[pacman-dev] String Freeze for 3.0 release
If you don't look at the commit messages from CVS, I'll post this again here: * Hopefully the LAST big update of the language files before release. Translators and developers should count this as the string freeze unless something REALLY essential comes up. Send in patches to these translations when you get a chance (and patches are appreciated, as they are much easier to deal with). Aaron and I will not make any non-essential changes to strings from here until release date, so a final patch on all of the translations would be appreciated (taken against the latest translation checkins). Anyone out there want to update the French translation? We (and I'm sure the French community) would appreciate it. -Dan
2007/3/4, Dan McGee
If you don't look at the commit messages from CVS, I'll post this again here:
* Hopefully the LAST big update of the language files before release. Translators and developers should count this as the string freeze unless something REALLY essential comes up. Send in patches to these translations when you get a chance (and patches are appreciated, as they are much easier to deal with).
Hi Dan, I noticed that a new message has changed but I don't know if this is really essential to patch lib/libalpm/po/it.po. I refer to the change: msgid "sha1(%s) = %s" to msgid "md5(%s) = %s" Anyway I send you my patch, apply it or ignore it. -- Giovanni Scafora Arch Linux Trusted User (voidnull) http://www.archlinux.org linuxmania@gmail.com
On 3/6/07, Giovanni Scafora
2007/3/4, Dan McGee
: If you don't look at the commit messages from CVS, I'll post this again here:
* Hopefully the LAST big update of the language files before release. Translators and developers should count this as the string freeze unless something REALLY essential comes up. Send in patches to these translations when you get a chance (and patches are appreciated, as they are much easier to deal with).
Hi Dan,
I noticed that a new message has changed but I don't know if this is really essential to patch lib/libalpm/po/it.po. I refer to the change: msgid "sha1(%s) = %s" to msgid "md5(%s) = %s" Anyway I send you my patch, apply it or ignore it.
Translations should be as up-to-date as possible, so they aren't frozen; just the original English strings. Of course, it is really hard for us to not change them as you can see. :) -Dan
On 3/6/07, Dan McGee
msgid "sha1(%s) = %s" to msgid "md5(%s) = %s" Anyway I send you my patch, apply it or ignore it.
Translations should be as up-to-date as possible, so they aren't frozen; just the original English strings. Of course, it is really hard for us to not change them as you can see. :)
Also, these two strings are most likely fine untranslated, as I doubt the "MD5" algorithm has a translation 8)
2007/3/6, Aaron Griffin
Also, these two strings are most likely fine untranslated, as I doubt the "MD5" algorithm has a translation 8)
I have not translated these two strings, I know very well that "MD5" and "SHA1" are most likely fine untranslated. But if you change the original message: msgid "sha1(%s) = %s" to msgid "md5(%s) = %s" I must change msgstr "sha1(%s) = %s" to msgstr "md5(%s) = %s" -- Giovanni Scafora Arch Linux Trusted User (voidnull) http://www.archlinux.org linuxmania@gmail.com
On 3/6/07, Giovanni Scafora
2007/3/6, Aaron Griffin
: Also, these two strings are most likely fine untranslated, as I doubt the "MD5" algorithm has a translation 8)
I have not translated these two strings, I know very well that "MD5" and "SHA1" are most likely fine untranslated. But if you change the original message: msgid "sha1(%s) = %s" to msgid "md5(%s) = %s" I must change msgstr "sha1(%s) = %s" to msgstr "md5(%s) = %s"
For things like this, we'll pull strings like this out of the _() gettext handler in pacman 3.1, so they won't show up at all. But we'll hold off for now. -Dan
Sorry guys, I did break the string freeze today as you may have seen in one of my commits, but it is a small change. If you cant figure out the %2$s notation at first glance with that first string, it may help to look at 'man 3 printf'. Short answer is that allows arguements passed to printf to be used twice without being passed twice. -Dan
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Giovanni Scafora