[pacman-dev] Deadline for translations?
Hi, are there any deadlines for translations? I think it would be usefull to include our translation into the first public test version. (is it still planed for 14.2?) Pierre
On 2/11/07, Pierre Schmitz <pierre@archlinux.de> wrote:
are there any deadlines for translations? I think it would be usefull to include our translation into the first public test version. (is it still planed for 14.2?)
We didn't set any hard deadlines, but as soon as the translation is done and sent to the ML, we can check it in and it will be included in any subsequent releases. If you could get it in before the 14th, that would probably be ideal. Note to any other translators reading this- if you can't make a deadline, no worries. The biggest deadline that really needs meeting is when it goes into [current]. -Dan
Am Sonntag, 11. Februar 2007 20:13:14 schrieb Dan McGee:
We didn't set any hard deadlines, but as soon as the translation is done and sent to the ML, we can check it in and it will be included in any subsequent releases. If you could get it in before the 14th, that would probably be ideal.
OK, I have set our internal deadline to 13.2. 22:00 (Europe/Berlin). After this I`ll send a copy of the translation to this ml. This way it should be possible to get a more "solid" translation for the release tu [current].
On 2/11/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Sonntag, 11. Februar 2007 20:13:14 schrieb Dan McGee:
We didn't set any hard deadlines, but as soon as the translation is done and sent to the ML, we can check it in and it will be included in any subsequent releases. If you could get it in before the 14th, that would probably be ideal.
OK, I have set our internal deadline to 13.2. 22:00 (Europe/Berlin). After this I`ll send a copy of the translation to this ml. This way it should be possible to get a more "solid" translation for the release tu [current].
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge. -Dan
2007/2/11, Dan McGee <dpmcgee@gmail.com>:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
I hope to send italian .po files within 2 days. I waited for your OK to translate man pages and docs. -- Giovanni Scafora Arch Linux Trusted User & Package Maintainer (voidnull) http://www.archlinux.org linuxmania@gmail.com
On 2/11/07, Giovanni Scafora <linuxmania@gmail.com> wrote:
2007/2/11, Dan McGee <dpmcgee@gmail.com>:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
I hope to send italian .po files within 2 days. I waited for your OK to translate man pages and docs.
Quick comment on this- I need to do some more research, but I'd love to move the manpages to a different (hopefully easier) format than straight groff macros like they are now. This obviously isn't going to happen soon, so if you feel like a lot of people will benefit from a translation, then go ahead, but if we do go ahead with a migration to something else, it may make more sense to wait on the translation. By the way, is anyone working on updating the French translation (po files)? I know we have one and I don't remember anyone on this list saying they could update it. If anyone wants to step forward and do that, it would be appreciated. -Dan
Am Sonntag, 11. Februar 2007 23:24:20 schrieb Dan McGee:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
How should I synchronize to the latest English translation? -- http://www.archlinux.de
2007/2/12, Pierre Schmitz <pierre@archlinux.de>:
Am Sonntag, 11. Februar 2007 23:24:20 schrieb Dan McGee:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
How should I synchronize to the latest English translation?
I think you are looking for msgmerge (in the gettext package), as easy to use as: $> msgmerge it.po pacman.pot > it.new.po -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User
Am Montag, 12. Februar 2007 16:06:17 schrieb Alessio 'mOLOk' Bolognino:
2007/2/12, Pierre Schmitz <pierre@archlinux.de>:
Am Sonntag, 11. Februar 2007 23:24:20 schrieb Dan McGee:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
How should I synchronize to the latest English translation?
I think you are looking for msgmerge (in the gettext package), as easy to use as: $> msgmerge it.po pacman.pot > it.new.po
I think I got it with "make update-po" (as described in "translation-help"). The result wasn`t allways optimal but a good start. Another question: What about all the blanks within the strings? Are they used for proper indention? For example "Version :" What should we do if the translated text is longer than the English one (including spaces)? Pierre -- http://www.archlinux.de
2007/2/12, Pierre Schmitz <pierre@archlinux.de>:
Am Montag, 12. Februar 2007 16:06:17 schrieb Alessio 'mOLOk' Bolognino:
2007/2/12, Pierre Schmitz <pierre@archlinux.de>:
Am Sonntag, 11. Februar 2007 23:24:20 schrieb Dan McGee:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
How should I synchronize to the latest English translation?
I think you are looking for msgmerge (in the gettext package), as easy to use as: $> msgmerge it.po pacman.pot > it.new.po
I think I got it with "make update-po" (as described in "translation-help"). The result wasn`t allways optimal but a good start.
Another question: What about all the blanks within the strings? Are they used for proper indention? For example "Version :" What should we do if the translated text is longer than the English one (including spaces)?
I think that the best thing is to keep aligned the messages where is needed (e.g pacman -Qi ) and keep the lines length < 80 chars (that's what we do in Archlinux Italia) -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User
On 2/12/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Montag, 12. Februar 2007 16:06:17 schrieb Alessio 'mOLOk' Bolognino:
2007/2/12, Pierre Schmitz <pierre@archlinux.de>:
Am Sonntag, 11. Februar 2007 23:24:20 schrieb Dan McGee:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
How should I synchronize to the latest English translation?
I think you are looking for msgmerge (in the gettext package), as easy to use as: $> msgmerge it.po pacman.pot > it.new.po
I think I got it with "make update-po" (as described in "translation-help"). The result wasn`t allways optimal but a good start.
This seems to be the best way I know of, because you need to update the .pot file as well before you can do a merge. I will try to put some updated pot files soon into CVS, but you can always take this step on your own.
Another question: What about all the blanks within the strings? Are they used for proper indention? For example "Version :" What should we do if the translated text is longer than the English one (including spaces)?
Yes, they are usually for proper indentation and spacing. Sometimes seeing them in the context of the code may be helpful, note that their positions are listed in the po files. The spaces in the instance you mentioned above are not crucial, the biggest idea is simply making sure all of those labels are the same length. -Dan
On 2/12/07, Dan McGee <dpmcgee@gmail.com> wrote:
On 2/12/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Montag, 12. Februar 2007 16:06:17 schrieb Alessio 'mOLOk' Bolognino:
2007/2/12, Pierre Schmitz <pierre@archlinux.de>:
Am Sonntag, 11. Februar 2007 23:24:20 schrieb Dan McGee:
That would be great. Keep in mind that having a good start to the translation helps a lot, obviously messages will change but the translation tools rectify that. There have been a few minor string changes since we last updated the po files, but nothing huge.
How should I synchronize to the latest English translation?
I think you are looking for msgmerge (in the gettext package), as easy to use as: $> msgmerge it.po pacman.pot > it.new.po
I think I got it with "make update-po" (as described in "translation-help"). The result wasn`t allways optimal but a good start.
This seems to be the best way I know of, because you need to update the .pot file as well before you can do a merge. I will try to put some updated pot files soon into CVS, but you can always take this step on your own.
Just discovered this- "make libalpm.pot-update" works to just update the pot file. This can then be followed by a "make it.po-update" or any other language to update the respective po file.
Another question: What about all the blanks within the strings? Are they used for proper indention? For example "Version :" What should we do if the translated text is longer than the English one (including spaces)?
Yes, they are usually for proper indentation and spacing. Sometimes seeing them in the context of the code may be helpful, note that their positions are listed in the po files. The spaces in the instance you mentioned above are not crucial, the biggest idea is simply making sure all of those labels are the same length.
-Dan
2007/2/11, Pierre Schmitz <pierre@archlinux.de>:
OK, I have set our internal deadline to 13.2. 22:00 (Europe/Berlin). After this I`ll send a copy of the translation to this ml. This way it should be possible to get a more "solid" translation for the release tu [current].
OK, me too. I`ll send a copy of the translation to this ml 13-2-2007 22:00 (Europe/Rome). At the moment, I got 2 files: pacman_it.po 208 messages libalpm_it.po 291 messages -- Giovanni Scafora Arch Linux Trusted User & Package Maintainer (voidnull) http://www.archlinux.org linuxmania@gmail.com
participants (4)
-
Alessio 'mOLOk' Bolognino
-
Dan McGee
-
Giovanni Scafora
-
Pierre Schmitz