Re: [groff] [patch] modernize -T ascii rendering of opening single quote

On Monday, February 18, 2019 4:23 AM, Ralph Corderoy wrote: > Hi Ingo, > > The latest US-ASCII standard, ANSI INCITS 4-1986 (R2007), > . . . > I think you have misinterpreted the above. > The table on physical page 16 of the above US-ASCII standard says > . . . > That makes clear that 27 and 6

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

> > > ISO 646 removed the ambiguity by assigning the neutral apostrophe > > > to 27h and the grave accent to 60h, but strictly, it isn't "ASCII." > > > > So why don't we leave the ascii device as it is and create a new > > iso646 device with the proposed changes? > > Are you suggesting that iso6

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

Hi, > It might have been a Sun/SPARC terminal, which uses the nicest looking > console font in existence: > > The font in question (Gallant) is still used by Solaris and was (until > recently) used by OpenBSD before t

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

Hi Bjarni, > The expression "modernize" in this context has a manipulative > character. Who wants to be against "modernization"! Could have been worse, `Progress Denier!' :-) -- Cheers, Ralph.

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

Hi Anthony, > ` and ' are not directional quotes in ASCII output. They are grave > accent and straight quote. In ASCII, `' are both left/right quotes and grave/acute accents. > This was common practice historically Common practice historically, I was there for some of it, was to use `' as left/

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

Hi Tadziu, > > ISO 646 removed the ambiguity by assigning the neutral apostrophe to > > 27h and the grave accent to 60h, but strictly, it isn't "ASCII." > > So why don't we leave the ascii device as it is and create a new > iso646 device with the proposed changes? Are you suggesting that iso646 b

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

Hi Ingo, > > Due to some, all?, man renderers trying to keep a shell backquote as > > a paste-able backquote, for example. > > > > .\" For UTF-8, map some characters conservatively for the sake > > .\" of easy cut and paste. > > . > > .if '\*[.T]'utf8' \{\ > > . rchar \- - '

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

Hi Ingo, > The latest US-ASCII standard, ANSI INCITS 4-1986 (R2007), > > http://sliderule.mraiow.com/w/images/7/73/ASCII.pdf > > says on page 16; > > 0x60 LEFT SINGLE QUOTATION MARK, GRAVE ACCENT > > with this footnote: > > These characters should not be used in international interchange >

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

> ISO 646 removed the ambiguity by assigning the neutral apostrophe > to 27h and the grave accent to 60h, but strictly, it isn't "ASCII." So why don't we leave the ascii device as it is and create a new iso646 device with the proposed changes?

Re: [groff] [patch] modernize -T ascii rendering of opening single quote

*> I do seem to recall at least one terminal that displayed opening and> closing quotes (for the life of me, I cannot remember which one; I> honestly had more important things to commit to memory).* It might have been a Sun/SPARC terminal, which uses the nicest looking console font in existence: [