bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texinfo-6.8.90 pretest


From: pertusus
Subject: Re: texinfo-6.8.90 pretest
Date: Sun, 23 Oct 2022 01:42:14 +0200

On Sat, Oct 22, 2022 at 09:36:20PM +0100, Gavin Smith wrote:
> On Sat, Oct 22, 2022 at 09:39:14PM +0300, Eli Zaretskii wrote:
> > > If this works then we could switch to it and not use I18N::Langinfo at
> > > all.
> > 
> > This works here, and produces the codepage number.  But (due to the
> > Windows peculiarities which I won't go into), it isn't the same
> > codepage number as the "current system ANSI codepage", which is
> > retrieved by the GetACP call I showed in my previous message.  So from
> > my POV, on Windows it is better to use the GetACP call via Win32::API
> > module, as that produces a codepage that is more accurate in some
> > cases.
> > 
> > In any case, both methods produce just a number, not an encoding
> > identifier.  We will need to prepend something to it, like "CP" maybe,
> > depending on how the codeset is used by texi2any.
> 
> Could you try the following?

In case this works, could you tell use, Eli, if there is a need to
document something about Win32::API being needed, or is it automatically
present on Windows perl that do not already have information available
through I18N::Langinfo?  (My very wild guess is that perl on windows in
environement emulating GNU/Linux or another Unix, such as cygwin, MinGW
or the Windows Subsystem for Linux have langinfo.)

-- 
Pat



reply via email to

[Prev in Thread] Current Thread [Next in Thread]