[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Avoid apostrophe being output as non-ASCII quote in Info output
From: |
Gavin Smith |
Subject: |
Re: Avoid apostrophe being output as non-ASCII quote in Info output |
Date: |
Thu, 23 Feb 2023 22:09:23 +0000 |
On Thu, Feb 23, 2023 at 08:50:15AM +0100, Patrice Dumas wrote:
> > The latter would probably be an improvement for --- and -- too, as
> > the two types of dash may appear indistinguishable in a fixed width font:
> >
> > a — b – c
>
> A -- becomes - with ASCII_PUNCTUATION=1, so it isn't more distinguishable
> than the unicode ndash. To make it distinguishable, we should have ---
> remains --- and -- remains --.
>
The point was to distinguish em dash from en dash, not en dash from
hyphen. A single ASCII hyphen seems to be appropriate to use for an
en dash.
> This looks good to me. The only issue I see is that the original report
> that made us add ASCII_PUNCTUATION asked for everything relevant to be
> ASCII, including what can be set with *QUOTE_SYMBOL. Now, to get the
> same effect one would have to set
> ASCII_GLYPH=1 OPEN_QUOTE_SYMBOL=` CLOSE_QUOTE_SYMBOL='
> OPEN_DOUBLE_QUOTE_SYMBOL=" CLOSE_DOUBLE_QUOTE_SYMBOL="
>
> Should we add another customization option that does that (and also sets
> ASCII_PUNCTUATION=1 for consistency)?
Good point, that is a lot. It would be good to have an option that
sets all of these.