[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Texinfo Windows patch: Non-ASCII text output
From: |
Eli Zaretskii |
Subject: |
Re: Texinfo Windows patch: Non-ASCII text output |
Date: |
Fri, 26 Dec 2014 12:09:10 +0200 |
> Date: Fri, 26 Dec 2014 19:13:24 +1000
> From: Jason Hood <address@hidden>
> CC: address@hidden
>
> On 26/12/2014 18:37, Eli Zaretskii wrote:
> > The speed is fine on my machines, and cputs does NOT write one
> > character at a time, it uses WriteConsole. Only cprintf writes one
> > character at a time.
>
> Not according to the Visual Studio 2010 source, which is presumably
> similar to what MSVCRT.DLL would use.
Depends on the Windows version. I looked in the version that is used
on XP, and will check with newer versions later. (I think I did check
in Studio 2010 sources at the time, but maybe I misremember.)
In any case, since with my patches we will never write UTF-8 via
cputs, this is a non-issue, I think.
> Why else do you think you needed to convert to UTF-16?
I don't know. The Windows console internals are notoriously
under-documented, so many times I need to accept factoids without
really understanding them.
Again, I don't think this is an issue anymore, as we both agree that
cputs should not be used for UTF encoded text.