> > > 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 becomes the new `C locale' device > to fit that?
Not at all. I see the "C" locale as a system administrator's or programmer's locale. This is the clientele that values not losing the visual distinction between opening and closing quotes. No, the iso646 device would be only for those users who have to use a "modern" font with ISO 646 encoding (as opposed to old-style ASCII with symmetric quotes) on terminals that do not support the full Unicode. Myself, I use fonts with symmetric quotes. I vote for groff's ascii (and latin1) device to continue mapping the quotes identically from input to output.
