[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: simplifying configuration of encoded characters/entities output

From: Patrice Dumas
Subject: Re: simplifying configuration of encoded characters/entities output
Date: Wed, 29 Dec 2021 15:31:49 +0100

On Wed, Dec 29, 2021 at 02:08:42PM +0000, Gavin Smith wrote:
> On Wed, Dec 29, 2021 at 01:25:15PM +0000, Gavin Smith wrote:
> > I think Unicode directional quotes should be turned on by
> > default, simply because people would be upset if documents with
> > '@documentencoding UTF-8' suddenly stopped having them.  (If Info
> > had never had Unicode directional quotes I would have opposed changing to
> > output them because they are unnecessary in a plain text format, but by
> > now far too many people will be used to having them and would view a
> > change back to 'this' or `this' as a regression.)
> > 
> Done in 03a78a01c8.  The name of the NO_UTF8_PUNCTUATION variable can
> change if there are better ideas (technically speaking any ASCII
> punctuation is also UTF-8 punctuation too).
> I'm going to try to integrate it with the rest of the code a bit
> better.

I proposed DISABLE_PUNCTUATION_ENCODING in a mail I just sent in the
old thread.

I will reproduce here what I said in that thread, I think that doing
what Alan want would imply:
* added quotes as ASCII
* dashes and quotes appearing in the document ``, ---, ' as ASCII
* some brace_no_arg_commands @-commands as ASCII, those that are not
  in the 7bit ascii range and correspond to punctuation, maybe along
  @minus, @dots, @enddots, @quotedblleft, @quotedblright,
  @quoteleft, @quoteright.  Maybe also, but I am not sure,
  @quotedblbase, @quotesinglbase.

I think that your change does the first two, but no_extra_unicode does
not corresponds to the third point.  I am pretty sure that it prevents
any conversion of @-commands like @l{} to unicode/utf8.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]