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>"Free Culture
" by @lessig - The background story for Creative Commons - new edition available
</title>
11 <link>http://people.skolelinux.org/pere/blog/_Free_Culture__by__lessig___The_background_story_for_Creative_Commons___new_edition_available.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/_Free_Culture__by__lessig___The_background_story_for_Creative_Commons___new_edition_available.html
</guid>
13 <pubDate>Fri,
23 Oct
2015 12:
10:
00 +
0200</pubDate>
14 <description><p
><a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22402863.html
">Click
15 here to buy the book
</a
>.
</p
>
17 <p
>In
2004, as the
<a href=
"https://creativecommons.org/
">Creative Commons
18 movement
</a
> gained momentum, its creator Lawrence Lessig wrote the
19 book
<a href=
"https://en.wikipedia.org/wiki/Free_Culture_(book)
">Free
20 Culture
</a
> to explain the problems with increasing copyright
21 regulation and suggest some solutions. I read the book back then and
22 was moved very by it. Reading the book inspired me and changed the
23 way I looked on copyright law, and I would love it if more people
24 would read it too.
</p
>
26 <p
>Because of this, I decided in the summer of
2012 to translate it to
27 Norwegian Bokmål and publish it for those of my friends and family
28 that prefer to read books in Norwegian. I translated the book using
29 docbook and a gettext PO file, and a byproduct of this process is a
30 new edition of the English original. I
've been in touch with the
31 author during by work, and he said it was fine with him if I also
32 published an English version. So I decided to do so. Today, I made
34 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22402863.html
">available
35 for sale on Lulu.com
</a
>, for those interested in a paper book. This
38 <p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2015-
10-
23-free-culture-english-published-cover.png
"/
></p
>
40 <p
>The Norwegian Bokmål version will be available for purchase in a
41 few days. I also plan to publish a French version in a few weeks or
42 months, depending on the amount of people with knowledge of French to
43 join the translation project. So far there is only one active
44 person, but the French book is almost completely translated but
45 need some proof reading.
</p
>
47 <p
>The book is also available in PDF, ePub and MOBI formats from
48 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">my
49 github project page
</a
>. Note the ePub and MOBI versions have some
50 formatting problems I believe is due to bugs in the docbook tool
51 dbtoepub (Debian BTS issues
52 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
795842">#
795842</a
>
54 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
796871">#
796871</a
>),
55 but I have not taken the time to investigate. I recommend the PDF and
56 ePub version for now, as they seem to show up fine in the viewers I
57 have available.
</p
>
59 <p
>After the translation to Norwegian Bokmål was complete, I was able
60 to secure some sponsoring from
61 <a href=
"http://www.nuugfoundation.no/
">the NUUG Foundation
</a
> to
62 print the book. This is the reason their logo is located on the back
63 cover. I am very grateful for their contribution, and will use it to
64 give a copy of the Norwegian edition to members of the Norwegian
65 Parliament and other decision makers here in Norway.
</p
>
70 <title>French Docbook/PDF/EPUB/MOBI edition of the Free Culture book
</title>
71 <link>http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html
</link>
72 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html
</guid>
73 <pubDate>Thu,
1 Oct
2015 13:
20:
00 +
0200</pubDate>
74 <description><p
>As I wrap up the Norwegian version of
75 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Free
76 Culture
</a
> book by Lawrence Lessig (still waiting for my final proof
77 reading copy to arrive in the mail), my great
78 <a href=
"http://dblatex.sourceforge.net/
">dblatex
</a
> helper and
79 developer of the dblatex docbook processor, Benoît Guillon, decided a
80 to try to create a French version of the book. He started with the
81 French translation available from the
82 <a href=
"http://www.wikilivres.ca/wiki/Culture_libre
">Wikilivres wiki
83 pages
</a
>, and wrote a program to convert it into a PO file, allowing
84 the translation to be integrated into the po4a based framework I use
85 to create the Norwegian translation from the English edition. We meet
86 on the
<a href=
"irc://irc.freenode.net/%
23dblatex
">#dblatex IRC
87 channel
</a
> to discuss the work. If you want to help create a French
89 <a href=
"https://github.com/marsgui/free-culture-lessig
">his git
90 repository
</a
> and join us on IRC. If the French edition look good,
91 we might publish it as a paper book on lulu.com. A French version of
92 the drawings and the cover need to be provided for this to happen.
</p
>
97 <title>Book cover for the Free Culture book finally done
</title>
98 <link>http://people.skolelinux.org/pere/blog/Book_cover_for_the_Free_Culture_book_finally_done.html
</link>
99 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Book_cover_for_the_Free_Culture_book_finally_done.html
</guid>
100 <pubDate>Thu,
3 Sep
2015 21:
00:
00 +
0200</pubDate>
101 <description><p
>Creating a good looking book cover proved harder than I expected.
102 I wanted to create a cover looking similar to the original cover of
104 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Free
105 Culture
</a
> book we are translating to Norwegian, and I wanted it in
106 vector format for high resolution printing. But my inkscape knowledge
107 were not nearly good enough to pull that off.
109 <p
>But thanks to the great inkscape community, I was able to wrap up
110 the cover yesterday evening. I asked on the
111 <a href=
"irc://irc.freenode.net/%
23inkscape
">#inkscape IRC channel
</a
>
112 on Freenode for help and clues, and Marc Jeanmougin (Mc-) volunteered
113 to try to recreate it based on the PDF of the cover from the HTML
114 version. Not only did he create a
115 <a href=
"https://marc.jeanmougin.fr/share/copy1.svg
">SVG document with
116 the original and his vector version side by side
</a
>, he even provided
117 an
<a href=
"https://marc.jeanmougin.fr/share/out-
1.ogv
">instruction
118 video
</a
> explaining how he did it
</a
>. But the instruction video is
119 not easy to follow for an untrained inkscape user. The video is a
120 recording on how he did it, and he is obviously very experienced as
121 the menu selections are very quick and he mentioned on IRC that he did
122 use some keyboard shortcuts that can
't be seen on the video, but it
123 give a good idea about the inkscape operations to use to create the
124 stripes with the embossed copyright sign in the center.
</p
>
126 <p
>I took his SVG file, copied the vector image and re-sized it to fit
127 on the cover I was drawing. I am happy with the end result, and the
128 current english version look like this:
</p
>
130 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
03-free-culture-cover.png
" width=
"70%
" align=
"center
"/
>
132 <p
>I am not quite sure about the text on the back, but guess it will
133 do. I picked three quotes from the official site for the book, and
134 hope it will work to trigger the interest of potential readers. The
135 Norwegian cover will look the same, but with the texts and bar code
136 replaced with the Norwegian version.
</p
>
138 <p
>The book is very close to being ready for publication, and I expect
139 to upload the final draft to Lulu in the next few days and order a
140 final proof reading copy to verify that everything look like it should
141 before allowing everyone to order their own copy of Free Culture, in
142 English or Norwegian Bokmål. I
'm waiting to give the the productive
143 proof readers a chance to complete their work.
</p
>
148 <title>In my hand, a pocket book edition of the Norwegian Free Culture book!
</title>
149 <link>http://people.skolelinux.org/pere/blog/In_my_hand__a_pocket_book_edition_of_the_Norwegian_Free_Culture_book_.html
</link>
150 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/In_my_hand__a_pocket_book_edition_of_the_Norwegian_Free_Culture_book_.html
</guid>
151 <pubDate>Wed,
19 Aug
2015 22:
10:
00 +
0200</pubDate>
152 <description><p
>Today, finally, my first printed draft edition of the Norwegian
153 translation of Free Culture I have been working on for the last few
154 years arrived in the mail. I had to fake a cover to get the interior
155 printed, and the exterior of the book look awful, but that is
156 irrelevant at this point. I asked for a printed pocket book version
157 to get an idea about the font sizes and paper format as well as how
158 good the figures and images look in print, but also to test what the
159 pocket book version would look like. After receiving the
500 page
160 pocket book, it became obvious to me that that pocket book size is too
161 small for this book. I believe the book is too thick, and several
162 tables and figures do not look good in the size they get with that
163 small page sizes. I believe I will go with the
5.5x8.5 inch size
164 instead. A surprise discovery from the paper version was how bad the
165 URLs look in print. They are very hard to read in the colophon page.
166 The URLs are red in the PDF, but light gray on paper. I need to
167 change the color of links somehow to look better. But there is a
168 printed book in my hand, and it feels great. :)
</p
>
170 <p
>Now I only need to fix the cover, wrap up the postscript with the
171 store behind the book, and collect the last corrections from the proof
172 readers before the book is ready for proper printing. Cover artists
173 willing to work for free and create a Creative Commons licensed vector
174 file looking similar to the original is most welcome, as my skills as
175 a graphics designer are mostly missing.
</p
>
180 <title>First paper version of the Norwegian Free Culture book heading my way
</title>
181 <link>http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html
</link>
182 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html
</guid>
183 <pubDate>Sun,
9 Aug
2015 10:
15:
00 +
0200</pubDate>
184 <description><p
>Typesetting a book is harder than I hoped. As the translation is
185 mostly done, and a volunteer proof reader was going to check the text
186 on paper, it was time this summer to focus on formatting my translated
187 <a href=
"http://www.docbook.org/
">docbook
</a
> based version of the
188 <a href=
"http://free-culture.cc/
">Free Culture
</a
> book by Lawrence
189 Lessig. I
've been trying to get both docboox-xsl+fop and dblatex to
190 give me a good looking PDF, but in the end I went with dblatex, because
191 its Debian maintainer and upstream developer were responsive and very
192 helpful in solving my formatting challenges.
</p
>
194 <p
>Last night, I finally managed to create a PDF that no longer made
195 <a href=
"http://www.lulu.com/
">Lulu.com
</a
> complain after uploading,
196 and I ordered a text version of the book on paper. It is lacking a
197 proper book cover and is not tagged with the correct ISBN number, but
198 should give me an idea what the finished book will look like.
</p
>
200 <p
>Instead of using Lulu, I did consider printing the book using
201 <a href=
"http://www.createspace.com/
">CreateSpace
</a
>, but ended up
202 using Lulu because it had smaller book size options (CreateSpace seem
203 to lack pocket book with extended distribution). I looked for a
204 similar service in Norway, but have not seen anything so far. Please
205 let me know if I am missing out on something here.
</p
>
207 <p
>But I still struggle to decide the book size. Should I go for
208 pocket book (
4.25x6.875 inches /
10.8x17.5 cm) with
556 pages, Digest
209 (
5.5x8.5 inches /
14x21.6 cm) with
323 pages or US Trade (
6x8 inches /
210 15.3x22.9 cm) with
280 pages? Fewer pager give a cheaper book, and a
211 smaller book is easier to carry around. The test book I ordered was
212 pocket book sized, to give me an idea how well that fit in my hand,
213 but I suspect I will end up using a digest sized book in the end to
214 bring the prize down further.
</p
>
216 <p
>My biggest challenge at the moment is making nice cover art. My
217 inkscape skills are not yet up to the task of replicating the original
218 cover in SVG format. I also need to figure out what to write about
219 the book on the back (will most likely use the same text as the
220 description on web based book stores). I would love help with this,
221 if you are willing to license the art source and final version using
222 the same CC license as the book. My artistic skills are not really up
223 to the task.
</p
>
225 <p
>I plan to publish the book in both English and Norwegian and on
226 paper, in PDF form as well as EPUB and MOBI format. The current
227 status can as usual be found on
228 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
229 in the archive/ directory. So far I have spent all time on making the
230 PDF version look good. Someone should probably do the same with the
231 dbtoepub generated e-book. Help is definitely needed here, as I
232 expect to run out of steem before I find time to improve the epub
233 formatting.
</p
>
235 <p
>Please let me know via github if you find typos in the book or
236 discover translations that should be improved. The final proof
237 reading is being done right now, and I expect to publish the finished
238 result in a few months.
</p
>
243 <title>Typesetting DocBook footnotes as endnotes with dblatex
</title>
244 <link>http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html
</link>
245 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html
</guid>
246 <pubDate>Thu,
16 Jul
2015 18:
10:
00 +
0200</pubDate>
247 <description><p
>I
'm still working on the Norwegian version of the
248 <a href=
"http://free-culture.cc/
">Free Culture book by Lawrence
249 Lessig
</a
>, and is now working on the final typesetting and layout.
250 One of the features I want to get the structure similar to the
251 original book is to typeset the footnotes as endnotes in the notes
252 chapter. Based on the
253 <a href=
"https://bugs.debian.org/
685063">feedback from the Debian
254 maintainer and the dblatex developer
</a
>, I came up with this recipe I
255 would like to share with you. The proposal was to create a new LaTeX
256 class file and add the LaTeX code there, but this is not always
257 practical, when I want to be able to replace the class using a make
258 file variable. So my proposal misuses the latex.begindocument XSL
259 parameter value, to get a small fragment into the correct location in
260 the generated LaTeX File.
</p
>
262 <p
>First, decide where in the DocBook document to place the endnotes,
263 and add this text there:
</p
>
266 &lt;?latex \theendnotes ?
&gt;
269 <p
>Next, create a xsl stylesheet file dblatex-endnotes.xsl to add the
270 code needed to add the endnote instructions in the preamble of the
271 generated LaTeX document, with content like this:
</p
>
274 &lt;?xml version=
'1.0'?
&gt;
275 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
276 &lt;xsl:param name=
"latex.begindocument
"&gt;
277 &lt;xsl:text
&gt;
278 \usepackage{endnotes}
279 \let\footnote=\endnote
280 \def\enoteheading{\mbox{}\par\vskip-\baselineskip }
282 &lt;/xsl:text
&gt;
283 &lt;/xsl:param
&gt;
284 &lt;/xsl:stylesheet
&gt;
287 <p
>Finally, load this xsl file when running dblatex, for example like
291 dblatex --xsl-user=dblatex-endnotes.xsl freeculture.nb.xml
294 <p
>The end result can be seen on github, where
295 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">my
296 book project
</a
> is located.
</p
>
301 <title>Proof reading the Norwegian translation of Free Culture by Lessig
</title>
302 <link>http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html
</link>
303 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html
</guid>
304 <pubDate>Sat,
4 Apr
2015 09:
30:
00 +
0200</pubDate>
305 <description><p
>During eastern I had some time to continue working on the Norwegian
306 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
307 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
308 At the moment I am proof reading the finished text, looking for typos,
309 inconsistent wordings and sentences that do not flow as they should.
310 I
'm more than two thirds done with the text, and welcome others to
311 check the text up to chapter
13. The current status is available on the
312 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
313 project pages. You can also check out the
314 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>,
315 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
316 and HTML version available in the
317 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive
">archive
318 directory
</a
>.
</p
>
320 <p
>Please report typos, bugs and improvements to the github project if
321 you find any.
</p
>
326 <title>Opphavsretts-status for «Empty Socks» fra
1927?
</title>
327 <link>http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html
</link>
328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html
</guid>
329 <pubDate>Fri,
12 Dec
2014 14:
30:
00 +
0100</pubDate>
330 <description><p
>For noen dager siden
331 <a href=
"http://www.nb.no/Hva-skjer/Aktuelt/Nyheter/Tapt-filmskatt-fra-Disney-funnet-i-Nasjonalbiblioteket
">annonserte
332 Nasjonalbiblioteket gladnyheten
</a
> om at de i sine arkiver hadde
333 funnet et nitratfilm-eksemplar av en
87 år gammel Disney-film ved navn
334 Empty Socks, en film som tidligere var antatt tapt og der det i følge
335 nyhetsmeldinger var kun ca.
25 sekunder bevart for ettertiden.
336 Nasjonalbiblioteket hadde
5 minutter og
30 sekunder av filmen i sitt
337 magasin. Dette er flott for bevaringen av verdens kulturarv.
5,
5
338 minutter mindre tapt enn vi trodde av vår felles historie.
</p
>
340 <p
>Men hvordan kunne filmen gå tapt, når arkivlovene i USA krevde at
341 publiserte filmer på den tiden ble deponert i bibliotek? Forklaringen
342 har jeg fra Lawrence Lessig og boken
343 <a href=
"http://free-culture.cc/
">Free Culture
</a
>, som jeg holder på
344 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">å
345 oversette til norsk
</a
>:
</p
>
347 <p
><blockquote
>
348 <p
>Dette er delvis på grunn av loven. Opphavsrettseiere var tidlig i
349 amerikansk opphavsrettslov nødt til å deponere kopier av sine verk i
350 biblioteker. Disse kopiene skulle både sikre spredning av kunnskap,
351 og sikre at det fantes en kopi av verket tilgjengelig når vernetiden
352 utløp, slik at andre kunne få tilgang til og kopiere verket.
</p
>
354 <p
>Disse reglene gjaldt også for filmer. Men i
1915 gjorde
355 kongressbiblioteket et unntak for film. Filmer kunne bli
356 opphavsrettsbeskyttet så lenge det ble gjort slik deponering. Men
357 filmskaperne fikk så lov til å låne tilbake de deponerte filmene -
358 så lenge de ville uten noe kostnad. Bare i
1915 var det mer enn
5475
359 filmer deponert og “lånt tilbake”. Dermed var det ikke noe eksemplar
360 i noe bibliotek når vernetiden til filmen utløp. Eksemplaret
361 eksisterer - hvis den finnes i det hele tatt - i arkivbiblioteket
362 til filmselskapet.
</p
>
363 </blockquote
></p
>
365 <p
>Nyheten gjorde meg nysgjerrig på om filmen kunne være falt i det
366 fri. En
87 år gammel film kunne jo tenkes å ha blitt en del av
367 allemannseiet, slik at vi alle kan bruke den til å bygge videre på vår
368 felles kultur uten å måtte be om tillatelse - slik Walt Disney gjorde
369 det i starten av sin karriere. Jeg spurte nasjonalbiblioteket, og de
370 sa nei. Hvordan kan det ha seg med en så gammel film? Jeg besteme
371 meg for å undersøke nærmere. En kan finne informasjon om den norske
373 <a href=
"https://lovdata.no/dokument/NL/lov/
1961-
05-
12-
2">Lovdata
</a
>
374 og
</a
>Wikipedia
</A
>. Her er et relevant
<a
375 href=
"https://no.wikipedia.org/wiki/Opphavsrett#Vernetid
">utsnitt fra
376 siden om opphavsrett i den norske Wikipedia
</a
>:
</p
>
378 <p
><blockquote
>
379 Ifølge åndsverkloven §§
40-
41 utløper vernetiden for et åndsverk
70
380 år etter utløpet av opphavspersonens dødsår. [...] For filmverk
381 gjelder særlige regler: Her kommer ikke alle mulige opphavspersoner
382 i betraktning, men kun hovedregissøren, manusforfatteren,
383 dialogforfatteren og komponisten av filmmusikken. Vernetiden
384 begynner å løpe etter utgangen av dødsåret til den lengstlevende av
385 disse. [...] Der opphavspersonen er ukjent, utløper opphavsretten
70
386 år etter første kjente offentliggjørelse av verket. Det er kun de
387 økonomiske rettighetene som faller bort i det vernetiden er
388 utløpt. De ideelle rettighetene må fortsatt respekteres, noe som
389 blant annet innebærer at man plikter å navngi opphavspersonen ved
391 </blockquote
></p
>
393 <p
>I følge nettstedet
394 <a href=
"http://www.disneyshorts.org/shorts.aspx?shortID=
75">The
395 Encyclopedia of Disney Animated Shorts
</a
> er følgende personer gitt
396 æren for denne kortfilmen:
</p
>
400 <dt
>Regissør
</dt
>
401 <dd
><a href=
"https://en.wikipedia.org/wiki/Walt_Disney
">Walt Disney
</a
> (
1901-
12-
05 –
1966-
12-
15) +
70 år =
2037</dd
>
404 <dd
><a href=
"https://en.wikipedia.org/wiki/Ub_Iwerks
">Ub Iwerks
</a
> (
1901-
03-
24 –
1971-
07-
07) +
70 år =
2042
405 <br
><a href=
"https://en.wikipedia.org/wiki/Rollin_Hamilton
">Rollin
"Ham
" Hamilton
</a
> (
1898-
10-
28 -
1951-
06-
03) +
70 år =
2022
406 <br
><a href=
"https://en.wikipedia.org/wiki/Harman_and_Ising
">Hugh Harman
</a
> (
1903-
08-
31 –
1982-
11-
25) +
70 år =
2053</dd
>
409 <dd
>Mike Marcus (?-?)
</dd
>
413 <p
>Alle fødsels- og dødsdatoene er fra engelske Wikipedia. Det er
414 ikke oppgitt navn på manusforfatter, dialogforfatter og komponist, men
415 jeg mistenker at tegnerne vil få opphavsrettigheter på tegnefilmer her
416 i Norge, og tar derfor med disse. Kameramannen vil ikke få noen
417 rettigheter så vidt jeg forstår, og er derfor ignorert her.
</p
>
419 <p
>Slik jeg forstår den norske opphavsretten vil dermed dette
420 filmverket bli allemannseie (også kalt å falle i det fri) i
2053,
126
421 år etter at det ble utgitt. Hvis kun regissørens rettigheter er
422 relevante, vil det skje i
2037,
110 år etter at det ble utgitt. Etter
423 det vil enhver kunne dele det med alle de har lyst til, fremføre det
424 offentlig eller klippe og lime i det for å lage sin egen film basert
425 på det - helt uten å måtte spørre noen om lov.
</p
>
427 <p
>Måtte så Nasjonalbiblioteket spørre om lov før de kunne kopiere
428 sitt nitrat-eksemplar over på mer varig format? Nei, heldigvis.
429 Åndsverklovens §
16 sier at arkiv, bibliotek, museer og undervisnings-
430 og forskningsinstitusjoner har rett til å fremstille eksemplar av verk
431 for konserverings- og sikringsformål og andre særskilte formål.
</p
>
436 <title>98.6 percent done with the Norwegian draft translation of Free Culture
</title>
437 <link>http://people.skolelinux.org/pere/blog/
98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</link>
438 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</guid>
439 <pubDate>Wed,
23 Jul
2014 22:
40:
00 +
0200</pubDate>
440 <description><p
>This summer I finally had time to continue working on the Norwegian
441 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
442 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
443 to get a Norwegian text explaining the problems with todays copyright
444 law. Yesterday, I finally completed translated the book text. There
445 are still some foot/end notes left to translate, the colophon page
446 need to be rewritten, and a few words and phrases still need to be
447 translated, but the Norwegian text is ready for the first proof
448 reading. :) More spell checking is needed, and several illustrations
449 need to be cleaned up. The work stopped up because I had to give
450 priority to other projects the last year, and the progress graph of
451 the translation show this very well:
</p
>
453 <p
><img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
"></p
>
455 <p
>If you want to read the result, check out the
456 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
457 project pages and the
458 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>,
459 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
460 and HTML version available in the
461 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive
">archive
462 directory
</a
>.
</p
>
464 <p
>Please report typos, bugs and improvements to the github project if
465 you find any.
</p
>
470 <title>90 percent done with the Norwegian draft translation of Free Culture
</title>
471 <link>http://people.skolelinux.org/pere/blog/
90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</link>
472 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</guid>
473 <pubDate>Fri,
2 Aug
2013 10:
40:
00 +
0200</pubDate>
474 <description><p
>It has been a while since my last update. Since last summer, I
475 have worked on a Norwegian
476 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
477 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
478 to get a Norwegian text explaining the problems with the copyright
479 law. Yesterday, I finally broken the
90% mark, when counting the
480 number of strings to translate. Due to real life constraints, I have
481 not had time to work on it since March, but when the summer broke out,
482 I found time to work on it again. Still lots of work left, but the
483 first draft is nearing completion. I created a graph to show the
484 progress of the translation:
</p
>
486 <p
><img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
"></p
>
488 <p
>When the first draft is done, the translated text need to be
489 proof read, and the remaining formatting problems with images and SVG
490 drawings need to be fixed. There are probably also some index entries
491 missing that need to be added. This can be done by comparing the
492 index entries listed in the SiSU version of the book, or comparing the
493 English docbook version with the paper version. Last, the colophon
494 page with ISBN numbers etc need to be wrapped up before the release is
495 done. I should also figure out how to get correct Norwegian sorting
496 of the index pages. All docbook tools I have tried so far (xmlto,
497 docbook-xsl, dblatex) get the order of symbols and the special
498 Norwegian letters ÆØÅ wrong.
</p
>
500 <p
>There is still need for translators and people with docbook
501 knowledge, to be able to get a good looking book (I still struggle
502 with dblatex, xmlto and docbook-xsl) as well as to do the draft
503 translation and proof reading. And I would like the figures to be
504 redrawn as SVGs to make it easy to translate them. Any SVG master
505 around? There are also some legal terms that are unfamiliar to me.
506 If you want to help, please get in touch with me, and check out the
507 project files currently available from
508 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
510 <p
>If you are curious what the translated book currently look like,
512 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
514 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
515 are published on github. The HTML version is published as well, but
516 github hand it out with MIME type text/plain, confusing browsers, so I
517 saw no point in linking to that version.
</p
>
522 <title>Typesetting a short story using docbook for PDF, HTML and EPUB
</title>
523 <link>http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</link>
524 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</guid>
525 <pubDate>Sun,
24 Mar
2013 17:
30:
00 +
0100</pubDate>
526 <description><p
>A few days ago, during a discussion in
527 <a href=
"http://www.efn.no/
">EFN
</a
> about interesting books to read
528 about copyright and the data retention directive, a suggestion to read
529 the
1968 short story Kodémus by
530 <a href=
"http://web2.gyldendal.no/toraage/
">Tore Åge Bringsværd
</a
>
531 came up. The text was only available in old paper books, and thus not
532 easily available for current and future generations. Some of the
533 people participating in the discussion contacted the author, and
534 reported back
2013-
03-
19 that the author was OK with releasing the
535 short story using a
<a href=
"http://www.creativecommons.org/
">Creative
536 Commons
</a
> license. The text was quickly scanned and OCR-ed, and we
537 were ready to start on the editing and typesetting.
</p
>
539 <p
>As I already had some experience formatting text in my project to
540 provide a Norwegian version of the Free Culture book by Lawrence
541 Lessig, I chipped in and set up a
542 <a href=
"http://www.docbook.org/
">DocBook
</a
> processing framework to
543 generate PDF, HTML and EPUB version of the short story. The tools to
544 transform DocBook to different formats are already in my Linux
545 distribution of choice,
<a href=
"http://www.debian.org/
">Debian
</a
>, so
546 all I had to do was to use the
547 <a href=
"http://dblatex.sourceforge.net/
">dblatex
</a
>,
548 <a href=
"http://docbook.sourceforge.net/release/xsl/current/epub/README
">dbtoepub
</a
>
549 and
<a href=
"https://fedorahosted.org/xmlto/
">xmlto
</a
> tools to do the
550 conversion. After a few days, we decided to replace dblatex with
552 <a href=
"http://wiki.docbook.org/DocBookXslStylesheets
">docbook-xsl
</a
>),
553 to get the copyright information to show up in the PDF and to get a
554 nicer
&lt;variablelist
&gt; typesetting, but that is just a minor
555 technical detail.
</p
>
557 <p
>There were a few challenges, of course. We want to typeset the
558 short story to look like the original, and that require fairly good
559 control over the layout. The original short story have three
560 parts/scenes separated by a single horizontally centred star (*), and
561 the paragraphs do not contain only flowing text, but dialogs and text
562 that started on a new line in the middle of the paragraph.
</p
>
564 <p
>I initially solved the first challenge by using a paragraph with a
565 single star in it, ie
&lt;para
&gt;*
&lt;/para
&gt;, but it made sure a
566 placeholder indicated where the scene shifted. This did not look too
567 good without the centring. The next approach was to create a new
568 preprocessor directive
&lt;?newscene?
&gt;, mapping to
"&lt;hr/
&gt;
"
569 for HTML and
"&lt;fo:block text-align=
"center
"&gt;
&lt;fo:leader
570 leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
&lt;/fo:block
&gt;
"
571 for FO/PDF output (did not try to implement this in dblatex, as we had
572 switched at this time). The HTML XSL file looked like this:
</p
>
574 <p
><blockquote
><pre
>
575 &lt;?xml version=
'1.0'?
&gt;
576 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
577 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
579 &lt;/xsl:template
&gt;
580 &lt;/xsl:stylesheet
&gt;
581 </pre
></blockquote
></p
>
583 <p
>And the FO/PDF XSL file looked like this:
</p
>
585 <p
><blockquote
><pre
>
586 &lt;?xml version=
'1.0'?
&gt;
587 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
588 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
589 &lt;fo:block text-align=
"center
"&gt;
590 &lt;fo:leader leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
591 &lt;/fo:block
&gt;
592 &lt;/xsl:template
&gt;
593 &lt;/xsl:stylesheet
&gt;
594 </pre
></blockquote
></p
>
596 <p
>Finally, I came across the
&lt;bridgehead
&gt; tag, which seem to be
597 a good fit for the task at hand, and I replaced
&lt;?newscene?
&gt;
598 with
&lt;bridgehead
&gt;*
&lt;/bridgehead
&gt;. It isn
't centred, but we
599 can fix it with some XSL rule if the current visual layout isn
't
602 <p
>I did not find a good DocBook compliant way to solve the
603 linebreak/paragraph challenge, so I ended up creating a new processor
604 directive
&lt;?linebreak?
&gt;, mapping to
&lt;br/
&gt; in HTML, and
605 &lt;fo:block/
&gt; in FO/PDF. I suspect there are better ways to do
606 this, and welcome ideas and patches on github. The HTML XSL file now
607 look like this:
</p
>
609 <p
><blockquote
><pre
>
610 &lt;?xml version=
'1.0'?
&gt;
611 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
612 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
614 &lt;/xsl:template
&gt;
615 &lt;/xsl:stylesheet
&gt;
616 </pre
></blockquote
></p
>
618 <p
>And the FO/PDF XSL file looked like this:
</p
>
620 <p
><blockquote
><pre
>
621 &lt;?xml version=
'1.0'?
&gt;
622 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'
623 xmlns:fo=
"http://www.w3.org/
1999/XSL/Format
"&gt;
624 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
625 &lt;fo:block/
&gt;
626 &lt;/xsl:template
&gt;
627 &lt;/xsl:stylesheet
&gt;
628 </pre
></blockquote
></p
>
630 <p
>One unsolved challenge is our wish to expose different ISBN numbers
631 per publication format, while keeping all of them in some conditional
632 structure in the DocBook source. No idea how to do this, so we ended
633 up listing all the ISBN numbers next to their format in the colophon
636 <p
>If you want to check out the finished result, check out the
637 <a href=
"https://github.com/sickel/kodemus
">source repository at
639 (
<a href=
"https://github.com/EFN/kodemus
">future/new/official
640 repository
</a
>). We expect it to be ready and announced in a few
646 <title>Piratpartiet på opphavs-retrett?
</title>
647 <link>http://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html
</link>
648 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html
</guid>
649 <pubDate>Wed,
19 Dec
2012 13:
10:
00 +
0100</pubDate>
650 <description><p
>Jeg ble overrasket over å se at Piratpartiet i
651 <a href=
"http://www.aftenposten.no/kultur/Piratpartiet-stiller-til-Stortingsvalget-
7073298.html
">Aftenposten
</a
>
652 er referert på følgende:
</p
>
655 Når det gjelder retten til opphavsrett for kulturproduktene, mener
656 Piratpartiet av levetid +
14 år er tilfredsstillende.
659 <p
>Det betyr en vernetid langt ut over det kommersielle livet til de
660 aller fleste opphavsrettsbeskyttede verker, og er i strid med slik i
661 hvert fall jeg har tolket punkt
5 i
662 <a href=
"http://people.opera.com/howcome/
2012/piratpartiet/kjerneprogram.html
">kjerneprogrammet
663 til Piratpartiet
</a
>:
</p
>
666 <p
><strong
>5: Åndsverk og patenter: tilbake til start
</strong
></p
>
668 <table border=
"1">
669 <tr
><th
>forslag:
</th
><td
>14 års opphavsrett og ingen
670 programvarepatenter
</td
></tr
>
672 <tr
><th
>grunn:
</th
><td
>Den første loven om opphavsrett spesifiserte
14
673 års vernetid. Senere har mediabransjens lobbyister stadig presset
674 loven mot lengre vern, nå er det
70 år etter forfatters død. Dette
675 gjør at mange verk glemmes og går tapt, noe som er skadelig for norsk
676 språk og kultur. Vi til tilbake til start:
14 års
677 vernetid. Patentloven sier klart at dataprogrammer ikke kan
678 patenteres. Likevel klarer patentadvokater å lure gjennom
679 programvarepatenter. Slike patenter gjør dingsene våre dyrere og kan i
680 enkelte tilfelle stoppe dem helt.
</th
></tr
>
684 <p
>Den opprinnelige opphavsretten var på
14 år totalt, ikke
14 år
685 etter opphavspersonens død. Jeg tenkte først dette kanskje var
686 feilsitering fra Aftenposten, men jeg finner samme påstand i en
<a
687 href=
"http://piratpartietnorge.org/om-gramo-og-piratpolitikken/
">bloggpost
688 fra Geir Aaslid
</a
> på Piratpartietes offisielle nettsider. Der
689 skriver han følgende:
</p
>
692 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
693 mange bransjer, med ulike behov. Enhver reform er en forbedring men
694 det er nærliggende å anta at en opphavsrett på levetid +
14 år er
695 fullt ut tilfredstillende for musikk, film, litteratur og spill.
698 <p
>Det virker dermed på meg som om Piratpartiet allerede har gjort
699 retrett fra sin beundringsverdige holdning om at det holdt med
14 års
700 total vernetid, til sin nye som tar utgangspunkt i levetiden til
701 opphavspersonen. Jeg håper det baserer seg på en misforståelse hos
702 piratlederen som blir korrigert tilbake til
14 års total vernetid før
703 partiet stiller til valg.
</p
>
705 <p
>Hvis du lurer på hvilke problemer lang vernetid bringer med seg,
706 anbefaler jeg å lese boken
<a href=
"http://free-culture.cc/
">Free
707 Culture
</a
> av Lawrence Lessig. Jeg og en liten gruppe andre er igang
709 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">oversette
710 boken til bokmål
</a
> og tar gjerne imot hjelp med oversettelse og
711 korrekturlesing.
</p
>
713 <p
><strong
>Oppdatering
2012-
12-
20</strong
>: Oppdaget at
714 <a href=
"http://piratpartietnorge.org/om-gramo-og-piratpolitikken/
">bloggposten
715 til Geir Aaslid
</a
> er endret siden i går, og nå inneholder følgende
716 avsnitt i stedet for det jeg siterte over:
</p
>
719 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
720 mange bransjer, med ulike behov. Enhver reform er en forbedring men
721 det er nærliggende å anta at en opphavsrett lik levetiden, evt +
14 år
722 er fullt ut tilfredstillende for mange skapere av musikk, film,
723 litteratur og spill. Det er for det meste de store forlagene som er
727 <p
>I tillegg har det dukket opp en setning nederst
"Dette dokumentet
728 er et utkast til svar på et angrep på Piratpartiet fra Gramo. Det
729 endrer seg derfor over tid og den endelige versjonen er det som blir
730 publisert på Hardware.no
", som tyder på at originalformuleringen ikke
731 var veloverveid og sitatet i Aftenposten kanskje var basert på en
732 misforståelse.
</p
>
737 <title>Why isn
't the value of copyright taxed?
</title>
738 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_the_value_of_copyright_taxed_.html
</link>
739 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_the_value_of_copyright_taxed_.html
</guid>
740 <pubDate>Sat,
17 Nov
2012 11:
30:
00 +
0100</pubDate>
741 <description><p
>While working on a
742 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Norwegian
743 translation of the Free Culture by Lawrence Lessig
</a
> (
76% done),
744 which cover the problems with todays copyright law and how it stifles
745 creativity, one idea occurred to me. The idea is to get the tax
746 office to help make more works enter the public domain and also help
747 make it easier to clear rights for using copyrighted works.
</p
>
749 <p
>I mentioned this idea briefly during Yesterdays
750 <a href=
"http://www.farmann.no/
2012/
11/
14/john-perry-barlow-in-oslo-friday-nov-
16
751 -
15-
30-
19-
00/
">presentation
752 by John Perry Barlow
</a
>, and concluded that it was best to put it
753 in writing for a wider audience. The idea is not really based on the
754 argument that copyrighted works are
"intellectual property
", as the
755 core requirement is that copyrighted work have value for the copyright
756 holder and the tax office like to collect their share from any value
757 controlled by the citizens in a country. I
'm sharing the idea here to
758 let others consider it and perhaps shoot it down with a fresh set of
761 <p
>Most valuables are taxed by the government. At least here in
762 Norway, the amount of money you have, the value of our land property,
763 the value of your house, the value of your car, the value of our
764 stocks and other valuables are all added together. If the tax value
765 of these values exceed your debt, you have to pay the tax office some
766 taxes for these values. And copyrighted work have value. It have
767 value for the rights holder, who can earn money selling access to the
768 work. But it is not included in the tax calculations? Why not?
</p
>
770 <p
>If the government want to tax copyrighted works, it would want to
771 maintain a database of all the copyrighted works and who are the
772 rights holders for a given works, to be able to associate the works
773 value to the right citizen or company for tax purposes. If such
774 database exist, it will become a lot easier to find out who to talk to
775 for clearing permissions to use a copyrighted work, which is a very
776 hard operation with todays copyright law. To ensure that copyright
777 holders keep the database up-to-date, it would have to become a
778 requirement to be able to collect money for granting access to
779 copyrighted works that the work is listed in the database with the
780 correct right holder.
</p
>
782 <p
>If copyright causes copyright holders to have to pay more taxes,
783 they will have a small incentive to
"disown
" their copyright, and let
784 the work enter the public domain. For works with several right holders
785 one of the right holders could state (and get it registered in the
786 database) that she do not need to be consulted when clearing rights to
787 use the work in question and thus will not get any income from that
788 work. Stating this would have to be impossible to revert and stop the
789 tax office from adding the value of that work to the given citizens
790 tax calculation. I assume the copyright law would stay the same,
791 allowing creators to pick a license of their choosing, and also
792 allowing them to put their work directly in the public domain. The
793 existence of such database will make it even easier to clear rights,
794 and if the right holders listed in the database is taxed, this system
795 would increase the amount of works that enter the public domain.
</p
>
797 <p
>The effect would be that the tax office help to make it easier to
798 get rights to use the works that have not yet entered the public
799 domain and help to get more work into the public domain and .
</p
>
801 <p
>Why have such taxing not happened yet? I am sure the tax office
802 would like to tax copyrighted work values if they could.
</p
>
807 <title>Seventy percent done with Norwegian docbook version of Free Culture
</title>
808 <link>http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</link>
809 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</guid>
810 <pubDate>Sun,
23 Sep
2012 09:
30:
00 +
0200</pubDate>
811 <description><p
>Since this summer, I have worked in my spare time on a Norwegian
<a
812 href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
<a
813 href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
814 The reason is that this book is a great primer on what problems exist
815 in the current copyright laws, and I want it to be available also for
816 those that are reluctant do read an English book.
819 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
820 for volunteers
</a
> to help me, but too few have volunteered so far,
821 and progress is a bit slow. Anyway, today I broken the
70 percent
822 mark for the first rough translation. At the moment, less than
700
823 strings (paragraphs, index terms, titles) are left to translate. With
824 my current progress of
10-
20 strings per day, it will take a while to
825 complete the translation. This graph show the updated progress:
</p
>
827 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
829 <p
>Progress have slowed down lately due to family and work
830 commitments. If you want to help, please get in touch, and check out
831 the project files currently available from
832 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
834 <p
>If you are curious what the translated book currently look like,
836 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
838 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
839 are published on github. The HTML version is published as well, but
840 github hand it out with MIME type text/plain, confusing browsers, so I
841 saw no point in linking to that version.
</p
>
846 <title>Half way there with translated docbook version of Free Culture
</title>
847 <link>http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</link>
848 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</guid>
849 <pubDate>Fri,
17 Aug
2012 21:
50:
00 +
0200</pubDate>
850 <description><p
>In my spare time, I currently work on a Norwegian
851 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
852 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
853 to get a Norwegian text explaining the problems with the copyright law
854 I can give to my parents and others that are reluctant to read an
855 English book. It is a marvellous set of examples on how the ever
856 expanding copyright regulations hurt culture and society. When the
857 translation is done, I hope to find funding to print and ship a copy
858 to all the members of the Norwegian parliament, before they sit down
859 to debate the latest revisions to the Norwegian copyright law. This
861 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
862 for volunteers
</a
> to help me, and I have been able to secure the
863 valuable contribution from at least one other Norwegian.
</p
>
865 <p
>Two days ago, we finally broke the
50% mark. Then more than
50% of
866 the number of strings to translate (normally paragraphs, but also
867 titles and index entries are also counted). All parts from the
868 beginning up to and including chapter four is translated. So is
869 chapters six, seven and the conclusion. I created a graph to show the
872 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
874 <p
>The number of strings to translate increase as I insert the index
875 entries into the docbook. They were missing with the docbook version
876 I initially started with. There are still quite a few index entries
877 missing, but everyone starting with A, B, O, Z and Y are done. I
878 currently focus on completing the index entries, to get a complete
879 english version of the docbook source.
</p
>
881 <p
>There is still need for translators and people with docbook
882 knowledge, to be able to get a good looking book (I still struggle
883 with dblatex, xmlto and docbook-xsl) as well as to do the draft
884 translation and proof reading. And I would like the figures to be
885 redrawn as SVGs to make it easy to translate them. Any SVG master
886 around? I am sure there are some legal terms that are unfamiliar to
887 me. If you want to help, please get in touch, and check out the
888 project files currently available from
<a
889 href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
891 <p
>If you are curious what the translated book currently look like,
893 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
895 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
896 are published on github. The HTML version is published as well, but
897 github hand it out with MIME type text/plain, confusing browsers, so I
898 saw no point in linking to that version.
</p
>
903 <title>Notes on language codes for Norwegian docbook processing...
</title>
904 <link>http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</link>
905 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</guid>
906 <pubDate>Fri,
10 Aug
2012 21:
00:
00 +
0200</pubDate>
907 <description><p
>In
<a href=
"http://www.docbook.org/
">docbook
</a
> one can specify
908 the language used at the top, and the processing pipeline will use
909 this information to pick the correct translations for
'chapter
',
'see
910 also
',
'index
' etc. And for most languages used with docbook, I guess
911 this work just fine. For example a German user can start the document
912 with
&lt;book lang=
"de
"&gt;, and the document will show up with the
913 correct content with any of the docbook processors. This is not the
914 case for the language
915 <a href=
"http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
">I
916 am working with at the moment
</a
>, Norwegian Bokmål.
</p
>
918 <p
>For a while, I was confused about which language code to use,
919 because I was unable to find any language code that would work across
920 all tools. I am currently testing dblatex, xmlto, docbook-xsl, and
921 dbtoepub, and they do not handle Norwegian Bokmål the same way. Some
922 of them do not handle it at all.
</p
>
924 <p
>A bit of background information is probably needed to understand
925 this mess. Norwegian is not one, but two written variants. The
926 variants are Norwegian Nynorsk and Norwegian Bokmål. There are three
927 two letter language codes associated with these languages, Norwegian
928 is
'no
', Norwegian Nynorsk is
'nn
' and Norwegian Bokmål is
'nb
'.
929 Historically the
'no
' language code was used for Norwegian Bokmål, but
930 many years ago this was found to be å bad idea, and the recommendation
931 is to use the most specific language code instead, to avoid confusion.
932 In the transition period it is a good idea to make sure
'no
' was an
933 alias for
'nb
'.
</p
>
935 <p
>Back to docbook processing tools in Debian. The dblatex tool only
936 understand
'nn
'. There are translations for
'no
', but not
'nb
' (BTS
937 <a href=
"http://bugs.debian.org/
684391">#
684391</a
>), but due to a bug
938 (BTS
<a href=
"http://bugs.debian.org/
682936">#
682936</a
>) the
'no
'
939 language code is not recognised. The docbook-xsl tool chain only
940 recognise
'nn
' and
'nb
', but not
'no
'. The xmlto tool only recognise
941 'nn
' and
'nb
', but not
'no
'. The end result that there is no language
942 code I can use to get the docbook file working with all of these tools
943 at the same time. :(
</p
>
945 <p
>The correct solution is to use
&lt;book lang=
"nb
"&gt;, but it will
946 take time before that will work with all the free software docbook
947 processors. :(
</p
>
949 <p
>Oh, the joy of well integrated tools. :/
</p
>
954 <title>Best way to create a docbook book?
</title>
955 <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</link>
956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</guid>
957 <pubDate>Tue,
31 Jul
2012 22:
00:
00 +
0200</pubDate>
958 <description><p
>I tried to send this text to the
959 <a href=
"https://lists.oasis-open.org/archives/docbook-apps/
">docbook-apps
960 mailing list at lists.oasis-open.org
</a
>, but it only accept messages
961 from subscribers and rejected my post, and I completely lack the
962 bandwidth required to subscribe to another mailing list, so instead I
963 try to post my message here and hope my blog readers can help me
966 <p
>I am quite new to docbook processing, and am climbing a steep
967 learning curve at the moment.
</p
>
969 <p
>To give you some background, I am working on a Norwegian
970 translation of the book Free Culture by Lawrence Lessig, and I use
971 docbook to handle the process. The files to build the book are
973 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
974 The book got around
400 pages with parts, images, footnotes, tables,
975 index entries etc, which has proven to be a challenge for the free
976 software docbook processors. My build platform is Debian GNU/Linux
979 <p
>I want to build PDF, EPUB and HTML version of the book, and have
980 tried different tool chains to do the conversion from docbook to these
981 formats. I am currently focusing on the PDF version, and have a few
986 <li
>Using dblatex, the
&lt;part
&gt; handling is not the way I want to,
987 as
&lt;/part
&gt; do not really end the
&lt;part
&gt;. (See
988 <a href=
"http://bugs.debian.org/
683166">BTS report #
683166</a
>), the
989 xetex backend (needed to process UTF-
8) give incorrect hyphens in
990 index references spanning several pages (See
991 <a href=
"http://bugs.debian.org/
682901">BTS report #
682901</a
>), and
992 I am unable to get the norwegian template texts (See
993 <a href=
"http://bugs.debian.org/
682936">BTS report #
682936</a
>).
</li
>
995 <li
>Using straight xmlto fail with some latex error (See
996 <a href=
"http://bugs.debian.org/
683163">BTS report
997 #
683163</a
>).
</li
>
999 <li
>Using xmlto with the fop backend fail to handle images (do not
1000 show up in the PDF), fail to handle a long footnote (overlap
1001 footnote and text body, see
1002 <a href=
"http://bugs.debian.org/
683197">BTS report #
683197</a
>), and
1003 fail to create a correct index (some lack page ref, and the page
1004 refs listed are not right).
</li
>
1006 <li
>Using xmlto with the dblatex backend behave like dblatex.
</li
>
1008 <li
>Using docbook-xls with xsltproc + fop have the same footnote and
1009 index problems the xmlto + fop processing.
</li
>
1013 <p
>So I wonder, what would be the best way to create the PDF version
1014 of this book? Are some of the bugs found above solved in new or
1015 experimental versions of some docbook tool chain?
</p
>
1017 <p
>What about HTML and EPUB versions?
</p
>
1022 <title>Free Culture in Norwegian -
5 chapters done,
74 percent left to do
</title>
1023 <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</link>
1024 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</guid>
1025 <pubDate>Sat,
21 Jul
2012 20:
00:
00 +
0200</pubDate>
1026 <description><p
>I reported earlier that I am working on
1027 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">a
1028 norwegian version
</a
> of the book
1029 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
1030 Progress is good, and yesterday I got a major contribution from Anders
1031 Hagen Jarmund completing chapter six. The source files as well as a
1032 PDF and EPUB version of this book are available from
1033 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
1035 <p
>I am happy to report that the draft for the first two chapters
1036 (preface, introduction) is complete, and three other chapters are also
1037 completely translated. This completes
26 percent of the number of
1038 strings (equivalent to paragraphs) in the book, and there is thus
74
1039 percent left to translate. A graph of the progress is present at the
1040 bottom of the github project page. There is still room for more
1041 contributors. Get in touch or send github pull requests with fixes if
1042 you got time and are willing to help make this book make it to
1045 <p
>The book translation framework could also be a good basis for other
1046 translations, if you want the book to be available in your
1052 <title>Call for help from docbook expert to tag Free Culture by Lawrence Lessig
</title>
1053 <link>http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</link>
1054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</guid>
1055 <pubDate>Mon,
16 Jul
2012 22:
50:
00 +
0200</pubDate>
1056 <description><p
>I am currently working on a
1057 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">project
1058 to translate
</a
> the book
1059 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig
1060 to Norwegian. And the source we base our translation on is the
1061 <a href=
"http://en.wikipedia.org/wiki/DocBook
">docbook
</a
> version, to
1062 allow us to use po4a and .po files to handle the translation, and for
1063 this to work well the docbook source document need to be properly
1064 tagged. The source files of this project is available from
1065 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
1067 <p
>The problem is that the docbook source have flaws, and we have
1068 no-one involved in the project that is a docbook expert. Is there a
1069 docbook expert somewhere that is interested in helping us create a
1070 well tagged docbook version of the book, and adjust our build process
1071 for the PDF, EPUB and HTML version of the book? This will provide a
1072 well tagged English version (our source document), and make it a lot
1073 easier for us to create a good Norwegian version. If you can and want
1074 to help, please get in touch with me or fork the github project and
1075 send pull requests with fixes. :)
</p
>
1080 <title>Fri programvare -
"fri
" som i
"talefrihet
", ikke som i
"fri bar
"</title>
1081 <link>http://people.skolelinux.org/pere/blog/Fri_programvare____fri__som_i__talefrihet___ikke_som_i__fri_bar_.html
</link>
1082 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fri_programvare____fri__som_i__talefrihet___ikke_som_i__fri_bar_.html
</guid>
1083 <pubDate>Sun,
15 Jul
2012 21:
20:
00 +
0200</pubDate>
1084 <description><p
>Et ofte brukt sitat i fri programvareverden er Stallman-sitatet
1085 «
<a href=
"http://www.gnu.org/philosophy/free-sw.html.en
">Free Software,
1086 "free
" as in
"free speech
", not as in
"free beer
"</a
>». Men det er
1087 ikke direkte overførbart til norsk, da det baserer seg på koblingen
1088 gratis/fri på engelsk. En direkte oversettelse ville være «Fri
1089 programvare,
"fri
" som i
"talefrihet
", ikke som
"gratis øl
"», og det
1090 går jo glipp av poenget. I forbindelse med at vi er
1091 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">igang
1092 med å oversette
</a
> <a href=
"http://free-culture.cc/
">Free Culture
</a
>
1093 av Lawrence Lessig, måtte jeg forsøke a finne en bedre
1094 oversettelse.
</p
>
1096 <p
>Mitt forslag til oversettelse blir dermed å droppe ølet, og heller
1097 fokusere på det kjente norske uttrykket
"fri bar
". Dermed blir
1098 oversettelsen «Fri programvare -
"fri
" som i
"talefrihet
", ikke som i
1099 "fri bar
"».
</p
>
1101 <p
>Noen som har bedre forslag?
</p
>
1103 <p
>Forøvrig bruker jeg fri programvare som et samlebegrep på norsk for
1104 begge de engelske uttrykkene Free Software og Open Source, jamfør
1105 <a href=
"http://www.nuug.no/dokumenter/folder-friprogramvare.pdf
">NUUGs
1106 lille folder om temaet
</a
>.
</p
>
1111 <title>Dugnad for å sende norsk versjon av Free Culture til stortingets representanter!
</title>
1112 <link>http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</link>
1113 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</guid>
1114 <pubDate>Wed,
11 Jul
2012 09:
00:
00 +
0200</pubDate>
1115 <description><p
>Da opphavsrettsloven ble revidert i forrige runde rundt
2005, var
1116 det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
1117 Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
1118 og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
1119 representanter fikk en norsk utgave av boken
1120 <a href=
"http://free-culture.cc/
">Free Culture
</a
> av Lawrence Lessig
1121 som forklarte litt om problemstillingene. Vi endte opp med å
1122 prioritere utvikling i
1123 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>-prosjektet i
1124 stedet, så den oversatte boken så aldri dagens lys. Men i forrige uke
1125 ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
1126 bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
1127 sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
1128 fordel for forlag og store mediehus fortsatt trenger en annen vinkling
1129 i debatten.
</p
>
1131 <p
>Planen min er å oversette boka på dugnad, sette den opp for
1132 trykking med en av de mange
1133 <a href=
"http://no.wikipedia.org/wiki/Trykk_på_forespørsel
">trykk på
1134 forespørsel
</a
>-tjenestene, skaffe sponsor til å finansiere trykking
1135 til stortingsrepresentantene og alle som har bidratt med
1136 oversettelser. Kanskje vi også kan få en avtale med et forlag om
1137 publisering når boka er ferdig? Kommentarene til
1138 <a href=
"http://newth.net/eirik/
2011/
04/
01/e-selvpublisering/
">Eirik
1140 <a href=
"http://www.espen.com/norskblogg/archives/
2008/
09/erfaringer_med_publishing_on_demand.html
">Espen
1141 Andersen
</a
> om erfaringene med selvpublisering og trykk på
1142 forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
1143 <a href=
"http://www.lulu.com/
">Lulu
</a
> er en grei leverandør av
1144 trykketjenester til prosjektet.
</p
>
1146 <p
>Jeg har satt opp
1147 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">et
1148 Github-prosjekt
</a
> for a lage boken, basert på Docbook-utgaven jeg
1149 fant fra Hans Schou. Skolelinux har hatt byggesystem for å lage
1150 oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
1151 kopiert og utvidet dette oppsettet. Originalteksten er i Docbook, og
1152 oversettelsen gjøres i .po-filer med hjelp av vanlige
1153 oversetterverktøy brukt i fri programvareverden. Dernest tar
1154 byggesystemet over og lager PDF og EPUB-utgave av den oversatte
1155 teksten. Resultatet kan ses i Github-prosjektet. For å komme raskt
1156 igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
1157 til norsk, noe som grovoversatte ca.
1300 av de ca.
1700 tekstbitene
1158 boken består av. Jeg håper nå at flere kan bidra med å få
1159 oversettelsen på plass, slik at teksten kan være klar i løpet av
1160 høsten. Når alt er oversatt må teksten gjennomgås for feil og
1161 konsistent språk. Totalt er det nok mange timer som trengs for å
1162 gjennomføre oversettelsen.
</p
>
1164 <p
>Økonomien i dette er ikke avskrekkende.
169
1165 stortingsrepresentanter og nesten like mange varamedlemmer bør få
1166 bøker, og estimert produduksjonskostnad for hver bok er rundt
6 EURO i
1167 følge et raskt estimat fra Lulu. Jeg vet ennå ikke hvor mange sider
1168 det blir i størrelsen
5,
5" x
8.5" (det er ca.
140 sider i A4-format),
1169 så jeg gjettet på
400 sider. Jeg tror originalutgaven har nesten
400
1170 sider. For
169*
2 eksemplarer snakker vi om en trykkekostnad på
1171 ca.
2000 EURO, dvs. ca
15 000 NOK. Det burde være mulig å finne en
1172 sponsor for å dekke en slik sum. I tillegg kommer distribusjon og
1173 porto, som antagelig kommer på like mye.
</p
>
1175 <p
>Kan du bidra med oversettelse og docbook-typesetting? Ta kontakt
1176 og send patcher i github. Jeg legger gjerne inn folk i prosjektet
1177 slik at du kan oppdatere direkte.
</p
>
projects / homepage.git / blob