ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Characters not displaying correctly in browser

May 23, 2008 6:28am

Subscribe [2]
  • #1 / May 23, 2008 6:28am

    familychoice

    59 posts

    Hi,

    I have a standard website setup, based on the Boyink tutorial. Nothing fancy, and I haven’t changed any settings in the control panel regarding the formatting of blog entries or the way text is displayed.

    However, all my blog posts aren’t displaying characters such as (english) pound signs and other special characters - they look fine in the admin panel preview, but viewed in a browser they’re all wrong and replaced by other characters and boxes.

    Can anyone suggest what I’m doing wrong?

    I’m using this as the doctype in my head tag - I was using a strict version but changed to see if it would fix the display issues:

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">

    Thanks.

  • #2 / May 23, 2008 6:33am

    Ingmar

    29245 posts

    Do you have a link to the site in question? It’s not so much the doctype as the content encoding you need to be concerned about. In your rendered template you should probably have this:

    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
  • #3 / May 23, 2008 6:36am

    familychoice

    59 posts

    Do you have a link to the site in question? It’s not so much the doctype as the content encoding you need to be concerned about. In your rendered template you should probably have this:

    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />

    Hi Ingmar - thanks for the reply. I’ll add that to the doctype.

    I’ve found an answer in the Knowledge Base - I need to have the “Automatically Convert High ASCII Text to Entities” set to yes as it wasn’t set as a default.

    This seems to fix it, thanks again.

  • #4 / May 23, 2008 6:39am

    Ingmar

    29245 posts

    Actually, if you’re using utf-8 you should not have to do this, but whatever works for you, as always 😊

  • #5 / May 23, 2008 6:59am

    familychoice

    59 posts

    Actually, if you’re using utf-8 you should not have to do this, but whatever works for you, as always 😊

    Ahhhhaaa…..I was using

    <meta http-equiv="content-type" content="text/html;charset=iso-8859-2" />

    So, by replacing that part with

    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    I wouldn’t have to have the “Automatically Convert High ASCII Text to Entities” set to yes?

  • #6 / May 23, 2008 7:18am

    Ingmar

    29245 posts

    Yes, exactly. Everyting, ie your database, control panel and website, would then be in utf-8 aka Unicode, putting an instant end to all encoding issues. Well, in theory, at least 😊

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases