Re: [Libreoffice-commits] core.git: tell msvc our source code is written using utf-8

Stephan Bergmann <sbergman -AT- redhat.com>
Thu, 24 Aug 2017 15:04:03 +0200

On 08/17/2017 10:33 AM, Stephan Bergmann wrote:

Are we confident that all relevant toolchains treat C++ source files asUTF-8 now? How about e.g. Linux, where I could imagine that GCC/Clangwould base their behavior on LC_* env vars?

Turns out GCC/Clang have a corresponding flag, now set with<https://cgit.freedesktop.org/libreoffice/core/commit/?id=30935cf8adf8747b46ea485ba4a320b542a4f7a5>"Explicitly specify -finput-charset=UTF-8 for GCC/Clang".

That means that if all agree that UTF-8 encoded C++ source files are agood idea, we can now use actual Unicode content (instead of \uXXXX,\UXXXXXXXX escapes) in u8/u/U string literals on master.

Context

Re: [Libreoffice-commits] core.git: tell msvc our source code is written using utf-8 · Stephan Bergmann
- Re: [Libreoffice-commits] core.git: tell msvc our source code is written using utf-8 · Stephan Bergmann
  - Re: [Libreoffice-commits] core.git: tell msvc our source code is written using utf-8 · Mark Hung
  - Re: [Libreoffice-commits] core.git: tell msvc our source code is written using utf-8 · Caolán McNamara

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.