[prev in list] [next in list] [prev in thread] [next in thread] 

List:       konq-bugs
Subject:    [Bug 106554] New: wrong encoding of CSS style stored in separate file
From:       Jan "Kundrát" <jkt () flaska ! net>
Date:       2005-05-31 12:13:42
Message-ID: 20050531141341.106554.jkt () flaska ! net
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=106554         
           Summary: wrong encoding of CSS style stored in separate file (not
                    conforming to CSS/2.1)
           Product: konqueror
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: khtml
        AssignedTo: konq-bugs kde org
        ReportedBy: jkt flaska net


Version:           3.4.0 (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 3.3.5-20050130 (Gentoo Linux 3.3.5.20050130-r1, \
                ssp-3.3.5.20050130-1, pie-8.7.7.1) 
OS:                Linux

Konqueror/3.4.0 doesn't conform to CSS/2.1 standard as defined in \
http://www.w3.org/TR/CSS21/syndata.html#q23 - section about encoding (character set) \
of external CSS style. Suppose we have HTML page written in UTF-8 (server sends \
"Content-Type: text/html; charset=utf-8") which referrs to CSS in external file on \
the same server. It's clearly illustrated in \
http://dev.gentoo.org/~neysx/wwwgo/index.xml.html which referrs to \
http://dev.gentoo.org/~neysx/wwwgo/css/main.css . Later is also in UTF-8, but the \
server doesn't specify the "charset" part of Content-Type header. According to the \
CSS/2.1 specs, correct behaviour would be to:

1) An HTTP "charset" parameter in a "Content-Type" field (or similar parameters in \
other protocols) - not usable in this case

2) BOM and/or  charset (see below) - also doesn't apply

3) <link charset=""> or other metadata from the linking mechanism (if any)
charset of referring stylesheet or document (if any) - this should be used, but isn't \
- se below

4) Assume UTF-8 - fallback, but should *not* happen as it would break a lot of pages, \
IMHO


So, to the point 3 - you should use the same encoding as the HTML page has, which is \
UTF-8, in this case. But current behavior is that if you have set (in browser prefs) \
anything else as a "default codepage", it is used, which is bad.

Why is this important? In that particular case, external CSS sheet is used to add \
"content:" property to the links in the left hand column, which should result in a \
nice arrow before each link. But because konqueror uses other encoding for CSS file \
parsing, user doesn't see arrow, but some garbage characters. I can provide \
screenshot. _______________________________________________
Konq-bugs mailing list
Konq-bugs@mail.kde.org
https://mail.kde.org/mailman/listinfo/konq-bugs


[prev in list] [next in list] [prev in thread] [next in thread]