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