Bug 128785 - Characters thrown away without warning when opening using wrong encoding
Summary: Characters thrown away without warning when opening using wrong encoding
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-07 20:42 UTC by Reuben Thomas
Modified: 2007-05-19 16:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Reuben Thomas 2006-06-07 20:42:54 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Kate doesn't warn me when I open, for example, an ISO-8859-1 file with utf-8 encoding. It simply throws away the characters that are invalid under the selected encoding.

Note: there are several bugs about what happens when the file is SAVED, but in fact, in this case that is too late, as the invalid characters have already been removed, and the problem occurs when the file is OPENED.
Comment 1 Jaison Lee 2006-06-07 21:37:02 UTC
Bug #55355 is exactly what you are describing, right down to the same encodings you are having problems with.


*** This bug has been marked as a duplicate of 55355 ***
Comment 2 Reuben Thomas 2006-06-07 21:47:32 UTC
I don't think this bug is a dup. The bug you've made it a dup of is actually a wishlist item, asking for better behaviour in future (auto-detection of encodings). Providing this would indeed fix my problem, but it's hard.

I'm just asking for a simple warning, to avoid data loss, which is much simpler to implement and hence has a chance of being implemented sooner.

I'd agree that this bug is a dup iff you intend to implement encoding detection soon. Otherwise, I think folding a current bug into a future wishlist item is a bad idea.
Comment 3 Christoph Cullmann 2007-05-19 16:17:06 UTC
There is now a warning that the file was no correct utf-8 and chars got lost...