Character encoding issues after updating

RT Users
1

Hi,

After having successfully implemented version 3.6.4 in our organization, I have started an attempt at updating the installation to 3.8.1. It seems to be successful, however I have one show stopping issue. When I look at the tickets the Turkish characters we use have become corrupted. Here is what I do in terms of upgrading the database:

  • I copy the database to a new one using phpmyadmin (I can run the new version now! even without the db update, but with the character issues)
  • I run the update script over the copy (from the temporary directory that holds the ‘upgrade’ directory)
  • I am using the copy for the new installation as I have to keep the original database in one piece, it is live…

When I look at the fields in the database I see no differences between the two (‘fotokopi(C500) sarı ve mavi toner bitik!’ remains ‘fotokopi(C500) sarı ve mavi toner bitik!’ - apparently we need blue and yellow toner for a printer ;-), so that makes me think something changed somewhere else. 3.6.4 shows this ticket as it should, with a dotless i, 3.8.1 gives ‘ı’

When I play with the character encoding using my browser I am not able to get things to show up right.

Any suggestions would be great.

– Jac
Istanbul, Turkey

2

Hi,

After having successfully implemented version 3.6.4 in our organization, I
have started an attempt at updating the installation to 3.8.1. It seems to
be successful, however I have one show stopping issue. When I look at the
tickets the Turkish characters we use have become corrupted. Here is what
I do in terms of upgrading the database:

There’s an upgrade script one needs to run, documented in the UPGRADING
file. It’s badly named (etc/schema.mysql-4.0-4.1.pl), but you need it.

3

Thanks heaps! I read the README and UPGRADING instructions but somehow missed UPGRADING.mysql. Sorry for bothering you! Keep up the good work! – JacFrom: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Mon 10/20/2008 3:46 PM
To: Jac Gubbels GUBBELS
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] character encoding issues after updating

Hi,

After having successfully implemented version 3.6.4 in our organization, I
have started an attempt at updating the installation to 3.8.1. It seems to
be successful, however I have one show stopping issue. When I look at the
tickets the Turkish characters we use have become corrupted. Here is what
I do in terms of upgrading the database:

There’s an upgrade script one needs to run, documented in the UPGRADING
file. It’s badly named (etc/schema.mysql-4.0-4.1.pl), but you need it.

  • I copy the database to a new one using phpmyadmin (I can run the new
    version now! even without the db update, but with the character issues)
  • I run the update script over the copy (from the temporary directory that
    holds the ‘upgrade’ directory)
  • I am using the copy for the new installation as I have to keep the
    original database in one piece, it is live…

When I look at the fields in the database I see no differences between the
two (‘fotokopi(C500) sarı ve mavi toner bitik!’ remains ‘fotokopi(C500)
sarı ve mavi toner bitik!’ - apparently we need blue and yellow toner
for a printer ;-), so that makes me think something changed somewhere
else. 3.6.4 shows this ticket as it should, with a dotless i, 3.8.1 gives
‘ı’

When I play with the character encoding using my browser I am not able to
get things to show up right.

Any suggestions would be great.

– Jac
Istanbul, Turkey

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com