This is the mail archive of the
glibc-cvs@sourceware.org
mailing list for the glibc project.
GNU C Library master sources branch master updated. glibc-2.22-660-g97ee300
- From: eggert at sourceware dot org
- To: glibc-cvs at sourceware dot org
- Date: 10 Jan 2016 08:21:05 -0000
- Subject: GNU C Library master sources branch master updated. glibc-2.22-660-g97ee300
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via 97ee300903cdc0a0052d09ed7c3f7779a303d625 (commit)
from 812618055e5645473dc6d991b5954e40fc4dc2b5 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=97ee300903cdc0a0052d09ed7c3f7779a303d625
commit 97ee300903cdc0a0052d09ed7c3f7779a303d625
Author: Paul Eggert <eggert@cs.ucla.edu>
Date: Sun Jan 10 00:20:03 2016 -0800
Fix doc quoting problems with Texinfo 5
Without this change, in the info file output, Texinfo 5 quotes code
in text with undirected single quotes 'like this' and generates
code examples that with many PDF readers cannot be cut out of PDFs
and pasted into code.
* manual/libc.texinfo: Configure the libc manual like the GNU
Emacs manual, by using @documentencoding and setting
txicodequoteundirected and txicodequotebacktick. This way,
Texinfo 5 quotes code in text with directed single quotes â??like
thisâ?? and produces examples that can be cut out of PDFs. This
change causes Texinfo 5 to generate info files that contain UTF-8
characters in the set {'â??', 'â??', 'â??', 'â??', 'Ã?', 'ä', 'ö', 'â??',
'â??', 'â??', '©', 'â??', 'â?¢', 'â?¦'}, which is OK nowadays.
diff --git a/ChangeLog b/ChangeLog
index 515d173..5392b11 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,19 @@
+2016-01-10 Paul Eggert <eggert@cs.ucla.edu>
+
+ Fix doc quoting problems with Texinfo 5
+ Without this change, in the info file output, Texinfo 5 quotes code
+ in text with undirected single quotes 'like this' and generates
+ code examples that with many PDF readers cannot be cut out of PDFs
+ and pasted into code.
+ * manual/libc.texinfo: Configure the libc manual like the GNU
+ Emacs manual, by using @documentencoding and setting
+ txicodequoteundirected and txicodequotebacktick. This way,
+ Texinfo 5 quotes code in text with directed single quotes â??like
+ thisâ?? and produces examples that can be cut out of PDFs. This
+ change causes Texinfo 5 to generate info files that contain UTF-8
+ characters in the set {'â??', 'â??', 'â??', 'â??', 'Ã?', 'ä', 'ö', 'â??',
+ 'â??', 'â??', '©', 'â??', 'â?¢', 'â?¦'}, which is OK nowadays.
+
2016-01-08 Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
* sysdeps/unix/sysv/linux/powerpc/htm.h (__libc_tbegin,
diff --git a/manual/libc.texinfo b/manual/libc.texinfo
index 573c30f..c4138db 100644
--- a/manual/libc.texinfo
+++ b/manual/libc.texinfo
@@ -2,6 +2,13 @@
@comment %**start of header (This is for running Texinfo on a region.)
@setfilename libc.info
@settitle The GNU C Library
+@documentencoding UTF-8
+@c '@codequotebacktick on' and '@codequoteundirected on' require
+@c Texinfo 5.0 or later, so use the older equivalent @set variables
+@c supported in Texinfo 4.11 and later.
+@set txicodequoteundirected
+@set txicodequotebacktick
+
@c setchapternewpage odd
@include macros.texi
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 16 ++++++++++++++++
manual/libc.texinfo | 7 +++++++
2 files changed, 23 insertions(+), 0 deletions(-)
hooks/post-receive
--
GNU C Library master sources