Bug 174792

Summary: Regression: Kate in KDE 4 cannot read cp1255 text.
Product: [Applications] kate Reporter: Dotan Cohen <kde-2011.08>
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: kde-2011.08, shai
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Hebrew (cp1255) file

Description Dotan Cohen 2008-11-10 17:21:32 UTC
Version:            (using KDE 4.1.1)
Installed from:    Ubuntu Packages

I have a text file created on MS Windows with Hebrew text. In KDE 3.x when I open the file in Kate I get Gibberish as Kate assumes UTF-8 text. However, I can manually change the encoding to cp1255 and then Kate displays the file just fine.

In KDE 4.1 when I open the file in Kate I get the same Gibberish, however, selecting cp1255 does not change the way that Kate displays the file. I still get Gibberish.

Note that services such as http://gibberish.co.il cannot translate the Gibberish that Kate produces as all the characters are identical. So this could even be considered a dataloss situation.
Comment 1 Dotan Cohen 2008-11-10 17:23:06 UTC
Created attachment 28459 [details]
Hebrew (cp1255) file

In KDE 3.x I can manually change Kate's encoding to cp1255 to read this file. This cannot be done in KDE 4.x.
Comment 2 Dotan Cohen 2008-11-28 18:04:35 UTC
The problem still exists in Trunk.
Comment 3 Dotan Cohen 2008-11-29 23:22:53 UTC
It seems that this problem was not present in KDE 4.1, it is new in KDE 4.2.
Comment 4 Shai 2008-11-30 01:03:06 UTC
Works for me -- I don't see the bug in KDE built from trunk today.

Note: I recently ran into several weird problems with trunk. One of them prompted me to reconfigure Qt, which caused KDE to be rebuilt cleanly; all the others (which I have good reason to believe were unrelated to the configuration change) mysteriously went away. Try cleaning and rebuilding.
Comment 5 Dotan Cohen 2008-12-13 16:25:17 UTC
Seems to be fixed in latest Trunk. Thanks.