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

List:       kde-bugs-dist
Subject:    [Bug 105037] New: Characters not included in charset are replaced
From:       Alexander Skwar <alexander () skwar ! name>
Date:       2005-05-03 16:21:59
Message-ID: 20050503182156.105037.alexander () skwar ! name
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=105037         
           Summary: Characters not included in charset are replaced by ?
                    (question mark)
           Product: knode
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: knode-devel kde org
        ReportedBy: alexander skwar name


Version:           0.9.0 (using KDE 3.4.0, Gentoo)
Compiler:          gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r2, \
                ssp-3.4.3.20050110-0, pie-8.7.7)
OS:                Linux (i686) release 2.6.11-ck4.ASN.002.reiser4

When I reply to a post and use characters that are not included in the charset of the \
original article, KNode 0.9.0 (with KDE 3.4.0) replaces those characters by ? \
(question marks), so that the article is technically correct. Instead of doing this, \
I'd expect KNode to at least issue some sort of warning, that characters will be \
replaced. The IMO correct and most user friendly solution would be, if KNode would \
automatically chose the correct charset - just like Thunderbird/Mozilla MailNews \
does.

Reproduce:
In KNode setup, under "Aritkelversand" (Composition?), select "iso-8859-1" as default \
charset. DE-select "Beim Antworten eigenen Standard-Zeichensatz verwenden" ("Use own \
charset"?).

Post an article with a character set of "iso-8859-1" and these letters: "äöüß"

Compose a followup to this article and type a character that's not included in the \
"iso-8859-1" charset; eg. the Euro sign "€".

Fetch the post from the server. You'll see that the € (Euro) has been *silently* \
replaced by a ? (question mark). That's so, that the article is technically correct, \
I suppose.


The best solution would be, that KNode upon detecting the presence of illegal \
characters (like it already does - else the € wouldn't have been replaced by a ?) \
warns the user and automatically choses the correct charset. I don't know how to \
automatically detect this, but other programs can do this.


That's a (minor) bug, as the user will not always be aware that KNode silently \
replaces characters he typed by something else.


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