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