[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Encoding of documentation for GUI browser (Windows)
From: |
Mike Miller |
Subject: |
Re: Encoding of documentation for GUI browser (Windows) |
Date: |
Fri, 6 May 2016 11:02:53 -0700 |
User-agent: |
Mutt/1.6.0 (2016-04-01) |
On Fri, May 06, 2016 at 10:53:27 -0700, Rik wrote:
> On 05/06/2016 10:42 AM, Daniel J Sebald wrote:
> > Rik,
> >
> > Check the origin of that apostrophe in the source code. Even the linux
> > variant doesn't seem standard. That apostrophe isn't something on the
> > conventional keyboard. I have ` and '. Ah, wait. That apostrophe is
> > coming from Tex's encoding, isn't it? Try a different Tex encoding
> > sequence to get the more conventional apostrophe.
> >
> Shouldn't Texinfo have put in a correct character? Or is it the fact that
> the documentation was generated in a tarball originally destined for Linux,
> and then not updated during the MXE build because the tarball goes out of
> its way to avoid recreating the documentation?
Texinfo is using LEFT SINGLE QUOTATION MARK (U+2018) and RIGHT SINGLE
QUOTATION MARK (U+2019). These are “correct” characters, this is just
more of the known problems with UTF-8 encoded strings on Windows.
--
mike
Re: Encoding of documentation for GUI browser (Windows), Colin Macdonald, 2016/05/06