[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: creating a QString with (escaped) unicode characters
From:       Thiago Macieira <thiago.macieira () kdemail ! net>
Date:       2005-01-28 10:05:02
Message-ID: 200501280805.10344.thiago.macieira () kdemail ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Paul Temple wrote:
>Or is it common for kde projects to use utf8 encoding for the
>source code? It don't think so, because then I would have never
>had a problem with (some of) the kdeedu/kiten files.

All KDE source code is encoded UTF-8, even the comments. The official part 
of KDE, anyways. We can't dictate what other people do with their own 
code.

C and C++ only know about char and wchar_t. I don't remember ever seeing 
\uXXXX in C. And even if you could do that, you'd need a wide-char string 
(L"a string"), if that is possible. To top all that, I don't think 
QString provides conversion to/from UCS-4 wchar_t.

-- 
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

3. Ac seo woruld wearð geborod, swá se Scieppend cweað "Gewurde Unix" and 
wundor fremede and him "Unix" genemned, þæt is se rihtendgesamnung.

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]