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 c2dcd42dbedb00ede00e33857e45ee224913a7ed..16e1bb2a70c2e9c28ecdb172b445887c992e4acb 100644 (file)
--- a/blog/archive/2012/07/07.rss
+++ b/blog/archive/2012/07/07.rss
@@ -6,6 +6,117 @@
                 <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>        
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html</guid>
+                <pubDate>Wed, 25 Jul 2012 21:10:00 +0200</pubDate>
+               <description>&lt;p&gt;DIFI har
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html&quot;&gt;en
+høring gående&lt;/a&gt; om ny versjon av statens standardkatalog, med frist
+2012-09-30, der det foreslås å fjerne ODF fra katalogen og ta inn ISO
+OOXML.  I den anledning minnes jeg
+&lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf&quot;&gt;notatet
+FAD skrev&lt;/a&gt; da versjon 2 av standardkatalogen var under
+utarbeidelse, da FAD og DIFI fortsatt forsto poenget med og verdien av
+frie og åpne standarder.&lt;/p&gt;
+
+&lt;p&gt;Det er mange som tror at OOXML er ett spesifikt format, men det
+brukes ofte som fellesbetegnelse for både formatet spesifisert av
+ECMA, ISO, og formatet produsert av Microsoft Office (aka docx), som
+dessverre ikke er det samme formatet.  Fra en av de som implementerte
+støtte for docx-formatet i KDE fikk jeg høre at ISO-spesifikasjonen
+var en nyttig referanse, men at det var mange avvik som gjorde at en
+ikke kunne gå ut ifra at Microsoft Office produserte dokumenter i
+henhold til ISO-spesifikasjonen.&lt;/p&gt;
+
+&lt;p&gt;ISOs OOXML-spesifikasjon har (eller hadde, usikker på om
+kommentaren er oppdatert) i følge
+&lt;a href=&quot;http://surguy.net/articles/ooxml-validation-and-technical-review.xml&quot;&gt;Inigo
+Surguy&lt;/a&gt; feil i mer enn 10% av eksemplene, noe som i tillegg gjør
+det vanskelig å bruke spesifikasjonen til å implementere støtte for
+ISO OOXML.  Jeg har ingen erfaring med å validere OOXML-dokumenter
+selv, men ser at
+&lt;a href=&quot;http://www.microsoft.com/en-us/download/details.aspx?id=5124&quot;&gt;Microsoft
+har laget en validator&lt;/a&gt; som jeg ikke kan teste da den kun er
+tilgjengelig på MS Windows.  Finner også en annen kalt
+&lt;a href=&quot;http://code.google.com/p/officeotron/&quot;&gt;Office-O-Tron&lt;/A&gt; som
+er oppdatert i fjor.  Lurer på om de validerer at dokumenter er i
+formatet til Microsoft office, eller om de validerer at de er i
+henhold til formatene spesifisert av ECMA og ISO. Det hadde også vært
+interessant å se om docx-dokumentene publisert av det offentlige er
+gyldige ISO OOXML-dokumenter.&lt;/p&gt;
+</description>
+       </item>
+       
        <item>
                <title>Free Culture in Norwegian - 5 chapters done, 74 percent left to do</title>
                <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html</link>        
@@ -17,7 +128,7 @@ norwegian version&lt;/a&gt; of the book
 &lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig.
 Progress is good, and yesterday I got a major contribution from Anders
 Hagen Jarmund completing chapter six.  The source files as well as a
-PDF and EPUB version of this book is available from
+PDF and EPUB version of this book are available from
 &lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;
 
 &lt;p&gt;I am happy to report that the draft for the first two chapters
@@ -27,7 +138,7 @@ strings (equivalent to paragraphs) in the book, and there is thus 74
 percent left to translate.  A graph of the progress is present at the
 bottom of the github project page.  There is still room for more
 contributors.  Get in touch or send github pull requests with fixes if
-you got time and am willing to help make this book make it to
+you got time and are willing to help make this book make it to
 print. :)&lt;/p&gt;
 
 &lt;p&gt;The book translation framework could also be a good basis for other
@@ -1053,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 å