Bug#175064: DocBook XML conversion is read with this script
Hi,
On Mon, Apr 25, 2011 at 05:25:31AM -0500, Jonathan Nieder wrote:
> Hi Osamu,
>
> Osamu Aoki wrote:
>
> > By extracting attached file into source and running "make", it will do
> > the magic of converting to DocBok XML and then to PDF etc.
> > (Need the sid version of the latest debiandoc-sgml)
>
> Very neat. I also had to install dblatex. I like the separation
> between automated conversion and patches to fix it up. Some quick
> reactions:
>
> . The generated HTML refers to some missing files like
> "images/prev.gif". I assume "make publish" would have taken care of
> that; maybe it would be possible for a similar target to take care
> of putting a symlink or copy of the images/ dir in the source tree
> for easy previewing.
I was lazy to copy that kind of script to the makefile. You can find it
in maint-guide subversion. This bug report was a reminder and promting
for me to cordinate this conversion with people in charge of publishing
policy. This is to show this conversion is possible with minimal
transtion work.
> . The lack of indentation in the source is nice. Less fussy.
That is not my intention. XML makes no distinction. I think it may be
good idea to run some kind of lint program on XML source.
> . That said, if there were a way to preserve the whitespace of the
> original and just substitute tags (so diff-ing between the before
> and after would be possible), that would be even better. I
> understand that's probably impossible. I fell back to using "git
> diff --no-index --word-diff=color" to find meaningful differences.
If you want to do this, conversion needs to be done differently with
much more manual works.
> . Sometimes the spacing around closing tags looks unidiomatic, as in
>
> ... The detailed
> procedure for gracefully orphaning a package can be found in the Debian
> Developer's Reference (see <xref linkend="related"/> ). </para> </footnote>
I noticed this while working on maint-guide conversion. Bug filed.
> The extra space carries over to the rendered HTML, too. Is that
> intentional?
No.
> . Quotation marks were lost, for example in “Originally called "Debian
> GNU/Linux Policy Manual", ...” at the start of the policy manual.
I was wondering on the same problem on maint-guide conversion. Bug
filed.
> . Aside from the quotation marks and spaces, I couldn't find any
> artifacts. Seems like a good conversion.
I am busy fixing maint-guide now. Please let me know how I get changes
commited. Access to git branch will be nice.
Osamu
> Thanks much; nicely done.
> Jonathan
Reply to: