Hi,
I'm using RT 2.1.48 and I access it in my own language (as
expected witch is brazilian portuguese) but I also noticed some problems in
some caracters specially on combined caracters like “A acute” (á). all
accented caracters have the same problems. I tried to change directly at
file “/opt/rt3/lib/RT/I18N/pt_br.po” but I didn’t have success. How can I
make those caracters to be shown as expected? Is it fixed on RT 2.1.50?
I hope someone can help me.
bye.
Rafael Máximo
“Rafael” == Rafael Maximo maximo@maximo.br.fm writes:
Rafael> Hi, I’m using RT 2.1.48 and I access it in my own language
Rafael> (as expected witch is brazilian portuguese) but I also
Rafael> noticed some problems in some caracters specially on
Rafael> combined caracters like “A acute” (á). all accented
Rafael> caracters have the same problems. I tried to change directly
Rafael> at file “/opt/rt3/lib/RT/I18N/pt_br.po” but I didn’t have
Rafael> success. How can I make those caracters to be shown as
Rafael> expected? Is it fixed on RT 2.1.50?
I contributed the Brazilian Portuguese translation but I’m not keeping
pace with RT development I’m sad to say. I just downloaded the last
version and compared the pt_bt.po file with the fr.po and they seem to
agree in the encoding of accented characters (UTF-8). Could you try
the French or the Spanish translation to see if the display problem
persists?
BTW, I’ve just counted 346 non-translated entries in it and I’ll try
to translate them in the next few days. I’d appreciate if you send
comments and criticisms about the translation proper directly to me.
Até,
Gustavo.
Gustavo,
The French version seems to be working but i tried with Spanish
version and i got the same problem as the problem I reported.
With this information i tried to see the diferencies between the
French e Portuguese version and when i removed lines 3 and 4 from the file
pt_br.po:
—lines removed from pt_br.po—
msgid “”
msgstr “”
and after that the Portuguese version worked without problems. It’s very
interesting because i thought those two lines were required.
I think you did a very good job translating RT to Brazilian
Portuguese.
bye.
At 08:41 AM 28/11/2002, you wrote:
“Rafael” == Rafael Maximo maximo@maximo.br.fm writes:
Rafael> Hi, I’m using RT 2.1.48 and I access it in my own language
Rafael> (as expected witch is brazilian portuguese) but I also
Rafael> noticed some problems in some caracters specially on
Rafael> combined caracters like “A acute” (á). all accented
Rafael> caracters have the same problems. I tried to change directly
Rafael> at file “/opt/rt3/lib/RT/I18N/pt_br.po” but I didn’t have
Rafael> success. How can I make those caracters to be shown as
Rafael> expected? Is it fixed on RT 2.1.50?I contributed the Brazilian Portuguese translation but I’m not keeping
pace with RT development I’m sad to say. I just downloaded the last
version and compared the pt_bt.po file with the fr.po and they seem to
agree in the encoding of accented characters (UTF-8). Could you try
the French or the Spanish translation to see if the display problem
persists?BTW, I’ve just counted 346 non-translated entries in it and I’ll try
to translate them in the next few days. I’d appreciate if you send
comments and criticisms about the translation proper directly to me.Até,
Gustavo.
Rafael Máximo
“Rafael” == Rafael Maximo maximo@maximo.br.fm writes:
Rafael> Gustavo, The French version seems to be working but i tried
Rafael> with Spanish version and i got the same problem as the
Rafael> problem I reported.
Rafael> With this information i tried to see the
Rafael> diferencies between the French e Portuguese version and when
Rafael> i removed lines 3 and 4 from the file pt_br.po:
Rafael> —lines removed from pt_br.po—
Rafael> msgid “”
Rafael> msgstr “”
Rafael> and after that the Portuguese version worked without
Rafael> problems. It’s very interesting because i thought those two
Rafael> lines were required.
I got quickly over the gettext documentation and couldn’t find why
these lines should be required before the file’s initial headers. I
checked the version I sent in May and found that it already had them,
but I can’t remember having put them there on purpose.
I guess their presence hides the initial headers which determine the
character encoding of the file (UTF-8). If this is correct these
lines shouldn’t really be there.
Does anyone in this list know better?
Rafael> I think you did a very good job translating RT to
Rafael> Brazilian Portuguese.
Thanks. But I’m sure it could use some improvements. 
Gustavo.
I got quickly over the gettext documentation and couldn’t find why
these lines should be required before the file’s initial headers. I
checked the version I sent in May and found that it already had them,
but I can’t remember having put them there on purpose.I guess their presence hides the initial headers which determine the
character encoding of the file (UTF-8). If this is correct these
lines shouldn’t really be there.Does anyone in this list know better?
They’re required for locale::maketext::lexicon to do the right thing.
I know that older versions of locale::maketext::lexicon had issues with
extra newlines in the message catalogs. Make sure you’re running the
most recent version.
»|« Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
At 03:10 PM 28/11/2002, you wrote:
I got quickly over the gettext documentation and couldn’t find why
these lines should be required before the file’s initial headers. I
checked the version I sent in May and found that it already had them,
but I can’t remember having put them there on purpose.I guess their presence hides the initial headers which determine the
character encoding of the file (UTF-8). If this is correct these
lines shouldn’t really be there.Does anyone in this list know better?
They’re required for locale::maketext::lexicon to do the right thing.
I know that older versions of locale::maketext::lexicon had issues with
extra newlines in the message catalogs. Make sure you’re running the
most recent version.
I got the new version of Locale::Maketext::Lexicon but i still got the same
problem, and now i have another one. When someone send an e-mail to RT and
if the email has accented caracters, they will not be shown correctly on RT
neither on the replied email.
Any suggestions?
–
»|« Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Rafael Máximo