Umlaute ÄÖÜ problem - with UTF-8 !! Umlaute ÄÖÜ problem - with UTF-8 !!
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Umlaute ÄÖÜ problem - with UTF-8 !!

Started by seppi, December 29, 2005, 04:14:01 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

seppi

I cant get the german umlaute working. I installed the 1.4.2 version and diddn´t change anything.

What should i do to get it work. ( I searched for the problem but the change to utf-8 doesn´t help me)

if i change firefox 1.5 language from westlich-iso8859-1 to utf-8 it works great. But i can´t require this to every user whos surfing by.

Nibbler

Update to 1.4.3 and post a link to your gallery.

Cyclist

#2
I have a similar problem but with v1.43: In the database tables all content shows up fine but on the website on my test server (not online yet) all special characters are displayed wrong. I use utf-8 now. The characters from the language files are displayed correctly but those within the database tables not. collation is utf8_unicode_ci. Is that wrong? It's a new installation.

Some of the wrong characters:

Ä turns ă
È turns ɢ class= or sometimes just ɢ
è turns 颠class= or sometimes just 颠
Ü turns ?
(Internet Explorer)

with firefox other wrong characters are displayed.


Joachim Müller

as far as I remember, you have performed an upgrade, so your old content is still in latin-encoded. Run the charsetmgr if possible. If you can't, you'll have to convert your content manually.

Cyclist

#4
No, I didn't perform an upgrade. I started with cpg with v1.42.

I have two test installations on my test server: one using the old ISO and a new one using utf-8.

First I tried to convert the iso into utf-8 but this was a bad idea because then all characters in the database are displayed wrong althiugh the frontend looks fine.

So I decided to run a fresh install based on utf-8, but with utf-8 there is the problem I described. ISO works better but keyword search and special characters are a problem when searching.

Right now I have no idea what solution is better because both cause big problems.