Re: [Mantisbt-lang] update brazilian portuguese (HOLD ON!)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi All,

I really didnt knew that we had a official translation team, then i did=
 what I did ...

I Use IE 6.0 dont think that its an ancient, or maybe is ... 

BTW, if i cant translate so, why i=B4m on this list ?

I ask by now that i get removed from here.

tks
Felipe Tonioli

*********** REPLY SEPARATOR  ***********

On 27/09/2004 at 19:18 Juliano Ravasi Ferraz wrote:

>Felipe Tonioli wrote:
>> Hi All,
>
>Hi Felipe,
>
>> I've made a few changes to localization for portuguese.
>
>I'm currently maintaining the Brazilian Portuguese translation since 
>June, because I moved to Mantis 0.18.3 and found the translation very 
>unmaintened and unusable (wrong translations, broken php code, lots of 
>missing text and so on). By the way, I made it from the ground up, 
>without even looking at the old file.
>
>I've taken this responsability myself to avoid having Mantis again like 
>it was in 0.18.3, and this is how it was working since I joined the 
>translation team. I provided updated pt-br translations in time, without 
>any delay, before 0.19.0a1, 0.19.0a2, 0.19.0rc1 and 0.19.0.
>
>You could have asked me first, since I'm really present as a maintainer 
>of this translation.
>
>> The most important is to change special chars from they instead to=
 escape
>> sequences. Its will turn the localization more usable, because, in some
>> cases, like mine, I got strange things into screen.
>
>Sorry but, with all respect, I really disagree with this. Escape 
>sequences are already deprecated for some years ago, and it isn't even 
>recomended in the latest HTML 4.0 and XHTML 1.0 (this is the output that 
>Mantis generates) standards. These escape sequences were invented while 
>the HTTP protocol was used over the ancient 7 bit protocols (TCP/IP is 8 
>bit) and to support just Latin-American languages (although it was 
>extended with unicode thereafter).
>
>They were deprecated since (1) TCP/IP supports 8 bit transmissions 
>without any special encoding, (2) the world is not limited to just 
>America and Latin-America, (3) it is not feasible to create escape 
>sequences for every CJK character (although you can write the unicode 
>value of the character, but this increases the overall text size by a 
>factor of 2 or 3) and (4) it is painfully hard to read and write such 
>sequences in a text editor.
>
>The first string in the translation file ($s_charset =3D 'iso-8859-1') is 
>the encoding used to generate a proper Content-Type for every page 
>generated, so, there is no need to escape every 8bit character while we 
>use this encoding. BTW, the translation you just sent is adequate for a 
>'us-ascii' encoding.
>
>If you look at the other translation files, you'll see that they use 
>extended characters without any guilt. If you "get strange things into 
>screen", then you should be using a really ancient browser, that is 
>unable correctly display any major brazilian site (including 
>www.google.com.br).
>
>Other problems:
>   1. you escaped strings that are used to send e-mail messages (that 
>are not in HTML, and so, don't have escape sequences);
>   2. although you can escape the whole structure of the Mantis site, 
>Mantis doesn't escape text written in issue descriptions or bugnotes, a 
>PHP htmlentities(..., 'ISO-8859-1') call won't escape those characters 
>since there is no need for this;
>   3. there are already plans to support UTF-8 (issue 4084), which makes 
>your change pointless, since all browsers that support UTF-8 also 
>supports ISO-8859 and many other commonly used encodings.
>
>For all these reasons, I can't see any point on this change. And sorry, 
>I won't support it if it was to be "Opera&ccedil;&atilde;o" where 
>"Opera=E7=E3o" is much more readable, is easier to maintain, and is 
>supported by every browser less than 7 years old.
>
>> It was made in the last file downloaded, so i thing that everything
>going to
>> work fine.
>
>Which was compatible with revision 1.206 of strings_english.txt. Here, 
>in my computer, I have the same file that I last updated today morning, 
>and is compatible with revision 1.213 (I don't send the translated file 
>for every change since there is no use to overload the Mantis 
>developers). If you'd asked me, I could have sent you this one (although 
>there are still differences in our thinkings about the above things).
>
>No offenses, best regards,
>
>-- 
>       _______________________
>  ____/ Juliano Ravasi Ferraz \_______________________________
>|    =AB contact#juliano=B7info =BB=AB http://www.juliano.info/ =BB    |
>|  GnuPG: 5105 46CC B2B7 F0CD 5F47 E740 72CA 54F4 DF37 9E96  |
>
>Having a home is much better than having just documents and settings.
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
>Project Admins to receive an Apple iPod Mini FREE for your judgement on
>who ports your project to Linux PPC the best. Sponsored by IBM.
>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
>_______________________________________________
>Mantisbt-lang mailing list
>Man...@li...
>https://lists.sourceforge.net/lists/listinfo/mantisbt-lang