Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: Character problem after upgrading from 1.3.2 to 1.4.4  (Read 3430 times)

0 Members and 1 Guest are viewing this topic.

javelinworld

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 21
Character problem after upgrading from 1.3.2 to 1.4.4
« on: March 26, 2006, 06:59:20 pm »

I updated from 1.3.2 to 1.4.4 and I have pb with accentuated character like "é" "è" "ê"
The main langage of my gallery is french.
The  URL : http://jerome.chevillat.free.fr/cpg132/index.php

I have "Ath讥s 2004 " instead of "Athènes 2004"... the problem is the same in every langage !!! I always have "Ath讥s 2004 "

Moreover at the bottom of the main page in the last additions files I have something strange : Jarkko KOSKI VĈČļ/span>
vu 35 fois
30 Aout 2005


I do not understand why /span is written :o
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: Character problem after upgrading from 1.3.2 to 1.4.4
« Reply #1 on: March 27, 2006, 07:30:14 am »

has been asked before. You have non-unicode text in your database, but you now use utf-8 (unicode). Either use the charset you used when originally populating the content or use charsetmgr.php to convert your database's textual content to utf-8 (recommended). Please search, this has been asked before. The html tag </span> probably shines through because one of your special chars that shows up garbled equals a >, no need to worry about this particular issue. Fix the garbled special chars first.
Logged

javelinworld

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 21
Re: Character problem after upgrading from 1.3.2 to 1.4.4
« Reply #2 on: March 27, 2006, 10:49:31 pm »

Ok thanks
But charsetmgr.php said that I already use  utf-8...
I tried iconv with the same result...

I have to modify each corrupted word now
Logged
Pages: [1]   Go Up
 

Page created in 0.014 seconds with 15 queries.