<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2005/01/03/DocBook-05</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/01/03/DocBook-05"/><id>http://norman.walsh.name/2005/01/03/DocBook-05/comments.atom</id><updated>2012-02-13T08:39:06.18182Z</updated><entry><title>Comment 1 on /2005/01/03/DocBook-05</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/01/03/DocBook-05#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2005-01-04T16:10:41Z</published><updated>2005-01-04T16:10:41Z</updated><author><name>Bruce D'Arcus</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>For me, the most frustrating issue relating to packaging was the DTD-based toolchain.  So, I have my document with its doctype declaration and I want to transform it.  I rummage around and figure out how to get an xslt processor working.  But wait, I can't actually run the damned process because the processor wants to know where the DTD is.</p>

<p>Now I have to figure out how to deal with catalog files (not at all fun!), or I just remove the declaration and try again.  But wait, the document contains entities, and the processor again chokes.</p>

<p>Perhaps with v5, the task can be made easier for new users by simplifying the above mess?  Maybe a simple shell script for running the transformation would help too?</p>
  </div></content></entry><entry><title>Comment 2 on /2005/01/03/DocBook-05</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/01/03/DocBook-05#comment0002"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0002</id><published>2005-01-09T18:43:37Z</published><updated>2005-01-09T18:43:37Z</updated><author><name>Jeroen Ruigrok van der Werven</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>FreeBSD has a textproc/xmlcatmgr (which I think comes from NetBSD) that automates registration of new DTDs in the catalogs.  Might be useful?</p>
  </div></content></entry><entry><title>Comment 3 on /2005/01/03/DocBook-05</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/01/03/DocBook-05#comment0003"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0003</id><published>2005-01-10T19:04:42Z</published><updated>2005-01-10T19:04:42Z</updated><author><name>Ismael Olea</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>IMO, xmlto (http://freshmeat.net/projects/xmlto/) is a great and stable wrapper for xml processing. Is available for years in all main Linux distros AFAIK. I feel using something like:
</p><pre>
    $ xmlto pdf document.xml
    $ xmlto xhtml document.xml
</pre>

is not so hard for a user.
<p>
 Thus, xmlto and the the related packages is a present packaging solution in *IX, where we have a well structured catalog registry system  and filesystem standar which keeps things clear and easy to use with the remote package updaters like yum, urpmi or apt.

</p><p>
An about whishes, I think the present stylesheets still needs a lot of love. The present output, specially the PDF one is not as beauty as I think it could be. And nicer PDF and HTML would be an eternal gift for the users :-D</p></div></content></entry><entry><title>Comment 4 on /2005/01/03/DocBook-05</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/01/03/DocBook-05#comment0004"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0004</id><published>2005-01-17T03:33:44Z</published><updated>2005-01-17T03:33:44Z</updated><author><name>Ian E. Gorman</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>"Better Packaging for Users."
The "Docbook Element Reference" in the Docbook 5.0 Definitive Guide is a _big_ improvement in this area.  The content model is now formatted for eyeball parsers.  I found the reference section (operator definitions!) and the examples in Chapter 2 (the cookbook) essential to getting started, and would have found it easier with the new Definitive Guide.</p>
  </div></content></entry><entry><title>Comment 5 on /2005/01/03/DocBook-05</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/01/03/DocBook-05#comment0005"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0005</id><published>2007-03-14T10:12:08Z</published><updated>2007-03-14T10:12:08Z</updated><author><name>Matej Cepl</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Docbook reference as info file for Emacs.</p>
  </div></content></entry></feed>

