• Resolved crashnet

    (@crashnet)


    using 2.6.1,

    1) DB is using latin1-swedish-c1
    2) DB_CHARSET came as UTF-8, but i switched it to empty
    3) DB_COLLATE is empty
    4) “Encoding for pages e feeds” came as UTF-8, but the visible text in the theme’s files (which i translated to portuguese, thus it contains accents) shows funny chars where the accents are unless i change it to iso-8859-1. BUT when i change it to iso-8859-1, the admin language file in use (pt_BR.mo) start using messy chars where the accents are.

    whats the correct combination to get both the admin and the public facing side to get the accents right?

    TIA!

Viewing 13 replies - 1 through 13 (of 13 total)
  • Your only problem is that when saving the theme’s template files you didn’t save them with utf-8. Even Notepad has this options, so use it. Then you will be fine with the default utf-8. It will serve you well on long run.

    Thread Starter crashnet

    (@crashnet)

    thanks moshu.

    hmmm, i’m using ultra-edit, and it defaults to UTF-8… maybe i need to save them as UNICODE?

    when i re-open the files (after the editing) they show up fine in ultraedit. (and as mentioned, they actually show up fine in the admin section IF i set the encoding on pages to ISO-8859-1)

    they actually show up fine in the admin section IF i set the encoding on pages to ISO-8859-1

    Which means you saved them with that encoding not utf-8. And we can argue about it all day long, the error will not go away until you try to do what I told you: save them in Notepad selecting the utf-8 encoding. Period.

    Thread Starter crashnet

    (@crashnet)

    they were saved as UTF-8, because if i put UTF-8 in “Encoding for pages e feeds” the theme AND the admin display accents correctly. the good news: now NEW comments also appear correctly. problem was that after changed DB_COLLATE to empty and left UTF-8 for “Encoding for pages e feeds” i didnt submit a NEW comment to test. i just saw that the older comment, submitted prior to changing DB_COLLATE, was messed up and assumed that combination wasnt working.

    in a few words, DB_COLLATE = ” fixed it.

    thanks moshu!

    Seemingly we were talking about two different things all the time. I was referring to this:

    but the visible text in the theme’s files (which i translated to portuguese, thus it contains accents) shows funny chars where the accents are unless i change it to iso-8859-1

    hi every one
    please i need some help
    what i must do to write my post or pages in russian language , iam new user with wordpress blogs and i don’t know what i can do ..
    thanks

    well, as long as you input Russian language on your computer ( you got MS Windows, right? ) you can type in WordPress Editor Window in Russian.

    Some specific information could be found scroll down for Russian there

    removed

    Thread Starter crashnet

    (@crashnet)

    but the visible text in the theme's files (which i translated to portuguese, thus it contains accents) shows funny chars where the accents are unless i change it to iso-8859-1

    we were talking about the same thing. i had two problems that occurred mutually exclusively. one of them was the problem above.

    even after thinking i had fixed it, the “the visible text in the theme’s files” was still being displayed as messed up. FYI this is what finally nailed down every the last problem i had: saving it as “UTF-8 NO BOM” instead of plain “UTF-8”

    reference: https://unicode.org/faq/utf_bom.html#BOM

    hi

    What`s the correct encoding that I have to use to work on the feed of browser Safari and also to the Technorati to the Portuguese?

    The encoding UTF-8 and iso-8859-1 don’t work!

    thanks

    Your blog has the right utf-8 encoding, so don’t mess with it!

    I don’t understand your question, sorry.

    moshu, plz, look my technorati in https://technorati.com/blogs/gilbertoconsoni.com and see the problem with the special caracters!!!

    I need some encoding that work on the Technorat (https://technorati.com/blogs/gilbertoconsoni.com) and to Safari feed…

    You cannot do anything about it. It is not a WordPress issue, it is a technorati problem.
    Look at the 12 blog reactions below your blog’s description:
    e.g. mercúrio fulminante and thalles.blog. Both are hosted by the same pro server (on wordpress.com), both have encoding utf-8. One looks OK, the other is screwed up…

    So, stop worrying about technorati – it sucks.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘encoding problems’ is closed to new replies.