Messed-up encoding in doc-comments (in the popup-widget)

Milian Wolff mail at milianw.de
Tue Jul 7 13:27:59 UTC 2009


Niko Sams wrote:
> On Tue, Jul 7, 2009 at 14:53, Milian Wolff<mail at milianw.de> wrote:
>> Hey guys, I want to fix bug https://bugs.kde.org/show_bug.cgi?id=183182 but
>> am a bit lost. Can someone give me a bit of insight?
>>
>> What I found out is that it only affects doc-comments and that it is not due
>> to formatComment().
>>
>> 1) How could I properly debug this stuff? kDebug() doesn't seem to work
>> fine. Could I use GDB and somehow print me the text and see where it gets
>> corrupted?
>>
>> 2) Could the popup-widget be the culprit? Where are its sources again?
> 
> Shouldn't the DUChain already contain correctly encoded strings?
> So the correct conversions would have to be done by the lexer
> of the language plugin.
> 
> Niko

It works for identifier (like function names, methods, classes 
variables) etc. and the logic in the parsesession is the same. Hence I 
doubt the language plugin/lexer is messing things up.

-- 
Milian Wolff
http://milianw.de




More information about the KDevelop-devel mailing list