summaryrefslogtreecommitdiff
path: root/src/os/windows/string_uniscribe.cpp
diff options
context:
space:
mode:
authorPatric Stout <truebrain@openttd.org>2020-12-14 20:25:01 +0100
committerGitHub <noreply@github.com>2020-12-14 20:25:01 +0100
commit68f9925cd4c8b29dbdac301e86bd9fc6f5a7fb27 (patch)
tree7089a650e6372e6ea37b3d6a60e9359e19120ae1 /src/os/windows/string_uniscribe.cpp
parentb14e3b9b9df2294e1f0b7fab8b2c23381e32ade7 (diff)
downloadopenttd-68f9925cd4c8b29dbdac301e86bd9fc6f5a7fb27.tar.xz
Codechange: use \u to indicate unicode chars in strings (#8379)
With \x, we sometimes had to do the "" trick, as the length is not predefined. With C++11 bringing \u to the specs, which has a preset length, we no longer need the "" trick. We set the strings to u8, to ensure all compilers use UTF-8 encoding for the \u characters. This was triggered by newer CLangs, which start to warn if you use "" in the middle of a string, wondering if that was your intention. It is a good question. And this is our answer :)
Diffstat (limited to 'src/os/windows/string_uniscribe.cpp')
0 files changed, 0 insertions, 0 deletions