Bug 105037 - Characters not included in charset are replaced by ? (question mark)
Summary: Characters not included in charset are replaced by ? (question mark)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-03 18:21 UTC by Alexander Skwar
Modified: 2018-09-04 18:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Skwar 2005-05-03 18:21:56 UTC
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.
Comment 1 Tassilo Horn 2005-05-04 11:09:32 UTC
Hi,
I think KMail's solution is the best. (Look at Kmail -> settings -> Composer -> Charset tab.) There you can have a list of encodings, and KMail checks it topdown for every outgoing mail till it finds an encoding which contains all needed letters.

As an example my list is like this:

  us-ascii     // "Bla bla."
  iso-8859-1   // "Blä blöü."
  iso-8859-15  // "Blä blöü with €."
  utf-8        

So if I don't have Umlaute in my mail, the charset will be us-ascii, with Umlaute it'll be iso-8859-1, if I use the Euro-sign it'll be iso-8859-15 and if I suddenly start writing chinese, well, than it will be utf-8.

Regards,
Tassilo
Comment 2 Alexander Skwar 2005-05-04 11:55:39 UTC
Yes, that sounds like a good solution. What happens in KMail, if you respond to iso-8859-15 Mail and use only us-ascii characters? Will the mail be encoded in iso-8859-15? That is exactly what SHOULD happen, IMO.

BTW: The KMail is solution your proposing here, is also what Thunderbird/Mozilla is using.
Comment 3 Tassilo Horn 2005-05-04 14:09:04 UTC
The answer to a iso-8859-15 encoded message will also be encoded in iso-8859-15, even if it contains no letters requiring iso-8859-15.
Comment 4 Karl Ove Hufthammer 2005-09-06 11:48:08 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 Alexander Skwar 2007-07-12 09:52:01 UTC
I'm curious - will eventually something be done about this bug? I mean, it just recently celebrated it's 2nd birthday...
Comment 6 Andrew Crouthamel 2018-09-04 18:32:26 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.