On Thu, Feb 23, 2023 at 10:09:25PM +0000, Gavin Smith wrote: > > 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.
I added it as NO_GRATUITIOUS_UTF8, although it may be better to make the "super-option" "ASCII_PUNCTUATION" (the original variable), and rename the current ASCII_PUNCTUATION to something else, e.g. 'ASCII_DASHES_AND_QUOTES'.