From: Thomas Rast <trast@student.ethz.ch> To: <git@vger.kernel.org> Cc: Anders Kaseorg <andersk@mit.edu>, Miklos Vajna <vmiklos@frugalware.org>, Junio C Hamano <gitster@pobox.com>, bill lam <cbill.lam@gmail.com> Subject: [PATCH v3] Quote ' as \(aq in manpages Date: Thu, 22 Oct 2009 10:19:06 +0200 [thread overview] Message-ID: <232607a038ef84087b7c8c69e9038ec6c9f6ba01.1256199311.git.trast@student.ethz.ch> (raw) In-Reply-To: <alpine.DEB.2.00.0910211824220.5105@dr-wily.mit.edu> The docbook/xmlto toolchain insists on quoting ' as \'. This does achieve the quoting goal, but modern 'man' implementations turn the apostrophe into a unicode "proper" apostrophe (given the right circumstances), breaking code examples in many of our manpages. Quote them as \(aq instead, which is an "apostrophe quote" as per the groff_char manpage. Unfortunately, as Anders Kaseorg kindly pointed out, this is not portable beyond groff, so we add an extra Makefile variable GNU_ROFF which you need to enable to get the new quoting. Thanks also to Miklos Vajna for documentation. Signed-off-by: Thomas Rast <trast@student.ethz.ch> --- Anders Kaseorg wrote: > On Wed, 21 Oct 2009, Junio C Hamano wrote: > > > +# Define GNU_ROFF if you have GNU roff and you don't want to have pretty > > > +# apostrophe so that cut&pasting examples to the shell will work. > > > > This makes it sound as if groff is the only roff implementation that has > > this problem---iow, if we use non-GNU roff then the documentation comes > > out just fine. Is that the case? > > Yes: I'll take your word for it, but I cannot test with anything non-GNU. > In order to build a manpage that can be viewed correctly on both > platforms, the conditional logic should live in the manpage itself (as per > the bug comments I linked to and Thomas quoted from). I reworded Miklos' doc patch a bit to indicate that it's about the target system, and also added a slightly longer comment to the Documentation/Makefile for completeness. Documentation/Makefile | 8 ++++++++ Documentation/manpage-quote-apos.xsl | 16 ++++++++++++++++ Makefile | 4 ++++ 3 files changed, 28 insertions(+), 0 deletions(-) create mode 100644 Documentation/manpage-quote-apos.xsl diff --git a/Documentation/Makefile b/Documentation/Makefile index 06b0c57..cd5b439 100644 --- a/Documentation/Makefile +++ b/Documentation/Makefile @@ -103,6 +103,14 @@ ifdef DOCBOOK_SUPPRESS_SP XMLTO_EXTRA += -m manpage-suppress-sp.xsl endif +# If your target system uses GNU groff, it may try to render +# apostrophes as a "pretty" apostrophe using unicode. This breaks +# cut&paste, so you should set GNU_ROFF to force them to be ASCII +# apostrophes. Unfortunately does not work with non-GNU roff. +ifdef GNU_ROFF +XMLTO_EXTRA += -m manpage-quote-apos.xsl +endif + SHELL_PATH ?= $(SHELL) # Shell quote; SHELL_PATH_SQ = $(subst ','\'',$(SHELL_PATH)) diff --git a/Documentation/manpage-quote-apos.xsl b/Documentation/manpage-quote-apos.xsl new file mode 100644 index 0000000..aeb8839 --- /dev/null +++ b/Documentation/manpage-quote-apos.xsl @@ -0,0 +1,16 @@ +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" + version="1.0"> + +<!-- work around newer groff/man setups using a prettier apostrophe + that unfortunately does not quote anything when cut&pasting + examples to the shell --> +<xsl:template name="escape.apostrophe"> + <xsl:param name="content"/> + <xsl:call-template name="string.subst"> + <xsl:with-param name="string" select="$content"/> + <xsl:with-param name="target">'</xsl:with-param> + <xsl:with-param name="replacement">\(aq</xsl:with-param> + </xsl:call-template> +</xsl:template> + +</xsl:stylesheet> diff --git a/Makefile b/Makefile index fea237b..2ccbe4a 100644 --- a/Makefile +++ b/Makefile @@ -159,6 +159,10 @@ all:: # Define ASCIIDOC_NO_ROFF if your DocBook XSL escapes raw roff directives # (versions 1.72 and later and 1.68.1 and earlier). # +# Define GNU_ROFF if your target system uses GNU groff. This forces +# apostrophes to be ASCII so that cut&pasting examples to the shell +# will work. +# # Define NO_PERL_MAKEMAKER if you cannot use Makefiles generated by perl's # MakeMaker (e.g. using ActiveState under Cygwin). # -- 1.6.5.1.144.g316236
next prev parent reply other threads:[~2009-10-22 8:19 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-12 10:29 quote in help code example bill lam 2009-10-12 19:40 ` Miklos Vajna 2009-10-13 2:16 ` bill lam 2009-10-13 10:19 ` Miklos Vajna 2009-10-13 14:06 ` bill lam 2009-10-13 15:30 ` Miklos Vajna 2009-10-13 20:15 ` Thomas Rast 2009-10-15 12:02 ` Thomas Rast 2009-10-21 8:24 ` [PATCH] Quote ' as \(aq in manpages Thomas Rast 2009-10-21 10:38 ` Miklos Vajna 2009-10-21 18:01 ` Anders Kaseorg 2009-10-21 18:57 ` [PATCH v2] " Thomas Rast 2009-10-21 21:31 ` [PATCH] Document GNU_ROFF in Makefile Miklos Vajna 2009-10-21 22:22 ` Junio C Hamano 2009-10-21 22:51 ` Anders Kaseorg 2009-10-22 8:19 ` Thomas Rast [this message] 2009-10-21 21:42 ` [PATCH v2] Quote ' as \(aq in manpages Anders Kaseorg 2009-10-12 21:06 ` quote in help code example Junio C Hamano
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=232607a038ef84087b7c8c69e9038ec6c9f6ba01.1256199311.git.trast@student.ethz.ch \ --to=trast@student.ethz.ch \ --cc=andersk@mit.edu \ --cc=cbill.lam@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=vmiklos@frugalware.org \ --subject='Re: [PATCH v3] Quote '\'' as \(aq in manpages' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).