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 freeculture
</title>
5 <description>Entries tagged freeculture
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Typesetting a short story using docbook for PDF, HTML and EPUB
</title>
11 <link>http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</guid>
13 <pubDate>Sun,
24 Mar
2013 17:
30:
00 +
0100</pubDate>
14 <description><p
>A few days ago, during a discussion in
15 <a href=
"http://www.efn.no/
">EFN
</a
> about interesting books to read
16 about copyright and the data retention directive, a suggestion to read
17 the
1968 short story Kodémus by
18 <a href=
"http://web2.gyldendal.no/toraage/
">Tore Åge Bringsværd
</a
>
19 came up. The text was only available in old paper books, and thus not
20 easily available for current and future generations. Some of the
21 people participating in the discussion contacted the author, and
22 reported back
2013-
03-
19 that the author was OK with releasing the
23 short story using a
<a href=
"http://www.creativecommons.org/
">Creative
24 Commons
</a
> license. The text was quickly scanned and OCR-ed, and we
25 were ready to start on the editing and typesetting.
</p
>
27 <p
>As I already had some experience formatting text in my project to
28 provide a Norwegian version of the Free Culture book by Lawrence
29 Lessig, I chipped in and set up a
30 <a href=
"http://www.docbook.org/
">DocBook
</a
> processing framework to
31 generate PDF, HTML and EPUB version of the short story. The tools to
32 transform DocBook to different formats are already in my Linux
33 distribution of choice,
<a href=
"http://www.debian.org/
">Debian
</a
>, so
34 all I had to do was to use the
35 <a href=
"http://dblatex.sourceforge.net/
">dblatex
</a
>,
36 <a href=
"http://docbook.sourceforge.net/release/xsl/current/epub/README
">dbtoepub
</a
>
37 and
<a href=
"https://fedorahosted.org/xmlto/
">xmlto
</a
> tools to do the
38 conversion. After a few days, we decided to replace dblatex with
40 <a href=
"http://wiki.docbook.org/DocBookXslStylesheets
">docbook-xsl
</a
>),
41 to get the copyright information to show up in the PDF and to get a
42 nicer
&lt;variablelist
&gt; typesetting, but that is just a minor
43 technical detail.
</p
>
45 <p
>There were a few challenges, of course. We want to typeset the
46 short story to look like the original, and that require fairly good
47 control over the layout. The original short story have three
48 parts/scenes separated by a single horizontally centred star (*), and
49 the paragraphs do not contain only flowing text, but dialogs and text
50 that started on a new line in the middle of the paragraph.
</p
>
52 <p
>I initially solved the first challenge by using a paragraph with a
53 single star in it, ie
&lt;para
&gt;*
&lt;/para
&gt;, but it made sure a
54 placeholder indicated where the scene shifted. This did not look too
55 good without the centring. The next approach was to create a new
56 preprocessor directive
&lt;?newscene?
&gt;, mapping to
"&lt;hr/
&gt;
"
57 for HTML and
"&lt;fo:block text-align=
"center
"&gt;
&lt;fo:leader
58 leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
&lt;/fo:block
&gt;
"
59 for FO/PDF output (did not try to implement this in dblatex, as we had
60 switched at this time). The HTML XSL file looked like this:
</p
>
62 <p
><blockquote
><pre
>
63 &lt;?xml version=
'1.0'?
&gt;
64 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
65 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
67 &lt;/xsl:template
&gt;
68 &lt;/xsl:stylesheet
&gt;
69 </pre
></blockquote
></p
>
71 <p
>And the FO/PDF XSL file looked like this:
</p
>
73 <p
><blockquote
><pre
>
74 &lt;?xml version=
'1.0'?
&gt;
75 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
76 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
77 &lt;fo:block text-align=
"center
"&gt;
78 &lt;fo:leader leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
79 &lt;/fo:block
&gt;
80 &lt;/xsl:template
&gt;
81 &lt;/xsl:stylesheet
&gt;
82 </pre
></blockquote
></p
>
84 <p
>Finally, I came across the
&lt;bridgehead
&gt; tag, which seem to be
85 a good fit for the task at hand, and I replaced
&lt;?newscene?
&gt;
86 with
&lt;bridgehead
&gt;*
&lt;/bridgehead
&gt;. It isn
't centred, but we
87 can fix it with some XSL rule if the current visual layout isn
't
90 <p
>I did not find a good DocBook compliant way to solve the
91 linebreak/paragraph challenge, so I ended up creating a new processor
92 directive
&lt;?linebreak?
&gt;, mapping to
&lt;br/
&gt; in HTML, and
93 &lt;fo:block/
&gt; in FO/PDF. I suspect there are better ways to do
94 this, and welcome ideas and patches on github. The HTML XSL file now
95 look like this:
</p
>
97 <p
><blockquote
><pre
>
98 &lt;?xml version=
'1.0'?
&gt;
99 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
100 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
102 &lt;/xsl:template
&gt;
103 &lt;/xsl:stylesheet
&gt;
104 </pre
></blockquote
></p
>
106 <p
>And the FO/PDF XSL file looked like this:
</p
>
108 <p
><blockquote
><pre
>
109 &lt;?xml version=
'1.0'?
&gt;
110 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'
111 xmlns:fo=
"http://www.w3.org/
1999/XSL/Format
"&gt;
112 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
113 &lt;fo:block/
&gt;
114 &lt;/xsl:template
&gt;
115 &lt;/xsl:stylesheet
&gt;
116 </pre
></blockquote
></p
>
118 <p
>One unsolved challenge is our wish to expose different ISBN numbers
119 per publication format, while keeping all of them in some conditional
120 structure in the DocBook source. No idea how to do this, so we ended
121 up listing all the ISBN numbers next to their format in the colophon
124 <p
>If you want to check out the finished result, check out the
125 <a href=
"https://github.com/sickel/kodemus
">source repository at
127 (
<a href=
"https://github.com/EFN/kodemus
">future/new/official
128 repository
</a
>). We expect it to be ready and announced in a few
134 <title>Piratpartiet på opphavs-retrett?
</title>
135 <link>http://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html
</link>
136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html
</guid>
137 <pubDate>Wed,
19 Dec
2012 13:
10:
00 +
0100</pubDate>
138 <description><p
>Jeg ble overrasket over å se at Piratpartiet i
139 <a href=
"http://www.aftenposten.no/kultur/Piratpartiet-stiller-til-Stortingsvalget-
7073298.html
">Aftenposten
</a
>
140 er referert på følgende:
</p
>
143 Når det gjelder retten til opphavsrett for kulturproduktene, mener
144 Piratpartiet av levetid +
14 år er tilfredsstillende.
147 <p
>Det betyr en vernetid langt ut over det kommersielle livet til de
148 aller fleste opphavsrettsbeskyttede verker, og er i strid med slik i
149 hvert fall jeg har tolket punkt
5 i
150 <a href=
"http://people.opera.com/howcome/
2012/piratpartiet/kjerneprogram.html
">kjerneprogrammet
151 til Piratpartiet
</a
>:
</p
>
154 <p
><strong
>5: Åndsverk og patenter: tilbake til start
</strong
></p
>
156 <table border=
"1">
157 <tr
><th
>forslag:
</th
><td
>14 års opphavsrett og ingen
158 programvarepatenter
</td
></tr
>
160 <tr
><th
>grunn:
</th
><td
>Den første loven om opphavsrett spesifiserte
14
161 års vernetid. Senere har mediabransjens lobbyister stadig presset
162 loven mot lengre vern, nå er det
70 år etter forfatters død. Dette
163 gjør at mange verk glemmes og går tapt, noe som er skadelig for norsk
164 språk og kultur. Vi til tilbake til start:
14 års
165 vernetid. Patentloven sier klart at dataprogrammer ikke kan
166 patenteres. Likevel klarer patentadvokater å lure gjennom
167 programvarepatenter. Slike patenter gjør dingsene våre dyrere og kan i
168 enkelte tilfelle stoppe dem helt.
</th
></tr
>
172 <p
>Den opprinnelige opphavsretten var på
14 år totalt, ikke
14 år
173 etter opphavspersonens død. Jeg tenkte først dette kanskje var
174 feilsitering fra Aftenposten, men jeg finner samme påstand i en
<a
175 href=
"http://piratpartietnorge.org/om-gramo-og-piratpolitikken/
">bloggpost
176 fra Geir Aaslid
</a
> på Piratpartietes offisielle nettsider. Der
177 skriver han følgende:
</p
>
180 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
181 mange bransjer, med ulike behov. Enhver reform er en forbedring men
182 det er nærliggende å anta at en opphavsrett på levetid +
14 år er
183 fullt ut tilfredstillende for musikk, film, litteratur og spill.
186 <p
>Det virker dermed på meg som om Piratpartiet allerede har gjort
187 retrett fra sin beundringsverdige holdning om at det holdt med
14 års
188 total vernetid, til sin nye som tar utgangspunkt i levetiden til
189 opphavspersonen. Jeg håper det baserer seg på en misforståelse hos
190 piratlederen som blir korrigert tilbake til
14 års total vernetid før
191 partiet stiller til valg.
</p
>
193 <p
>Hvis du lurer på hvilke problemer lang vernetid bringer med seg,
194 anbefaler jeg å lese boken
<a href=
"http://free-culture.cc/
">Free
195 Culture
</a
> av Lawrence Lessig. Jeg og en liten gruppe andre er igang
197 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">oversette
198 boken til bokmål
</a
> og tar gjerne imot hjelp med oversettelse og
199 korrekturlesing.
</p
>
201 <p
><strong
>Oppdatering
2012-
12-
20</strong
>: Oppdaget at
202 <a href=
"http://piratpartietnorge.org/om-gramo-og-piratpolitikken/
">bloggposten
203 til Geir Aaslid
</a
> er endret siden i går, og nå inneholder følgende
204 avsnitt i stedet for det jeg siterte over:
</p
>
207 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
208 mange bransjer, med ulike behov. Enhver reform er en forbedring men
209 det er nærliggende å anta at en opphavsrett lik levetiden, evt +
14 år
210 er fullt ut tilfredstillende for mange skapere av musikk, film,
211 litteratur og spill. Det er for det meste de store forlagene som er
215 <p
>I tillegg har det dukket opp en setning nederst
"Dette dokumentet
216 er et utkast til svar på et angrep på Piratpartiet fra Gramo. Det
217 endrer seg derfor over tid og den endelige versjonen er det som blir
218 publisert på Hardware.no
", som tyder på at originalformuleringen ikke
219 var veloverveid og sitatet i Aftenposten kanskje var basert på en
220 misforståelse.
</p
>
225 <title>Why isn
't the value of copyright taxed?
</title>
226 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_the_value_of_copyright_taxed_.html
</link>
227 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_the_value_of_copyright_taxed_.html
</guid>
228 <pubDate>Sat,
17 Nov
2012 11:
30:
00 +
0100</pubDate>
229 <description><p
>While working on a
230 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Norwegian
231 translation of the Free Culture by Lawrence Lessig
</a
> (
76% done),
232 which cover the problems with todays copyright law and how it stifles
233 creativity, one idea occurred to me. The idea is to get the tax
234 office to help make more works enter the public domain and also help
235 make it easier to clear rights for using copyrighted works.
</p
>
237 <p
>I mentioned this idea briefly during Yesterdays
238 <a href=
"http://www.farmann.no/
2012/
11/
14/john-perry-barlow-in-oslo-friday-nov-
16
239 -
15-
30-
19-
00/
">presentation
240 by John Perry Barlow
</a
>, and concluded that it was best to put it
241 in writing for a wider audience. The idea is not really based on the
242 argument that copyrighted works are
"intellectual property
", as the
243 core requirement is that copyrighted work have value for the copyright
244 holder and the tax office like to collect their share from any value
245 controlled by the citizens in a country. I
'm sharing the idea here to
246 let others consider it and perhaps shoot it down with a fresh set of
249 <p
>Most valuables are taxed by the government. At least here in
250 Norway, the amount of money you have, the value of our land property,
251 the value of your house, the value of your car, the value of our
252 stocks and other valuables are all added together. If the tax value
253 of these values exceed your debt, you have to pay the tax office some
254 taxes for these values. And copyrighted work have value. It have
255 value for the rights holder, who can earn money selling access to the
256 work. But it is not included in the tax calculations? Why not?
</p
>
258 <p
>If the government want to tax copyrighted works, it would want to
259 maintain a database of all the copyrighted works and who are the
260 rights holders for a given works, to be able to associate the works
261 value to the right citizen or company for tax purposes. If such
262 database exist, it will become a lot easier to find out who to talk to
263 for clearing permissions to use a copyrighted work, which is a very
264 hard operation with todays copyright law. To ensure that copyright
265 holders keep the database up-to-date, it would have to become a
266 requirement to be able to collect money for granting access to
267 copyrighted works that the work is listed in the database with the
268 correct right holder.
</p
>
270 <p
>If copyright causes copyright holders to have to pay more taxes,
271 they will have a small incentive to
"disown
" their copyright, and let
272 the work enter the public domain. For works with several right holders
273 one of the right holders could state (and get it registered in the
274 database) that she do not need to be consulted when clearing rights to
275 use the work in question and thus will not get any income from that
276 work. Stating this would have to be impossible to revert and stop the
277 tax office from adding the value of that work to the given citizens
278 tax calculation. I assume the copyright law would stay the same,
279 allowing creators to pick a license of their choosing, and also
280 allowing them to put their work directly in the public domain. The
281 existence of such database will make it even easier to clear rights,
282 and if the right holders listed in the database is taxed, this system
283 would increase the amount of works that enter the public domain.
</p
>
285 <p
>The effect would be that the tax office help to make it easier to
286 get rights to use the works that have not yet entered the public
287 domain and help to get more work into the public domain and .
</p
>
289 <p
>Why have such taxing not happened yet? I am sure the tax office
290 would like to tax copyrighted work values if they could.
</p
>
295 <title>Seventy percent done with Norwegian docbook version of Free Culture
</title>
296 <link>http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</link>
297 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</guid>
298 <pubDate>Sun,
23 Sep
2012 09:
30:
00 +
0200</pubDate>
299 <description><p
>Since this summer, I have worked in my spare time on a Norwegian
<a
300 href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
<a
301 href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
302 The reason is that this book is a great primer on what problems exist
303 in the current copyright laws, and I want it to be available also for
304 those that are reluctant do read an English book.
307 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
308 for volunteers
</a
> to help me, but too few have volunteered so far,
309 and progress is a bit slow. Anyway, today I broken the
70 percent
310 mark for the first rough translation. At the moment, less than
700
311 strings (paragraphs, index terms, titles) are left to translate. With
312 my current progress of
10-
20 strings per day, it will take a while to
313 complete the translation. This graph show the updated progress:
</p
>
315 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
317 <p
>Progress have slowed down lately due to family and work
318 commitments. If you want to help, please get in touch, and check out
319 the project files currently available from
320 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
322 <p
>If you are curious what the translated book currently look like,
324 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
326 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
327 are published on github. The HTML version is published as well, but
328 github hand it out with MIME type text/plain, confusing browsers, so I
329 saw no point in linking to that version.
</p
>
334 <title>Half way there with translated docbook version of Free Culture
</title>
335 <link>http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</link>
336 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</guid>
337 <pubDate>Fri,
17 Aug
2012 21:
50:
00 +
0200</pubDate>
338 <description><p
>In my spare time, I currently work on a Norwegian
339 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
340 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
341 to get a Norwegian text explaining the problems with the copyright law
342 I can give to my parents and others that are reluctant to read an
343 English book. It is a marvellous set of examples on how the ever
344 expanding copyright regulations hurt culture and society. When the
345 translation is done, I hope to find funding to print and ship a copy
346 to all the members of the Norwegian parliament, before they sit down
347 to debate the latest revisions to the Norwegian copyright law. This
349 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
350 for volunteers
</a
> to help me, and I have been able to secure the
351 valuable contribution from at least one other Norwegian.
</p
>
353 <p
>Two days ago, we finally broke the
50% mark. Then more than
50% of
354 the number of strings to translate (normally paragraphs, but also
355 titles and index entries are also counted). All parts from the
356 beginning up to and including chapter four is translated. So is
357 chapters six, seven and the conclusion. I created a graph to show the
360 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
362 <p
>The number of strings to translate increase as I insert the index
363 entries into the docbook. They were missing with the docbook version
364 I initially started with. There are still quite a few index entries
365 missing, but everyone starting with A, B, O, Z and Y are done. I
366 currently focus on completing the index entries, to get a complete
367 english version of the docbook source.
</p
>
369 <p
>There is still need for translators and people with docbook
370 knowledge, to be able to get a good looking book (I still struggle
371 with dblatex, xmlto and docbook-xsl) as well as to do the draft
372 translation and proof reading. And I would like the figures to be
373 redrawn as SVGs to make it easy to translate them. Any SVG master
374 around? I am sure there are some legal terms that are unfamiliar to
375 me. If you want to help, please get in touch, and check out the
376 project files currently available from
<a
377 href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
379 <p
>If you are curious what the translated book currently look like,
381 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
383 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
384 are published on github. The HTML version is published as well, but
385 github hand it out with MIME type text/plain, confusing browsers, so I
386 saw no point in linking to that version.
</p
>
391 <title>Notes on language codes for Norwegian docbook processing...
</title>
392 <link>http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</link>
393 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</guid>
394 <pubDate>Fri,
10 Aug
2012 21:
00:
00 +
0200</pubDate>
395 <description><p
>In
<a href=
"http://www.docbook.org/
">docbook
</a
> one can specify
396 the language used at the top, and the processing pipeline will use
397 this information to pick the correct translations for
'chapter
',
'see
398 also
',
'index
' etc. And for most languages used with docbook, I guess
399 this work just fine. For example a German user can start the document
400 with
&lt;book lang=
"de
"&gt;, and the document will show up with the
401 correct content with any of the docbook processors. This is not the
402 case for the language
403 <a href=
"http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
">I
404 am working with at the moment
</a
>, Norwegian Bokmål.
</p
>
406 <p
>For a while, I was confused about which language code to use,
407 because I was unable to find any language code that would work across
408 all tools. I am currently testing dblatex, xmlto, docbook-xsl, and
409 dbtoepub, and they do not handle Norwegian Bokmål the same way. Some
410 of them do not handle it at all.
</p
>
412 <p
>A bit of background information is probably needed to understand
413 this mess. Norwegian is not one, but two written variants. The
414 variants are Norwegian Nynorsk and Norwegian Bokmål. There are three
415 two letter language codes associated with these languages, Norwegian
416 is
'no
', Norwegian Nynorsk is
'nn
' and Norwegian Bokmål is
'nb
'.
417 Historically the
'no
' language code was used for Norwegian Bokmål, but
418 many years ago this was found to be å bad idea, and the recommendation
419 is to use the most specific language code instead, to avoid confusion.
420 In the transition period it is a good idea to make sure
'no
' was an
421 alias for
'nb
'.
</p
>
423 <p
>Back to docbook processing tools in Debian. The dblatex tool only
424 understand
'nn
'. There are translations for
'no
', but not
'nb
' (BTS
425 <a href=
"http://bugs.debian.org/
684391">#
684391</a
>), but due to a bug
426 (BTS
<a href=
"http://bugs.debian.org/
682936">#
682936</a
>) the
'no
'
427 language code is not recognised. The docbook-xsl tool chain only
428 recognise
'nn
' and
'nb
', but not
'no
'. The xmlto tool only recognise
429 'nn
' and
'nb
', but not
'no
'. The end result that there is no language
430 code I can use to get the docbook file working with all of these tools
431 at the same time. :(
</p
>
433 <p
>The correct solution is to use
&lt;book lang=
"nb
"&gt;, but it will
434 take time before that will work with all the free software docbook
435 processors. :(
</p
>
437 <p
>Oh, the joy of well integrated tools. :/
</p
>
442 <title>Best way to create a docbook book?
</title>
443 <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</link>
444 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</guid>
445 <pubDate>Tue,
31 Jul
2012 22:
00:
00 +
0200</pubDate>
446 <description><p
>I tried to send this text to the
447 <a href=
"https://lists.oasis-open.org/archives/docbook-apps/
">docbook-apps
448 mailing list at lists.oasis-open.org
</a
>, but it only accept messages
449 from subscribers and rejected my post, and I completely lack the
450 bandwidth required to subscribe to another mailing list, so instead I
451 try to post my message here and hope my blog readers can help me
454 <p
>I am quite new to docbook processing, and am climbing a steep
455 learning curve at the moment.
</p
>
457 <p
>To give you some background, I am working on a Norwegian
458 translation of the book Free Culture by Lawrence Lessig, and I use
459 docbook to handle the process. The files to build the book are
461 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
462 The book got around
400 pages with parts, images, footnotes, tables,
463 index entries etc, which has proven to be a challenge for the free
464 software docbook processors. My build platform is Debian GNU/Linux
467 <p
>I want to build PDF, EPUB and HTML version of the book, and have
468 tried different tool chains to do the conversion from docbook to these
469 formats. I am currently focusing on the PDF version, and have a few
474 <li
>Using dblatex, the
&lt;part
&gt; handling is not the way I want to,
475 as
&lt;/part
&gt; do not really end the
&lt;part
&gt;. (See
476 <a href=
"http://bugs.debian.org/
683166">BTS report #
683166</a
>), the
477 xetex backend (needed to process UTF-
8) give incorrect hyphens in
478 index references spanning several pages (See
479 <a href=
"http://bugs.debian.org/
682901">BTS report #
682901</a
>), and
480 I am unable to get the norwegian template texts (See
481 <a href=
"http://bugs.debian.org/
682936">BTS report #
682936</a
>).
</li
>
483 <li
>Using straight xmlto fail with some latex error (See
484 <a href=
"http://bugs.debian.org/
683163">BTS report
485 #
683163</a
>).
</li
>
487 <li
>Using xmlto with the fop backend fail to handle images (do not
488 show up in the PDF), fail to handle a long footnote (overlap
489 footnote and text body, see
490 <a href=
"http://bugs.debian.org/
683197">BTS report #
683197</a
>), and
491 fail to create a correct index (some lack page ref, and the page
492 refs listed are not right).
</li
>
494 <li
>Using xmlto with the dblatex backend behave like dblatex.
</li
>
496 <li
>Using docbook-xls with xsltproc + fop have the same footnote and
497 index problems the xmlto + fop processing.
</li
>
501 <p
>So I wonder, what would be the best way to create the PDF version
502 of this book? Are some of the bugs found above solved in new or
503 experimental versions of some docbook tool chain?
</p
>
505 <p
>What about HTML and EPUB versions?
</p
>
510 <title>Free Culture in Norwegian -
5 chapters done,
74 percent left to do
</title>
511 <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</link>
512 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</guid>
513 <pubDate>Sat,
21 Jul
2012 20:
00:
00 +
0200</pubDate>
514 <description><p
>I reported earlier that I am working on
515 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">a
516 norwegian version
</a
> of the book
517 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
518 Progress is good, and yesterday I got a major contribution from Anders
519 Hagen Jarmund completing chapter six. The source files as well as a
520 PDF and EPUB version of this book are available from
521 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
523 <p
>I am happy to report that the draft for the first two chapters
524 (preface, introduction) is complete, and three other chapters are also
525 completely translated. This completes
26 percent of the number of
526 strings (equivalent to paragraphs) in the book, and there is thus
74
527 percent left to translate. A graph of the progress is present at the
528 bottom of the github project page. There is still room for more
529 contributors. Get in touch or send github pull requests with fixes if
530 you got time and are willing to help make this book make it to
533 <p
>The book translation framework could also be a good basis for other
534 translations, if you want the book to be available in your
540 <title>Call for help from docbook expert to tag Free Culture by Lawrence Lessig
</title>
541 <link>http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</link>
542 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</guid>
543 <pubDate>Mon,
16 Jul
2012 22:
50:
00 +
0200</pubDate>
544 <description><p
>I am currently working on a
545 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">project
546 to translate
</a
> the book
547 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig
548 to Norwegian. And the source we base our translation on is the
549 <a href=
"http://en.wikipedia.org/wiki/DocBook
">docbook
</a
> version, to
550 allow us to use po4a and .po files to handle the translation, and for
551 this to work well the docbook source document need to be properly
552 tagged. The source files of this project is available from
553 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
555 <p
>The problem is that the docbook source have flaws, and we have
556 no-one involved in the project that is a docbook expert. Is there a
557 docbook expert somewhere that is interested in helping us create a
558 well tagged docbook version of the book, and adjust our build process
559 for the PDF, EPUB and HTML version of the book? This will provide a
560 well tagged English version (our source document), and make it a lot
561 easier for us to create a good Norwegian version. If you can and want
562 to help, please get in touch with me or fork the github project and
563 send pull requests with fixes. :)
</p
>
568 <title>Fri programvare -
"fri
" som i
"talefrihet
", ikke som i
"fri bar
"</title>
569 <link>http://people.skolelinux.org/pere/blog/Fri_programvare____fri__som_i__talefrihet___ikke_som_i__fri_bar_.html
</link>
570 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fri_programvare____fri__som_i__talefrihet___ikke_som_i__fri_bar_.html
</guid>
571 <pubDate>Sun,
15 Jul
2012 21:
20:
00 +
0200</pubDate>
572 <description><p
>Et ofte brukt sitat i fri programvareverden er Stallman-sitatet
573 «
<a href=
"http://www.gnu.org/philosophy/free-sw.html.en
">Free Software,
574 "free
" as in
"free speech
", not as in
"free beer
"</a
>». Men det er
575 ikke direkte overførbart til norsk, da det baserer seg på koblingen
576 gratis/fri på engelsk. En direkte oversettelse ville være «Fri
577 programvare,
"fri
" som i
"talefrihet
", ikke som
"gratis øl
"», og det
578 går jo glipp av poenget. I forbindelse med at vi er
579 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">igang
580 med å oversette
</a
> <a href=
"http://free-culture.cc/
">Free Culture
</a
>
581 av Lawrence Lessig, måtte jeg forsøke a finne en bedre
582 oversettelse.
</p
>
584 <p
>Mitt forslag til oversettelse blir dermed å droppe ølet, og heller
585 fokusere på det kjente norske uttrykket
"fri bar
". Dermed blir
586 oversettelsen «Fri programvare -
"fri
" som i
"talefrihet
", ikke som i
587 "fri bar
"».
</p
>
589 <p
>Noen som har bedre forslag?
</p
>
591 <p
>Forøvrig bruker jeg fri programvare som et samlebegrep på norsk for
592 begge de engelske uttrykkene Free Software og Open Source, jamfør
593 <a href=
"http://www.nuug.no/dokumenter/folder-friprogramvare.pdf
">NUUGs
594 lille folder om temaet
</a
>.
</p
>
599 <title>Dugnad for å sende norsk versjon av Free Culture til stortingets representanter!
</title>
600 <link>http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</link>
601 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</guid>
602 <pubDate>Wed,
11 Jul
2012 09:
00:
00 +
0200</pubDate>
603 <description><p
>Da opphavsrettsloven ble revidert i forrige runde rundt
2005, var
604 det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
605 Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
606 og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
607 representanter fikk en norsk utgave av boken
608 <a href=
"http://free-culture.cc/
">Free Culture
</a
> av Lawrence Lessig
609 som forklarte litt om problemstillingene. Vi endte opp med å
610 prioritere utvikling i
611 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>-prosjektet i
612 stedet, så den oversatte boken så aldri dagens lys. Men i forrige uke
613 ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
614 bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
615 sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
616 fordel for forlag og store mediehus fortsatt trenger en annen vinkling
617 i debatten.
</p
>
619 <p
>Planen min er å oversette boka på dugnad, sette den opp for
620 trykking med en av de mange
621 <a href=
"http://no.wikipedia.org/wiki/Trykk_på_forespørsel
">trykk på
622 forespørsel
</a
>-tjenestene, skaffe sponsor til å finansiere trykking
623 til stortingsrepresentantene og alle som har bidratt med
624 oversettelser. Kanskje vi også kan få en avtale med et forlag om
625 publisering når boka er ferdig? Kommentarene til
626 <a href=
"http://newth.net/eirik/
2011/
04/
01/e-selvpublisering/
">Eirik
628 <a href=
"http://www.espen.com/norskblogg/archives/
2008/
09/erfaringer_med_publishing_on_demand.html
">Espen
629 Andersen
</a
> om erfaringene med selvpublisering og trykk på
630 forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
631 <a href=
"http://www.lulu.com/
">Lulu
</a
> er en grei leverandør av
632 trykketjenester til prosjektet.
</p
>
634 <p
>Jeg har satt opp
635 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">et
636 Github-prosjekt
</a
> for a lage boken, basert på Docbook-utgaven jeg
637 fant fra Hans Schou. Skolelinux har hatt byggesystem for å lage
638 oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
639 kopiert og utvidet dette oppsettet. Originalteksten er i Docbook, og
640 oversettelsen gjøres i .po-filer med hjelp av vanlige
641 oversetterverktøy brukt i fri programvareverden. Dernest tar
642 byggesystemet over og lager PDF og EPUB-utgave av den oversatte
643 teksten. Resultatet kan ses i Github-prosjektet. For å komme raskt
644 igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
645 til norsk, noe som grovoversatte ca.
1300 av de ca.
1700 tekstbitene
646 boken består av. Jeg håper nå at flere kan bidra med å få
647 oversettelsen på plass, slik at teksten kan være klar i løpet av
648 høsten. Når alt er oversatt må teksten gjennomgås for feil og
649 konsistent språk. Totalt er det nok mange timer som trengs for å
650 gjennomføre oversettelsen.
</p
>
652 <p
>Økonomien i dette er ikke avskrekkende.
169
653 stortingsrepresentanter og nesten like mange varamedlemmer bør få
654 bøker, og estimert produduksjonskostnad for hver bok er rundt
6 EURO i
655 følge et raskt estimat fra Lulu. Jeg vet ennå ikke hvor mange sider
656 det blir i størrelsen
5,
5" x
8.5" (det er ca.
140 sider i A4-format),
657 så jeg gjettet på
400 sider. Jeg tror originalutgaven har nesten
400
658 sider. For
169*
2 eksemplarer snakker vi om en trykkekostnad på
659 ca.
2000 EURO, dvs. ca
15 000 NOK. Det burde være mulig å finne en
660 sponsor for å dekke en slik sum. I tillegg kommer distribusjon og
661 porto, som antagelig kommer på like mye.
</p
>
663 <p
>Kan du bidra med oversettelse og docbook-typesetting? Ta kontakt
664 og send patcher i github. Jeg legger gjerne inn folk i prosjektet
665 slik at du kan oppdatere direkte.
</p
>