git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thomas Ackermann <th.acker@arcor.de>
To: jrnieder@gmail.com, th.acker@arcor.de
Cc: git@vger.kernel.org
Subject: Aw: Re: Re: [PATCH] Remove pdf target from Makefiles
Date: Tue, 18 Jun 2013 19:30:37 +0200 (CEST)	[thread overview]
Message-ID: <1169504685.1649588.1371576637888.JavaMail.ngmail@webmail20.arcor-online.net> (raw)

> 
> 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?
> 
The latter is correct ;-)
In my commit message I talked about style files meaning
/etc/asciidoc/dblatex/asciidoc-dblatex.xsl and /etc/asciidoc/dblatex/asciidoc-dblatex.sty
which are used when creating user-manual.pdf out of user-manual.xml
and ./Documentation/docbook.xsl which is used for creating user-manual.html
out of user-manual.xml.
When I want to tweak the html generation rules I also have to tweak the pdf
generation rules because html and pdf should be as similiar to each other as
possible. But the pdf rules are global rules so we have to introduce rules
local to git and also tweak both rule sets in parallel.
I asked myself "Is this really worth the effort or should we drop user-manual.pdf 
and spend our efforts better on user-manual.txt and user-manual.html?"
and so came up with this patch ...


---
Thomas

             reply	other threads:[~2013-06-18 17:30 UTC|newest]

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

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1169504685.1649588.1371576637888.JavaMail.ngmail@webmail20.arcor-online.net \
    --to=th.acker@arcor.de \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).