Encoding issues in cmake files

Aleix Pol aleixpol at kde.org
Thu Feb 7 15:27:29 UTC 2013

On Thu, Feb 7, 2013 at 3:30 PM, Andreas Pakulat <apaku at gmx.de> wrote:

> Hi,
> just happened to see
> http://quickgit.kde.org/?p=kdevelop.git&a=commit&h=15bee005db20b380c0b4335d03afb0f17a4e750c
> on irc and I think the fix is wrong. CMake files do not have an
> encoding specification, so either cmake dictates an encoding in its
> documentation (or its own parser) or it does not. In the latter case a
> user needs to be able to decide which encoding to use for parsing
> cmake files, just using his local 8 bit encoding can be wrong as well.
> In particular for utf16 files or for people regularly working with two
> different encoding (thats the case a lot in asia). It also can already
> break on windows with utf-8 encoded cmake files, since the local 8 bit
> encoding there is latin1.
> Andreas
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel

Well, it will be broken either way, because we're assuming latin1 anyway.
Right now, locally it works the same way at least in my system, so it maps
better how cmake works.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20130207/ea9601ed/attachment.html>

More information about the KDevelop-devel mailing list