Generated.

[homepage.git] / blog / archive / 2012 / 07 / 07.rss

diff --git a/blog/archive/2012/07/07.rss b/blog/archive/2012/07/07.rss
index f042b20ffb1572e2d6df111666e4c679f3b553db..16e1bb2a70c2e9c28ecdb172b445887c992e4acb 100644 (file)
--- a/blog/archive/2012/07/07.rss
+++ b/blog/archive/2012/07/07.rss
@@ -6,6 +6,74 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
 
        
+       <item>
+               <title>Best way to create a docbook book?</title>
+               <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html</link>        
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html</guid>
+                <pubDate>Tue, 31 Jul 2012 22:00:00 +0200</pubDate>
+               <description>&lt;p&gt;I tried to send this text to the
+&lt;a href=&quot;https://lists.oasis-open.org/archives/docbook-apps/&quot;&gt;docbook-apps
+mailing list at lists.oasis-open.org&lt;/a&gt;, but it only accept messages
+from subscribers and rejected my post, and I completely lack the
+bandwidth required to subscribe to another mailing list, so instead I
+try to post my message here and hope my blog readers can help me
+out.&lt;/p&gt;
+
+&lt;p&gt;I am quite new to docbook processing, and am climbing a steep
+learning curve at the moment.&lt;/p&gt;
+
+&lt;p&gt;To give you some background, I am working on a Norwegian
+translation of the book Free Culture by Lawrence Lessig, and I use
+docbook to handle the process.  The files to build the book are
+available from
+&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.
+The book got around 400 pages with parts, images, footnotes, tables,
+index entries etc, which has proven to be a challenge for the free
+software docbook processors.  My build platform is Debian GNU/Linux
+Squeeze.&lt;/p&gt;
+
+&lt;p&gt;I want to build PDF, EPUB and HTML version of the book, and have
+tried different tool chains to do the conversion from docbook to these
+formats.  I am currently focusing on the PDF version, and have a few
+problems.&lt;/p&gt;
+
+&lt;ul&gt;
+
+&lt;li&gt;Using dblatex, the &amp;lt;part&amp;gt; handling is not the way I want to,
+   as &amp;lt;/part&amp;gt; do not really end the &amp;lt;part&amp;gt;. (See
+   &lt;a href=&quot;http://bugs.debian.org/683166&quot;&gt;BTS report #683166&lt;/a&gt;), the
+   xetex backend (needed to process UTF-8) give incorrect hyphens in
+   index references spanning several pages (See
+   &lt;a href=&quot;http://bugs.debian.org/682901&quot;&gt;BTS report #682901&lt;/a&gt;), and
+   I am unable to get the norwegian template texts (See
+   &lt;a href=&quot;http://bugs.debian.org/682936&quot;&gt;BTS report #682936&lt;/a&gt;).&lt;/li&gt;
+
+&lt;li&gt;Using straight xmlto fail with some latex error (See
+   &lt;a href=&quot;http://bugs.debian.org/683163&quot;&gt;BTS report
+   #683163&lt;/a&gt;).&lt;/li&gt;
+
+&lt;li&gt;Using xmlto with the fop backend fail to handle images (do not
+   show up in the PDF), fail to handle a long footnote (overlap
+   footnote and text body, see
+   &lt;a href=&quot;http://bugs.debian.org/683197&quot;&gt;BTS report #683197&lt;/a&gt;), and
+   fail to create a correct index (some lack page ref, and the page
+   refs listed are not right).&lt;/li&gt;
+
+&lt;li&gt;Using xmlto with the dblatex backend behave like dblatex.&lt;/li&gt;
+
+&lt;li&gt;Using docbook-xls with xsltproc + fop have the same footnote and
+   index problems the xmlto + fop processing.&lt;/li&gt;
+
+&lt;/ul&gt;
+
+&lt;p&gt;So I wonder, what would be the best way to create the PDF version
+of this book?  Are some of the bugs found above solved in new or
+experimental versions of some docbook tool chain?&lt;/p&gt;
+
+&lt;p&gt;What about HTML and EPUB versions?&lt;/p&gt;
+</description>
+       </item>
+       
        <item>
                <title>OOXML og standardisering</title>
                <link>http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html</link>        
@@ -1096,12 +1164,12 @@ Nå har jeg holdt øye med alle disse i over en måned, og kan fortelle
 hvor mange priser for 95-oktan bensin de har klart å samle inn i juni
 2012:&lt;/p&gt;
 
-&lt;p&gt;&lt;table border=&quot;1&quot;&gt;
+&lt;table border=&quot;1&quot;&gt;
 &lt;tr&gt;&lt;th&gt;Tjeneste&lt;/th&gt;&lt;th&gt;Antall målinger i juni 2012&lt;/th&gt;&lt;/tr&gt;
 &lt;tr&gt;&lt;td&gt;Bitfactorys bensinpris-app&lt;/td&gt;&lt;td&gt;7687&lt;/td&gt;&lt;/tr&gt;
 &lt;tr&gt;&lt;td&gt;Drivstoffpriser.no&lt;/td&gt;&lt;td&gt;1788&lt;/td&gt;&lt;/tr&gt;
 &lt;tr&gt;&lt;td&gt;Dinsides prisliste&lt;/td&gt;&lt;td&gt;322&lt;/td&gt;&lt;/tr&gt;
-&lt;table&gt;&lt;/p&gt;
+&lt;/table&gt;
 
 &lt;p&gt;Det er dermed åpenbart at Dinsides tjeneste henger langt etter de
 andre to, og at Bitfactorys løsning er den som har størst sjanse for å