Re: Encoding of documentation for GUI browser (Windows)

[Nicholas Jankowski]

On Fri, May 6, 2016 at 2:21 PM, Daniel J Sebald <address@hidden> wrote:

On 05/06/2016 01:02 PM, Mike Miller wrote:

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.

OK, but I'm guessing U+0027

http://unicode-table.com/en/0027/

apostrophe is the "standard", and that no matter the font set that Windows uses the choice is likely to be some type of apostrophe.

Here is the U+2018 and U+2019 variant

http://unicode-table.com/en/2019/

Look at the related character glyphs on the webpage and U+0027 is classified as just "apostrophe".

Dan

This also related to bug #46637: mxe-octave: update GNU Texinfo to version 6

https://savannah.gnu.org/bugs/?46637

Here's the initial discussion thread:
http://octave.1599824.n4.nabble.com/invalid-character-for-plot-x-y-FMT-tp4673894p4673914.html

The apostrophe issue came up back in December regarding the documentation for plot.  the user was copying pasting the parameter strings for colors or something, and the help text displays it as 

`k'  blacK

Copy and paste from 'help plot' throws a syntax error. Anything called as @samp(X) or @code(stuff), and maybe some others, come up that way.

Nick J.