Re: [Kdiff3-user] Decoding a cp1251 file saved as utf8?

[Angel T. <fn...@fm...>]

On 02/16/11 21:54, Joachim Eibl wrote:
> Hi Angel,
>
> No good news: When looking at the output in hex
> (e.g. via  od -t x cp1251.saved.as.utf8.txt )
> you see that there is no useful information left anymore.
>
> 0000000 efbdbfef bfefbdbf bdbfefbd efbdbfef
> 0000020 bfefbdbf bdbfefbd efbdbfef bfefbdbf
> 0000040 bdbfefbd efbdbfef bfefbdbf bdbfefbd
> 0000060 efbdbfef bfefbdbf bdbfefbd efbdbfef
> 0000100 bfefbdbf bdbfefbd efbdbfef bfefbdbf
> 0000120 bdbfefbd efbdbfef 000abdbf
>
> So in your concrete situation I can't do much for you.
>
> But I must admit, that I was not aware of that problem. As I mentioned before
> I expected no irreversible conversion loss, but now I think that Qt internally
> converts to 16 bit  although UTF8 allows 32 bit characters. So most random
> combinations will result in a "invalid" character.
>
> I will try to detect this and display a warning in KDiff3 for such situations.
>
> Thanks for telling! I really do hope you find some backup.

Hello Joachim,

And don't worry.  The file I lost in this incident was not too long and 
I was able to remember its contents.

Despite this little problem, I am still a happy user of KDiff3. I also 
think that the suggested warning (or smth similar) is highly desirable 
in this situation.

Best regards,
Angel Tsankov