Cpp Parser & multibyte chars (bug 274430)

Sven Brauch svenbrauch at googlemail.com
Sun Nov 20 11:01:30 UTC 2011

I suffer from the same problem, althogh I don't know exactly *how*
(there's random fails, but I don't know when exactly they occur -- i
think if files do not use utf8 and do not explicitly specify this, but
still use non-ascii characters). However it's quite a bit easier in
python, because _most_ files have the encoding denoted in the header
(it's required when using fancy characters in the source code). So I'd
be interested in knowing the text editor's encoding for a specific
file, too.


>> Whats the efficiency problem with QString here? After all indexing into
>> it to get a QChar out should be O(1), right?
>>> It shouldn't be too complicated though to map ranges regarding utf8 when
>>> doing the highlighting in the editor.
>> Then you break things for anybody not using utf-8 which is just as
>> valid as a source file encoding.
>> Andreas
> Now it's broken for people using utf8 apparently, so I don't think it's a
> valid concern.
> Aleix
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

More information about the KDevelop-devel mailing list