[rt-users] RT2 to RT3 migration ... gosh .. HELP !

[Paulo Pinto]

Well...

This is kind'a weird ...

 - If I change the autohandler file to use iso-8859-1 and leave RT_SiteConfig.pm with the UTF-8, stuff from "metadata" (custom fields, etc) is Ok but the tickets are garbled.

- If I change the autohandler file to use UTF-8 and change RT_SiteConfig.pm to use iso-8859-1, tickets are ok ... but the stuff from "metadata" is garbled...

- If I change both to use iso-8859-1, Metadata OK but tickets garbled.

- If I change both to use UTF-8, Metadata garbled but tickets OK ..

Any guesses ? :-/



Cheers,

-----

Try this (an old post):

Well, it looks like I solved the Accents problem:

1) Open your RT_SiteConfig.pm

2) Search for the RT UTF-8 Settings

3) Check if you have this: Set($EmailOutputEncoding , 'iso-8859-1'); 

Probably you have 'UTF-8' now. Change it to iso-8859-1. Restart Apache and

it should work (at least, works here).

-----Original Message-----

From: Paulo Pinto [mailto:pspa at gp.novis.pt]

Sent: Jueves, 02 de Octubre de 2003 01:23 p.m.

To: rt-users at lists.fsck.com

Subject: [rt-users] RT2 to RT3 migration ... gosh .. HELP !



Hi all

Finally (and after the Storable problems have been solved), I'm almost ready

to upgrade my RT2 system to RT3.

The problem lies on the portuguese characters ( ç, ã , õ ... ) 

The original system is a RedHat 7.3 /Mysql 3 ... the new one is a RedHat 9 /

Mysql 4.

Analyzing the database "dump" (made with rt2-to-rt3 package), all the files

in it are ISO-8859 encoded (including the metadata).

It seems that mason is "forcing" the content to be UTF-8 .. so, the

portuguese chars are completely garbled on the web interface ...

Forcing mason to use en_US encoding (editing the autohandler file), it seems

that the data loaded from the "metadata" file diplays OK ... but the ticket

data is garbled (again, ISO-8859 encoding being displayed in UTF-8 ).

Is there a way to work around this ?

TIA

--

Paulo Pinto

Mainroad IT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20031002/ca3a962d/attachment.htm>