How to convert the Guide's xml source files into (chunked) HTML locally?

Marko Käning MK-MacPorts at techno.ms
Sat Oct 30 12:22:49 PDT 2010


Well, now I'm finally able to transform the file I want to manipulate into HTML:
---
MP-devel:resources marko$ xsltproc chunk.xsl ../xml/using.xml
Error: no ID for constraint linkend: reference.phases.
Error: no ID for constraint linkend: internals.images.
Error: no ID for constraint linkend: reference.phases.
Error: no ID for constraint linkend: reference.livecheck.
Error: no ID for constraint linkend: development.
Error: no ID for constraint linkend: development.variants.
Writing using.variants.html for section(using.variants)
Writing using.common-tasks.html for section(using.common-tasks)
Writing using.binaries.html for section(using.binaries)
Writing index.html for chapter(using)
MP-devel:resources marko$ svn st
?       using.common-tasks.html
?       using.binaries.html
?       index.html
?       using.variants.html
M       chunk.xsl
---

I had to adapt the path to the docbook's XSL files on my system like this:
---
MP-devel:resources marko$ svn diff
Index: chunk.xsl
===================================================================
--- chunk.xsl	(revision 72883)
+++ chunk.xsl	(working copy)
@@ -1,5 +1,5 @@
 <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
-    <xsl:import href="xsl/xhtml/chunk.xsl"/>
+    <xsl:import href="/opt/macports-test/share/xsl/docbook-xsl/xhtml/chunk.xsl"/>
     <xsl:include href="base.xsl"/>
     <!-- Include tab switching for chunk and single-page -->
     <xsl:include href="tabs.xsl"/>
MP-devel:resources marko$ 
---

Note that the path is actually xsl/docbook-xsl/xhtml and NOT xsl/xhtml !!!

Hmmm, this all looks like as if the conversion process on MacPorts' svn server is somehow parametrized to avoid this problem. (And I simply don't know the magic…)

Anyway, for now the most important part works: i.e. I am able to locally preview my own changes to the documentation, despite the above errors.
All is fine now, but I am still interested to learn how the documentation is being properly build by MacPorts itself.


I plan to insert a little section to the Guide about how to contribute and test one's own changes to this Guide. :-)


More information about the macports-dev mailing list