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