1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged docbook
</title>
5 <description>Entries tagged docbook
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Typesetting a short story using docbook for PDF, HTML and EPUB
</title>
11 <link>http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</guid>
13 <pubDate>Sun,
24 Mar
2013 17:
30:
00 +
0100</pubDate>
14 <description><p
>A few days ago, during a discussion in
15 <a href=
"http://www.efn.no/
">EFN
</a
> about interesting books to read
16 about copyright and the data retention directive, a suggestion to read
17 the
1968 short story Kodémus by
18 <a href=
"http://web2.gyldendal.no/toraage/
">Tore Åge Bringsværd
</a
>
19 came up. The text was only available in old paper books, and thus not
20 easily available for current and future generations. Some of the
21 people participating in the discussion contacted the author, and
22 reported back
2013-
03-
19 that the author was OK with releasing the
23 short story using a
<a href=
"http://www.creativecommons.org/
">Creative
24 Commons
</a
> license. The text was quickly scanned and OCR-ed, and we
25 were ready to start on the editing and typesetting.
</p
>
27 <p
>As I already had some experience formatting text in my project to
28 provide a Norwegian version of the Free Culture book by Lawrence
29 Lessig, I chipped in and set up a
30 <a href=
"http://www.docbook.org/
">DocBook
</a
> processing framework to
31 generate PDF, HTML and EPUB version of the short story. The tools to
32 transform DocBook to different formats are already in my Linux
33 distribution of choice,
<a href=
"http://www.debian.org/
">Debian
</a
>, so
34 all I had to do was to use the
35 <a href=
"http://dblatex.sourceforge.net/
">dblatex
</a
>,
36 <a href=
"http://docbook.sourceforge.net/release/xsl/current/epub/README
">dbtoepub
</a
>
37 and
<a href=
"https://fedorahosted.org/xmlto/
">xmlto
</a
> tools to do the
38 conversion. After a few days, we decided to replace dblatex with
40 <a href=
"http://wiki.docbook.org/DocBookXslStylesheets
">docbook-xsl
</a
>),
41 to get the copyright information to show up in the PDF and to get a
42 nicer
&lt;variablelist
&gt; typesetting, but that is just a minor
43 technical detail.
</p
>
45 <p
>There were a few challenges, of course. We want to typeset the
46 short story to look like the original, and that require fairly good
47 control over the layout. The original short story have three
48 parts/scenes separated by a single horizontally centred star (*), and
49 the paragraphs do not contain only flowing text, but dialogs and text
50 that started on a new line in the middle of the paragraph.
</p
>
52 <p
>I initially solved the first challenge by using a paragraph with a
53 single star in it, ie
&lt;para
&gt;*
&lt;/para
&gt;, but it made sure a
54 placeholder indicated where the scene shifted. This did not look too
55 good without the centring. The next approach was to create a new
56 preprocessor directive
&lt;?newscene?
&gt;, mapping to
"&lt;hr/
&gt;
"
57 for HTML and
"&lt;fo:block text-align=
"center
"&gt;
&lt;fo:leader
58 leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
&lt;/fo:block
&gt;
"
59 for FO/PDF output (did not try to implement this in dblatex, as we had
60 switched at this time). The HTML XSL file looked like this:
</p
>
62 <p
><blockquote
><pre
>
63 &lt;?xml version=
'1.0'?
&gt;
64 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
65 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
67 &lt;/xsl:template
&gt;
68 &lt;/xsl:stylesheet
&gt;
69 </pre
></blockquote
></p
>
71 <p
>And the FO/PDF XSL file looked like this:
</p
>
73 <p
><blockquote
><pre
>
74 &lt;?xml version=
'1.0'?
&gt;
75 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
76 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
77 &lt;fo:block text-align=
"center
"&gt;
78 &lt;fo:leader leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
79 &lt;/fo:block
&gt;
80 &lt;/xsl:template
&gt;
81 &lt;/xsl:stylesheet
&gt;
82 </pre
></blockquote
></p
>
84 <p
>Finally, I came across the
&lt;bridgehead
&gt; tag, which seem to be
85 a good fit for the task at hand, and I replaced
&lt;?newscene?
&gt;
86 with
&lt;bridgehead
&gt;*
&lt;/bridgehead
&gt;. It isn
't centred, but we
87 can fix it with some XSL rule if the current visual layout isn
't
90 <p
>I did not find a good DocBook compliant way to solve the
91 linebreak/paragraph challenge, so I ended up creating a new processor
92 directive
&lt;?linebreak?
&gt;, mapping to
&lt;br/
&gt; in HTML, and
93 &lt;fo:block/
&gt; in FO/PDF. I suspect there are better ways to do
94 this, and welcome ideas and patches on github. The HTML XSL file now
95 look like this:
</p
>
97 <p
><blockquote
><pre
>
98 &lt;?xml version=
'1.0'?
&gt;
99 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
100 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
102 &lt;/xsl:template
&gt;
103 &lt;/xsl:stylesheet
&gt;
104 </pre
></blockquote
></p
>
106 <p
>And the FO/PDF XSL file looked like this:
</p
>
108 <p
><blockquote
><pre
>
109 &lt;?xml version=
'1.0'?
&gt;
110 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'
111 xmlns:fo=
"http://www.w3.org/
1999/XSL/Format
"&gt;
112 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
113 &lt;fo:block/
&gt;
114 &lt;/xsl:template
&gt;
115 &lt;/xsl:stylesheet
&gt;
116 </pre
></blockquote
></p
>
118 <p
>One unsolved challenge is our wish to expose different ISBN numbers
119 per publication format, while keeping all of them in some conditional
120 structure in the DocBook source. No idea how to do this, so we ended
121 up listing all the ISBN numbers next to their format in the colophon
124 <p
>If you want to check out the finished result, check out the
125 <a href=
"https://github.com/sickel/kodemus
">source repository at
127 (
<a href=
"https://github.com/EFN/kodemus
">future/new/official
128 repository
</a
>). We expect it to be ready and announced in a few
134 <title>Seventy percent done with Norwegian docbook version of Free Culture
</title>
135 <link>http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</link>
136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</guid>
137 <pubDate>Sun,
23 Sep
2012 09:
30:
00 +
0200</pubDate>
138 <description><p
>Since this summer, I have worked in my spare time on a Norwegian
<a
139 href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
<a
140 href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
141 The reason is that this book is a great primer on what problems exist
142 in the current copyright laws, and I want it to be available also for
143 those that are reluctant do read an English book.
146 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
147 for volunteers
</a
> to help me, but too few have volunteered so far,
148 and progress is a bit slow. Anyway, today I broken the
70 percent
149 mark for the first rough translation. At the moment, less than
700
150 strings (paragraphs, index terms, titles) are left to translate. With
151 my current progress of
10-
20 strings per day, it will take a while to
152 complete the translation. This graph show the updated progress:
</p
>
154 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
156 <p
>Progress have slowed down lately due to family and work
157 commitments. If you want to help, please get in touch, and check out
158 the project files currently available from
159 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
161 <p
>If you are curious what the translated book currently look like,
163 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
165 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
166 are published on github. The HTML version is published as well, but
167 github hand it out with MIME type text/plain, confusing browsers, so I
168 saw no point in linking to that version.
</p
>
173 <title>Half way there with translated docbook version of Free Culture
</title>
174 <link>http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</link>
175 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</guid>
176 <pubDate>Fri,
17 Aug
2012 21:
50:
00 +
0200</pubDate>
177 <description><p
>In my spare time, I currently work on a Norwegian
178 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
179 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
180 to get a Norwegian text explaining the problems with the copyright law
181 I can give to my parents and others that are reluctant to read an
182 English book. It is a marvellous set of examples on how the ever
183 expanding copyright regulations hurt culture and society. When the
184 translation is done, I hope to find funding to print and ship a copy
185 to all the members of the Norwegian parliament, before they sit down
186 to debate the latest revisions to the Norwegian copyright law. This
188 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
189 for volunteers
</a
> to help me, and I have been able to secure the
190 valuable contribution from at least one other Norwegian.
</p
>
192 <p
>Two days ago, we finally broke the
50% mark. Then more than
50% of
193 the number of strings to translate (normally paragraphs, but also
194 titles and index entries are also counted). All parts from the
195 beginning up to and including chapter four is translated. So is
196 chapters six, seven and the conclusion. I created a graph to show the
199 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
201 <p
>The number of strings to translate increase as I insert the index
202 entries into the docbook. They were missing with the docbook version
203 I initially started with. There are still quite a few index entries
204 missing, but everyone starting with A, B, O, Z and Y are done. I
205 currently focus on completing the index entries, to get a complete
206 english version of the docbook source.
</p
>
208 <p
>There is still need for translators and people with docbook
209 knowledge, to be able to get a good looking book (I still struggle
210 with dblatex, xmlto and docbook-xsl) as well as to do the draft
211 translation and proof reading. And I would like the figures to be
212 redrawn as SVGs to make it easy to translate them. Any SVG master
213 around? I am sure there are some legal terms that are unfamiliar to
214 me. If you want to help, please get in touch, and check out the
215 project files currently available from
<a
216 href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
218 <p
>If you are curious what the translated book currently look like,
220 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
222 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
223 are published on github. The HTML version is published as well, but
224 github hand it out with MIME type text/plain, confusing browsers, so I
225 saw no point in linking to that version.
</p
>
230 <title>Notes on language codes for Norwegian docbook processing...
</title>
231 <link>http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</link>
232 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</guid>
233 <pubDate>Fri,
10 Aug
2012 21:
00:
00 +
0200</pubDate>
234 <description><p
>In
<a href=
"http://www.docbook.org/
">docbook
</a
> one can specify
235 the language used at the top, and the processing pipeline will use
236 this information to pick the correct translations for
'chapter
',
'see
237 also
',
'index
' etc. And for most languages used with docbook, I guess
238 this work just fine. For example a German user can start the document
239 with
&lt;book lang=
"de
"&gt;, and the document will show up with the
240 correct content with any of the docbook processors. This is not the
241 case for the language
242 <a href=
"http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
">I
243 am working with at the moment
</a
>, Norwegian Bokmål.
</p
>
245 <p
>For a while, I was confused about which language code to use,
246 because I was unable to find any language code that would work across
247 all tools. I am currently testing dblatex, xmlto, docbook-xsl, and
248 dbtoepub, and they do not handle Norwegian Bokmål the same way. Some
249 of them do not handle it at all.
</p
>
251 <p
>A bit of background information is probably needed to understand
252 this mess. Norwegian is not one, but two written variants. The
253 variants are Norwegian Nynorsk and Norwegian Bokmål. There are three
254 two letter language codes associated with these languages, Norwegian
255 is
'no
', Norwegian Nynorsk is
'nn
' and Norwegian Bokmål is
'nb
'.
256 Historically the
'no
' language code was used for Norwegian Bokmål, but
257 many years ago this was found to be å bad idea, and the recommendation
258 is to use the most specific language code instead, to avoid confusion.
259 In the transition period it is a good idea to make sure
'no
' was an
260 alias for
'nb
'.
</p
>
262 <p
>Back to docbook processing tools in Debian. The dblatex tool only
263 understand
'nn
'. There are translations for
'no
', but not
'nb
' (BTS
264 <a href=
"http://bugs.debian.org/
684391">#
684391</a
>), but due to a bug
265 (BTS
<a href=
"http://bugs.debian.org/
682936">#
682936</a
>) the
'no
'
266 language code is not recognised. The docbook-xsl tool chain only
267 recognise
'nn
' and
'nb
', but not
'no
'. The xmlto tool only recognise
268 'nn
' and
'nb
', but not
'no
'. The end result that there is no language
269 code I can use to get the docbook file working with all of these tools
270 at the same time. :(
</p
>
272 <p
>The correct solution is to use
&lt;book lang=
"nb
"&gt;, but it will
273 take time before that will work with all the free software docbook
274 processors. :(
</p
>
276 <p
>Oh, the joy of well integrated tools. :/
</p
>
281 <title>Best way to create a docbook book?
</title>
282 <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</link>
283 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</guid>
284 <pubDate>Tue,
31 Jul
2012 22:
00:
00 +
0200</pubDate>
285 <description><p
>I tried to send this text to the
286 <a href=
"https://lists.oasis-open.org/archives/docbook-apps/
">docbook-apps
287 mailing list at lists.oasis-open.org
</a
>, but it only accept messages
288 from subscribers and rejected my post, and I completely lack the
289 bandwidth required to subscribe to another mailing list, so instead I
290 try to post my message here and hope my blog readers can help me
293 <p
>I am quite new to docbook processing, and am climbing a steep
294 learning curve at the moment.
</p
>
296 <p
>To give you some background, I am working on a Norwegian
297 translation of the book Free Culture by Lawrence Lessig, and I use
298 docbook to handle the process. The files to build the book are
300 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
301 The book got around
400 pages with parts, images, footnotes, tables,
302 index entries etc, which has proven to be a challenge for the free
303 software docbook processors. My build platform is Debian GNU/Linux
306 <p
>I want to build PDF, EPUB and HTML version of the book, and have
307 tried different tool chains to do the conversion from docbook to these
308 formats. I am currently focusing on the PDF version, and have a few
313 <li
>Using dblatex, the
&lt;part
&gt; handling is not the way I want to,
314 as
&lt;/part
&gt; do not really end the
&lt;part
&gt;. (See
315 <a href=
"http://bugs.debian.org/
683166">BTS report #
683166</a
>), the
316 xetex backend (needed to process UTF-
8) give incorrect hyphens in
317 index references spanning several pages (See
318 <a href=
"http://bugs.debian.org/
682901">BTS report #
682901</a
>), and
319 I am unable to get the norwegian template texts (See
320 <a href=
"http://bugs.debian.org/
682936">BTS report #
682936</a
>).
</li
>
322 <li
>Using straight xmlto fail with some latex error (See
323 <a href=
"http://bugs.debian.org/
683163">BTS report
324 #
683163</a
>).
</li
>
326 <li
>Using xmlto with the fop backend fail to handle images (do not
327 show up in the PDF), fail to handle a long footnote (overlap
328 footnote and text body, see
329 <a href=
"http://bugs.debian.org/
683197">BTS report #
683197</a
>), and
330 fail to create a correct index (some lack page ref, and the page
331 refs listed are not right).
</li
>
333 <li
>Using xmlto with the dblatex backend behave like dblatex.
</li
>
335 <li
>Using docbook-xls with xsltproc + fop have the same footnote and
336 index problems the xmlto + fop processing.
</li
>
340 <p
>So I wonder, what would be the best way to create the PDF version
341 of this book? Are some of the bugs found above solved in new or
342 experimental versions of some docbook tool chain?
</p
>
344 <p
>What about HTML and EPUB versions?
</p
>
349 <title>Free Culture in Norwegian -
5 chapters done,
74 percent left to do
</title>
350 <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</link>
351 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</guid>
352 <pubDate>Sat,
21 Jul
2012 20:
00:
00 +
0200</pubDate>
353 <description><p
>I reported earlier that I am working on
354 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">a
355 norwegian version
</a
> of the book
356 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
357 Progress is good, and yesterday I got a major contribution from Anders
358 Hagen Jarmund completing chapter six. The source files as well as a
359 PDF and EPUB version of this book are available from
360 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
362 <p
>I am happy to report that the draft for the first two chapters
363 (preface, introduction) is complete, and three other chapters are also
364 completely translated. This completes
26 percent of the number of
365 strings (equivalent to paragraphs) in the book, and there is thus
74
366 percent left to translate. A graph of the progress is present at the
367 bottom of the github project page. There is still room for more
368 contributors. Get in touch or send github pull requests with fixes if
369 you got time and are willing to help make this book make it to
372 <p
>The book translation framework could also be a good basis for other
373 translations, if you want the book to be available in your
379 <title>Call for help from docbook expert to tag Free Culture by Lawrence Lessig
</title>
380 <link>http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</link>
381 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</guid>
382 <pubDate>Mon,
16 Jul
2012 22:
50:
00 +
0200</pubDate>
383 <description><p
>I am currently working on a
384 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">project
385 to translate
</a
> the book
386 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig
387 to Norwegian. And the source we base our translation on is the
388 <a href=
"http://en.wikipedia.org/wiki/DocBook
">docbook
</a
> version, to
389 allow us to use po4a and .po files to handle the translation, and for
390 this to work well the docbook source document need to be properly
391 tagged. The source files of this project is available from
392 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
394 <p
>The problem is that the docbook source have flaws, and we have
395 no-one involved in the project that is a docbook expert. Is there a
396 docbook expert somewhere that is interested in helping us create a
397 well tagged docbook version of the book, and adjust our build process
398 for the PDF, EPUB and HTML version of the book? This will provide a
399 well tagged English version (our source document), and make it a lot
400 easier for us to create a good Norwegian version. If you can and want
401 to help, please get in touch with me or fork the github project and
402 send pull requests with fixes. :)
</p
>
407 <title>Dugnad for å sende norsk versjon av Free Culture til stortingets representanter!
</title>
408 <link>http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</link>
409 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</guid>
410 <pubDate>Wed,
11 Jul
2012 09:
00:
00 +
0200</pubDate>
411 <description><p
>Da opphavsrettsloven ble revidert i forrige runde rundt
2005, var
412 det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
413 Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
414 og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
415 representanter fikk en norsk utgave av boken
416 <a href=
"http://free-culture.cc/
">Free Culture
</a
> av Lawrence Lessig
417 som forklarte litt om problemstillingene. Vi endte opp med å
418 prioritere utvikling i
419 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>-prosjektet i
420 stedet, så den oversatte boken så aldri dagens lys. Men i forrige uke
421 ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
422 bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
423 sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
424 fordel for forlag og store mediehus fortsatt trenger en annen vinkling
425 i debatten.
</p
>
427 <p
>Planen min er å oversette boka på dugnad, sette den opp for
428 trykking med en av de mange
429 <a href=
"http://no.wikipedia.org/wiki/Trykk_på_forespørsel
">trykk på
430 forespørsel
</a
>-tjenestene, skaffe sponsor til å finansiere trykking
431 til stortingsrepresentantene og alle som har bidratt med
432 oversettelser. Kanskje vi også kan få en avtale med et forlag om
433 publisering når boka er ferdig? Kommentarene til
434 <a href=
"http://newth.net/eirik/
2011/
04/
01/e-selvpublisering/
">Eirik
436 <a href=
"http://www.espen.com/norskblogg/archives/
2008/
09/erfaringer_med_publishing_on_demand.html
">Espen
437 Andersen
</a
> om erfaringene med selvpublisering og trykk på
438 forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
439 <a href=
"http://www.lulu.com/
">Lulu
</a
> er en grei leverandør av
440 trykketjenester til prosjektet.
</p
>
442 <p
>Jeg har satt opp
443 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">et
444 Github-prosjekt
</a
> for a lage boken, basert på Docbook-utgaven jeg
445 fant fra Hans Schou. Skolelinux har hatt byggesystem for å lage
446 oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
447 kopiert og utvidet dette oppsettet. Originalteksten er i Docbook, og
448 oversettelsen gjøres i .po-filer med hjelp av vanlige
449 oversetterverktøy brukt i fri programvareverden. Dernest tar
450 byggesystemet over og lager PDF og EPUB-utgave av den oversatte
451 teksten. Resultatet kan ses i Github-prosjektet. For å komme raskt
452 igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
453 til norsk, noe som grovoversatte ca.
1300 av de ca.
1700 tekstbitene
454 boken består av. Jeg håper nå at flere kan bidra med å få
455 oversettelsen på plass, slik at teksten kan være klar i løpet av
456 høsten. Når alt er oversatt må teksten gjennomgås for feil og
457 konsistent språk. Totalt er det nok mange timer som trengs for å
458 gjennomføre oversettelsen.
</p
>
460 <p
>Økonomien i dette er ikke avskrekkende.
169
461 stortingsrepresentanter og nesten like mange varamedlemmer bør få
462 bøker, og estimert produduksjonskostnad for hver bok er rundt
6 EURO i
463 følge et raskt estimat fra Lulu. Jeg vet ennå ikke hvor mange sider
464 det blir i størrelsen
5,
5" x
8.5" (det er ca.
140 sider i A4-format),
465 så jeg gjettet på
400 sider. Jeg tror originalutgaven har nesten
400
466 sider. For
169*
2 eksemplarer snakker vi om en trykkekostnad på
467 ca.
2000 EURO, dvs. ca
15 000 NOK. Det burde være mulig å finne en
468 sponsor for å dekke en slik sum. I tillegg kommer distribusjon og
469 porto, som antagelig kommer på like mye.
</p
>
471 <p
>Kan du bidra med oversettelse og docbook-typesetting? Ta kontakt
472 og send patcher i github. Jeg legger gjerne inn folk i prosjektet
473 slik at du kan oppdatere direkte.
</p
>