> 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
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
and spend our efforts better on user-manual.txt and user-manual.html?"
and so came up with this patch ...
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html