Summary: | Characters thrown away without warning when opening using wrong encoding | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Reuben Thomas <rrt> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Reuben Thomas
2006-06-07 20:42:54 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 *** 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. There is now a warning that the file was no correct utf-8 and chars got lost... |