Escaping of special characters

[Rexxer]

Hi,
I just upgraded to Version 0.9-beta3.

With this Version I see a bug where the WYSIWYG editor doesn't escape Umlaut-characters. Here I reproduced the bug on supersized.org

If it's a known bug (or even fixed in SVN already), you can ignore this post.

[garvinhicking]

What do you mean? Umlauts don't need to be escaped -- the HTTP headers set the content type, so you can use native umlauts.

Entities like ä are sooooo 90'ies

Regards,
Garvin

[Rexxer]

What do you mean? Umlauts don't need to be escaped -- the HTTP headers set the content type, so you can use native umlauts.

Entities like ä are sooooo 90'ies

Regards,
Garvin

Hmm. Can anyone tell that to my local Server(Debian c't-edition)? It seems to drop Umlaut characters. Well, maybe it's just sooo 90'ies, too?

[garvinhicking]

Which browser are you using? I can access your supersized demo just fine and everything works properly there!

I have no experience about how the Debian c't edition is powered, but the generated HTML is all valid and show work even in Netscape 4.0...

Using HTML entities, when the ISO-8859-1 charset is declared and the document is XHTML, this will even result in the page not getting validated, BTW.

Regards,
Garvin

[Rexxer]

Which browser are you using? I can access your supersized demo just fine and everything works properly there!

That one seems to work here, too. When I access my 'local' s9y it just seems to loose the umlaut characters. I'm running Firefox 1.0.7 on Linux. But the same happens using IE 6.0 on Windows. I guess I'll have to do somethint to the configuration of my Apache then...

I have no experience about how the Debian c't edition is powered, but the generated HTML is all valid and show work even in Netscape 4.0...

Using HTML entities, when the ISO-8859-1 charset is declared and the document is XHTML, this will even result in the page not getting validated, BTW.

Regards,
Garvin

I guess it's the codepage that's not declared correctly here. As I said, it's probably something in my Apache's configuration.

BTW: keep up the great work.

[garvinhicking]

Rexxer,

you are probably right. It might be that Apache ovverrides the HTTP headers with its own and messing with the codepage. Maybe the c't guys can be of help there, they are surely quite experienced when it comes to that

BTW: keep up the great work.

Thanks a lot!

Best regards,
Garvin