Raiders of the Lost Encoding

  • xeophin

    (@xeophin)


    19 years, 4 months ago

    I can’t make any sense of this problem, but maybe someone else here can …
    Head over with Firefox to my blog at http://tapestry.xeophin.net and click on a single post (or a category, will give the same results). What happens (at least whenever I try this) is, that the encoding (utf-8) gets lost, FF switches back to ISO-somewhat and kicks into quirks-mode. As if this wouldn’t be enough, FF displays some oddly displaced characters in the left top corner of the window. Ouch!
    That doesn’t happen neither in Opera or Safari – haven’t tried with IE (Mac), as it will mercilessly crash because of my stylesheet …
    My error-log shows long rows of “Headers already sentâ€?-messages, but obviously this doesn’t seem to break the page much – except in Firefox. Any ideas, where I could continue my bug-hunt?

Viewing 10 replies - 1 through 10 (of 10 total)
  • machine609

    (@machine609)

    19 years, 4 months ago

    Looks fine in IE 6.0

    moshu

    (@moshu)

    19 years, 4 months ago

    Checked in IE 5.5 (Win) and FF, but I couldn’t reproduce any of the errors you’ve mentioned. In both cases the site looks fine.

    Thread Starter xeophin

    (@xeophin)

    19 years, 4 months ago

    Really? Even if you go to a single post, i. e. something like this: http://tapestry.xeophin.net/threads/2004/11/29/wiki-aventurica/ ?
    If it doesn’t happen, that would be extremely odd …

    pericat

    (@pericat)

    19 years, 4 months ago

    xeophin, I don’t have a solution for you, but I did see the behaviour just as you describe it. When I then re-set my browser window to interpret the page as utf-8, the odd characters in the topleft corner went away, and the text of the page returned to normal.
    Are you using the same template to build your main page as the one you use to build your category and individual pages?

    Thread Starter xeophin

    (@xeophin)

    19 years, 4 months ago

    Yes, it’s all done with the index.php. It seems as the information normally sent with the header seems to get lost and Firefox returns to its default encoding (which means that if utf-8 is set as the browser’s default encoding, this probably won’t happen.)

    pericat

    (@pericat)

    19 years, 4 months ago

    All I can attest to is what I see; my site is likewise set to UTF-8 throughout, and I use index.php to handle main, category and individual views alike, yet FF does not switch out charsets on its own, as it does with your site.
    Your site is more complicated in its display, though. You may want to set up a parallel test site as a mirror, and see what you can make of that. Unless someone here has the solution already.

    adsworth

    (@adsworth)

    19 years, 4 months ago

    Hi xeophin,
    I don’t know which version of WP you are using.
    If you’re using an alpha of 1.3 have a look at http://mosquito.wordpress.org/view.php?id=479
    Also read the comments at the end of the bug, there is a little quirk with the MySQL statement.
    Maybe ithelps with 1.2 as well.
    Regards
    adsworth

    Thread Starter xeophin

    (@xeophin)

    19 years, 4 months ago

    I’m using WP 1.2.1, forgot to mention it, sorry.
    @adsworth: I don’t think that this is the same problem – in my case, not only the content from the database is encoded wrong, but the whole page – which means also the static parts that aren’t fetched out of a database. Apart from that, I think the bug you mentioned would affect all browsers, not just Firefox alone – which happens with my page and is definitely weird.

    adsworth

    (@adsworth)

    19 years, 4 months ago

    hi xeophin,
    I just checked your page again. If you manually set set the character encoding to UTF-8 in firefox (View / Character Encoding /Unicode). The page displays correctly.
    I suggest you add this line:
    header('Content-Type: text/html; charset=' . get_settings('blog_charset'));
    on line 45 of wp-settings.php
    I bet it’ll work afterwards.
    Regards
    Adsworth

    Thread Starter xeophin

    (@xeophin)

    19 years, 4 months ago

    Problem solved, accidentally … somewhere while editing the index.php, I must have saved it encoded as UTF-8 with BOM (whatever this is). Obviously, Firefox chokes on that. Solution: always save your files without BOM.
    So, and now I’m going to hunt down any XML-errors … when sending files as application/xhtml+xml, those browsers just become merciless …

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Raiders of the Lost Encoding’ is closed to new replies.