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>New book,
"Fri kultur
" by @lessig, a Norwegian Bokmål translation of
"Free Culture
" from
2004</title>
11 <link>http://people.skolelinux.org/pere/blog/New_book___Fri_kultur__by__lessig__a_Norwegian_Bokm_l_translation_of__Free_Culture__from_2004.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_book___Fri_kultur__by__lessig__a_Norwegian_Bokm_l_translation_of__Free_Culture__from_2004.html
</guid>
13 <pubDate>Sat,
31 Oct
2015 09:
00:
00 +
0100</pubDate>
14 <description><p
>People keep asking me where to get the various forms of the book I
15 published last week, the Norwegian Bokmål edition of Lawrence Lessigs
16 book Free Culture. It was published on paper via lulu.com, and is
17 also available in PDF, ePub and MOBI format. I currently sell the
18 paper edition for self cost from lulu.com, but might extend the
19 distribution to book stores like Amazon and Barnes
& Noble later.
20 This will double the price and force me to make a profit from selling
21 the book. Anyway, here are links to get the book in different
26 <li
><a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22406445.html
">Buy
27 paper edition from lulu.com
</a
></li
>
29 <li
><a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.pdf
">Download
30 PDF, size
7.9 MiB
</a
> (gratis/free)
</li
>
32 <li
><a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.epub
">Download
33 ePub, size
11 MiB
</a
> (gratis/free)
</li
>
35 <li
><a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.mobi
">Download
36 MOBI, size
3.8 MiB
</a
> (gratis/free)
</li
>
40 <p
>Note that the MOBI version have problems with the table of content,
41 at least with the viewers I have been able to test. And the ePub file
42 have several problems according to
43 <a href=
"https://github.com/IDPF/epubcheck
">epubcheck
</a
>, but seem
44 to display fine in the viewers I have tested. All the files needed to
45 create the book in various forms are available from
46 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">the
47 github project page
</a
>.
</p
>
49 <p
>The project got press coverage from the Norwegian IT news site
50 digi.no. Check out the article
51 "<a href=
"http://www.digi.no/juss_og_samfunn/
2015/
10/
29/vil-apne-politikernes-oyne-for-creative-commons
">Vil
52 åpne politikernes øyne for Creative Commons
</a
>".
</li
>
54 <p
>I
've
<a href=
"http://people.skolelinux.org/pere/blog/tags/freeculture
">blogged
55 about the project
</a
> as it moved along. The blogs document the translation
56 progress and insights I had along the way.
</p
>
61 <title>Gavebok overlevert Stortinget i dag
</title>
62 <link>http://people.skolelinux.org/pere/blog/Gavebok_overlevert_Stortinget_i_dag.html
</link>
63 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gavebok_overlevert_Stortinget_i_dag.html
</guid>
64 <pubDate>Thu,
29 Oct
2015 11:
50:
00 +
0100</pubDate>
65 <description><p
>Like før kl.
11 i dag leverte jeg fem esker med gaveinnpakkede
66 bøker til Stortinget, for utdeling til alle stortingsrepresentanter.
67 Det ble etterfulgt av følgende pressemelding. Stor takk til NUUG for
68 lån av epostliste for å sende ut pressemeldingen.
</p
>
72 <p
><strong
>Er opphavsretten for streng, spør ny bok
</strong
></p
>
74 <p
>I dag kommer boken «
<a href=
"http://free-culture.cc/
">Fri
75 kultur
</a
>» av Lawrence Lessig ut på norsk. Boken handler om
76 utviklingen og utvidelsene opphavsretten har hatt de siste
40 årene.
77 Boken er i dag gitt i gave til alle stortingsrepresentantene.
78 Oversetter og utgiver Petter Reinholdtsen håper Stortinget vil tenke
79 seg om to ganger neste gang det er snakk om utvidelse av
80 opphavsretten.
</p
>
82 <p
>Boken forteller om hvordan store medieaktører ved hjelp av
83 opphavsretten bruker teknologi til å begrense kulturen og kontrollere
84 kreativiteten. Den er skrevet av stifteren av
85 <a href=
"https://creativecommons.org/
">Creative Commons
</a
>, professor
86 Lawrence Lessig, som for tiden er med i kampen om å bli Demokratenes
87 <a href=
"https://lessig2016.us/
">presidentkandidat i USA sitt
88 presidentvalg i
2016</a
>. Lessig ble sist omtalt i norske medier da
89 NRK i høst viste dokumentaren «Kampen for et demokratisk internett»
91 <a href=
"https://archive.org/details/TheInternetsOwnBoyTheStoryOfAaronSwartz
">tilgjengelig
92 fra The Internet Archive
</a
>.
</p
>
94 <p
>Boken beskriver hvordan opphavsrettens makt i USA har blitt
95 betydelig utvidet etter
1974 langs fem kritiske akser: varighet (fra
96 32 til
95 år), omfang (fra utgivere til alle), rekkevidde (gjelder nå
97 enhver fremvisning via datamaskin), kontroll (avledede verk er
98 definert så bredt at i praksis alle nye åndsverk risikerer søksmål fra
99 en opphavsrettsinnehaver) og til sist maktkonsentrasjon og integrering
100 av mediebransjen. Den dokumenterer også hvordan medieindustrien har
101 lyktes med å bruke rettsvesenet til å begrense konkurranse, og i
102 praksis har skaffet seg vetorett over teknologiske nyvinninger.
103 Nedlasting av fritt, lovlig og i utgangspunktet gratis materiale
104 stoppes med tekniske sperrer og lobbyert lovvern av sperrene.
</p
>
106 <p
>Utvidelsene illustreres i boken med ulike eksempler. For eksempel
107 en demonstrasjon av at Walt Disney ville ha blitt ansett som en
108 opphavsrettspirat dersom han gjorde i dag det han gjorde på
109 1930-tallet. Boken beskriver hvordan vern av åndsverk er bra, men at
110 mer vern ikke nødvendigvis er bedre.
<?p
>
112 <p
>Petter Reinholdtsen, som sammen med flere frivillige har oversatt
113 boken på fritiden de siste
3 årene, håper at boken vil gjøre en
114 forskjell. «Når en vet hvordan opphavsrettens varighet i Norge, uten
115 opposisjon på Stortinget, ble utvidet nok en gang i mai i fjor, og
116 hvordan Norges handelspartner USA gjennom de nye handelsavtalene
117 Trans-Pacific Partnership og Transatlantic Trade and Investment
119 <a href=
"https://www.eff.org/deeplinks/
2015/
10/final-leaked-tpp-text-all-we-feared
">ønsker
120 å utvide opphavsrettens makt også i andre land
</a
>, håper jeg at flere
121 vil spørre: Er det virkelig fornuftig å gjøre de samme utvidelsene i
122 Norge?», spør han. «Jeg håper boken kan bidra til kunnskap og
123 forståelse, og kan gi Stortinget et bedre grunnlag til å ta riktige
124 beslutninger som ivaretar befolkningens og samfunnets interesser i
127 <p
>Petter Reinholdtsen er en mangeårig fri programvareutvikler som har
128 vært med på å lage systemer som operativsystemet Debian, IT-løsningen
129 Skolelinux, borgerportalen FiksGataMi og innsynstjenesten Mimes brønn.
130 Han forteller han selv har opplevd problemene utvidet varighet,
131 omfang, rekkevidde og kontroll i opphavsretten medfører og at boken
132 var en oppvekker. «Jeg håper andre finner boken like interessant som
133 jeg gjorde. Boken kan
134 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">lastes
135 gratis ned fra github
</a
> eller
136 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22406445.html
">kjøpes
137 på papir fra lulu.com
</a
>,» avslutter Reinholdtsen.
</p
>
141 <p
>Så får vi se om det har noen positiv effekt. :)
</p
>
146 <title>"Fri kultur
" av @lessig - norsk utgave av
"Free Culture
" tilgjengelig på papir, PDF og ePub
</title>
147 <link>http://people.skolelinux.org/pere/blog/_Fri_kultur__av__lessig___norsk_utgave_av__Free_Culture__tilgjengelig_p__papir__PDF_og_ePub.html
</link>
148 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/_Fri_kultur__av__lessig___norsk_utgave_av__Free_Culture__tilgjengelig_p__papir__PDF_og_ePub.html
</guid>
149 <pubDate>Wed,
28 Oct
2015 09:
30:
00 +
0100</pubDate>
150 <description><p
><a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22406445.html
">Klikk her for å kjøpe boken
</a
>.
</p
>
152 <p
>I
2004, mens
<a href=
"https://creativecommons.org/
">Creative
153 Commons-bevegelsen
</a
> vokste frem, skrev bevegelsens stifter Lawrence
155 <a href=
"https://en.wikipedia.org/wiki/Free_Culture_(book)
">Free
156 Culture
</a
> for å forklare problemene med økene åndsverksregulering og
157 for å foreslå noen løsninger. Jeg leste boken den gangen, og den både
158 inspirerte meg og endret på hvordan jeg så på opphavsrettslovigving.
159 Jeg skulle ønske flere folk leste denne boken. Den gir en god
160 gjennomgang av hvordan økende åndsverksregulering skader både
161 nyskapning og kulturlivet, og skisserer hvordan både lovgivere og oss
162 vanlige borgere kan bidra for å få slutt på dette.
</p
>
164 <p
>Derfor bestemte jeg meg sommeren
2012 for å oversette den til norsk
165 bokmål og gjøre den tilgjengelig for de blant mine venner og familie
166 som foretrekker å lese bøker på norsk. Jeg oversatte boken ved hjelp
167 av docbook og en gettext PO-fil, og endte opp med to utgaver, en på
168 norsk og en på engelsk. Den engelske publiserte jeg i forrige uke, og
169 den norske utgaven på papir
170 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22406445.html
">er
171 nå klar for salg
</a
>. Jeg fikk heldigvis hjelp med oversetting og
172 korrekturlesing av den norske utgaven fra en rekke frivillige. Se
173 side
245 for en komplett liste. Slik ser omslaget ut:
175 <p align=
"center
"><a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22406445.html
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2015-
10-
28-free-culture-norwegian-published-cover.png
"/
></a
></p
>
177 <p
>I tillegg til den norske og engelske utgaven holder vi på med en
178 fransk utgave. Den koordineres av dblatex-utvikleren Benoît Guillon,
179 og oversettelsen var komplett denne uka men må korrekturleses før den
180 kan gis ut. Flere frivillige trengs her, så ta kontakt med Benoît
181 hvis du vil bidra.
</p
>
183 <p
>Boken er også tilgjengelig i PDF, ePub og MOBI-format fra
184 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">min
185 github-prosjektside
</a
>. Merk at ePub og MOBI-utgavene har noen
186 formatteringsproblemer som jeg tror kommer av feil i docbook-verktøyet
187 dbtoepub (Debian BTS-rapporter
188 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
795842">#
795842</a
>
190 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
796871">#
796871</a
>),
191 men jeg har ikke tatt meg tid til å undersøke problemene. For de som
192 vil ha elektronisk kopi anbefaler jeg å bruke PDF- og ePub-utgaven i
193 denne omgang, da de ser ut til å hånderes bra av de fremviserne jeg
194 har tilgjengelig.
</p
>
196 <p
>Etter at oversettelsen til bokmål var ferdig klarte jeg å overtale
197 <a href=
"http://www.nuugfoundation.no/
">NUUG Foundation
</a
> til å
198 sponse trykking av boken. Det er årsaken til at stiftelsens logo er
199 på baksiden av omslaget. Jeg er svært takknemlig for dette, og bruker
200 bidraget til å gi en kopi av den norske utgaven til alle
201 Stortingsrepresentanter og andre beslutningstakere her i Norge.
</p
>
206 <title>"Free Culture
" by @lessig - The background story for Creative Commons - new edition available
</title>
207 <link>http://people.skolelinux.org/pere/blog/_Free_Culture__by__lessig___The_background_story_for_Creative_Commons___new_edition_available.html
</link>
208 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/_Free_Culture__by__lessig___The_background_story_for_Creative_Commons___new_edition_available.html
</guid>
209 <pubDate>Fri,
23 Oct
2015 12:
10:
00 +
0200</pubDate>
210 <description><p
><a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22402863.html
">Click
211 here to buy the book
</a
>.
</p
>
213 <p
>In
2004, as the
<a href=
"https://creativecommons.org/
">Creative Commons
214 movement
</a
> gained momentum, its creator Lawrence Lessig wrote the
215 book
<a href=
"https://en.wikipedia.org/wiki/Free_Culture_(book)
">Free
216 Culture
</a
> to explain the problems with increasing copyright
217 regulation and suggest some solutions. I read the book back then and
218 was very moved by it. Reading the book inspired me and changed the
219 way I looked on copyright law, and I would love it if more people
220 would read it too.
</p
>
222 <p
>Because of this, I decided in the summer of
2012 to translate it to
223 Norwegian Bokmål and publish it for those of my friends and family
224 that prefer to read books in Norwegian. I translated the book using
225 docbook and a gettext PO file, and a byproduct of this process is a
226 new edition of the English original. I
've been in touch with the
227 author during by work, and he said it was fine with him if I also
228 published an English version. So I decided to do so. Today, I made
230 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22402863.html
">available
231 for sale on Lulu.com
</a
>, for those interested in a paper book. This
234 <p align=
"center
"><a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22402863.html
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2015-
10-
23-free-culture-english-published-cover.png
"/
></a
></p
>
236 <p
>The Norwegian Bokmål version will be available for purchase in a
237 few days. I also plan to publish a French version in a few weeks or
238 months, depending on the amount of people with knowledge of French to
239 join the translation project. So far there is only one active
240 person, but the French book is almost completely translated but
241 need some proof reading.
</p
>
243 <p
>The book is also available in PDF, ePub and MOBI formats from
244 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">my
245 github project page
</a
>. Note the ePub and MOBI versions have some
246 formatting problems I believe is due to bugs in the docbook tool
247 dbtoepub (Debian BTS issues
248 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
795842">#
795842</a
>
250 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
796871">#
796871</a
>),
251 but I have not taken the time to investigate. I recommend the PDF and
252 ePub version for now, as they seem to show up fine in the viewers I
253 have available.
</p
>
255 <p
>After the translation to Norwegian Bokmål was complete, I was able
256 to secure some sponsoring from
257 <a href=
"http://www.nuugfoundation.no/
">the NUUG Foundation
</a
> to
258 print the book. This is the reason their logo is located on the back
259 cover. I am very grateful for their contribution, and will use it to
260 give a copy of the Norwegian edition to members of the Norwegian
261 Parliament and other decision makers here in Norway.
</p
>
266 <title>French Docbook/PDF/EPUB/MOBI edition of the Free Culture book
</title>
267 <link>http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html
</link>
268 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html
</guid>
269 <pubDate>Thu,
1 Oct
2015 13:
20:
00 +
0200</pubDate>
270 <description><p
>As I wrap up the Norwegian version of
271 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Free
272 Culture
</a
> book by Lawrence Lessig (still waiting for my final proof
273 reading copy to arrive in the mail), my great
274 <a href=
"http://dblatex.sourceforge.net/
">dblatex
</a
> helper and
275 developer of the dblatex docbook processor, Benoît Guillon, decided a
276 to try to create a French version of the book. He started with the
277 French translation available from the
278 <a href=
"http://www.wikilivres.ca/wiki/Culture_libre
">Wikilivres wiki
279 pages
</a
>, and wrote a program to convert it into a PO file, allowing
280 the translation to be integrated into the po4a based framework I use
281 to create the Norwegian translation from the English edition. We meet
282 on the
<a href=
"irc://irc.freenode.net/%
23dblatex
">#dblatex IRC
283 channel
</a
> to discuss the work. If you want to help create a French
285 <a href=
"https://github.com/marsgui/free-culture-lessig
">his git
286 repository
</a
> and join us on IRC. If the French edition look good,
287 we might publish it as a paper book on lulu.com. A French version of
288 the drawings and the cover need to be provided for this to happen.
</p
>
293 <title>Book cover for the Free Culture book finally done
</title>
294 <link>http://people.skolelinux.org/pere/blog/Book_cover_for_the_Free_Culture_book_finally_done.html
</link>
295 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Book_cover_for_the_Free_Culture_book_finally_done.html
</guid>
296 <pubDate>Thu,
3 Sep
2015 21:
00:
00 +
0200</pubDate>
297 <description><p
>Creating a good looking book cover proved harder than I expected.
298 I wanted to create a cover looking similar to the original cover of
300 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Free
301 Culture
</a
> book we are translating to Norwegian, and I wanted it in
302 vector format for high resolution printing. But my inkscape knowledge
303 were not nearly good enough to pull that off.
305 <p
>But thanks to the great inkscape community, I was able to wrap up
306 the cover yesterday evening. I asked on the
307 <a href=
"irc://irc.freenode.net/%
23inkscape
">#inkscape IRC channel
</a
>
308 on Freenode for help and clues, and Marc Jeanmougin (Mc-) volunteered
309 to try to recreate it based on the PDF of the cover from the HTML
310 version. Not only did he create a
311 <a href=
"https://marc.jeanmougin.fr/share/copy1.svg
">SVG document with
312 the original and his vector version side by side
</a
>, he even provided
313 an
<a href=
"https://marc.jeanmougin.fr/share/out-
1.ogv
">instruction
314 video
</a
> explaining how he did it
</a
>. But the instruction video is
315 not easy to follow for an untrained inkscape user. The video is a
316 recording on how he did it, and he is obviously very experienced as
317 the menu selections are very quick and he mentioned on IRC that he did
318 use some keyboard shortcuts that can
't be seen on the video, but it
319 give a good idea about the inkscape operations to use to create the
320 stripes with the embossed copyright sign in the center.
</p
>
322 <p
>I took his SVG file, copied the vector image and re-sized it to fit
323 on the cover I was drawing. I am happy with the end result, and the
324 current english version look like this:
</p
>
326 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
03-free-culture-cover.png
" width=
"70%
" align=
"center
"/
>
328 <p
>I am not quite sure about the text on the back, but guess it will
329 do. I picked three quotes from the official site for the book, and
330 hope it will work to trigger the interest of potential readers. The
331 Norwegian cover will look the same, but with the texts and bar code
332 replaced with the Norwegian version.
</p
>
334 <p
>The book is very close to being ready for publication, and I expect
335 to upload the final draft to Lulu in the next few days and order a
336 final proof reading copy to verify that everything look like it should
337 before allowing everyone to order their own copy of Free Culture, in
338 English or Norwegian Bokmål. I
'm waiting to give the the productive
339 proof readers a chance to complete their work.
</p
>
344 <title>In my hand, a pocket book edition of the Norwegian Free Culture book!
</title>
345 <link>http://people.skolelinux.org/pere/blog/In_my_hand__a_pocket_book_edition_of_the_Norwegian_Free_Culture_book_.html
</link>
346 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/In_my_hand__a_pocket_book_edition_of_the_Norwegian_Free_Culture_book_.html
</guid>
347 <pubDate>Wed,
19 Aug
2015 22:
10:
00 +
0200</pubDate>
348 <description><p
>Today, finally, my first printed draft edition of the Norwegian
349 translation of Free Culture I have been working on for the last few
350 years arrived in the mail. I had to fake a cover to get the interior
351 printed, and the exterior of the book look awful, but that is
352 irrelevant at this point. I asked for a printed pocket book version
353 to get an idea about the font sizes and paper format as well as how
354 good the figures and images look in print, but also to test what the
355 pocket book version would look like. After receiving the
500 page
356 pocket book, it became obvious to me that that pocket book size is too
357 small for this book. I believe the book is too thick, and several
358 tables and figures do not look good in the size they get with that
359 small page sizes. I believe I will go with the
5.5x8.5 inch size
360 instead. A surprise discovery from the paper version was how bad the
361 URLs look in print. They are very hard to read in the colophon page.
362 The URLs are red in the PDF, but light gray on paper. I need to
363 change the color of links somehow to look better. But there is a
364 printed book in my hand, and it feels great. :)
</p
>
366 <p
>Now I only need to fix the cover, wrap up the postscript with the
367 store behind the book, and collect the last corrections from the proof
368 readers before the book is ready for proper printing. Cover artists
369 willing to work for free and create a Creative Commons licensed vector
370 file looking similar to the original is most welcome, as my skills as
371 a graphics designer are mostly missing.
</p
>
376 <title>First paper version of the Norwegian Free Culture book heading my way
</title>
377 <link>http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html
</link>
378 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html
</guid>
379 <pubDate>Sun,
9 Aug
2015 10:
15:
00 +
0200</pubDate>
380 <description><p
>Typesetting a book is harder than I hoped. As the translation is
381 mostly done, and a volunteer proof reader was going to check the text
382 on paper, it was time this summer to focus on formatting my translated
383 <a href=
"http://www.docbook.org/
">docbook
</a
> based version of the
384 <a href=
"http://free-culture.cc/
">Free Culture
</a
> book by Lawrence
385 Lessig. I
've been trying to get both docboox-xsl+fop and dblatex to
386 give me a good looking PDF, but in the end I went with dblatex, because
387 its Debian maintainer and upstream developer were responsive and very
388 helpful in solving my formatting challenges.
</p
>
390 <p
>Last night, I finally managed to create a PDF that no longer made
391 <a href=
"http://www.lulu.com/
">Lulu.com
</a
> complain after uploading,
392 and I ordered a text version of the book on paper. It is lacking a
393 proper book cover and is not tagged with the correct ISBN number, but
394 should give me an idea what the finished book will look like.
</p
>
396 <p
>Instead of using Lulu, I did consider printing the book using
397 <a href=
"http://www.createspace.com/
">CreateSpace
</a
>, but ended up
398 using Lulu because it had smaller book size options (CreateSpace seem
399 to lack pocket book with extended distribution). I looked for a
400 similar service in Norway, but have not seen anything so far. Please
401 let me know if I am missing out on something here.
</p
>
403 <p
>But I still struggle to decide the book size. Should I go for
404 pocket book (
4.25x6.875 inches /
10.8x17.5 cm) with
556 pages, Digest
405 (
5.5x8.5 inches /
14x21.6 cm) with
323 pages or US Trade (
6x8 inches /
406 15.3x22.9 cm) with
280 pages? Fewer pager give a cheaper book, and a
407 smaller book is easier to carry around. The test book I ordered was
408 pocket book sized, to give me an idea how well that fit in my hand,
409 but I suspect I will end up using a digest sized book in the end to
410 bring the prize down further.
</p
>
412 <p
>My biggest challenge at the moment is making nice cover art. My
413 inkscape skills are not yet up to the task of replicating the original
414 cover in SVG format. I also need to figure out what to write about
415 the book on the back (will most likely use the same text as the
416 description on web based book stores). I would love help with this,
417 if you are willing to license the art source and final version using
418 the same CC license as the book. My artistic skills are not really up
419 to the task.
</p
>
421 <p
>I plan to publish the book in both English and Norwegian and on
422 paper, in PDF form as well as EPUB and MOBI format. The current
423 status can as usual be found on
424 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
425 in the archive/ directory. So far I have spent all time on making the
426 PDF version look good. Someone should probably do the same with the
427 dbtoepub generated e-book. Help is definitely needed here, as I
428 expect to run out of steem before I find time to improve the epub
429 formatting.
</p
>
431 <p
>Please let me know via github if you find typos in the book or
432 discover translations that should be improved. The final proof
433 reading is being done right now, and I expect to publish the finished
434 result in a few months.
</p
>
439 <title>Typesetting DocBook footnotes as endnotes with dblatex
</title>
440 <link>http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html
</link>
441 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html
</guid>
442 <pubDate>Thu,
16 Jul
2015 18:
10:
00 +
0200</pubDate>
443 <description><p
>I
'm still working on the Norwegian version of the
444 <a href=
"http://free-culture.cc/
">Free Culture book by Lawrence
445 Lessig
</a
>, and is now working on the final typesetting and layout.
446 One of the features I want to get the structure similar to the
447 original book is to typeset the footnotes as endnotes in the notes
448 chapter. Based on the
449 <a href=
"https://bugs.debian.org/
685063">feedback from the Debian
450 maintainer and the dblatex developer
</a
>, I came up with this recipe I
451 would like to share with you. The proposal was to create a new LaTeX
452 class file and add the LaTeX code there, but this is not always
453 practical, when I want to be able to replace the class using a make
454 file variable. So my proposal misuses the latex.begindocument XSL
455 parameter value, to get a small fragment into the correct location in
456 the generated LaTeX File.
</p
>
458 <p
>First, decide where in the DocBook document to place the endnotes,
459 and add this text there:
</p
>
462 &lt;?latex \theendnotes ?
&gt;
465 <p
>Next, create a xsl stylesheet file dblatex-endnotes.xsl to add the
466 code needed to add the endnote instructions in the preamble of the
467 generated LaTeX document, with content like this:
</p
>
470 &lt;?xml version=
'1.0'?
&gt;
471 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
472 &lt;xsl:param name=
"latex.begindocument
"&gt;
473 &lt;xsl:text
&gt;
474 \usepackage{endnotes}
475 \let\footnote=\endnote
476 \def\enoteheading{\mbox{}\par\vskip-\baselineskip }
478 &lt;/xsl:text
&gt;
479 &lt;/xsl:param
&gt;
480 &lt;/xsl:stylesheet
&gt;
483 <p
>Finally, load this xsl file when running dblatex, for example like
487 dblatex --xsl-user=dblatex-endnotes.xsl freeculture.nb.xml
490 <p
>The end result can be seen on github, where
491 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">my
492 book project
</a
> is located.
</p
>
497 <title>Proof reading the Norwegian translation of Free Culture by Lessig
</title>
498 <link>http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html
</link>
499 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html
</guid>
500 <pubDate>Sat,
4 Apr
2015 09:
30:
00 +
0200</pubDate>
501 <description><p
>During eastern I had some time to continue working on the Norwegian
502 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
503 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
504 At the moment I am proof reading the finished text, looking for typos,
505 inconsistent wordings and sentences that do not flow as they should.
506 I
'm more than two thirds done with the text, and welcome others to
507 check the text up to chapter
13. The current status is available on the
508 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
509 project pages. You can also check out the
510 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>,
511 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
512 and HTML version available in the
513 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive
">archive
514 directory
</a
>.
</p
>
516 <p
>Please report typos, bugs and improvements to the github project if
517 you find any.
</p
>
522 <title>Opphavsretts-status for «Empty Socks» fra
1927?
</title>
523 <link>http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html
</link>
524 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html
</guid>
525 <pubDate>Fri,
12 Dec
2014 14:
30:
00 +
0100</pubDate>
526 <description><p
>For noen dager siden
527 <a href=
"http://www.nb.no/Hva-skjer/Aktuelt/Nyheter/Tapt-filmskatt-fra-Disney-funnet-i-Nasjonalbiblioteket
">annonserte
528 Nasjonalbiblioteket gladnyheten
</a
> om at de i sine arkiver hadde
529 funnet et nitratfilm-eksemplar av en
87 år gammel Disney-film ved navn
530 Empty Socks, en film som tidligere var antatt tapt og der det i følge
531 nyhetsmeldinger var kun ca.
25 sekunder bevart for ettertiden.
532 Nasjonalbiblioteket hadde
5 minutter og
30 sekunder av filmen i sitt
533 magasin. Dette er flott for bevaringen av verdens kulturarv.
5,
5
534 minutter mindre tapt enn vi trodde av vår felles historie.
</p
>
536 <p
>Men hvordan kunne filmen gå tapt, når arkivlovene i USA krevde at
537 publiserte filmer på den tiden ble deponert i bibliotek? Forklaringen
538 har jeg fra Lawrence Lessig og boken
539 <a href=
"http://free-culture.cc/
">Free Culture
</a
>, som jeg holder på
540 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">å
541 oversette til norsk
</a
>:
</p
>
543 <p
><blockquote
>
544 <p
>Dette er delvis på grunn av loven. Opphavsrettseiere var tidlig i
545 amerikansk opphavsrettslov nødt til å deponere kopier av sine verk i
546 biblioteker. Disse kopiene skulle både sikre spredning av kunnskap,
547 og sikre at det fantes en kopi av verket tilgjengelig når vernetiden
548 utløp, slik at andre kunne få tilgang til og kopiere verket.
</p
>
550 <p
>Disse reglene gjaldt også for filmer. Men i
1915 gjorde
551 kongressbiblioteket et unntak for film. Filmer kunne bli
552 opphavsrettsbeskyttet så lenge det ble gjort slik deponering. Men
553 filmskaperne fikk så lov til å låne tilbake de deponerte filmene -
554 så lenge de ville uten noe kostnad. Bare i
1915 var det mer enn
5475
555 filmer deponert og “lånt tilbake”. Dermed var det ikke noe eksemplar
556 i noe bibliotek når vernetiden til filmen utløp. Eksemplaret
557 eksisterer - hvis den finnes i det hele tatt - i arkivbiblioteket
558 til filmselskapet.
</p
>
559 </blockquote
></p
>
561 <p
>Nyheten gjorde meg nysgjerrig på om filmen kunne være falt i det
562 fri. En
87 år gammel film kunne jo tenkes å ha blitt en del av
563 allemannseiet, slik at vi alle kan bruke den til å bygge videre på vår
564 felles kultur uten å måtte be om tillatelse - slik Walt Disney gjorde
565 det i starten av sin karriere. Jeg spurte nasjonalbiblioteket, og de
566 sa nei. Hvordan kan det ha seg med en så gammel film? Jeg besteme
567 meg for å undersøke nærmere. En kan finne informasjon om den norske
569 <a href=
"https://lovdata.no/dokument/NL/lov/
1961-
05-
12-
2">Lovdata
</a
>
570 og
</a
>Wikipedia
</A
>. Her er et relevant
<a
571 href=
"https://no.wikipedia.org/wiki/Opphavsrett#Vernetid
">utsnitt fra
572 siden om opphavsrett i den norske Wikipedia
</a
>:
</p
>
574 <p
><blockquote
>
575 Ifølge åndsverkloven §§
40-
41 utløper vernetiden for et åndsverk
70
576 år etter utløpet av opphavspersonens dødsår. [...] For filmverk
577 gjelder særlige regler: Her kommer ikke alle mulige opphavspersoner
578 i betraktning, men kun hovedregissøren, manusforfatteren,
579 dialogforfatteren og komponisten av filmmusikken. Vernetiden
580 begynner å løpe etter utgangen av dødsåret til den lengstlevende av
581 disse. [...] Der opphavspersonen er ukjent, utløper opphavsretten
70
582 år etter første kjente offentliggjørelse av verket. Det er kun de
583 økonomiske rettighetene som faller bort i det vernetiden er
584 utløpt. De ideelle rettighetene må fortsatt respekteres, noe som
585 blant annet innebærer at man plikter å navngi opphavspersonen ved
587 </blockquote
></p
>
589 <p
>I følge nettstedet
590 <a href=
"http://www.disneyshorts.org/shorts.aspx?shortID=
75">The
591 Encyclopedia of Disney Animated Shorts
</a
> er følgende personer gitt
592 æren for denne kortfilmen:
</p
>
596 <dt
>Regissør
</dt
>
597 <dd
><a href=
"https://en.wikipedia.org/wiki/Walt_Disney
">Walt Disney
</a
> (
1901-
12-
05 –
1966-
12-
15) +
70 år =
2037</dd
>
600 <dd
><a href=
"https://en.wikipedia.org/wiki/Ub_Iwerks
">Ub Iwerks
</a
> (
1901-
03-
24 –
1971-
07-
07) +
70 år =
2042
601 <br
><a href=
"https://en.wikipedia.org/wiki/Rollin_Hamilton
">Rollin
"Ham
" Hamilton
</a
> (
1898-
10-
28 -
1951-
06-
03) +
70 år =
2022
602 <br
><a href=
"https://en.wikipedia.org/wiki/Harman_and_Ising
">Hugh Harman
</a
> (
1903-
08-
31 –
1982-
11-
25) +
70 år =
2053</dd
>
605 <dd
>Mike Marcus (?-?)
</dd
>
609 <p
>Alle fødsels- og dødsdatoene er fra engelske Wikipedia. Det er
610 ikke oppgitt navn på manusforfatter, dialogforfatter og komponist, men
611 jeg mistenker at tegnerne vil få opphavsrettigheter på tegnefilmer her
612 i Norge, og tar derfor med disse. Kameramannen vil ikke få noen
613 rettigheter så vidt jeg forstår, og er derfor ignorert her.
</p
>
615 <p
>Slik jeg forstår den norske opphavsretten vil dermed dette
616 filmverket bli allemannseie (også kalt å falle i det fri) i
2053,
126
617 år etter at det ble utgitt. Hvis kun regissørens rettigheter er
618 relevante, vil det skje i
2037,
110 år etter at det ble utgitt. Etter
619 det vil enhver kunne dele det med alle de har lyst til, fremføre det
620 offentlig eller klippe og lime i det for å lage sin egen film basert
621 på det - helt uten å måtte spørre noen om lov.
</p
>
623 <p
>Måtte så Nasjonalbiblioteket spørre om lov før de kunne kopiere
624 sitt nitrat-eksemplar over på mer varig format? Nei, heldigvis.
625 Åndsverklovens §
16 sier at arkiv, bibliotek, museer og undervisnings-
626 og forskningsinstitusjoner har rett til å fremstille eksemplar av verk
627 for konserverings- og sikringsformål og andre særskilte formål.
</p
>
632 <title>98.6 percent done with the Norwegian draft translation of Free Culture
</title>
633 <link>http://people.skolelinux.org/pere/blog/
98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</link>
634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</guid>
635 <pubDate>Wed,
23 Jul
2014 22:
40:
00 +
0200</pubDate>
636 <description><p
>This summer I finally had time to continue working on the Norwegian
637 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
638 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
639 to get a Norwegian text explaining the problems with todays copyright
640 law. Yesterday, I finally completed translated the book text. There
641 are still some foot/end notes left to translate, the colophon page
642 need to be rewritten, and a few words and phrases still need to be
643 translated, but the Norwegian text is ready for the first proof
644 reading. :) More spell checking is needed, and several illustrations
645 need to be cleaned up. The work stopped up because I had to give
646 priority to other projects the last year, and the progress graph of
647 the translation show this very well:
</p
>
649 <p
><img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
"></p
>
651 <p
>If you want to read the result, check out the
652 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>
653 project pages and the
654 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>,
655 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
656 and HTML version available in the
657 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive
">archive
658 directory
</a
>.
</p
>
660 <p
>Please report typos, bugs and improvements to the github project if
661 you find any.
</p
>
666 <title>90 percent done with the Norwegian draft translation of Free Culture
</title>
667 <link>http://people.skolelinux.org/pere/blog/
90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</link>
668 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html
</guid>
669 <pubDate>Fri,
2 Aug
2013 10:
40:
00 +
0200</pubDate>
670 <description><p
>It has been a while since my last update. Since last summer, I
671 have worked on a Norwegian
672 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
673 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
674 to get a Norwegian text explaining the problems with the copyright
675 law. Yesterday, I finally broken the
90% mark, when counting the
676 number of strings to translate. Due to real life constraints, I have
677 not had time to work on it since March, but when the summer broke out,
678 I found time to work on it again. Still lots of work left, but the
679 first draft is nearing completion. I created a graph to show the
680 progress of the translation:
</p
>
682 <p
><img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
"></p
>
684 <p
>When the first draft is done, the translated text need to be
685 proof read, and the remaining formatting problems with images and SVG
686 drawings need to be fixed. There are probably also some index entries
687 missing that need to be added. This can be done by comparing the
688 index entries listed in the SiSU version of the book, or comparing the
689 English docbook version with the paper version. Last, the colophon
690 page with ISBN numbers etc need to be wrapped up before the release is
691 done. I should also figure out how to get correct Norwegian sorting
692 of the index pages. All docbook tools I have tried so far (xmlto,
693 docbook-xsl, dblatex) get the order of symbols and the special
694 Norwegian letters ÆØÅ wrong.
</p
>
696 <p
>There is still need for translators and people with docbook
697 knowledge, to be able to get a good looking book (I still struggle
698 with dblatex, xmlto and docbook-xsl) as well as to do the draft
699 translation and proof reading. And I would like the figures to be
700 redrawn as SVGs to make it easy to translate them. Any SVG master
701 around? There are also some legal terms that are unfamiliar to me.
702 If you want to help, please get in touch with me, and check out the
703 project files currently available from
704 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
706 <p
>If you are curious what the translated book currently look like,
708 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
710 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
711 are published on github. The HTML version is published as well, but
712 github hand it out with MIME type text/plain, confusing browsers, so I
713 saw no point in linking to that version.
</p
>
718 <title>Typesetting a short story using docbook for PDF, HTML and EPUB
</title>
719 <link>http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</link>
720 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html
</guid>
721 <pubDate>Sun,
24 Mar
2013 17:
30:
00 +
0100</pubDate>
722 <description><p
>A few days ago, during a discussion in
723 <a href=
"http://www.efn.no/
">EFN
</a
> about interesting books to read
724 about copyright and the data retention directive, a suggestion to read
725 the
1968 short story Kodémus by
726 <a href=
"http://web2.gyldendal.no/toraage/
">Tore Åge Bringsværd
</a
>
727 came up. The text was only available in old paper books, and thus not
728 easily available for current and future generations. Some of the
729 people participating in the discussion contacted the author, and
730 reported back
2013-
03-
19 that the author was OK with releasing the
731 short story using a
<a href=
"http://www.creativecommons.org/
">Creative
732 Commons
</a
> license. The text was quickly scanned and OCR-ed, and we
733 were ready to start on the editing and typesetting.
</p
>
735 <p
>As I already had some experience formatting text in my project to
736 provide a Norwegian version of the Free Culture book by Lawrence
737 Lessig, I chipped in and set up a
738 <a href=
"http://www.docbook.org/
">DocBook
</a
> processing framework to
739 generate PDF, HTML and EPUB version of the short story. The tools to
740 transform DocBook to different formats are already in my Linux
741 distribution of choice,
<a href=
"http://www.debian.org/
">Debian
</a
>, so
742 all I had to do was to use the
743 <a href=
"http://dblatex.sourceforge.net/
">dblatex
</a
>,
744 <a href=
"http://docbook.sourceforge.net/release/xsl/current/epub/README
">dbtoepub
</a
>
745 and
<a href=
"https://fedorahosted.org/xmlto/
">xmlto
</a
> tools to do the
746 conversion. After a few days, we decided to replace dblatex with
748 <a href=
"http://wiki.docbook.org/DocBookXslStylesheets
">docbook-xsl
</a
>),
749 to get the copyright information to show up in the PDF and to get a
750 nicer
&lt;variablelist
&gt; typesetting, but that is just a minor
751 technical detail.
</p
>
753 <p
>There were a few challenges, of course. We want to typeset the
754 short story to look like the original, and that require fairly good
755 control over the layout. The original short story have three
756 parts/scenes separated by a single horizontally centred star (*), and
757 the paragraphs do not contain only flowing text, but dialogs and text
758 that started on a new line in the middle of the paragraph.
</p
>
760 <p
>I initially solved the first challenge by using a paragraph with a
761 single star in it, ie
&lt;para
&gt;*
&lt;/para
&gt;, but it made sure a
762 placeholder indicated where the scene shifted. This did not look too
763 good without the centring. The next approach was to create a new
764 preprocessor directive
&lt;?newscene?
&gt;, mapping to
"&lt;hr/
&gt;
"
765 for HTML and
"&lt;fo:block text-align=
"center
"&gt;
&lt;fo:leader
766 leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
&lt;/fo:block
&gt;
"
767 for FO/PDF output (did not try to implement this in dblatex, as we had
768 switched at this time). The HTML XSL file looked like this:
</p
>
770 <p
><blockquote
><pre
>
771 &lt;?xml version=
'1.0'?
&gt;
772 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
773 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
775 &lt;/xsl:template
&gt;
776 &lt;/xsl:stylesheet
&gt;
777 </pre
></blockquote
></p
>
779 <p
>And the FO/PDF XSL file looked like this:
</p
>
781 <p
><blockquote
><pre
>
782 &lt;?xml version=
'1.0'?
&gt;
783 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
784 &lt;xsl:template match=
"processing-instruction(
'newscene
')
"&gt;
785 &lt;fo:block text-align=
"center
"&gt;
786 &lt;fo:leader leader-pattern=
"rule
" rule-thickness=
"0.5pt
"/
&gt;
787 &lt;/fo:block
&gt;
788 &lt;/xsl:template
&gt;
789 &lt;/xsl:stylesheet
&gt;
790 </pre
></blockquote
></p
>
792 <p
>Finally, I came across the
&lt;bridgehead
&gt; tag, which seem to be
793 a good fit for the task at hand, and I replaced
&lt;?newscene?
&gt;
794 with
&lt;bridgehead
&gt;*
&lt;/bridgehead
&gt;. It isn
't centred, but we
795 can fix it with some XSL rule if the current visual layout isn
't
798 <p
>I did not find a good DocBook compliant way to solve the
799 linebreak/paragraph challenge, so I ended up creating a new processor
800 directive
&lt;?linebreak?
&gt;, mapping to
&lt;br/
&gt; in HTML, and
801 &lt;fo:block/
&gt; in FO/PDF. I suspect there are better ways to do
802 this, and welcome ideas and patches on github. The HTML XSL file now
803 look like this:
</p
>
805 <p
><blockquote
><pre
>
806 &lt;?xml version=
'1.0'?
&gt;
807 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'&gt;
808 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
810 &lt;/xsl:template
&gt;
811 &lt;/xsl:stylesheet
&gt;
812 </pre
></blockquote
></p
>
814 <p
>And the FO/PDF XSL file looked like this:
</p
>
816 <p
><blockquote
><pre
>
817 &lt;?xml version=
'1.0'?
&gt;
818 &lt;xsl:stylesheet xmlns:xsl=
"http://www.w3.org/
1999/XSL/Transform
" version=
'1.0'
819 xmlns:fo=
"http://www.w3.org/
1999/XSL/Format
"&gt;
820 &lt;xsl:template match=
"processing-instruction(
'linebreak)
"&gt;
821 &lt;fo:block/
&gt;
822 &lt;/xsl:template
&gt;
823 &lt;/xsl:stylesheet
&gt;
824 </pre
></blockquote
></p
>
826 <p
>One unsolved challenge is our wish to expose different ISBN numbers
827 per publication format, while keeping all of them in some conditional
828 structure in the DocBook source. No idea how to do this, so we ended
829 up listing all the ISBN numbers next to their format in the colophon
832 <p
>If you want to check out the finished result, check out the
833 <a href=
"https://github.com/sickel/kodemus
">source repository at
835 (
<a href=
"https://github.com/EFN/kodemus
">future/new/official
836 repository
</a
>). We expect it to be ready and announced in a few
842 <title>Piratpartiet på opphavs-retrett?
</title>
843 <link>http://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html
</link>
844 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html
</guid>
845 <pubDate>Wed,
19 Dec
2012 13:
10:
00 +
0100</pubDate>
846 <description><p
>Jeg ble overrasket over å se at Piratpartiet i
847 <a href=
"http://www.aftenposten.no/kultur/Piratpartiet-stiller-til-Stortingsvalget-
7073298.html
">Aftenposten
</a
>
848 er referert på følgende:
</p
>
851 Når det gjelder retten til opphavsrett for kulturproduktene, mener
852 Piratpartiet av levetid +
14 år er tilfredsstillende.
855 <p
>Det betyr en vernetid langt ut over det kommersielle livet til de
856 aller fleste opphavsrettsbeskyttede verker, og er i strid med slik i
857 hvert fall jeg har tolket punkt
5 i
858 <a href=
"http://people.opera.com/howcome/
2012/piratpartiet/kjerneprogram.html
">kjerneprogrammet
859 til Piratpartiet
</a
>:
</p
>
862 <p
><strong
>5: Åndsverk og patenter: tilbake til start
</strong
></p
>
864 <table border=
"1">
865 <tr
><th
>forslag:
</th
><td
>14 års opphavsrett og ingen
866 programvarepatenter
</td
></tr
>
868 <tr
><th
>grunn:
</th
><td
>Den første loven om opphavsrett spesifiserte
14
869 års vernetid. Senere har mediabransjens lobbyister stadig presset
870 loven mot lengre vern, nå er det
70 år etter forfatters død. Dette
871 gjør at mange verk glemmes og går tapt, noe som er skadelig for norsk
872 språk og kultur. Vi til tilbake til start:
14 års
873 vernetid. Patentloven sier klart at dataprogrammer ikke kan
874 patenteres. Likevel klarer patentadvokater å lure gjennom
875 programvarepatenter. Slike patenter gjør dingsene våre dyrere og kan i
876 enkelte tilfelle stoppe dem helt.
</th
></tr
>
880 <p
>Den opprinnelige opphavsretten var på
14 år totalt, ikke
14 år
881 etter opphavspersonens død. Jeg tenkte først dette kanskje var
882 feilsitering fra Aftenposten, men jeg finner samme påstand i en
<a
883 href=
"http://piratpartietnorge.org/om-gramo-og-piratpolitikken/
">bloggpost
884 fra Geir Aaslid
</a
> på Piratpartietes offisielle nettsider. Der
885 skriver han følgende:
</p
>
888 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
889 mange bransjer, med ulike behov. Enhver reform er en forbedring men
890 det er nærliggende å anta at en opphavsrett på levetid +
14 år er
891 fullt ut tilfredstillende for musikk, film, litteratur og spill.
894 <p
>Det virker dermed på meg som om Piratpartiet allerede har gjort
895 retrett fra sin beundringsverdige holdning om at det holdt med
14 års
896 total vernetid, til sin nye som tar utgangspunkt i levetiden til
897 opphavspersonen. Jeg håper det baserer seg på en misforståelse hos
898 piratlederen som blir korrigert tilbake til
14 års total vernetid før
899 partiet stiller til valg.
</p
>
901 <p
>Hvis du lurer på hvilke problemer lang vernetid bringer med seg,
902 anbefaler jeg å lese boken
<a href=
"http://free-culture.cc/
">Free
903 Culture
</a
> av Lawrence Lessig. Jeg og en liten gruppe andre er igang
905 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">oversette
906 boken til bokmål
</a
> og tar gjerne imot hjelp med oversettelse og
907 korrekturlesing.
</p
>
909 <p
><strong
>Oppdatering
2012-
12-
20</strong
>: Oppdaget at
910 <a href=
"http://piratpartietnorge.org/om-gramo-og-piratpolitikken/
">bloggposten
911 til Geir Aaslid
</a
> er endret siden i går, og nå inneholder følgende
912 avsnitt i stedet for det jeg siterte over:
</p
>
915 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
916 mange bransjer, med ulike behov. Enhver reform er en forbedring men
917 det er nærliggende å anta at en opphavsrett lik levetiden, evt +
14 år
918 er fullt ut tilfredstillende for mange skapere av musikk, film,
919 litteratur og spill. Det er for det meste de store forlagene som er
923 <p
>I tillegg har det dukket opp en setning nederst
"Dette dokumentet
924 er et utkast til svar på et angrep på Piratpartiet fra Gramo. Det
925 endrer seg derfor over tid og den endelige versjonen er det som blir
926 publisert på Hardware.no
", som tyder på at originalformuleringen ikke
927 var veloverveid og sitatet i Aftenposten kanskje var basert på en
928 misforståelse.
</p
>
933 <title>Why isn
't the value of copyright taxed?
</title>
934 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_the_value_of_copyright_taxed_.html
</link>
935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_the_value_of_copyright_taxed_.html
</guid>
936 <pubDate>Sat,
17 Nov
2012 11:
30:
00 +
0100</pubDate>
937 <description><p
>While working on a
938 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Norwegian
939 translation of the Free Culture by Lawrence Lessig
</a
> (
76% done),
940 which cover the problems with todays copyright law and how it stifles
941 creativity, one idea occurred to me. The idea is to get the tax
942 office to help make more works enter the public domain and also help
943 make it easier to clear rights for using copyrighted works.
</p
>
945 <p
>I mentioned this idea briefly during Yesterdays
946 <a href=
"http://www.farmann.no/
2012/
11/
14/john-perry-barlow-in-oslo-friday-nov-
16
947 -
15-
30-
19-
00/
">presentation
948 by John Perry Barlow
</a
>, and concluded that it was best to put it
949 in writing for a wider audience. The idea is not really based on the
950 argument that copyrighted works are
"intellectual property
", as the
951 core requirement is that copyrighted work have value for the copyright
952 holder and the tax office like to collect their share from any value
953 controlled by the citizens in a country. I
'm sharing the idea here to
954 let others consider it and perhaps shoot it down with a fresh set of
957 <p
>Most valuables are taxed by the government. At least here in
958 Norway, the amount of money you have, the value of our land property,
959 the value of your house, the value of your car, the value of our
960 stocks and other valuables are all added together. If the tax value
961 of these values exceed your debt, you have to pay the tax office some
962 taxes for these values. And copyrighted work have value. It have
963 value for the rights holder, who can earn money selling access to the
964 work. But it is not included in the tax calculations? Why not?
</p
>
966 <p
>If the government want to tax copyrighted works, it would want to
967 maintain a database of all the copyrighted works and who are the
968 rights holders for a given works, to be able to associate the works
969 value to the right citizen or company for tax purposes. If such
970 database exist, it will become a lot easier to find out who to talk to
971 for clearing permissions to use a copyrighted work, which is a very
972 hard operation with todays copyright law. To ensure that copyright
973 holders keep the database up-to-date, it would have to become a
974 requirement to be able to collect money for granting access to
975 copyrighted works that the work is listed in the database with the
976 correct right holder.
</p
>
978 <p
>If copyright causes copyright holders to have to pay more taxes,
979 they will have a small incentive to
"disown
" their copyright, and let
980 the work enter the public domain. For works with several right holders
981 one of the right holders could state (and get it registered in the
982 database) that she do not need to be consulted when clearing rights to
983 use the work in question and thus will not get any income from that
984 work. Stating this would have to be impossible to revert and stop the
985 tax office from adding the value of that work to the given citizens
986 tax calculation. I assume the copyright law would stay the same,
987 allowing creators to pick a license of their choosing, and also
988 allowing them to put their work directly in the public domain. The
989 existence of such database will make it even easier to clear rights,
990 and if the right holders listed in the database is taxed, this system
991 would increase the amount of works that enter the public domain.
</p
>
993 <p
>The effect would be that the tax office help to make it easier to
994 get rights to use the works that have not yet entered the public
995 domain and help to get more work into the public domain and .
</p
>
997 <p
>Why have such taxing not happened yet? I am sure the tax office
998 would like to tax copyrighted work values if they could.
</p
>
1003 <title>Seventy percent done with Norwegian docbook version of Free Culture
</title>
1004 <link>http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</link>
1005 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html
</guid>
1006 <pubDate>Sun,
23 Sep
2012 09:
30:
00 +
0200</pubDate>
1007 <description><p
>Since this summer, I have worked in my spare time on a Norwegian
<a
1008 href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
<a
1009 href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
1010 The reason is that this book is a great primer on what problems exist
1011 in the current copyright laws, and I want it to be available also for
1012 those that are reluctant do read an English book.
1015 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
1016 for volunteers
</a
> to help me, but too few have volunteered so far,
1017 and progress is a bit slow. Anyway, today I broken the
70 percent
1018 mark for the first rough translation. At the moment, less than
700
1019 strings (paragraphs, index terms, titles) are left to translate. With
1020 my current progress of
10-
20 strings per day, it will take a while to
1021 complete the translation. This graph show the updated progress:
</p
>
1023 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
1025 <p
>Progress have slowed down lately due to family and work
1026 commitments. If you want to help, please get in touch, and check out
1027 the project files currently available from
1028 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
1030 <p
>If you are curious what the translated book currently look like,
1032 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
1034 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
1035 are published on github. The HTML version is published as well, but
1036 github hand it out with MIME type text/plain, confusing browsers, so I
1037 saw no point in linking to that version.
</p
>
1042 <title>Half way there with translated docbook version of Free Culture
</title>
1043 <link>http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</link>
1044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</guid>
1045 <pubDate>Fri,
17 Aug
2012 21:
50:
00 +
0200</pubDate>
1046 <description><p
>In my spare time, I currently work on a Norwegian
1047 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
1048 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
1049 to get a Norwegian text explaining the problems with the copyright law
1050 I can give to my parents and others that are reluctant to read an
1051 English book. It is a marvellous set of examples on how the ever
1052 expanding copyright regulations hurt culture and society. When the
1053 translation is done, I hope to find funding to print and ship a copy
1054 to all the members of the Norwegian parliament, before they sit down
1055 to debate the latest revisions to the Norwegian copyright law. This
1057 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
1058 for volunteers
</a
> to help me, and I have been able to secure the
1059 valuable contribution from at least one other Norwegian.
</p
>
1061 <p
>Two days ago, we finally broke the
50% mark. Then more than
50% of
1062 the number of strings to translate (normally paragraphs, but also
1063 titles and index entries are also counted). All parts from the
1064 beginning up to and including chapter four is translated. So is
1065 chapters six, seven and the conclusion. I created a graph to show the
1068 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
1070 <p
>The number of strings to translate increase as I insert the index
1071 entries into the docbook. They were missing with the docbook version
1072 I initially started with. There are still quite a few index entries
1073 missing, but everyone starting with A, B, O, Z and Y are done. I
1074 currently focus on completing the index entries, to get a complete
1075 english version of the docbook source.
</p
>
1077 <p
>There is still need for translators and people with docbook
1078 knowledge, to be able to get a good looking book (I still struggle
1079 with dblatex, xmlto and docbook-xsl) as well as to do the draft
1080 translation and proof reading. And I would like the figures to be
1081 redrawn as SVGs to make it easy to translate them. Any SVG master
1082 around? I am sure there are some legal terms that are unfamiliar to
1083 me. If you want to help, please get in touch, and check out the
1084 project files currently available from
<a
1085 href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
1087 <p
>If you are curious what the translated book currently look like,
1089 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
1091 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
1092 are published on github. The HTML version is published as well, but
1093 github hand it out with MIME type text/plain, confusing browsers, so I
1094 saw no point in linking to that version.
</p
>
1099 <title>Notes on language codes for Norwegian docbook processing...
</title>
1100 <link>http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</link>
1101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</guid>
1102 <pubDate>Fri,
10 Aug
2012 21:
00:
00 +
0200</pubDate>
1103 <description><p
>In
<a href=
"http://www.docbook.org/
">docbook
</a
> one can specify
1104 the language used at the top, and the processing pipeline will use
1105 this information to pick the correct translations for
'chapter
',
'see
1106 also
',
'index
' etc. And for most languages used with docbook, I guess
1107 this work just fine. For example a German user can start the document
1108 with
&lt;book lang=
"de
"&gt;, and the document will show up with the
1109 correct content with any of the docbook processors. This is not the
1110 case for the language
1111 <a href=
"http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
">I
1112 am working with at the moment
</a
>, Norwegian Bokmål.
</p
>
1114 <p
>For a while, I was confused about which language code to use,
1115 because I was unable to find any language code that would work across
1116 all tools. I am currently testing dblatex, xmlto, docbook-xsl, and
1117 dbtoepub, and they do not handle Norwegian Bokmål the same way. Some
1118 of them do not handle it at all.
</p
>
1120 <p
>A bit of background information is probably needed to understand
1121 this mess. Norwegian is not one, but two written variants. The
1122 variants are Norwegian Nynorsk and Norwegian Bokmål. There are three
1123 two letter language codes associated with these languages, Norwegian
1124 is
'no
', Norwegian Nynorsk is
'nn
' and Norwegian Bokmål is
'nb
'.
1125 Historically the
'no
' language code was used for Norwegian Bokmål, but
1126 many years ago this was found to be å bad idea, and the recommendation
1127 is to use the most specific language code instead, to avoid confusion.
1128 In the transition period it is a good idea to make sure
'no
' was an
1129 alias for
'nb
'.
</p
>
1131 <p
>Back to docbook processing tools in Debian. The dblatex tool only
1132 understand
'nn
'. There are translations for
'no
', but not
'nb
' (BTS
1133 <a href=
"http://bugs.debian.org/
684391">#
684391</a
>), but due to a bug
1134 (BTS
<a href=
"http://bugs.debian.org/
682936">#
682936</a
>) the
'no
'
1135 language code is not recognised. The docbook-xsl tool chain only
1136 recognise
'nn
' and
'nb
', but not
'no
'. The xmlto tool only recognise
1137 'nn
' and
'nb
', but not
'no
'. The end result that there is no language
1138 code I can use to get the docbook file working with all of these tools
1139 at the same time. :(
</p
>
1141 <p
>The correct solution is to use
&lt;book lang=
"nb
"&gt;, but it will
1142 take time before that will work with all the free software docbook
1143 processors. :(
</p
>
1145 <p
>Oh, the joy of well integrated tools. :/
</p
>
1150 <title>Best way to create a docbook book?
</title>
1151 <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</link>
1152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</guid>
1153 <pubDate>Tue,
31 Jul
2012 22:
00:
00 +
0200</pubDate>
1154 <description><p
>I tried to send this text to the
1155 <a href=
"https://lists.oasis-open.org/archives/docbook-apps/
">docbook-apps
1156 mailing list at lists.oasis-open.org
</a
>, but it only accept messages
1157 from subscribers and rejected my post, and I completely lack the
1158 bandwidth required to subscribe to another mailing list, so instead I
1159 try to post my message here and hope my blog readers can help me
1162 <p
>I am quite new to docbook processing, and am climbing a steep
1163 learning curve at the moment.
</p
>
1165 <p
>To give you some background, I am working on a Norwegian
1166 translation of the book Free Culture by Lawrence Lessig, and I use
1167 docbook to handle the process. The files to build the book are
1169 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
1170 The book got around
400 pages with parts, images, footnotes, tables,
1171 index entries etc, which has proven to be a challenge for the free
1172 software docbook processors. My build platform is Debian GNU/Linux
1175 <p
>I want to build PDF, EPUB and HTML version of the book, and have
1176 tried different tool chains to do the conversion from docbook to these
1177 formats. I am currently focusing on the PDF version, and have a few
1182 <li
>Using dblatex, the
&lt;part
&gt; handling is not the way I want to,
1183 as
&lt;/part
&gt; do not really end the
&lt;part
&gt;. (See
1184 <a href=
"http://bugs.debian.org/
683166">BTS report #
683166</a
>), the
1185 xetex backend (needed to process UTF-
8) give incorrect hyphens in
1186 index references spanning several pages (See
1187 <a href=
"http://bugs.debian.org/
682901">BTS report #
682901</a
>), and
1188 I am unable to get the norwegian template texts (See
1189 <a href=
"http://bugs.debian.org/
682936">BTS report #
682936</a
>).
</li
>
1191 <li
>Using straight xmlto fail with some latex error (See
1192 <a href=
"http://bugs.debian.org/
683163">BTS report
1193 #
683163</a
>).
</li
>
1195 <li
>Using xmlto with the fop backend fail to handle images (do not
1196 show up in the PDF), fail to handle a long footnote (overlap
1197 footnote and text body, see
1198 <a href=
"http://bugs.debian.org/
683197">BTS report #
683197</a
>), and
1199 fail to create a correct index (some lack page ref, and the page
1200 refs listed are not right).
</li
>
1202 <li
>Using xmlto with the dblatex backend behave like dblatex.
</li
>
1204 <li
>Using docbook-xls with xsltproc + fop have the same footnote and
1205 index problems the xmlto + fop processing.
</li
>
1209 <p
>So I wonder, what would be the best way to create the PDF version
1210 of this book? Are some of the bugs found above solved in new or
1211 experimental versions of some docbook tool chain?
</p
>
1213 <p
>What about HTML and EPUB versions?
</p
>
1218 <title>Free Culture in Norwegian -
5 chapters done,
74 percent left to do
</title>
1219 <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</link>
1220 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</guid>
1221 <pubDate>Sat,
21 Jul
2012 20:
00:
00 +
0200</pubDate>
1222 <description><p
>I reported earlier that I am working on
1223 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">a
1224 norwegian version
</a
> of the book
1225 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
1226 Progress is good, and yesterday I got a major contribution from Anders
1227 Hagen Jarmund completing chapter six. The source files as well as a
1228 PDF and EPUB version of this book are available from
1229 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
1231 <p
>I am happy to report that the draft for the first two chapters
1232 (preface, introduction) is complete, and three other chapters are also
1233 completely translated. This completes
26 percent of the number of
1234 strings (equivalent to paragraphs) in the book, and there is thus
74
1235 percent left to translate. A graph of the progress is present at the
1236 bottom of the github project page. There is still room for more
1237 contributors. Get in touch or send github pull requests with fixes if
1238 you got time and are willing to help make this book make it to
1241 <p
>The book translation framework could also be a good basis for other
1242 translations, if you want the book to be available in your
1248 <title>Call for help from docbook expert to tag Free Culture by Lawrence Lessig
</title>
1249 <link>http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</link>
1250 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</guid>
1251 <pubDate>Mon,
16 Jul
2012 22:
50:
00 +
0200</pubDate>
1252 <description><p
>I am currently working on a
1253 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">project
1254 to translate
</a
> the book
1255 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig
1256 to Norwegian. And the source we base our translation on is the
1257 <a href=
"http://en.wikipedia.org/wiki/DocBook
">docbook
</a
> version, to
1258 allow us to use po4a and .po files to handle the translation, and for
1259 this to work well the docbook source document need to be properly
1260 tagged. The source files of this project is available from
1261 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
1263 <p
>The problem is that the docbook source have flaws, and we have
1264 no-one involved in the project that is a docbook expert. Is there a
1265 docbook expert somewhere that is interested in helping us create a
1266 well tagged docbook version of the book, and adjust our build process
1267 for the PDF, EPUB and HTML version of the book? This will provide a
1268 well tagged English version (our source document), and make it a lot
1269 easier for us to create a good Norwegian version. If you can and want
1270 to help, please get in touch with me or fork the github project and
1271 send pull requests with fixes. :)
</p
>
1276 <title>Fri programvare -
"fri
" som i
"talefrihet
", ikke som i
"fri bar
"</title>
1277 <link>http://people.skolelinux.org/pere/blog/Fri_programvare____fri__som_i__talefrihet___ikke_som_i__fri_bar_.html
</link>
1278 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fri_programvare____fri__som_i__talefrihet___ikke_som_i__fri_bar_.html
</guid>
1279 <pubDate>Sun,
15 Jul
2012 21:
20:
00 +
0200</pubDate>
1280 <description><p
>Et ofte brukt sitat i fri programvareverden er Stallman-sitatet
1281 «
<a href=
"http://www.gnu.org/philosophy/free-sw.html.en
">Free Software,
1282 "free
" as in
"free speech
", not as in
"free beer
"</a
>». Men det er
1283 ikke direkte overførbart til norsk, da det baserer seg på koblingen
1284 gratis/fri på engelsk. En direkte oversettelse ville være «Fri
1285 programvare,
"fri
" som i
"talefrihet
", ikke som
"gratis øl
"», og det
1286 går jo glipp av poenget. I forbindelse med at vi er
1287 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">igang
1288 med å oversette
</a
> <a href=
"http://free-culture.cc/
">Free Culture
</a
>
1289 av Lawrence Lessig, måtte jeg forsøke a finne en bedre
1290 oversettelse.
</p
>
1292 <p
>Mitt forslag til oversettelse blir dermed å droppe ølet, og heller
1293 fokusere på det kjente norske uttrykket
"fri bar
". Dermed blir
1294 oversettelsen «Fri programvare -
"fri
" som i
"talefrihet
", ikke som i
1295 "fri bar
"».
</p
>
1297 <p
>Noen som har bedre forslag?
</p
>
1299 <p
>Forøvrig bruker jeg fri programvare som et samlebegrep på norsk for
1300 begge de engelske uttrykkene Free Software og Open Source, jamfør
1301 <a href=
"http://www.nuug.no/dokumenter/folder-friprogramvare.pdf
">NUUGs
1302 lille folder om temaet
</a
>.
</p
>
1307 <title>Dugnad for å sende norsk versjon av Free Culture til stortingets representanter!
</title>
1308 <link>http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</link>
1309 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
</guid>
1310 <pubDate>Wed,
11 Jul
2012 09:
00:
00 +
0200</pubDate>
1311 <description><p
>Da opphavsrettsloven ble revidert i forrige runde rundt
2005, var
1312 det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
1313 Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
1314 og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
1315 representanter fikk en norsk utgave av boken
1316 <a href=
"http://free-culture.cc/
">Free Culture
</a
> av Lawrence Lessig
1317 som forklarte litt om problemstillingene. Vi endte opp med å
1318 prioritere utvikling i
1319 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>-prosjektet i
1320 stedet, så den oversatte boken så aldri dagens lys. Men i forrige uke
1321 ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
1322 bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
1323 sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
1324 fordel for forlag og store mediehus fortsatt trenger en annen vinkling
1325 i debatten.
</p
>
1327 <p
>Planen min er å oversette boka på dugnad, sette den opp for
1328 trykking med en av de mange
1329 <a href=
"http://no.wikipedia.org/wiki/Trykk_på_forespørsel
">trykk på
1330 forespørsel
</a
>-tjenestene, skaffe sponsor til å finansiere trykking
1331 til stortingsrepresentantene og alle som har bidratt med
1332 oversettelser. Kanskje vi også kan få en avtale med et forlag om
1333 publisering når boka er ferdig? Kommentarene til
1334 <a href=
"http://newth.net/eirik/
2011/
04/
01/e-selvpublisering/
">Eirik
1336 <a href=
"http://www.espen.com/norskblogg/archives/
2008/
09/erfaringer_med_publishing_on_demand.html
">Espen
1337 Andersen
</a
> om erfaringene med selvpublisering og trykk på
1338 forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
1339 <a href=
"http://www.lulu.com/
">Lulu
</a
> er en grei leverandør av
1340 trykketjenester til prosjektet.
</p
>
1342 <p
>Jeg har satt opp
1343 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">et
1344 Github-prosjekt
</a
> for a lage boken, basert på Docbook-utgaven jeg
1345 fant fra Hans Schou. Skolelinux har hatt byggesystem for å lage
1346 oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
1347 kopiert og utvidet dette oppsettet. Originalteksten er i Docbook, og
1348 oversettelsen gjøres i .po-filer med hjelp av vanlige
1349 oversetterverktøy brukt i fri programvareverden. Dernest tar
1350 byggesystemet over og lager PDF og EPUB-utgave av den oversatte
1351 teksten. Resultatet kan ses i Github-prosjektet. For å komme raskt
1352 igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
1353 til norsk, noe som grovoversatte ca.
1300 av de ca.
1700 tekstbitene
1354 boken består av. Jeg håper nå at flere kan bidra med å få
1355 oversettelsen på plass, slik at teksten kan være klar i løpet av
1356 høsten. Når alt er oversatt må teksten gjennomgås for feil og
1357 konsistent språk. Totalt er det nok mange timer som trengs for å
1358 gjennomføre oversettelsen.
</p
>
1360 <p
>Økonomien i dette er ikke avskrekkende.
169
1361 stortingsrepresentanter og nesten like mange varamedlemmer bør få
1362 bøker, og estimert produduksjonskostnad for hver bok er rundt
6 EURO i
1363 følge et raskt estimat fra Lulu. Jeg vet ennå ikke hvor mange sider
1364 det blir i størrelsen
5,
5" x
8.5" (det er ca.
140 sider i A4-format),
1365 så jeg gjettet på
400 sider. Jeg tror originalutgaven har nesten
400
1366 sider. For
169*
2 eksemplarer snakker vi om en trykkekostnad på
1367 ca.
2000 EURO, dvs. ca
15 000 NOK. Det burde være mulig å finne en
1368 sponsor for å dekke en slik sum. I tillegg kommer distribusjon og
1369 porto, som antagelig kommer på like mye.
</p
>
1371 <p
>Kan du bidra med oversettelse og docbook-typesetting? Ta kontakt
1372 og send patcher i github. Jeg legger gjerne inn folk i prosjektet
1373 slik at du kan oppdatere direkte.
</p
>