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

2019-02-08 Thread Jeff Conrad
On Friday, February 8, 2019 6:18 AM, Ingo Schwarze wrote > you seem to be reading too much into various sources, Quite likely, but perhaps no more so than anyone else. My point was simply that the distinction between “historical” and “modern” isn’t very helpful. If indeed X3.4-1967 called for a

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

2019-02-08 Thread Ingo Schwarze
Hi Jeff, you seem to be reading too much into various sources, but fortunately, it only tangentially affects what matters to the proposed patch: there can be little doubt that fonts more commonly show 0x60 as a grave accent today, and likely also in the past, and that that practice better matches

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

2019-02-08 Thread Jeff Conrad
On Friday, February 8, 2019, Ingo Schwarze wrote > > I think "historic" is pretty context dependent. As nearly as I can > > tell, ASA/ANSI X3.4 has called for 0x60 to encode "accent grave". > > Absolutely not: > > http://worldpowersystems.com/ARCHIVE/codes/X3.4-1963/page5.JPG > > In that sta

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

2019-02-08 Thread Ingo Schwarze
Hi Jeff, Jeff Conrad wrote on Fri, Feb 08, 2019 at 04:25:51AM +: > On Wednesday, February 6, 2019 6:39 AM, Ingo Schwarze wrote >> BENEFITS: >> - >> - stop relying on a historic meaning of ASCII 0c60 >>that was never portable and that conflicts with Unicode > I think "historic" i