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>First paper version of the Norwegian Free Culture book heading my way
</title>
11 <link>http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html
</guid>
13 <pubDate>Sun,
9 Aug
2015 10:
15:
00 +
0200</pubDate>
14 <description><p
>Typesetting a book is harder than I hoped. As the translation is
15 mostly done, and a volunteer proof reader was going to check the text
16 on paper, it was time this summer to focus on formatting my translated
17 <a href=
"http://www.docbook.org/
">docbook
</a
> based version of the
18 <a href=
"http://free-culture.cc/
">Free Culture
</a
> book by Lawrence
19 Lessig. I
've been trying to get both docboox-xsl+fop and dblatex to
20 give me a good looking PDF, but in the end I went with dblatex, because
21 its Debian maintainer and upstream developer were responsive and very
22 helpful in solving my formatting challenges.
</p
>
24 <p
>Last night, I finally managed to create a PDF that no longer made
25 <a href=
"http://www.lulu.com/
">Lulu.com
</a
> complain after uploading,
26 and I ordered a text version of the book on paper. It is lacking a
27 proper book cover and is not tagged with the correct ISBN number, but
28 should give me an idea what the finished book will look like.
</p
>
30 <p
>Instead of using Lulu, I did consider printing the book using
31 <a href=
"http://www.createspace.com/
">CreateSpace
</a
>, but ended up
32 using Lulu because it had smaller book size options (CreateSpace seem
33 to lack pocket book with extended distribution). I looked for a
34 similar service in Norway, but have not seen anything so far. Please
35 let me know if I am missing out on something here.
</p
>
37 <p
>But I still struggle to decide the book size. Should I go for
38 pocket book (
4.25x6.875 inches /
10.8x17.5 cm) with
556 pages, digest
39 (
5.5x8.5 inches /
14x21.6 cm) with
323 pages or US Trade (
6x8 inches /
40 15.3x22.9 cm) with
280 pages? Fewer pager give a cheaper book, and a
41 smaller book is easier to carry around. The test book I ordered was
42 pocket book sized, to give me an idea how well that fit in my hand,
43 but I suspect I will end up using a digest sized book in the end to
44 bring the prize down further.
</p
>
46 <p
>My biggest challenge at the moment is making nice cover art. My
47 inkscape skills are not yet up to the task of replicating the original
48 cover in SVG format. I also need to figure out what to write about
49 the book on the back (will most likely use the same text as the
50 description on web based book stores). I would love help with this,
51 if you are willing to license the art source and final version using
52 the same CC license as the book. My artistic skills are not really up
53 to the task.
</p
>
55 <p
>I plan to publish the book in both English and Norwegian and on
56 paper, in PDF form as well as EPUB and MOBI format. The current
57 status can as usual be found on
58 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
59 in the archive/ directory. So far I have spent all time on making the
60 PDF version look good. Someone should probably do the same with the
61 dbtoepub generated e-book. Help is definitely needed here, as I
62 expect to run out of steem before I find time to improve the epub
65 <p
>Please let me know via github if you find typos in the book or
66 discover translations that should be improved. The final proof
67 reading is being done right now, and I expect to publish the finished
68 result in a few months.
</p
>
73 <title>Typesetting DocBook footnotes as endnotes with dblatex
</title>
74 <link>http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html
</link>
75 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html
</guid>
76 <pubDate>Thu,
16 Jul
2015 18:
10:
00 +
0200</pubDate>
77 <description><p
>I
'm still working on the Norwegian version of the
78 <a href=
"http://free-culture.cc/
">Free Culture book by Lawrence
79 Lessig
</a
>, and is now working on the final typesetting and layout.
80 One of the features I want to get the structure similar to the
81 original book is to typeset the footnotes as endnotes in the notes
83 <a href=
"https://bugs.debian.org/
685063">feedback from the Debian
84 maintainer and the dblatex developer
</a
>, I came up with this recipe I
85 would like to share with you. The proposal was to create a new LaTeX
86 class file and add the LaTeX code there, but this is not always
87 practical, when I want to be able to replace the class using a make
88 file variable. So my proposal misuses the latex.begindocument XSL
89 parameter value, to get a small fragment into the correct location in
90 the generated LaTeX File.
</p
>
92 <p
>First, decide where in the DocBook document to place the endnotes,
93 and add this text there:
</p
>
96 &lt;?latex \theendnotes ?
&gt;
99 <p
>Next, create a xsl stylesheet file dblatex-endnotes.xsl to add the
100 code needed to add the endnote instructions in the preamble of the
101 generated LaTeX document, with content like this:
</p
>
104 &lt;?xml version=
'1.0'?
&gt;
105 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
106 &lt;xsl:param name=
"latex.begindocument
"&gt;
107 &lt;xsl:text
&gt;
108 \usepackage{endnotes}
109 \let\footnote=\endnote
110 \def\enoteheading{\mbox{}\par\vskip-\baselineskip }
112 &lt;/xsl:text
&gt;
113 &lt;/xsl:param
&gt;
114 &lt;/xsl:stylesheet
&gt;
117 <p
>Finally, load this xsl file when running dblatex, for example like
121 dblatex --xsl-user=dblatex-endnotes.xsl freeculture.nb.xml
124 <p
>The end result can be seen on github, where
125 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">my
126 book project
</a
> is located.
</p
>
131 <title>Proof reading the Norwegian translation of Free Culture by Lessig
</title>
132 <link>http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html
</link>
133 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html
</guid>
134 <pubDate>Sat,
4 Apr
2015 09:
30:
00 +
0200</pubDate>
135 <description><p
>During eastern I had some time to continue working on the Norwegian
136 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
137 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
138 At the moment I am proof reading the finished text, looking for typos,
139 inconsistent wordings and sentences that do not flow as they should.
140 I
'm more than two thirds done with the text, and welcome others to
141 check the text up to chapter
13. The current status is available on the
142 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
143 project pages. You can also check out the
144 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>,
145 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
146 and HTML version available in the
147 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive
">archive
148 directory
</a
>.
</p
>
150 <p
>Please report typos, bugs and improvements to the github project if
151 you find any.
</p
>
156 <title>98.6 percent done with the Norwegian draft translation of Free Culture
</title>
157 <link>http://people.skolelinux.org/pere/blog/
98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</link>
158 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</guid>
159 <pubDate>Wed,
23 Jul
2014 22:
40:
00 +
0200</pubDate>
160 <description><p
>This summer I finally had time to continue working on the Norwegian
161 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
162 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
163 to get a Norwegian text explaining the problems with todays copyright
164 law. Yesterday, I finally completed translated the book text. There
165 are still some foot/end notes left to translate, the colophon page
166 need to be rewritten, and a few words and phrases still need to be
167 translated, but the Norwegian text is ready for the first proof
168 reading. :) More spell checking is needed, and several illustrations
169 need to be cleaned up. The work stopped up because I had to give
170 priority to other projects the last year, and the progress graph of
171 the translation show this very well:
</p
>
173 <p
><img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
"></p
>
175 <p
>If you want to read the result, check out the
176 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
177 project pages and the
178 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>,
179 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
180 and HTML version available in the
181 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive
">archive
182 directory
</a
>.
</p
>
184 <p
>Please report typos, bugs and improvements to the github project if
185 you find any.
</p
>
190 <title>From English wiki to translated PDF and epub via Docbook
</title>
191 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
192 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
193 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
194 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
195 project
</a
> provide an instruction manual for teachers, system
196 administrators and other users that contain useful tips for setting up
197 and maintaining a Debian Edu installation. This text is about how the
198 text processing of this manual is handled in the project.
</p
>
200 <p
>One goal of the project is to provide information in the native
201 language of its users, and for this we need to handle translations.
202 But we also want to make sure each language contain the same
203 information, so for this we need a good way to keep the translations
204 in sync. And we want it to be easy for our users to improve the
205 documentation, avoiding the need to learn special formats or tools to
206 contribute, and the obvious way to do this is to make it possible to
207 edit the documentation using a web browser. We also want it to be
208 easy for translators to keep the translation up to date, and give them
209 help in figuring out what need to be translated. Here is the list of
210 tools and the process we have found trying to reach all these
213 <p
>We maintain the authoritative source of our manual in the
214 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
215 wiki
</a
>, as several wiki pages written in English. It consist of one
216 front page with references to the different chapters, several pages
217 for each chapter, and finally one
"collection page
" gluing all the
218 chapters together into one large web page (aka
219 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
220 AllInOne page
</a
>). The AllInOne page is the one used for further
221 processing and translations. Thanks to the fact that the
222 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
223 wiki.debian.org support exporting pages in
224 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
225 the list of pages to export using the raw version of the AllInOne
226 page, loop over each of them to generate a Docbook XML version of the
227 manual. This process also download images and transform image
228 references to use the locally downloaded images. The generated
229 Docbook XML files are slightly broken, so some post-processing is done
230 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
231 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
232 a handfull of images. The XML file can now be used to generate PDF, HTML
233 and epub versions of the English manual. This is the basic step of
234 our process, making PDF (using dblatex), HTML (using xsltproc) and
235 epub (using dbtoepub) version from Docbook XML, and the resulting files
236 are placed in the debian-edu-doc-en binary package.
</p
>
238 <p
>But English documentation is not enough for us. We want translated
239 documentation too, and we want to make it easy for translators to
240 track the English original. For this we use the
241 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
242 which allow us to transform the English Docbook XML file into a
243 translation file (a .pot file), usable with the normal gettext based
244 translation tools used by those translating free software. The pot
245 file is used to create and maintain translation files (several .po
246 files), which the translations update with the native language
247 translations of all titles, paragraphs and blocks of text in the
248 original. The next step is combining the original English Docbook XML
249 and the translation file (say debian-edu-wheezy-manual.nb.po), to
250 create a translated Docbook XML file (in this case
251 debian-edu-wheezy-manual.nb.xml). This translated (or partly
252 translated, if the translation is not complete) Docbook XML file can
253 then be used like the original to create a PDF, HTML and epub version
254 of the documentation.
</p
>
256 <p
>The translators use different tools to edit the .po files. We
258 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
259 while some use emacs and vi, others can use web based editors like
260 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
261 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
262 is where the .po file end up, in our git repository. Updated
263 translations can either be committed directly to git, or submitted as
264 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
265 against the debian-edu-doc package
</a
>.
</p
>
267 <p
>One challenge is images, which both might need to be translated (if
268 they show translated user applications), and are needed in different
269 formats when creating PDF and HTML versions (epub is a HTML version in
270 this regard). For this we transform the original PNG images to the
271 needed density and format during build, and have a way to provide
272 translated images by storing translated versions in
273 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
274 package maintainers know more.
</p
>
276 <p
>If you wonder what the result look like, we provide
277 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
278 of the documentation packages on the web
</a
>. See for example the
279 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
280 PDF version
</a
> or the
281 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
282 HTML version
</a
>. We do not yet build the epub version by default,
283 but perhaps it will be done in the future.
</p
>
285 <p
>To learn more, check out
286 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
287 debian-edu-doc package
</a
>,
288 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
289 manual on the wiki
</a
> and
290 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
291 translation instructions
</a
> in the manual.
</p
>
296 <title>90 percent done with the Norwegian draft translation of Free Culture
</title>
297 <link>http://people.skolelinux.org/pere/blog/
90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</link>
298 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</guid>
299 <pubDate>Fri,
2 Aug
2013 10:
40:
00 +
0200</pubDate>
300 <description><p
>It has been a while since my last update. Since last summer, I
301 have worked on a Norwegian
302 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
303 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
304 to get a Norwegian text explaining the problems with the copyright
305 law. Yesterday, I finally broken the
90% mark, when counting the
306 number of strings to translate. Due to real life constraints, I have
307 not had time to work on it since March, but when the summer broke out,
308 I found time to work on it again. Still lots of work left, but the
309 first draft is nearing completion. I created a graph to show the
310 progress of the translation:
</p
>
312 <p
><img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
"></p
>
314 <p
>When the first draft is done, the translated text need to be
315 proof read, and the remaining formatting problems with images and SVG
316 drawings need to be fixed. There are probably also some index entries
317 missing that need to be added. This can be done by comparing the
318 index entries listed in the SiSU version of the book, or comparing the
319 English docbook version with the paper version. Last, the colophon
320 page with ISBN numbers etc need to be wrapped up before the release is
321 done. I should also figure out how to get correct Norwegian sorting
322 of the index pages. All docbook tools I have tried so far (xmlto,
323 docbook-xsl, dblatex) get the order of symbols and the special
324 Norwegian letters ÆØÅ wrong.
</p
>
326 <p
>There is still need for translators and people with docbook
327 knowledge, to be able to get a good looking book (I still struggle
328 with dblatex, xmlto and docbook-xsl) as well as to do the draft
329 translation and proof reading. And I would like the figures to be
330 redrawn as SVGs to make it easy to translate them. Any SVG master
331 around? There are also some legal terms that are unfamiliar to me.
332 If you want to help, please get in touch with me, and check out the
333 project files currently available from
334 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
336 <p
>If you are curious what the translated book currently look like,
338 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
340 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
341 are published on github. The HTML version is published as well, but
342 github hand it out with MIME type text/plain, confusing browsers, so I
343 saw no point in linking to that version.
</p
>
348 <title>EFN nyutgir novellen Kodémus av Tor Åge Bringsværd
</title>
349 <link>http://people.skolelinux.org/pere/blog/EFN_nyutgir_novellen_Kod_mus_av_Tor__ge_Bringsv_rd.html
</link>
350 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/EFN_nyutgir_novellen_Kod_mus_av_Tor__ge_Bringsv_rd.html
</guid>
351 <pubDate>Wed,
27 Mar
2013 09:
50:
00 +
0100</pubDate>
352 <description><p
>For noen dager siden nevnte jeg at vi jobbet med å typesette en
353 novelle med
<a href=
"http://www.docbook.org/
">DocBook
</a
>. I dag ble
354 utgivelsen annonsert med følgende pressemelding fra Elektronisk
355 Forpost Norge), som jeg gjengir i sin helhet:
</p
>
357 <p
><blockquote
>
359 <p
><strong
>EFN nyutgir Kodémus:
</strong
></p
>
361 <p
><strong
>Tor Åge Bringsværd-novelle om IT og overvåkning fra
362 informasjonsteknologiens spedbarndom får nytt liv
</strong
></p
>
364 <p
>Elektronisk Forpost Norge (EFN) er veldig glad for anledningen til
365 å nyutgi Tor Åge Bringsværds novelle Kodémus i digitalt format for nye
366 (og gamle) generasjoner. Novellen ble skrevet så tidlig som vinteren
367 1968, og første gang trykt i novellesamlingen Probok på Gyldendal
370 <p
>Informasjonsteknologi spiller en sentral rolle i Kodémus, og det er
371 spennende å sammenligne beskrivelsen av IT fra
1968 med dagens IT i
372 2013. Forskjellene er mange -- men det er jammen likhetene også. Ikke
373 minst det at idag går jo nesten alle rundt med lillebrødre på seg!
</p
>
375 <p
>"Riktignok er det ikke påbudt å ha mobil,
" sier Thomas Gramstad,
376 leder i EFN.
"Men vi holder på å lage et samfunn der det blir så
377 upraktisk eller tungvint å ikke ha det, at man i praksis ikke slipper
378 unna. Og disse lillebrødrene sladrer hele tiden til staten (og til
379 mange andre) om hvor vi er, hva vi gjør, hva vi bryr oss om, hva vi
380 liker...
"</p
>
382 <p
>Det at Kodémus åpenbart er skrevet i en annen tid med en annen type
383 IT og likevel virker så relevant idag, er i seg selv et hardtslående
386 <p
>Tross sitt IT-tema fantes ikke Kodémus i elektronisk form, og
387 frivillige i EFN har skannet inn, OCR-tolket og korrekturlest
388 novellen, og deretter kodet den i en rekke digitale formater.
</p
>
390 <p
>Forfatteren har gitt tillatelse til publisering av Kodémus under ny
391 lisens, og novellen utgis av EFN med en Creative Commons (CC)
392 fribrukslisens (nærmere bestemt lisensen CC-BY-NC-ND). For leserne
393 eller brukerne innebærer dette at de får en klar og standardisert
394 beskjed om hvilke rettigheter de har til å dele novellen videre med
395 andre. For forfatteren innebærer dette økt synlighet og
396 tilgjengelighet for verket, slik at det ikke blir glemt, da
397 søkemotorer og nettlesere inneholder egne søkevalg for CC-lisenser, og
398 mange brukere søker etter verk som de vet de kan dele og bruke på
399 lovlig vis.
</p
>
401 <p
>EFN oppfordrer andre forfattere om å gi ut sine gamle tekster med
402 en fribrukslisens, slik at tekstene ikke blir glemt og for å stimulere
403 lovlig deling på nettet. EFN kan være behjelpelig med digitalisering
404 og utlegging på nett, i den grad det finnes kapasitet blant EFNs
405 medlemmer til dette. Vi mener at nyutgivelser av tekster under frie
406 lisenser kan øke interessen rundt forfatterskapet, og vil gjerne bidra
409 <p
>EFN utgir og deler med dette en novelle fra den digitale
410 informasjonsteknologiens tidligste barndom. En novelle som fortsatt er
411 full av vitalitet og aktualitet, og som derfor kan bidra til, og gi
412 ettertanke i dagens debatter om IT, personvern, overvåkning og
413 individets frihet og integritet.
</p
>
415 <p
>Du finner novellen her:
416 <br
><a href=
"http://efn.no/kodemus/
">http://efn.no/kodemus/
</a
></p
>
418 <p
>i flere forskjellige formater, for ulike plattformer. Per idag
419 finnes novellen i disse formatene: EPUB, MOBI, XML, HTML, PDF og
420 txt. Det kan bli flere formater senere, og evt. frivillige
421 bidragsytere til dette er velkommen.
</p
>
423 <p
>Kontaktperson for denne pressemeldingen,
</p
>
425 <p
>Thomas Gramstad
426 <br
>thomas@efn.no
427 <br
>4817 6875</p
>
431 <p
>EFN arbeider for dine borgerrettigheter i IT-samfunnet, for
432 nettverks- og delingskultur, personvern og frihet fra overvåkning,
433 åpne standarder, brukerstyrt programvare, retten til å kopiere, og
434 styrking av det digitale sivilsamfunnet m.m.
435 <br
><a href=
"http://efn.no/
">www.efn.no
</a
></p
>
437 </blockquote
></p
>
439 <p
>Jeg håper flere forfattere ser verdien av å gjøre kulturen
440 tilgjengelig for flere, og slår følge med Hr. Bringsværd i å gi ut
441 sine verker med bruksvilkår med færre bruksbegrensinger enn
442 opphavsretten legger opp til. Selv om jeg gjerne skulle sett at han
443 hadde brukt en Creative Commons-lisens som tillot avledede verker og
444 kommersiell bruk.
</p
>
449 <title>Typesetting a short story using docbook for PDF, HTML and EPUB
</title>
450 <link>http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</link>
451 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</guid>
452 <pubDate>Sun,
24 Mar
2013 17:
30:
00 +
0100</pubDate>
453 <description><p
>A few days ago, during a discussion in
454 <a href=
"http://www.efn.no/
">EFN
</a
> about interesting books to read
455 about copyright and the data retention directive, a suggestion to read
456 the
1968 short story Kodémus by
457 <a href=
"http://web2.gyldendal.no/toraage/
">Tore Åge Bringsværd
</a
>
458 came up. The text was only available in old paper books, and thus not
459 easily available for current and future generations. Some of the
460 people participating in the discussion contacted the author, and
461 reported back
2013-
03-
19 that the author was OK with releasing the
462 short story using a
<a href=
"http://www.creativecommons.org/
">Creative
463 Commons
</a
> license. The text was quickly scanned and OCR-ed, and we
464 were ready to start on the editing and typesetting.
</p
>
466 <p
>As I already had some experience formatting text in my project to
467 provide a Norwegian version of the Free Culture book by Lawrence
468 Lessig, I chipped in and set up a
469 <a href=
"http://www.docbook.org/
">DocBook
</a
> processing framework to
470 generate PDF, HTML and EPUB version of the short story. The tools to
471 transform DocBook to different formats are already in my Linux
472 distribution of choice,
<a href=
"http://www.debian.org/
">Debian
</a
>, so
473 all I had to do was to use the
474 <a href=
"http://dblatex.sourceforge.net/
">dblatex
</a
>,
475 <a href=
"http://docbook.sourceforge.net/release/xsl/current/epub/README
">dbtoepub
</a
>
476 and
<a href=
"https://fedorahosted.org/xmlto/
">xmlto
</a
> tools to do the
477 conversion. After a few days, we decided to replace dblatex with
479 <a href=
"http://wiki.docbook.org/DocBookXslStylesheets
">docbook-xsl
</a
>),
480 to get the copyright information to show up in the PDF and to get a
481 nicer
&lt;variablelist
&gt; typesetting, but that is just a minor
482 technical detail.
</p
>
484 <p
>There were a few challenges, of course. We want to typeset the
485 short story to look like the original, and that require fairly good
486 control over the layout. The original short story have three
487 parts/scenes separated by a single horizontally centred star (*), and
488 the paragraphs do not contain only flowing text, but dialogs and text
489 that started on a new line in the middle of the paragraph.
</p
>
491 <p
>I initially solved the first challenge by using a paragraph with a
492 single star in it, ie
&lt;para
&gt;*
&lt;/para
&gt;, but it made sure a
493 placeholder indicated where the scene shifted. This did not look too
494 good without the centring. The next approach was to create a new
495 preprocessor directive
&lt;?newscene?
&gt;, mapping to
"&lt;hr/
&gt;
"
496 for HTML and
"&lt;fo:block text-align=
"center
"&gt;
&lt;fo:leader
497 leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
&lt;/fo:block
&gt;
"
498 for FO/PDF output (did not try to implement this in dblatex, as we had
499 switched at this time). The HTML XSL file looked like this:
</p
>
501 <p
><blockquote
><pre
>
502 &lt;?xml version=
'1.0'?
&gt;
503 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
504 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
506 &lt;/xsl:template
&gt;
507 &lt;/xsl:stylesheet
&gt;
508 </pre
></blockquote
></p
>
510 <p
>And the FO/PDF XSL file looked like this:
</p
>
512 <p
><blockquote
><pre
>
513 &lt;?xml version=
'1.0'?
&gt;
514 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
515 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
516 &lt;fo:block text-align=
"center
"&gt;
517 &lt;fo:leader leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
518 &lt;/fo:block
&gt;
519 &lt;/xsl:template
&gt;
520 &lt;/xsl:stylesheet
&gt;
521 </pre
></blockquote
></p
>
523 <p
>Finally, I came across the
&lt;bridgehead
&gt; tag, which seem to be
524 a good fit for the task at hand, and I replaced
&lt;?newscene?
&gt;
525 with
&lt;bridgehead
&gt;*
&lt;/bridgehead
&gt;. It isn
't centred, but we
526 can fix it with some XSL rule if the current visual layout isn
't
529 <p
>I did not find a good DocBook compliant way to solve the
530 linebreak/paragraph challenge, so I ended up creating a new processor
531 directive
&lt;?linebreak?
&gt;, mapping to
&lt;br/
&gt; in HTML, and
532 &lt;fo:block/
&gt; in FO/PDF. I suspect there are better ways to do
533 this, and welcome ideas and patches on github. The HTML XSL file now
534 look like this:
</p
>
536 <p
><blockquote
><pre
>
537 &lt;?xml version=
'1.0'?
&gt;
538 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
539 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
541 &lt;/xsl:template
&gt;
542 &lt;/xsl:stylesheet
&gt;
543 </pre
></blockquote
></p
>
545 <p
>And the FO/PDF XSL file looked like this:
</p
>
547 <p
><blockquote
><pre
>
548 &lt;?xml version=
'1.0'?
&gt;
549 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'
550 xmlns:fo=
"http://www.w3.org/
1999/XSL/Format
"&gt;
551 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
552 &lt;fo:block/
&gt;
553 &lt;/xsl:template
&gt;
554 &lt;/xsl:stylesheet
&gt;
555 </pre
></blockquote
></p
>
557 <p
>One unsolved challenge is our wish to expose different ISBN numbers
558 per publication format, while keeping all of them in some conditional
559 structure in the DocBook source. No idea how to do this, so we ended
560 up listing all the ISBN numbers next to their format in the colophon
563 <p
>If you want to check out the finished result, check out the
564 <a href=
"https://github.com/sickel/kodemus
">source repository at
566 (
<a href=
"https://github.com/EFN/kodemus
">future/new/official
567 repository
</a
>). We expect it to be ready and announced in a few
573 <title>Seventy percent done with Norwegian docbook version of Free Culture
</title>
574 <link>http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</link>
575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</guid>
576 <pubDate>Sun,
23 Sep
2012 09:
30:
00 +
0200</pubDate>
577 <description><p
>Since this summer, I have worked in my spare time on a Norwegian
<a
578 href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
<a
579 href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
580 The reason is that this book is a great primer on what problems exist
581 in the current copyright laws, and I want it to be available also for
582 those that are reluctant do read an English book.
585 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
586 for volunteers
</a
> to help me, but too few have volunteered so far,
587 and progress is a bit slow. Anyway, today I broken the
70 percent
588 mark for the first rough translation. At the moment, less than
700
589 strings (paragraphs, index terms, titles) are left to translate. With
590 my current progress of
10-
20 strings per day, it will take a while to
591 complete the translation. This graph show the updated progress:
</p
>
593 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
595 <p
>Progress have slowed down lately due to family and work
596 commitments. If you want to help, please get in touch, and check out
597 the project files currently available from
598 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
600 <p
>If you are curious what the translated book currently look like,
602 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
604 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
605 are published on github. The HTML version is published as well, but
606 github hand it out with MIME type text/plain, confusing browsers, so I
607 saw no point in linking to that version.
</p
>
612 <title>Half way there with translated docbook version of Free Culture
</title>
613 <link>http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</link>
614 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</guid>
615 <pubDate>Fri,
17 Aug
2012 21:
50:
00 +
0200</pubDate>
616 <description><p
>In my spare time, I currently work on a Norwegian
617 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
618 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
619 to get a Norwegian text explaining the problems with the copyright law
620 I can give to my parents and others that are reluctant to read an
621 English book. It is a marvellous set of examples on how the ever
622 expanding copyright regulations hurt culture and society. When the
623 translation is done, I hope to find funding to print and ship a copy
624 to all the members of the Norwegian parliament, before they sit down
625 to debate the latest revisions to the Norwegian copyright law. This
627 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
628 for volunteers
</a
> to help me, and I have been able to secure the
629 valuable contribution from at least one other Norwegian.
</p
>
631 <p
>Two days ago, we finally broke the
50% mark. Then more than
50% of
632 the number of strings to translate (normally paragraphs, but also
633 titles and index entries are also counted). All parts from the
634 beginning up to and including chapter four is translated. So is
635 chapters six, seven and the conclusion. I created a graph to show the
638 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
640 <p
>The number of strings to translate increase as I insert the index
641 entries into the docbook. They were missing with the docbook version
642 I initially started with. There are still quite a few index entries
643 missing, but everyone starting with A, B, O, Z and Y are done. I
644 currently focus on completing the index entries, to get a complete
645 english version of the docbook source.
</p
>
647 <p
>There is still need for translators and people with docbook
648 knowledge, to be able to get a good looking book (I still struggle
649 with dblatex, xmlto and docbook-xsl) as well as to do the draft
650 translation and proof reading. And I would like the figures to be
651 redrawn as SVGs to make it easy to translate them. Any SVG master
652 around? I am sure there are some legal terms that are unfamiliar to
653 me. If you want to help, please get in touch, and check out the
654 project files currently available from
<a
655 href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
657 <p
>If you are curious what the translated book currently look like,
659 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
661 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
662 are published on github. The HTML version is published as well, but
663 github hand it out with MIME type text/plain, confusing browsers, so I
664 saw no point in linking to that version.
</p
>
669 <title>Notes on language codes for Norwegian docbook processing...
</title>
670 <link>http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</link>
671 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</guid>
672 <pubDate>Fri,
10 Aug
2012 21:
00:
00 +
0200</pubDate>
673 <description><p
>In
<a href=
"http://www.docbook.org/
">docbook
</a
> one can specify
674 the language used at the top, and the processing pipeline will use
675 this information to pick the correct translations for
'chapter
',
'see
676 also
',
'index
' etc. And for most languages used with docbook, I guess
677 this work just fine. For example a German user can start the document
678 with
&lt;book lang=
"de
"&gt;, and the document will show up with the
679 correct content with any of the docbook processors. This is not the
680 case for the language
681 <a href=
"http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
">I
682 am working with at the moment
</a
>, Norwegian Bokmål.
</p
>
684 <p
>For a while, I was confused about which language code to use,
685 because I was unable to find any language code that would work across
686 all tools. I am currently testing dblatex, xmlto, docbook-xsl, and
687 dbtoepub, and they do not handle Norwegian Bokmål the same way. Some
688 of them do not handle it at all.
</p
>
690 <p
>A bit of background information is probably needed to understand
691 this mess. Norwegian is not one, but two written variants. The
692 variants are Norwegian Nynorsk and Norwegian Bokmål. There are three
693 two letter language codes associated with these languages, Norwegian
694 is
'no
', Norwegian Nynorsk is
'nn
' and Norwegian Bokmål is
'nb
'.
695 Historically the
'no
' language code was used for Norwegian Bokmål, but
696 many years ago this was found to be å bad idea, and the recommendation
697 is to use the most specific language code instead, to avoid confusion.
698 In the transition period it is a good idea to make sure
'no
' was an
699 alias for
'nb
'.
</p
>
701 <p
>Back to docbook processing tools in Debian. The dblatex tool only
702 understand
'nn
'. There are translations for
'no
', but not
'nb
' (BTS
703 <a href=
"http://bugs.debian.org/
684391">#
684391</a
>), but due to a bug
704 (BTS
<a href=
"http://bugs.debian.org/
682936">#
682936</a
>) the
'no
'
705 language code is not recognised. The docbook-xsl tool chain only
706 recognise
'nn
' and
'nb
', but not
'no
'. The xmlto tool only recognise
707 'nn
' and
'nb
', but not
'no
'. The end result that there is no language
708 code I can use to get the docbook file working with all of these tools
709 at the same time. :(
</p
>
711 <p
>The correct solution is to use
&lt;book lang=
"nb
"&gt;, but it will
712 take time before that will work with all the free software docbook
713 processors. :(
</p
>
715 <p
>Oh, the joy of well integrated tools. :/
</p
>
720 <title>Best way to create a docbook book?
</title>
721 <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</link>
722 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</guid>
723 <pubDate>Tue,
31 Jul
2012 22:
00:
00 +
0200</pubDate>
724 <description><p
>I tried to send this text to the
725 <a href=
"https://lists.oasis-open.org/archives/docbook-apps/
">docbook-apps
726 mailing list at lists.oasis-open.org
</a
>, but it only accept messages
727 from subscribers and rejected my post, and I completely lack the
728 bandwidth required to subscribe to another mailing list, so instead I
729 try to post my message here and hope my blog readers can help me
732 <p
>I am quite new to docbook processing, and am climbing a steep
733 learning curve at the moment.
</p
>
735 <p
>To give you some background, I am working on a Norwegian
736 translation of the book Free Culture by Lawrence Lessig, and I use
737 docbook to handle the process. The files to build the book are
739 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
740 The book got around
400 pages with parts, images, footnotes, tables,
741 index entries etc, which has proven to be a challenge for the free
742 software docbook processors. My build platform is Debian GNU/Linux
745 <p
>I want to build PDF, EPUB and HTML version of the book, and have
746 tried different tool chains to do the conversion from docbook to these
747 formats. I am currently focusing on the PDF version, and have a few
752 <li
>Using dblatex, the
&lt;part
&gt; handling is not the way I want to,
753 as
&lt;/part
&gt; do not really end the
&lt;part
&gt;. (See
754 <a href=
"http://bugs.debian.org/
683166">BTS report #
683166</a
>), the
755 xetex backend (needed to process UTF-
8) give incorrect hyphens in
756 index references spanning several pages (See
757 <a href=
"http://bugs.debian.org/
682901">BTS report #
682901</a
>), and
758 I am unable to get the norwegian template texts (See
759 <a href=
"http://bugs.debian.org/
682936">BTS report #
682936</a
>).
</li
>
761 <li
>Using straight xmlto fail with some latex error (See
762 <a href=
"http://bugs.debian.org/
683163">BTS report
763 #
683163</a
>).
</li
>
765 <li
>Using xmlto with the fop backend fail to handle images (do not
766 show up in the PDF), fail to handle a long footnote (overlap
767 footnote and text body, see
768 <a href=
"http://bugs.debian.org/
683197">BTS report #
683197</a
>), and
769 fail to create a correct index (some lack page ref, and the page
770 refs listed are not right).
</li
>
772 <li
>Using xmlto with the dblatex backend behave like dblatex.
</li
>
774 <li
>Using docbook-xls with xsltproc + fop have the same footnote and
775 index problems the xmlto + fop processing.
</li
>
779 <p
>So I wonder, what would be the best way to create the PDF version
780 of this book? Are some of the bugs found above solved in new or
781 experimental versions of some docbook tool chain?
</p
>
783 <p
>What about HTML and EPUB versions?
</p
>
788 <title>Free Culture in Norwegian -
5 chapters done,
74 percent left to do
</title>
789 <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</link>
790 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</guid>
791 <pubDate>Sat,
21 Jul
2012 20:
00:
00 +
0200</pubDate>
792 <description><p
>I reported earlier that I am working on
793 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">a
794 norwegian version
</a
> of the book
795 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
796 Progress is good, and yesterday I got a major contribution from Anders
797 Hagen Jarmund completing chapter six. The source files as well as a
798 PDF and EPUB version of this book are available from
799 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
801 <p
>I am happy to report that the draft for the first two chapters
802 (preface, introduction) is complete, and three other chapters are also
803 completely translated. This completes
26 percent of the number of
804 strings (equivalent to paragraphs) in the book, and there is thus
74
805 percent left to translate. A graph of the progress is present at the
806 bottom of the github project page. There is still room for more
807 contributors. Get in touch or send github pull requests with fixes if
808 you got time and are willing to help make this book make it to
811 <p
>The book translation framework could also be a good basis for other
812 translations, if you want the book to be available in your
818 <title>Call for help from docbook expert to tag Free Culture by Lawrence Lessig
</title>
819 <link>http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</link>
820 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</guid>
821 <pubDate>Mon,
16 Jul
2012 22:
50:
00 +
0200</pubDate>
822 <description><p
>I am currently working on a
823 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">project
824 to translate
</a
> the book
825 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig
826 to Norwegian. And the source we base our translation on is the
827 <a href=
"http://en.wikipedia.org/wiki/DocBook
">docbook
</a
> version, to
828 allow us to use po4a and .po files to handle the translation, and for
829 this to work well the docbook source document need to be properly
830 tagged. The source files of this project is available from
831 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
833 <p
>The problem is that the docbook source have flaws, and we have
834 no-one involved in the project that is a docbook expert. Is there a
835 docbook expert somewhere that is interested in helping us create a
836 well tagged docbook version of the book, and adjust our build process
837 for the PDF, EPUB and HTML version of the book? This will provide a
838 well tagged English version (our source document), and make it a lot
839 easier for us to create a good Norwegian version. If you can and want
840 to help, please get in touch with me or fork the github project and
841 send pull requests with fixes. :)
</p
>
846 <title>Dugnad for å sende norsk versjon av Free Culture til stortingets representanter!
</title>
847 <link>http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</link>
848 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</guid>
849 <pubDate>Wed,
11 Jul
2012 09:
00:
00 +
0200</pubDate>
850 <description><p
>Da opphavsrettsloven ble revidert i forrige runde rundt
2005, var
851 det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
852 Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
853 og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
854 representanter fikk en norsk utgave av boken
855 <a href=
"http://free-culture.cc/
">Free Culture
</a
> av Lawrence Lessig
856 som forklarte litt om problemstillingene. Vi endte opp med å
857 prioritere utvikling i
858 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>-prosjektet i
859 stedet, så den oversatte boken så aldri dagens lys. Men i forrige uke
860 ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
861 bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
862 sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
863 fordel for forlag og store mediehus fortsatt trenger en annen vinkling
864 i debatten.
</p
>
866 <p
>Planen min er å oversette boka på dugnad, sette den opp for
867 trykking med en av de mange
868 <a href=
"http://no.wikipedia.org/wiki/Trykk_på_forespørsel
">trykk på
869 forespørsel
</a
>-tjenestene, skaffe sponsor til å finansiere trykking
870 til stortingsrepresentantene og alle som har bidratt med
871 oversettelser. Kanskje vi også kan få en avtale med et forlag om
872 publisering når boka er ferdig? Kommentarene til
873 <a href=
"http://newth.net/eirik/
2011/
04/
01/e-selvpublisering/
">Eirik
875 <a href=
"http://www.espen.com/norskblogg/archives/
2008/
09/erfaringer_med_publishing_on_demand.html
">Espen
876 Andersen
</a
> om erfaringene med selvpublisering og trykk på
877 forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
878 <a href=
"http://www.lulu.com/
">Lulu
</a
> er en grei leverandør av
879 trykketjenester til prosjektet.
</p
>
881 <p
>Jeg har satt opp
882 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">et
883 Github-prosjekt
</a
> for a lage boken, basert på Docbook-utgaven jeg
884 fant fra Hans Schou. Skolelinux har hatt byggesystem for å lage
885 oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
886 kopiert og utvidet dette oppsettet. Originalteksten er i Docbook, og
887 oversettelsen gjøres i .po-filer med hjelp av vanlige
888 oversetterverktøy brukt i fri programvareverden. Dernest tar
889 byggesystemet over og lager PDF og EPUB-utgave av den oversatte
890 teksten. Resultatet kan ses i Github-prosjektet. For å komme raskt
891 igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
892 til norsk, noe som grovoversatte ca.
1300 av de ca.
1700 tekstbitene
893 boken består av. Jeg håper nå at flere kan bidra med å få
894 oversettelsen på plass, slik at teksten kan være klar i løpet av
895 høsten. Når alt er oversatt må teksten gjennomgås for feil og
896 konsistent språk. Totalt er det nok mange timer som trengs for å
897 gjennomføre oversettelsen.
</p
>
899 <p
>Økonomien i dette er ikke avskrekkende.
169
900 stortingsrepresentanter og nesten like mange varamedlemmer bør få
901 bøker, og estimert produduksjonskostnad for hver bok er rundt
6 EURO i
902 følge et raskt estimat fra Lulu. Jeg vet ennå ikke hvor mange sider
903 det blir i størrelsen
5,
5" x
8.5" (det er ca.
140 sider i A4-format),
904 så jeg gjettet på
400 sider. Jeg tror originalutgaven har nesten
400
905 sider. For
169*
2 eksemplarer snakker vi om en trykkekostnad på
906 ca.
2000 EURO, dvs. ca
15 000 NOK. Det burde være mulig å finne en
907 sponsor for å dekke en slik sum. I tillegg kommer distribusjon og
908 porto, som antagelig kommer på like mye.
</p
>
910 <p
>Kan du bidra med oversettelse og docbook-typesetting? Ta kontakt
911 og send patcher i github. Jeg legger gjerne inn folk i prosjektet
912 slik at du kan oppdatere direkte.
</p
>