GNU bug report logs -
#16292
24.3.50; info docs now contain single straight quotes instead of `'
Previous Next
Reported by: Gregor Zattler <grfz <at> gmx.de>
Date: Sun, 29 Dec 2013 22:10:01 UTC
Severity: wishlist
Found in version 24.3.50
Fixed in version 24.4
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Fri, 02 May 2014 20:55:47 -0400
with message-id <2wvbtnisto.fsf <at> fencepost.gnu.org>
and subject line Re: bug#16292: 24.3.50; info docs now contain single straight quotes instead of `'
has caused the debbugs.gnu.org bug report #16292,
regarding 24.3.50; info docs now contain single straight quotes instead of `'
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
16292: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16292
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Dear emacs developers,
when I do a `make docs' the generated info files do not contain
`' -quotes any more but '' -quotes.
This breaks e.g. info+ fontification (a very helpful feature).
Reason is makeinfo >=5 produces either single straight quotes for
info files or single curly ones, depending on the document
encoding:
(from makeinfo maunal:)
'OPEN_QUOTE_SYMBOL'
When an opening quote is needed, e.g., for '@samp' output, use the
specified character; default '‘' for HTML, '‘' for
Docbook. For Info, the default depends on the enabled document
encoding (*note @documentencoding::); if no document encoding
is set, or the encoding is US-ASCII, etc., ''' is used.
This character usually appears as an undirected single quote
on modern systems. If the document encoding is Unicode, the
Info output uses a Unicode left quote.
[...]
(from makeinfo maunal:)
17.2 '@documentencoding ENC': Set Input Encoding
================================================
The '@documentencoding' command declares the input document encoding.
Write it on a line by itself, with a valid encoding specification
following, near the beginning of the file but after '@setfilename'
(*note @setfilename::):
@documentencoding ENC
At present, Texinfo supports only these encodings:
'US-ASCII'
This has no particular effect, but it's included for completeness.
'UTF-8'
The vast global character encoding, expressed in 8-bit bytes.
'ISO-8859-2'
'ISO-8859-1'
'ISO-8859-15'
[...]
Searching texinfos mailing list archives showed that this was
discussed roughly two years before and that it is the result of a
decision to go the same way as the rest of the world which
interprets ` as grave accent:
http://article.gmane.org/gmane.comp.tex.texinfo.bugs/5526/match=single+quotes :
|> For the record, RFC20 says the meaning of character 0x60 is
|> EITHER "grave accent" OR "opening single quotation mark". It
|> then says this character ".. should not be used without
|> determining that there is agreement between sender and recipient"
I think it's highly desirable to be able to tell beginning and
closing of enclosing characters apart. Therefore I consider the
info files single straight quotes a bug. I assume there is a way
to produce `' quotations with modern makeinfo or the *.texi files
should have @documentencoding directives which produce single
curly quotes.
Thanks for your attention, Gregor
[Message part 3 (message/rfc822, inline)]
Version: 24.4
Gregor Zattler wrote:
> or the *.texi files should have @documentencoding directives which
> produce single curly quotes.
They now do so, so the reported issue is fixed.
This bug report was last modified 11 years and 18 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.