Description

Problem

Garbled text because code-page is not correctly detected on IE6.

Description

Most themes have these settings in there css-settings (example from rightsidebar, but they're all the same):

    name = "rightsidebar"

    stylesheets_print = (
        # theme charset         media       basename
        (name,  'iso-8859-1',   'all',      'common'),
        (name,  'iso-8859-1',   'all',      'print'),
        )

    stylesheets = (
        # theme charset         media       basename
        (name,  'iso-8859-1',   'all',      'common'),
        (name,  'iso-8859-1',   'screen',   'screen'),
        (name,  'iso-8859-1',   'print',    'print'),
       )

but this is in my moin_config.py:

 # encoding and WikiName char sets
 # (change only for outside America or Western Europe)
 charset = 'UTF-8'

As you can see I use utf-8, this is not the same as the charset specified in the theme, as a result I get garbled text when using IE6. (I know I shouldn't be using IE, actually I don't, I hadn't noticed, this is not a problem using mozilla, somebody else noticed, and panicked, because she thought she had lost all her work ).

Example

Details

• Python Version	Python 2.3.2
  Server Setup and Version	Twisted 1.2.0

Discussion

I solved it by editing the theme, but it would be better if the theme would get the correct codepage moin_config.py, I suppose.

The CSS encoding is not related to the page encoding - If you want to change the css encoding, you must convert those file to the other encoding you want, and it must have the characters used in the CSS file.

I can not reproduce this bug on 1.3 development, using the default 'utf8' charset both with CGI or twisted installations. IE automatically select the correct encodings when loading a wiki page.

It might be a user error, maybe she choose the wrong encoding from the character code menu after the page was loaded?

Previous versions of moin used a character encoding meta tag, which is missing from both 1.2 and 1.3. I guess we have now another method to mark the encoding of the pages. Maybe this method is not supported well as the meta tag? -- NirSoffer 2004-07-31 19:28:15

I re-introduced the content-type meta tag, additionally to using the http headers. When we make a dump using moin_dump, we have no http headers, so it is needed there anyway. I also converted the css to utf-8, although any sane browser should have no problem with iso8859-1, either. Please test if that fixes it. -- ThomasWaldmann 2004-08-22 11:54:04

Plan

• Priority:

• Assigned to: ThomasWaldmann

• Status: fixed, we use meta-tag and utf-8 only in 1.3.

CategoryMoinMoinBugFixed