Default Encoding changes to UTF16 under windows since 3.0 Topic is solved

If you are using the main C++ distribution of wxWidgets, Feel free to ask any question related to wxWidgets development here. This means questions regarding to C++ and wxWidgets, not compile problems.
Post Reply
samsam598
Super wx Problem Solver
Super wx Problem Solver
Posts: 340
Joined: Mon Oct 06, 2008 12:55 pm

Default Encoding changes to UTF16 under windows since 3.0

Post by samsam598 »

Greetings!

Learnt from the doc this change under windows but keeps UTF8 encoding under *nix.Just wondering whether there is anything I should change or pay attention to according to this change,talking about my source code,or encoding of my source editor (say C::B),or when trying to interact with windows(or c)APIs?

Thanks and best regards,
Sam
Regards,
Sam
-------------------------------------------------------------------
Windows 10 64bit
VS Community 2019
msys2-mingw13.2.0 C::B character set: UTF-8/GBK(Chinese)
wxWidgets 3.3/3.2.4 Unicode Mono Static gcc static build
User avatar
doublemax
Moderator
Moderator
Posts: 19116
Joined: Fri Apr 21, 2006 8:03 pm
Location: $FCE2

Re: Default Encoding changes to UTF16 under windows since 3.

Post by doublemax »

In Unicode under Windows, the encoding has always been UTF-16 (UCS-2 to be more exact). Which part of the docs are you referring to?
Use the source, Luke!
samsam598
Super wx Problem Solver
Super wx Problem Solver
Posts: 340
Joined: Mon Oct 06, 2008 12:55 pm

Re: Default Encoding changes to UTF16 under windows since 3.

Post by samsam598 »

Thanks.I have thought this is the most newly change.

Here
http://docs.wxwidgets.org/trunk/overview_string.html
Regards,
Sam
-------------------------------------------------------------------
Windows 10 64bit
VS Community 2019
msys2-mingw13.2.0 C::B character set: UTF-8/GBK(Chinese)
wxWidgets 3.3/3.2.4 Unicode Mono Static gcc static build
User avatar
doublemax
Moderator
Moderator
Posts: 19116
Joined: Fri Apr 21, 2006 8:03 pm
Location: $FCE2

Re: Default Encoding changes to UTF16 under windows since 3.

Post by doublemax »

I think the new part is the UTF8 encoding on the other platforms. AFAIK that used to be UTF-32 before (not 100% sure about that as i only work under Windows).
Use the source, Luke!
Post Reply