Summary: | saving the destination file unexpectedly converts it to the locale encoding | ||
---|---|---|---|
Product: | [Applications] kompare | Reporter: | MikMak <m.viey> |
Component: | general | Assignee: | Kompare developers <kompare-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | andrew.crouthamel |
Priority: | NOR | ||
Version: | 4.1.2 | ||
Target Milestone: | --- | ||
Platform: | FreeBSD Ports | ||
OS: | FreeBSD | ||
Latest Commit: | Version Fixed In: |
Description
MikMak
2013-11-01 18:38:31 UTC
I cannot reproduce this here (Fedora 18, Kompare 4.1.2 from kdesdk 4.10.5). Both files are displayed as UTF-8 for me and the saved file is also in UTF-8. thanks for your reply. Surely because my locale on my BSD is ISO_8859... but this choice should not have any effect in Kompare. I tried kdiff3 and it works fine with utf-8 even if my locale is not utf-8. An ISO-8859 locale? Wow, such a thing still exists? ;-) So I tried running Kompare with the legacy locale (LANG=de_AT rather than the normal de_AT.UTF-8). I still cannot reproduce the "characters in destination view are printed with an latin-1 encoding and false diff are indicated" part, but I can confirm that saving the file writes it in the locale encoding. Yes, this is the problem. If you re-open the both same files there are some differences cause the two files are not in the same encoding. The normal behavior should be to save the file in the same encoding it was opened. It is not crazy... For my locale I must change that, it is the default locale in BSD. (and a bad idea that I can't explain) Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Hello, I have forgotten this report. I don't use kompare anymore. So I cannot try. I change my locale to UTF-8 now. So I think you could close this report, indeed. thanks Thanks for the update! |