[Top][All Lists]

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

bug#31815: 27.0; Inappropriate use of curly quotes in `info.el'

From: Drew Adams
Subject: bug#31815: 27.0; Inappropriate use of curly quotes in `info.el'
Date: Fri, 13 Jul 2018 09:28:31 -0700 (PDT)

> > I just got a copy of the control msg for this bug, saying
> > that it has been closed (I haven't received the usual help
> > msg for the bug filer saying that it was closed, however.)
> Perhaps you misread the control message? I set the bug to severity
> minor and tagged it notabug (to summarize Eli's response, which I
> basically agree with), but I didn't close it, and looking at...,
> it is not closed.

I see; thanks.  I didn't (still don't) understand the difference
between `notabug' and `closed'.  Is it wrong to assume that it
will be closed if it is not a bug?

> > The bug report was about the occurrence of such curly quotes
> > in the Lisp sources (`info.el'), not about their appearance
> > in Info files.  So your reply does not make sense to me.
> The curly quotes in the source are there to produce curly quotes in
> Info buffers. We want to produce curly quotes in info buffers to match
> the rest of the buffer content which comes from Info files which have
> curly quotes in them. Your suggestion to restore the ascii quotes
> would produce a buffer of mixed quoting styles.

I didn't suggest restoring the quotes to non-curly in Info.

[Though I would like it for users to be able to control
whether Info uses curly quotes.  We've been through that
before: Apparently Texinfo doesn't give us a choice here,
so, for example, option ` text-quoting-style' has no
effect on Info.  Too bad, but not everything is as
flexible for users as is Emacs.]

I suggested restoring them in the Lisp source files, not
in Info buffers.  The source files need not use the chars
literally to produce them for Info, AFAIK.


To be clear: I'm not even sure just what copy+paste gotcha
I stumbled upon, when trying to report bug #31807.  I think
that other times I've been able to copy+paste such chars
into bug reports, without a problem of any kind of unexpected
conversion.  See that bug thread for more info, maybe.

reply via email to

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