Version: 3.0.0b1 (using KDE 3.1.93 (CVS >= 20031028), Gentoo) Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice) OS: Linux (i686) release 2.4.20-gentoo-r8 I created a new cpp project and as author as usual Jörg Rüppel. The project option dialog shows it fine afterwards, by the sourcefile headers show this: Jörg Rüppel, which I don't like, since my name is spelled slightly different ;)
It shows like that where? Could it be that the editor you used is not configured correctly to read UTF-8?
Subject: Re: umlaut encoding problems when creating project I'm using katepart and it is set to UTF-8. Toggling the encoding options didn't help.
After changing the katepart option for "encoding to use for reading/writing files", you need to reload the file (i.e. by pressing F5) in order to get the changes. This works for me. However, reassigning to kate, because it belongs there. On the other hand, i am not sure, if all development tools like UTF Stuff in files. But that's another issue.
Oh, by the way, that might be a project policy. For instance, all KDE files are supposed to be UTF-8 encoded, even if your editor doesn't support it.
reassigning back, there is a ktexteditor::encoding interface, kdevelop should tell the texteditor part that the sources are utf-8
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.)
Subject: Re: umlaut encoding problems when creating project > ------- Additional Comments From jens.dagerbo@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? it is not really possible to detect if a file is in utf8, as normally nowhere any byteorder mask is inserted (not that kate part would look at it ;) therefor it would be nice if kdevelop as it knows that the files contains utf8 if it puts generated stuff in utf8 in them would tell the ktexteditor document which encoding to use for open it.