CMS Made Simple Forums

wientanz wrote: Now the tag works, but what I don't understand is why the umlaute like äüö and other characters like ß,é,è and the likes are displayed wrong. You'll find it here.

You must set the encoding of your template to ISO-8859-1 to show the umlauts right.

THX cyberman, you're my hero. Will try it this Sunday.

Won't work, still have the same troubles. My HEAD ist here:

Hmm  ...

Please try to set the wished encoding once again in "Administration - Layout - Templates - Template bearbeiten". There you will find an option "Kodierung".

Surprise, surprise, it worked! But only partially...

The content from the script is displayed correct. All the umlaute and other special characters are there. But what's wrong now are the umlaute in the CSSMenu. Now THEY are displayed incorrect:

http://www.bugovsky.com/index.php?page=Ballkalender

Ah yes, the breadcrumbs also display them wrong. Strange... I eliminated the head-tag I inserted manually before and just chose the right encoding as cyberman suggested. Don't wonder. The content of other articles should be correct, because they are already HTML entities since they were imported from Dreamweaver source.

*sigh*

wientanz wrote: Surprise, surprise, it worked! But only partially...

Wow, what have you doin' on this page - 1282 (!) xhtml warnings ...

The content from the script is displayed correct. All the umlaute and other special characters are there. But what's wrong now are the umlaute in the CSSMenu.

Don't know if I can call this a bug. The admin section has utf-8 encoding by default so menu data will written with this encoding. But if your menu entries has umlauts and your homepage is displayed with another encoding it's showing wrong.

Now you have two options. To the first you can correct the database manually (table cms_content). The other option is setting the admin encoding to iso-8859-1. It works cause I had translate the most of umlauts with entities (ä instead ä).

Don't forget "Clear cache"  .

I think I'll do a database dump from my DB (where all the Balltermine are stored), do a quick "Replace all ä with ä" and the llikes and switch back to utf... That's better than to change the whole system's encoding just for 1 article...

And the warnings? Weeeeell, warnings are no errors, right? Seriously, I have no idea. The DB script was written by somebody else, who left us, so I can't just ask him what he did. And the script itself is only part of a 10+ scripts system. Nothing big, but too much just to read through for me now.

wientanz wrote: That's better than to change the whole system's encoding just for 1 article...

You are the boss  ...

Utf8 IS my preferred encoding. The content from my script is not older than the 0.11, it was just created using Excel, saving to .csv-format and then uploading to the database. The person who entered the data didn't know anything about ASCII character sets or Unicode and didn't think about it. I know see the reason to adapt the data to ensure CMSMS compliance, but thanks for your answer nethertheless Patricia. Any input is appreciated

Sorry for not making sense. Too much studying, too little sleep. In short: I figured that out from the above posts from cyberman and my trials and errors.

Good night now....

haven't got it working yet, but know how to deal with it. Thanks to all of you out there!