[pacman-dev] [translation] pt-br translation for 3.2.1
And here it goes the pt-br translation for 3.2.1. -- Hugo
On Sun, Aug 24, 2008 at 4:27 PM, Hugo Doria <hugodoria@gmail.com> wrote:
And here it goes the pt-br translation for 3.2.1.
There are some strange changes, many colons that are supposed to be aligned were changed to be misaligned : #, c-format msgid "Version :" -msgstr "Versão :" +msgstr "Versão :" #, c-format msgid "URL :" -msgstr "URL :" +msgstr "URL :" It does not look that obvious in the mail, but when looking at the diff in my terminal with a monospace font, it leaves no doubt.
Hi Xavier, The problem is: When i use the old colons (that should be aligned) the output appears wrong. Take a look here: http://paste.archlinux-br.org/305 -- Hugo
On Sun, Aug 24, 2008 at 10:37 PM, Hugo Doria <hugodoria@gmail.com> wrote:
Hi Xavier,
The problem is: When i use the old colons (that should be aligned) the output appears wrong. Take a look here:
Sorry, I was wrong. The old colons were indeed not aligned either. But nor are the new ones. Just align them all in the .po file, as they should be. If pacman then has a problem to display unicode strings, this is a bug that should be fixed, not worked around. But everything should have been fixed during 3.1.x developments, so it really should work now.
On Sun, Aug 24, 2008 at 3:54 PM, Xavier <shiningxc@gmail.com> wrote:
On Sun, Aug 24, 2008 at 10:37 PM, Hugo Doria <hugodoria@gmail.com> wrote:
Hi Xavier,
The problem is: When i use the old colons (that should be aligned) the output appears wrong. Take a look here:
Sorry, I was wrong. The old colons were indeed not aligned either. But nor are the new ones. Just align them all in the .po file, as they should be. If pacman then has a problem to display unicode strings, this is a bug that should be fixed, not worked around. But everything should have been fixed during 3.1.x developments, so it really should work now.
So what is the plan here? In the version that just got pushed to the translation branch, they are all aligned crazily. I'm 100% with Xavier here- if there are alignment issues, we really need to address them in the code and not in the translated strings themselves. -Dan
On Mon, Aug 25, 2008 at 4:38 AM, Dan McGee <dpmcgee@gmail.com> wrote:
So what is the plan here? In the version that just got pushed to the translation branch, they are all aligned crazily. I'm 100% with Xavier here- if there are alignment issues, we really need to address them in the code and not in the translated strings themselves.
Now I have only one libalpm message missing from Turkish translation. If I get it today, and no pt-br update this evening, then I will fix the alignment issues myself. So 12 hours from now, everything should be fine and ready.
On Mon, Aug 25, 2008 at 8:38 AM, Xavier <shiningxc@gmail.com> wrote:
On Mon, Aug 25, 2008 at 4:38 AM, Dan McGee <dpmcgee@gmail.com> wrote:
So what is the plan here? In the version that just got pushed to the translation branch, they are all aligned crazily. I'm 100% with Xavier here- if there are alignment issues, we really need to address them in the code and not in the translated strings themselves.
Now I have only one libalpm message missing from Turkish translation. If I get it today, and no pt-br update this evening, then I will fix the alignment issues myself. So 12 hours from now, everything should be fine and ready.
Just for your information, I have the Turkish translation fix now.
On Mon, Aug 25, 2008 at 8:38 AM, Xavier <shiningxc@gmail.com> wrote:
On Mon, Aug 25, 2008 at 4:38 AM, Dan McGee <dpmcgee@gmail.com> wrote:
So what is the plan here? In the version that just got pushed to the translation branch, they are all aligned crazily. I'm 100% with Xavier here- if there are alignment issues, we really need to address them in the code and not in the translated strings themselves.
Now I have only one libalpm message missing from Turkish translation. If I get it today, and no pt-br update this evening, then I will fix the alignment issues myself. So 12 hours from now, everything should be fine and ready.
Ok so I fixed the issue myself, it actually took me less than 1 minute. As I expected, the output is perfectly fine when the po file itself is aligned properly.
participants (3)
-
Dan McGee
-
Hugo Doria
-
Xavier