Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'The encoding seems fine' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
The encoding seems fine
Authored by: chtito on May 31, '06 08:31:41AM

Actually the encoding seems to be perfectly ok. The problem is only in the http header: you now have to serve your pages in utf-8 instead of iso-8859-1. In php that would be something like: header('Content-Type: text/html; charset=iso-utf-8').



[ Reply to This | # ]
The encoding seems fine
Authored by: chtito on May 31, '06 08:33:48AM
in the previous comment read: header('Content-Type: text/html; charset=utf-8'); of course.

[ Reply to This | # ]
The encoding seems fine
Authored by: robg on May 31, '06 12:12:57PM

That's exactly what it was. It seems somewhere along the line, something switched.

So now I just have a minor cleanup job on some new comments -- thanks!

-rob.



[ Reply to This | # ]
Still problems...
Authored by: aamann on Jun 01, '06 09:57:28AM

Rob,

there still seem to be problems - all apostrophes show up as \' instead as ' only

(for and example, see comments to 10.4: Fix WebDAV under Apache2)



[ Reply to This | # ]
Still problems...
Authored by: robg on Jun 01, '06 09:59:09AM

The comments have issues that I'm trying to figure out -- the data file is identical in both versions of Geeklog, but the slashes show in the new version, not in the old version.

The slashes in the titles in the RSS feed, I'm not sure what to do about that. I've asked the plug-in author to take a look...

-rob.



[ Reply to This | # ]
Still problems...
Authored by: robg on Jun 05, '06 05:30:36AM

OK, the "backslash in older comments before single quotes" problem has now (finally, I hope!) been resolved.

-rob.



[ Reply to This | # ]