Home/ Questions/Q 937815
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T21:32:17+00:00

I’m working with a C++ sourcefile in which I would like to have a

  • 0

I’m working with a C++ sourcefile in which I would like to have a quoted string that contains Asian Unicode characters.

I’m working with QT on Windows, and the QT Creator development environment has no problem displaying the Unicode. The QStrings also have no problem storing Unicode. When I paste in my Unicode, it displays fine, something like:

#define MY_STRING 鸟

However, when I save, my lovely Unicode characters all become ? marks.

I tried to open up the source file and resave it as Unicode encoded. It then displays and saves correctly in QT Creator. However, on compile, it seems like the compiler has no idea what to do with this, and throws a ton of misguided errors and warnings, such as “stray \255 in program” and “null character(s) ignored”.

What’s the correct way to include Unicode in C++ source files?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Personally, I don’t use any non-ASCII characters in source code. The reason is that if you use arbitary Unicode characters in your source files, you have to worry about the encoding that the compiler considers the source file to be in, what execution character set it will use and how it’s going to do the source to execution character set conversion.

    I think that it’s a much better idea to have Unicode data in some sort of resource file, which could be compiled to static data at compile time or loaded at runtime for maximum flexibility. That way you can control how the encoding occurs, at not worry about how the compiler behaves which may be influence by the local locale settings at compile time.

    It does require a bit more infrastructure, but if you’re having to internationalize it’s well worth spending the time choosing or developing a flexible and robust strategy.

    While it’s possible to use universal character escapes (L'\uXXXX') or explicitly encoded byte sequences ("\xXX\xYY\xZZ") in source code, this makes Unicode strings virtually unreadable for humans. If you’re having translations made it’s easier for most people involved in the process to be able to deal with text in an agreed universal character encoding scheme.

    • 0