[Bug 68166] umlaut encoding problems when creating project

[Jens Dagerbo]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=68166     
jens.dagerbo at swipnet.se changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cullmann at kde.org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From jens.dagerbo at swipnet.se  2003-11-14 23:35 -------
I don't get this at all.. KDevelop just tells katepart to load a file, I don't see how it can be up to KDevelop to figure out the encoding and tell katepart?

Anyway, I created a new project, put "Jörg Rüppel" (dunno how this will look here) as "Author" and generated the project. Using the default katepart encoding setting for loading (on my system this apparently is "Western European (iso 8859-1)" ) I get the exakt effect Jörg reports.

However, if I either use "View -> Set Encoding.." and set "Unicode (utf8)" or go into "Settings -> Configure Editor" and set the katepart File Format encoding scheme to "Unicode (utf8)" in the "Open/Save" tab, and then reload the file, like Sascha suggests, I get the expected proper display.

In other words, I get the exact same behaviour as if I load the file in plain KWrite, and I cannot find a bug in this behaviour at all.

I'm closing this as WORKSFORME, as it doesn't look like anyone can confirm this bug. Jörg, please reopen if the problem persists, but also try it with plain KWrite (same editorpart) to try to figure out where the problem lies.

(BTW, there is something that might bite you when testing with KWrite. It appears KWrite doesn't save it's settings until you close the app. This means that if you open KWrite, change the encoding loading setting, reload the file and later open a new instance of KWrite, this second instance will not have the new setting. Also, when the both instances are closed, the setting that persists is the setting of the last one closed. This is typical application behaviour and not a bug of KWrite though.)