<link>http://people.skolelinux.org/pere/blog/</link>
<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
+ <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><p>I tried to send this text to the
+<ahref="https://lists.oasis-open.org/archives/docbook-apps/">docbook-apps
+mailing list at lists.oasis-open.org</a>, 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.</p>
+
+<p>I am quite new to docbook processing, and am climbing a steep
+learning curve at the moment.</p>
+
+<p>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
+<a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.
+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.</p>
+
+<p>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.</p>
+
+<ul>
+
+<li>Using dblatex, the &lt;part&gt; handling is not the way I want to,
+ as &lt;/part&gt; do not really end the &lt;part&gt;. (See
+ <a href="http://bugs.debian.org/683166">BTS report #683166</a>), the
+ xetex backend (needed to process UTF-8) give incorrect hyphens in
+ index references spanning several pages (See
+ <a href="http://bugs.debian.org/682901">BTS report #682901</a>), and
+ I am unable to get the norwegian template texts (See
+ <a href="http://bugs.debian.org/682936">BTS report #682936</a>).</li>
+
+<li>Using straight xmlto fail with some latex error (See
+ <a href="http://bugs.debian.org/683163">BTS report
+ #683163</a>).</li>
+
+<li>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
+ <a href="http://bugs.debian.org/683197">BTS report #683197</a>), and
+ fail to create a correct index (some lack page ref, and the page
+ refs listed are not right).</li>
+
+<li>Using xmlto with the dblatex backend behave like dblatex.</li>
+
+<li>Using docbook-xls with xsltproc + fop have the same footnote and
+ index problems the xmlto + fop processing.</li>
+
+</ul>
+
+<p>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?</p>
+
+<p>What about HTML and EPUB versions?</p>
+</description>
+ </item>
+
<item>
<title>OOXML og standardisering</title>
<link>http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html</link>
</description>
</item>
- <item>
- <title>Mer oppfølging fra MPEG-LA om avtale med dem for å kringkaste og publisere H.264-video</title>
- <link>http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</guid>
- <pubDate>Thu, 5 Jul 2012 23:50:00 +0200</pubDate>
- <description><p>I føljetongen om H.264
-<a href="http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html">forlot
-jeg leserne i undring</a> om hvor pakken fra MPEG-LA tok veien, og om
-hvilke selskaper i Norge som har avtale med MPEG-LA. Da Ryan hos
-MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
-og dagen etter fikk jeg følgende svar derfra:</p>
-
-<p><blockquote>
-<p>Date: Fri, 29 Jun 2012 18:32:34 +0000
-<br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
-<br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
-<br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
-<br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
-
-<p>Dear Mr. Reinholdtsen,</p>
-
-<p>Thank you for your message. As you know, Ryan is currently our of the
-office, so it will be my pleasure to assist you.</p>
-
-<p>Per your request, attached please find an electronic copy of the
-AVC Patent Portfolio License. Please note that the electronic copy of
-the License is provided as a convenience and for informational
-purposes only. When concluding the Licenses, only the hard copies
-provided by MPEG LA may be used.</p>
-
-<p>To your question, MPEG LA lists our Licensees on our website
-according to each program. The lists are in alphabetical order, so it
-is very easy to search.</p>
-
-<p>I hope that this was helpful. If we can be of additional
-assistance, please let me know.</p>
-
-<p>Kind regards,</p>
-
-<p>Sidney A. Wolf
-<br>Manager, Global Licensing
-<br>MPEG LA</p>
-</blockquote></p>
-
-<p>Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
-et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
-som må deles på individuell basis. Opphavsretten krever godkjenning
-fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
-opp med et spørsmål om dette var greit.</p>
-
-<p><blockquote>
-<p>Date: Wed, 4 Jul 2012 20:25:06 +0200
-<br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
-<br>To: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
-<br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
-<br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
-
-<p>Thank you for your reply.</p>
-
-<p>[Sidney Wolf]
-<br>&gt; Per your request, attached please find an electronic copy of the AVC
-<br>&gt; Patent Portfolio License. Please note that the electronic copy of
-<br>&gt; the License is provided as a convenience and for informational
-<br>&gt; purposes only. When concluding the Licenses, only the hard copies
-<br>&gt; provided by MPEG LA may be used.</p>
-
-<p>This is useful for me to learn, but the reason I asked for the
-Internet address of the licensing document was to ensure I could
-publish a link to it when I discuss the topic of H.264 licensing here
-in Norway, and allow others to verify my observations. I can not do
-the same with an email attachment. Thus I would like to ask you if it
-is OK with MPEG LA that I publish this document on the Internet for
-others to read?</p>
-
-<p>&gt; To your question, MPEG LA lists our Licensees on our website
-<br>&gt; according to each program. The lists are in alphabetical order, so
-<br>&gt; it is very easy to search.</p>
-
-<p>I am afraid this do not help me locate Norwegian companies in the
-list of Licensees. I do not know the name of all companies and
-organisations in Norway, and thus do not know how to locate the
-Norwegian ones on that list.</p>
-
-<p>&gt; I hope that this was helpful. If we can be of additional assistance,
-<br>&gt; please let me know.</p>
-
-<p>Absoutely helpful to learn more about how MPEG LA handle licensing.</p>
-
-<p>--
-<br>Happy hacking
-<br>Petter Reinholdtsen</p>
-</blockquote></p>
-
-<p>Jeg håpet også at det skulle være mulig å få vite hvilke av de
-mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
-i Norge. Begge mine håp falt i grus med svaret fra MPEG-LA.
-
-<p><blockquote>
-<p>Date: Thu, 5 Jul 2012 17:42:39 +0000
-<br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
-<br>To: 'Petter Reinholdtsen' &lt;pere (at) hungry.com&gt;
-<br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
-<br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
-
-<p>Dear Mr. Reinholdtsen,</p>
-
-<p>Thank you for your reply.</p>
-
-<p>We appreciate the additional explanation you have provided and for
-asking our permission to publish the electronic copy of the License in
-advance of doing so. Typically, MPEG LA prefers to distribute the
-electronic copies of our Licenses to interested parties. Therefore,
-please feel free to send interested parties to the AVC portion of our
-website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
-their further reference.</p>
-
-<p>As previously mentioned, MPEG LA maintains a list of Licensees in good
-standing on our website according to each program. Due to the large
-volume of Licensees, it would be administratively impractical to
-provide this level of detail to interested parties. Therefore, I am
-afraid we are not in a position to assist you with your request.</p>
-
-<p>Kind regards,</p>
-
-<p>Sidney A. Wolf
-<br>Manager, Global Licensing
-<br>MPEG LA</p>
-</blockquote></p>
-
-<p>Men takket være epostvedlegget kunne jeg søke på Google etter
-setningen "WHEREAS, a video standard commonly referred to as AVC has
-been defined and is referred to in this Agreement as the “AVC
-Standard” (as more fully defined herein below)" som finnes i avtalen,
-og lokalisere en kopi fra 2007 av
-<a href="http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm">lisensavtalen
-mellom MPEG-LA og DivX, Inc.</a>, slik at mine lesere kan se hvordan
-avtalen så ut da. Jeg har ikke sammenlignet tekstene for å se om noe
-har endret seg siden den tid, men satser på at teksten er representativ.</p>
-
-<p>Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
-MPEG-LA.</p>
-
-<p>Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
-klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
-interessant bloggpost fra 2010 hos LibreVideo med tittelen
-"<a href="http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/">MPEG-LA
-answers some questions about AVC/H.264 licensing</a>. Anbefales!</p>
-</description>
- </item>
-
</channel>
</rss>
projects / homepage.git / blobdiff