All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Fonseca <fonseca@diku.dk>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Adam Flott <adam@npjh.com>,
	git@vger.kernel.org
Subject: Re: man pages are littered with .ft C and others
Date: Tue, 5 Feb 2008 01:00:48 +0100	[thread overview]
Message-ID: <20080205000048.GA28020@diku.dk> (raw)
In-Reply-To: <200802050026.22262.jnareb@gmail.com>

Jakub Narebski <jnareb@gmail.com> wrote Tue, Feb 05, 2008:
> On Mon, 4 Feb 2008, Jonas Fonseca wrote:
> > Jakub Narebski <jnareb@gmail.com> wrote Sun, Feb 03, 2008:
> > > Junio C Hamano wrote:
> > > > Jakub Narebski <jnareb@gmail.com> writes:
> > > >
> > > > [From] http://thread.gmane.org/gmane.comp.version-control.git/53457/focus=53458
> > > Julian Phillips:
> > > > Are you using docbook xsl 1.72?  There are known problems building the 
> > > > manpages with that version.  1.71 works, and 1.73 should work when it get 
> > > > released.
> > 
> > I was able to solve this problem with this patch, which adds a XSL file
> > used specifically for DOCBOOK_XSL_172=YesPlease and where dots and
> > backslashes are escaped properly so they won't be substituted to the
> > wrong thing further down the "DocBook XSL pipeline". Doing the escaping
> > in the existing callout.xsl breaks v1.70.1. Hopefully v1.73 will end
> > this part of the manpage nightmare.
> 
> I have applied this patch, and it makes manpages worse, not better.
> I use DocBook XSL version 1.68.1

OK, I might have been a bit unclear, but the patch was not intended for
you but for users of version 1.72+. ;)

> P.S. writing subset of AsciiDoc in Perl, which would write manpages, HTML
> and perhaps info/texinfo files directly, without fragile xmlto toolchain,
> looks better and better...

But not as easy as just pulling the documentation branches.

-- 
Jonas Fonseca

  reply	other threads:[~2008-02-05  0:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 17:25 man pages are littered with .ft C and others Adam Flott
2008-02-02 17:46 ` Geert Bosch
2008-02-02 18:49 ` Jakub Narebski
2008-02-03  8:36   ` Junio C Hamano
2008-02-03 10:39     ` Jakub Narebski
2008-02-04 22:01       ` Jonas Fonseca
2008-02-04 23:26         ` Jakub Narebski
2008-02-05  0:00           ` Jonas Fonseca [this message]
2008-02-05  0:28             ` Junio C Hamano
2008-02-05  1:21           ` Jakub Narebski
2008-02-05  9:59         ` 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=20080205000048.GA28020@diku.dk \
    --to=fonseca@diku.dk \
    --cc=adam@npjh.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.