Recent

Author Topic: 3.0 RC2, Windows: non-unicode API by default?  (Read 8792 times)

balazsszekely

  • Guest
Re: 3.0 RC2, Windows: non-unicode API by default?
« Reply #15 on: October 10, 2017, 05:48:32 pm »
Could you tell please why you want to use the historical ANSI system codepages instead of Unicode?
Unicode has existed for decades and solves all problems inherent to the codepages.
If I understood him correctly the API calls are not linked directly to their _W equivalent. When you write CreateProcess is "mapped" to CreateProcessA not CreateProcessW.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4459
  • I like bugs.
Re: 3.0 RC2, Windows: non-unicode API by default?
« Reply #16 on: October 10, 2017, 07:38:42 pm »
If I understood him correctly the API calls are not linked directly to their _W equivalent. When you write CreateProcess is "mapped" to CreateProcessA not CreateProcessW.
True, in FPC 3.0.2 sources CreateProcess maps to CreateProcessA. In future the defaults must be changed to use the _W API versions. It is important for Unicode support, regardless of encoding.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

 

TinyPortal © 2005-2018