Date: Sat, 07 Sep 2019 08:53:46 -0700
On Saturday, 7 September 2019 08:47:43 PDT Thiago Macieira wrote:
> > You may not be aware, but after a discussion with some Microsoft folk, I
> > went ahead and submitted that as a feature request for the next major
> > release of Visual Studio. And from what I am told, they are seriously
> > considering it. The Windows console supports it, Windows supports it,
> > the MSVCRT runtime supports it when asked. All someone needs to do is
> > flip the switch for new projects targeting latest Windows 10 only, and
> > we've done it.
> >
> > Having char = utf8 across all the major platforms would be an *enormous*
> > win. Please aid that effort.
>
> Of course. How can I help?
By the way, is there a matching effort for MinGW? You need both major
environments to support the change, otherwise we end up with non-portable code
and therefore having to use GetCommandLineW + CommandLineToArgvW.
> > You may not be aware, but after a discussion with some Microsoft folk, I
> > went ahead and submitted that as a feature request for the next major
> > release of Visual Studio. And from what I am told, they are seriously
> > considering it. The Windows console supports it, Windows supports it,
> > the MSVCRT runtime supports it when asked. All someone needs to do is
> > flip the switch for new projects targeting latest Windows 10 only, and
> > we've done it.
> >
> > Having char = utf8 across all the major platforms would be an *enormous*
> > win. Please aid that effort.
>
> Of course. How can I help?
By the way, is there a matching effort for MinGW? You need both major
environments to support the change, otherwise we end up with non-portable code
and therefore having to use GetCommandLineW + CommandLineToArgvW.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel System Software Products
Received on 2019-09-07 17:53:48