git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: Re: [PATCH] Remove pdf target from Makefiles
Date: Tue, 18 Jun 2013 09:19:46 -0700	[thread overview]
Message-ID: <20130618161946.GA2887@elie.Belkin> (raw)
In-Reply-To: <146574770.2154401.1371542391078.JavaMail.ngmail@webmail18.arcor-online.net>

Thomas Ackermann wrote:

>>                                 Would generating different XML files
>> for the PDF and for other purposes (with different names) work as a
>> way to achieve that without losing the printable manual?
>
> This would be even worse when we have to create different xml depending on the
> wanted output. The problem here is in the xml->pdf/html step: I wanted to change
> the formatting of links in the pdf from "Section <number>" to "<section_name>" to
> make it the same as in the html. Thereby I noticed that the definition for this is
> in files from /etc/asciidoc/dblatex. So to change it we have to introduce our own files
> in ./Documentation and work on them to bring the formatting of user-manual.html
> and user-manual.pdf closer together.

Now I'm even more confused. ;-)

If I understood the original commit message correctly, you were saying
the XML file was not suitable for html generation and you wanted to
tweak it, and were dropping the PDF target to avoid breaking it.  Now
if I understand correctly you are saying the XML file actually *is*
suitable for html generation, and that the html generation rules just
need tweaking.  In that case, why remove the PDF target?

Puzzled,
Jonathan

      reply	other threads:[~2013-06-18 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18  7:59 Aw: Re: [PATCH] Remove pdf target from Makefiles Thomas Ackermann
2013-06-18 16:19 ` Jonathan Nieder [this message]

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=20130618161946.GA2887@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=th.acker@arcor.de \
    /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 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).