blog/tags/freeculture/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: Entries Tagged freeculture</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="freeculture.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21     <h3>Entries tagged "freeculture".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html">90 percent done with the Norwegian draft translation of Free Culture</a>
  26       </div>
  27       <div class="date">
  28          2nd August 2013
  29       </div>
  30       <div class="body">
  31         <p>It has been a while since my last update.  Since last summer, I
  32 have worked on a Norwegian
  33 <a href="http://www.docbook.org/">docbook</a> version of the 2004 book
  34 <a href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig,
  35 to get a Norwegian text explaining the problems with the copyright
  36 law.  Yesterday, I finally broken the 90% mark, when counting the
  37 number of strings to translate.  Due to real life constraints, I have
  38 not had time to work on it since March, but when the summer broke out,
  39 I found time to work on it again.  Still lots of work left, but the
  40 first draft is nearing completion.  I created a graph to show the
  41 progress of the translation:</p>
  42
  43 <p><img width="80%" align="center" src="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png"></p>
  44
  45 <p>When the first draft is done, the translated text need to be
  46 proof read, and the remaining formatting problems with images and SVG
  47 drawings need to be fixed.  There are probably also some index entries
  48 missing that need to be added.  This can be done by comparing the
  49 index entries listed in the SiSU version of the book, or comparing the
  50 English docbook version with the paper version.  Last, the colophon
  51 page with ISBN numbers etc need to be wrapped up before the release is
  52 done.  I should also figure out how to get correct Norwegian sorting
  53 of the index pages.  All docbook tools I have tried so far (xmlto,
  54 docbook-xsl, dblatex) get the order of symbols and the special
  55 Norwegian letters ÆØÅ wrong.</p>
  56
  57 <p>There is still need for translators and people with docbook
  58 knowledge, to be able to get a good looking book (I still struggle
  59 with dblatex, xmlto and docbook-xsl) as well as to do the draft
  60 translation and proof reading.  And I would like the figures to be
  61 redrawn as SVGs to make it easy to translate them.  Any SVG master
  62 around?  There are also some legal terms that are unfamiliar to me.
  63 If you want to help, please get in touch with me, and check out the
  64 project files currently available from
  65 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.</p>
  66
  67 <p>If you are curious what the translated book currently look like,
  68 the updated
  69 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true">PDF</a>
  70 and
  71 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true">EPUB</a>
  72 are published on github.  The HTML version is published as well, but
  73 github hand it out with MIME type text/plain, confusing browsers, so I
  74 saw no point in linking to that version.</p>
  75
  76       </div>
  77       <div class="tags">
  78
  79
  80         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
  81
  82
  83       </div>
  84     </div>
  85     <div class="padding"></div>
  86
  87     <div class="entry">
  88       <div class="title">
  89         <a href="http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html">Typesetting a short story using docbook for PDF, HTML and EPUB</a>
  90       </div>
  91       <div class="date">
  92         24th March 2013
  93       </div>
  94       <div class="body">
  95         <p>A few days ago, during a discussion in
  96 <a href="http://www.efn.no/">EFN</a> about interesting books to read
  97 about copyright and the data retention directive, a suggestion to read
  98 the 1968 short story Kodémus by
  99 <a href="http://web2.gyldendal.no/toraage/">Tore Åge Bringsværd</a>
 100 came up.  The text was only available in old paper books, and thus not
 101 easily available for current and future generations.  Some of the
 102 people participating in the discussion contacted the author, and
 103 reported back 2013-03-19 that the author was OK with releasing the
 104 short story using a <a href="http://www.creativecommons.org/">Creative
 105 Commons</a> license.  The text was quickly scanned and OCR-ed, and we
 106 were ready to start on the editing and typesetting.</p>
 107
 108 <p>As I already had some experience formatting text in my project to
 109 provide a Norwegian version of the Free Culture book by Lawrence
 110 Lessig, I chipped in and set up a
 111 <a href="http://www.docbook.org/">DocBook</a> processing framework to
 112 generate PDF, HTML and EPUB version of the short story.  The tools to
 113 transform DocBook to different formats are already in my Linux
 114 distribution of choice, <a href="http://www.debian.org/">Debian</a>, so
 115 all I had to do was to use the
 116 <a href="http://dblatex.sourceforge.net/">dblatex</a>,
 117 <a href="http://docbook.sourceforge.net/release/xsl/current/epub/README">dbtoepub</a>
 118 and <a href="https://fedorahosted.org/xmlto/">xmlto</a> tools to do the
 119 conversion.  After a few days, we decided to replace dblatex with
 120 xsltproc/fop (aka
 121 <a href="http://wiki.docbook.org/DocBookXslStylesheets">docbook-xsl</a>),
 122 to get the copyright information to show up in the PDF and to get a
 123 nicer &lt;variablelist&gt; typesetting, but that is just a minor
 124 technical detail.</p>
 125
 126 <p>There were a few challenges, of course.  We want to typeset the
 127 short story to look like the original, and that require fairly good
 128 control over the layout.  The original short story have three
 129 parts/scenes separated by a single horizontally centred star (*), and
 130 the paragraphs do not contain only flowing text, but dialogs and text
 131 that started on a new line in the middle of the paragraph.</p>
 132
 133 <p>I initially solved the first challenge by using a paragraph with a
 134 single star in it, ie &lt;para&gt;*&lt;/para&gt;, but it made sure a
 135 placeholder indicated where the scene shifted.  This did not look too
 136 good without the centring.  The next approach was to create a new
 137 preprocessor directive &lt;?newscene?&gt;, mapping to "&lt;hr/&gt;"
 138 for HTML and "&lt;fo:block text-align="center"&gt;&lt;fo:leader
 139 leader-pattern="rule" rule-thickness="0.5pt"/&gt;&lt;/fo:block&gt;"
 140 for FO/PDF output (did not try to implement this in dblatex, as we had
 141 switched at this time).  The HTML XSL file looked like this:</p>
 142
 143 <p><blockquote><pre>
 144 &lt;?xml version='1.0'?&gt;
 145 &lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'&gt;
 146   &lt;xsl:template match="processing-instruction('newscene')"&gt;
 147     &lt;hr/&gt;
 148   &lt;/xsl:template&gt;
 149 &lt;/xsl:stylesheet&gt;
 150 </pre></blockquote></p>
 151
 152 <p>And the FO/PDF XSL file looked like this:</p>
 153
 154 <p><blockquote><pre>
 155 &lt;?xml version='1.0'?&gt;
 156 &lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'&gt;
 157   &lt;xsl:template match="processing-instruction('newscene')"&gt;
 158     &lt;fo:block text-align="center"&gt;
 159       &lt;fo:leader leader-pattern="rule" rule-thickness="0.5pt"/&gt;
 160     &lt;/fo:block&gt;
 161   &lt;/xsl:template&gt;
 162 &lt;/xsl:stylesheet&gt;
 163 </pre></blockquote></p>
 164
 165 <p>Finally, I came across the &lt;bridgehead&gt; tag, which seem to be
 166 a good fit for the task at hand, and I replaced &lt;?newscene?&gt;
 167 with &lt;bridgehead&gt;*&lt;/bridgehead&gt;.  It isn't centred, but we
 168 can fix it with some XSL rule if the current visual layout isn't
 169 enough.</p>
 170
 171 <p>I did not find a good DocBook compliant way to solve the
 172 linebreak/paragraph challenge, so I ended up creating a new processor
 173 directive &lt;?linebreak?&gt;, mapping to &lt;br/&gt; in HTML, and
 174 &lt;fo:block/&gt; in FO/PDF.  I suspect there are better ways to do
 175 this, and welcome ideas and patches on github.  The HTML XSL file now
 176 look like this:</p>
 177
 178 <p><blockquote><pre>
 179 &lt;?xml version='1.0'?&gt;
 180 &lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'&gt;
 181   &lt;xsl:template match="processing-instruction('linebreak)"&gt;
 182     &lt;br/&gt;
 183   &lt;/xsl:template&gt;
 184 &lt;/xsl:stylesheet&gt;
 185 </pre></blockquote></p>
 186
 187 <p>And the FO/PDF XSL file looked like this:</p>
 188
 189 <p><blockquote><pre>
 190 &lt;?xml version='1.0'?&gt;
 191 &lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'
 192   xmlns:fo="http://www.w3.org/1999/XSL/Format"&gt;
 193   &lt;xsl:template match="processing-instruction('linebreak)"&gt;
 194     &lt;fo:block/&gt;
 195   &lt;/xsl:template&gt;
 196 &lt;/xsl:stylesheet&gt;
 197 </pre></blockquote></p>
 198
 199 <p>One unsolved challenge is our wish to expose different ISBN numbers
 200 per publication format, while keeping all of them in some conditional
 201 structure in the DocBook source.  No idea how to do this, so we ended
 202 up listing all the ISBN numbers next to their format in the colophon
 203 page.</p>
 204
 205 <p>If you want to check out the finished result, check out the
 206 <a href="https://github.com/sickel/kodemus">source repository at
 207 github</a>
 208 (<a href="https://github.com/EFN/kodemus">future/new/official
 209 repository</a>).  We expect it to be ready and announced in a few
 210 days.</p>
 211
 212       </div>
 213       <div class="tags">
 214
 215
 216         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 217
 218
 219       </div>
 220     </div>
 221     <div class="padding"></div>
 222
 223     <div class="entry">
 224       <div class="title">
 225         <a href="http://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html">Piratpartiet på opphavs-retrett?</a>
 226       </div>
 227       <div class="date">
 228         19th December 2012
 229       </div>
 230       <div class="body">
 231         <p>Jeg ble overrasket over å se at Piratpartiet i
 232 <a href="http://www.aftenposten.no/kultur/Piratpartiet-stiller-til-Stortingsvalget-7073298.html">Aftenposten</a>
 233 er referert på følgende:</p>
 234
 235 <blockquote>
 236 Når det gjelder retten til opphavsrett for kulturproduktene, mener
 237 Piratpartiet av levetid + 14 år er tilfredsstillende.
 238 </blockquote>
 239
 240 <p>Det betyr en vernetid langt ut over det kommersielle livet til de
 241 aller fleste opphavsrettsbeskyttede verker, og er i strid med slik i
 242 hvert fall jeg har tolket punkt 5 i
 243 <a href="http://people.opera.com/howcome/2012/piratpartiet/kjerneprogram.html">kjerneprogrammet
 244 til Piratpartiet</a>:</p>
 245
 246 <blockquote>
 247 <p><strong>5: Åndsverk og patenter: tilbake til start</strong></p>
 248
 249 <table border="1">
 250 <tr><th>forslag:</th><td>14 års opphavsrett og ingen
 251 programvarepatenter</td></tr>
 252
 253 <tr><th>grunn:</th><td>Den første loven om opphavsrett spesifiserte 14
 254 års vernetid. Senere har mediabransjens lobbyister stadig presset
 255 loven mot lengre vern, nå er det 70 år etter forfatters død. Dette
 256 gjør at mange verk glemmes og går tapt, noe som er skadelig for norsk
 257 språk og kultur. Vi til tilbake til start: 14 års
 258 vernetid. Patentloven sier klart at dataprogrammer ikke kan
 259 patenteres. Likevel klarer patentadvokater å lure gjennom
 260 programvarepatenter. Slike patenter gjør dingsene våre dyrere og kan i
 261 enkelte tilfelle stoppe dem helt.</th></tr>
 262 </table>
 263 </blockquote>
 264
 265 <p>Den opprinnelige opphavsretten var på 14 år totalt, ikke 14 år
 266 etter opphavspersonens død.  Jeg tenkte først dette kanskje var
 267 feilsitering fra Aftenposten, men jeg finner samme påstand i en <a
 268 href="http://piratpartietnorge.org/om-gramo-og-piratpolitikken/">bloggpost
 269 fra Geir Aaslid</a> på Piratpartietes offisielle nettsider.  Der
 270 skriver han følgende:</p>
 271
 272 <blockquote>
 273 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
 274 mange bransjer, med ulike behov. Enhver reform er en forbedring men
 275 det er nærliggende å anta at en opphavsrett på levetid + 14 år er
 276 fullt ut tilfredstillende for musikk, film, litteratur og spill.
 277 </blockquote>
 278
 279 <p>Det virker dermed på meg som om Piratpartiet allerede har gjort
 280 retrett fra sin beundringsverdige holdning om at det holdt med 14 års
 281 total vernetid, til sin nye som tar utgangspunkt i levetiden til
 282 opphavspersonen.  Jeg håper det baserer seg på en misforståelse hos
 283 piratlederen som blir korrigert tilbake til 14 års total vernetid før
 284 partiet stiller til valg.</p>
 285
 286 <p>Hvis du lurer på hvilke problemer lang vernetid bringer med seg,
 287 anbefaler jeg å lese boken <a href="http://free-culture.cc/">Free
 288 Culture</a> av Lawrence Lessig.  Jeg og en liten gruppe andre er igang
 289 med å
 290 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">oversette
 291 boken til bokmål</a> og tar gjerne imot hjelp med oversettelse og
 292 korrekturlesing.</p>
 293
 294 <p><strong>Oppdatering 2012-12-20</strong>: Oppdaget at
 295 <a href="http://piratpartietnorge.org/om-gramo-og-piratpolitikken/">bloggposten
 296 til Geir Aaslid</a> er endret siden i går, og nå inneholder følgende
 297 avsnitt i stedet for det jeg siterte over:</p>
 298
 299 <blockquote>
 300 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
 301 mange bransjer, med ulike behov. Enhver reform er en forbedring men
 302 det er nærliggende å anta at en opphavsrett lik levetiden, evt + 14 år
 303 er fullt ut tilfredstillende for mange skapere av musikk, film,
 304 litteratur og spill. Det er for det meste de store forlagene som er
 305 imot enhver reform.
 306 </blockquote>
 307
 308 <p>I tillegg har det dukket opp en setning nederst "Dette dokumentet
 309 er et utkast til svar på et angrep på Piratpartiet fra Gramo. Det
 310 endrer seg derfor over tid og den endelige versjonen er det som blir
 311 publisert på Hardware.no", som tyder på at originalformuleringen ikke
 312 var veloverveid og sitatet i Aftenposten kanskje var basert på en
 313 misforståelse.</p>
 314
 315       </div>
 316       <div class="tags">
 317
 318
 319         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 320
 321
 322       </div>
 323     </div>
 324     <div class="padding"></div>
 325
 326     <div class="entry">
 327       <div class="title">
 328         <a href="http://people.skolelinux.org/pere/blog/Why_isn_t_the_value_of_copyright_taxed_.html">Why isn't the value of copyright taxed?</a>
 329       </div>
 330       <div class="date">
 331         17th November 2012
 332       </div>
 333       <div class="body">
 334         <p>While working on a
 335 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">Norwegian
 336 translation of the Free Culture by Lawrence Lessig</a> (76% done),
 337 which cover the problems with todays copyright law and how it stifles
 338 creativity, one idea occurred to me.  The idea is to get the tax
 339 office to help make more works enter the public domain and also help
 340 make it easier to clear rights for using copyrighted works.</p>
 341
 342 <p>I mentioned this idea briefly during Yesterdays
 343 <a href="http://www.farmann.no/2012/11/14/john-perry-barlow-in-oslo-friday-nov-16
 344 -15-30-19-00/">presentation
 345 by John Perry Barlow</a>, and concluded that it was best to put it
 346 in writing for a wider audience.  The idea is not really based on the
 347 argument that copyrighted works are "intellectual property", as the
 348 core requirement is that copyrighted work have value for the copyright
 349 holder and the tax office like to collect their share from any value
 350 controlled by the citizens in a country.  I'm sharing the idea here to
 351 let others consider it and perhaps shoot it down with a fresh set of
 352 arguments.</p>
 353
 354 <p>Most valuables are taxed by the government.  At least here in
 355 Norway, the amount of money you have, the value of our land property,
 356 the value of your house, the value of your car, the value of our
 357 stocks and other valuables are all added together.  If the tax value
 358 of these values exceed your debt, you have to pay the tax office some
 359 taxes for these values.  And copyrighted work have value.  It have
 360 value for the rights holder, who can earn money selling access to the
 361 work.  But it is not included in the tax calculations?  Why not?</p>
 362
 363 <p>If the government want to tax copyrighted works, it would want to
 364 maintain a database of all the copyrighted works and who are the
 365 rights holders for a given works, to be able to associate the works
 366 value to the right citizen or company for tax purposes.  If such
 367 database exist, it will become a lot easier to find out who to talk to
 368 for clearing permissions to use a copyrighted work, which is a very
 369 hard operation with todays copyright law.  To ensure that copyright
 370 holders keep the database up-to-date, it would have to become a
 371 requirement to be able to collect money for granting access to
 372 copyrighted works that the work is listed in the database with the
 373 correct right holder.</p>
 374
 375 <p>If copyright causes copyright holders to have to pay more taxes,
 376 they will have a small incentive to "disown" their copyright, and let
 377 the work enter the public domain. For works with several right holders
 378 one of the right holders could state (and get it registered in the
 379 database) that she do not need to be consulted when clearing rights to
 380 use the work in question and thus will not get any income from that
 381 work.  Stating this would have to be impossible to revert and stop the
 382 tax office from adding the value of that work to the given citizens
 383 tax calculation.  I assume the copyright law would stay the same,
 384 allowing creators to pick a license of their choosing, and also
 385 allowing them to put their work directly in the public domain.  The
 386 existence of such database will make it even easier to clear rights,
 387 and if the right holders listed in the database is taxed, this system
 388 would increase the amount of works that enter the public domain.</p>
 389
 390 <p>The effect would be that the tax office help to make it easier to
 391 get rights to use the works that have not yet entered the public
 392 domain and help to get more work into the public domain and .</p>
 393
 394 <p>Why have such taxing not happened yet?  I am sure the tax office
 395 would like to tax copyrighted work values if they could.</p>
 396
 397       </div>
 398       <div class="tags">
 399
 400
 401         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 402
 403
 404       </div>
 405     </div>
 406     <div class="padding"></div>
 407
 408     <div class="entry">
 409       <div class="title">
 410         <a href="http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html">Seventy percent done with Norwegian docbook version of Free Culture</a>
 411       </div>
 412       <div class="date">
 413         23rd September 2012
 414       </div>
 415       <div class="body">
 416         <p>Since this summer, I have worked in my spare time on a Norwegian <a
 417 href="http://www.docbook.org/">docbook</a> version of the 2004 book <a
 418 href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig.
 419 The reason is that this book is a great primer on what problems exist
 420 in the current copyright laws, and I want it to be available also for
 421 those that are reluctant do read an English book.
 422
 423 When I started, I
 424 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">called
 425 for volunteers</a> to help me, but too few have volunteered so far,
 426 and progress is a bit slow.  Anyway, today I broken the 70 percent
 427 mark for the first rough translation.  At the moment, less than 700
 428 strings (paragraphs, index terms, titles) are left to translate.  With
 429 my current progress of 10-20 strings per day, it will take a while to
 430 complete the translation.  This graph show the updated progress:</p>
 431
 432 <img width="80%" align="center" src="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png">
 433
 434 <p>Progress have slowed down lately due to family and work
 435 commitments.  If you want to help, please get in touch, and check out
 436 the project files currently available from
 437 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.</p>
 438
 439 <p>If you are curious what the translated book currently look like,
 440 the updated
 441 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true">PDF</a>
 442 and
 443 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true">EPUB</a>
 444 are published on github.  The HTML version is published as well, but
 445 github hand it out with MIME type text/plain, confusing browsers, so I
 446 saw no point in linking to that version.</p>
 447
 448       </div>
 449       <div class="tags">
 450
 451
 452         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
 453
 454
 455       </div>
 456     </div>
 457     <div class="padding"></div>
 458
 459     <div class="entry">
 460       <div class="title">
 461         <a href="http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html">Half way there with translated docbook version of Free Culture</a>
 462       </div>
 463       <div class="date">
 464         17th August 2012
 465       </div>
 466       <div class="body">
 467         <p>In my spare time, I currently work on a Norwegian
 468 <a href="http://www.docbook.org/">docbook</a> version of the 2004 book
 469 <a href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig,
 470 to get a Norwegian text explaining the problems with the copyright law
 471 I can give to my parents and others that are reluctant to read an
 472 English book.  It is a marvellous set of examples on how the ever
 473 expanding copyright regulations hurt culture and society.  When the
 474 translation is done, I hope to find funding to print and ship a copy
 475 to all the members of the Norwegian parliament, before they sit down
 476 to debate the latest revisions to the Norwegian copyright law.  This
 477 summer I
 478 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">called
 479 for volunteers</a> to help me, and I have been able to secure the
 480 valuable contribution from at least one other Norwegian.</p>
 481
 482 <p>Two days ago, we finally broke the 50% mark.  Then more than 50% of
 483 the number of strings to translate (normally paragraphs, but also
 484 titles and index entries are also counted).  All parts from the
 485 beginning up to and including chapter four is translated.  So is
 486 chapters six, seven and the conclusion.  I created a graph to show the
 487 progress:</p>
 488
 489 <img width="80%" align="center" src="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png">
 490
 491 <p>The number of strings to translate increase as I insert the index
 492 entries into the docbook.  They were missing with the docbook version
 493 I initially started with.  There are still quite a few index entries
 494 missing, but everyone starting with A, B, O, Z and Y are done.  I
 495 currently focus on completing the index entries, to get a complete
 496 english version of the docbook source.</p>
 497
 498 <p>There is still need for translators and people with docbook
 499 knowledge, to be able to get a good looking book (I still struggle
 500 with dblatex, xmlto and docbook-xsl) as well as to do the draft
 501 translation and proof reading.  And I would like the figures to be
 502 redrawn as SVGs to make it easy to translate them.  Any SVG master
 503 around?  I am sure there are some legal terms that are unfamiliar to
 504 me.  If you want to help, please get in touch, and check out the
 505 project files currently available from <a
 506 href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.</p>
 507
 508 <p>If you are curious what the translated book currently look like,
 509 the updated
 510 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true">PDF</a>
 511 and
 512 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true">EPUB</a>
 513 are published on github.  The HTML version is published as well, but
 514 github hand it out with MIME type text/plain, confusing browsers, so I
 515 saw no point in linking to that version.</p>
 516
 517       </div>
 518       <div class="tags">
 519
 520
 521         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
 522
 523
 524       </div>
 525     </div>
 526     <div class="padding"></div>
 527
 528     <div class="entry">
 529       <div class="title">
 530         <a href="http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html">Notes on language codes for Norwegian docbook processing...</a>
 531       </div>
 532       <div class="date">
 533         10th August 2012
 534       </div>
 535       <div class="body">
 536         <p>In <a href="http://www.docbook.org/">docbook</a> one can specify
 537 the language used at the top, and the processing pipeline will use
 538 this information to pick the correct translations for 'chapter', 'see
 539 also', 'index' etc.  And for most languages used with docbook, I guess
 540 this work just fine.  For example a German user can start the document
 541 with &lt;book lang="de"&gt;, and the document will show up with the
 542 correct content with any of the docbook processors.  This is not the
 543 case for the language
 544 <a href="http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html">I
 545 am working with at the moment</a>, Norwegian Bokmål.</p>
 546
 547 <p>For a while, I was confused about which language code to use,
 548 because I was unable to find any language code that would work across
 549 all tools.  I am currently testing dblatex, xmlto, docbook-xsl, and
 550 dbtoepub, and they do not handle Norwegian Bokmål the same way.  Some
 551 of them do not handle it at all.</p>
 552
 553 <p>A bit of background information is probably needed to understand
 554 this mess.  Norwegian is not one, but two written variants.  The
 555 variants are Norwegian Nynorsk and Norwegian Bokmål.  There are three
 556 two letter language codes associated with these languages, Norwegian
 557 is 'no', Norwegian Nynorsk is 'nn' and Norwegian Bokmål is 'nb'.
 558 Historically the 'no' language code was used for Norwegian Bokmål, but
 559 many years ago this was found to be å bad idea, and the recommendation
 560 is to use the most specific language code instead, to avoid confusion.
 561 In the transition period it is a good idea to make sure 'no' was an
 562 alias for 'nb'.</p>
 563
 564 <p>Back to docbook processing tools in Debian.  The dblatex tool only
 565 understand 'nn'.  There are translations for 'no', but not 'nb' (BTS
 566 <a href="http://bugs.debian.org/684391">#684391</a>), but due to a bug
 567 (BTS <a href="http://bugs.debian.org/682936">#682936</a>) the 'no'
 568 language code is not recognised.  The docbook-xsl tool chain only
 569 recognise 'nn' and 'nb', but not 'no'.  The xmlto tool only recognise
 570 'nn' and 'nb', but not 'no'.  The end result that there is no language
 571 code I can use to get the docbook file working with all of these tools
 572 at the same time. :(</p>
 573
 574 <p>The correct solution is to use &lt;book lang="nb"&gt;, but it will
 575 take time before that will work with all the free software docbook
 576 processors. :(</p>
 577
 578 <p>Oh, the joy of well integrated tools. :/</p>
 579
 580       </div>
 581       <div class="tags">
 582
 583
 584         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
 585
 586
 587       </div>
 588     </div>
 589     <div class="padding"></div>
 590
 591     <div class="entry">
 592       <div class="title">
 593         <a href="http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html">Best way to create a docbook book?</a>
 594       </div>
 595       <div class="date">
 596         31st July 2012
 597       </div>
 598       <div class="body">
 599         <p>I tried to send this text to the
 600 <a href="https://lists.oasis-open.org/archives/docbook-apps/">docbook-apps
 601 mailing list at lists.oasis-open.org</a>, but it only accept messages
 602 from subscribers and rejected my post, and I completely lack the
 603 bandwidth required to subscribe to another mailing list, so instead I
 604 try to post my message here and hope my blog readers can help me
 605 out.</p>
 606
 607 <p>I am quite new to docbook processing, and am climbing a steep
 608 learning curve at the moment.</p>
 609
 610 <p>To give you some background, I am working on a Norwegian
 611 translation of the book Free Culture by Lawrence Lessig, and I use
 612 docbook to handle the process.  The files to build the book are
 613 available from
 614 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.
 615 The book got around 400 pages with parts, images, footnotes, tables,
 616 index entries etc, which has proven to be a challenge for the free
 617 software docbook processors.  My build platform is Debian GNU/Linux
 618 Squeeze.</p>
 619
 620 <p>I want to build PDF, EPUB and HTML version of the book, and have
 621 tried different tool chains to do the conversion from docbook to these
 622 formats.  I am currently focusing on the PDF version, and have a few
 623 problems.</p>
 624
 625 <ul>
 626
 627 <li>Using dblatex, the &lt;part&gt; handling is not the way I want to,
 628    as &lt;/part&gt; do not really end the &lt;part&gt;. (See
 629    <a href="http://bugs.debian.org/683166">BTS report #683166</a>), the
 630    xetex backend (needed to process UTF-8) give incorrect hyphens in
 631    index references spanning several pages (See
 632    <a href="http://bugs.debian.org/682901">BTS report #682901</a>), and
 633    I am unable to get the norwegian template texts (See
 634    <a href="http://bugs.debian.org/682936">BTS report #682936</a>).</li>
 635
 636 <li>Using straight xmlto fail with some latex error (See
 637    <a href="http://bugs.debian.org/683163">BTS report
 638    #683163</a>).</li>
 639
 640 <li>Using xmlto with the fop backend fail to handle images (do not
 641    show up in the PDF), fail to handle a long footnote (overlap
 642    footnote and text body, see
 643    <a href="http://bugs.debian.org/683197">BTS report #683197</a>), and
 644    fail to create a correct index (some lack page ref, and the page
 645    refs listed are not right).</li>
 646
 647 <li>Using xmlto with the dblatex backend behave like dblatex.</li>
 648
 649 <li>Using docbook-xls with xsltproc + fop have the same footnote and
 650    index problems the xmlto + fop processing.</li>
 651
 652 </ul>
 653
 654 <p>So I wonder, what would be the best way to create the PDF version
 655 of this book?  Are some of the bugs found above solved in new or
 656 experimental versions of some docbook tool chain?</p>
 657
 658 <p>What about HTML and EPUB versions?</p>
 659
 660       </div>
 661       <div class="tags">
 662
 663
 664         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
 665
 666
 667       </div>
 668     </div>
 669     <div class="padding"></div>
 670
 671     <div class="entry">
 672       <div class="title">
 673         <a href="http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html">Free Culture in Norwegian - 5 chapters done, 74 percent left to do</a>
 674       </div>
 675       <div class="date">
 676         21st July 2012
 677       </div>
 678       <div class="body">
 679         <p>I reported earlier that I am working on
 680 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">a
 681 norwegian version</a> of the book
 682 <a href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig.
 683 Progress is good, and yesterday I got a major contribution from Anders
 684 Hagen Jarmund completing chapter six.  The source files as well as a
 685 PDF and EPUB version of this book are available from
 686 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.</p>
 687
 688 <p>I am happy to report that the draft for the first two chapters
 689 (preface, introduction) is complete, and three other chapters are also
 690 completely translated.  This completes 26 percent of the number of
 691 strings (equivalent to paragraphs) in the book, and there is thus 74
 692 percent left to translate.  A graph of the progress is present at the
 693 bottom of the github project page.  There is still room for more
 694 contributors.  Get in touch or send github pull requests with fixes if
 695 you got time and are willing to help make this book make it to
 696 print. :)</p>
 697
 698 <p>The book translation framework could also be a good basis for other
 699 translations, if you want the book to be available in your
 700 language.</p>
 701
 702       </div>
 703       <div class="tags">
 704
 705
 706         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 707
 708
 709       </div>
 710     </div>
 711     <div class="padding"></div>
 712
 713     <div class="entry">
 714       <div class="title">
 715         <a href="http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html">Call for help from docbook expert to tag Free Culture by Lawrence Lessig</a>
 716       </div>
 717       <div class="date">
 718         16th July 2012
 719       </div>
 720       <div class="body">
 721         <p>I am currently working on a
 722 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">project
 723 to translate</a> the book
 724 <a href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig
 725 to Norwegian.  And the source we base our translation on is the
 726 <a href="http://en.wikipedia.org/wiki/DocBook">docbook</a> version, to
 727 allow us to use po4a and .po files to handle the translation, and for
 728 this to work well the docbook source document need to be properly
 729 tagged.  The source files of this project is available from
 730 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.</p>
 731
 732 <p>The problem is that the docbook source have flaws, and we have
 733 no-one involved in the project that is a docbook expert.  Is there a
 734 docbook expert somewhere that is interested in helping us create a
 735 well tagged docbook version of the book, and adjust our build process
 736 for the PDF, EPUB and HTML version of the book?  This will provide a
 737 well tagged English version (our source document), and make it a lot
 738 easier for us to create a good Norwegian version.  If you can and want
 739 to help, please get in touch with me or fork the github project and
 740 send pull requests with fixes. :)</p>
 741
 742       </div>
 743       <div class="tags">
 744
 745
 746         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 747
 748
 749       </div>
 750     </div>
 751     <div class="padding"></div>
 752
 753     <div class="entry">
 754       <div class="title">
 755         <a href="http://people.skolelinux.org/pere/blog/Fri_programvare____fri__som_i__talefrihet___ikke_som_i__fri_bar_.html">Fri programvare - "fri" som i "talefrihet", ikke som i "fri bar"</a>
 756       </div>
 757       <div class="date">
 758         15th July 2012
 759       </div>
 760       <div class="body">
 761         <p>Et ofte brukt sitat i fri programvareverden er Stallman-sitatet
 762 «<a href="http://www.gnu.org/philosophy/free-sw.html.en">Free Software,
 763 "free" as in "free speech", not as in "free beer"</a>».  Men det er
 764 ikke direkte overførbart til norsk, da det baserer seg på koblingen
 765 gratis/fri på engelsk.  En direkte oversettelse ville være «Fri
 766 programvare, "fri" som i "talefrihet", ikke som "gratis øl"», og det
 767 går jo glipp av poenget.  I forbindelse med at vi er
 768 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">igang
 769 med å oversette</a> <a href="http://free-culture.cc/">Free Culture</a>
 770 av Lawrence Lessig, måtte jeg forsøke a finne en bedre
 771 oversettelse.</p>
 772
 773 <p>Mitt forslag til oversettelse blir dermed å droppe ølet, og heller
 774 fokusere på det kjente norske uttrykket "fri bar".  Dermed blir
 775 oversettelsen «Fri programvare - "fri" som i "talefrihet", ikke som i
 776 "fri bar"».</p>
 777
 778 <p>Noen som har bedre forslag?</p>
 779
 780 <p>Forøvrig bruker jeg fri programvare som et samlebegrep på norsk for
 781 begge de engelske uttrykkene Free Software og Open Source, jamfør
 782 <a href="http://www.nuug.no/dokumenter/folder-friprogramvare.pdf">NUUGs
 783 lille folder om temaet</a>.</p>
 784
 785       </div>
 786       <div class="tags">
 787
 788
 789         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 790
 791
 792       </div>
 793     </div>
 794     <div class="padding"></div>
 795
 796     <div class="entry">
 797       <div class="title">
 798         <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">Dugnad for å sende norsk versjon av Free Culture til stortingets representanter!</a>
 799       </div>
 800       <div class="date">
 801         11th July 2012
 802       </div>
 803       <div class="body">
 804         <p>Da opphavsrettsloven ble revidert i forrige runde rundt 2005, var
 805 det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
 806 Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
 807 og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
 808 representanter fikk en norsk utgave av boken
 809 <a href="http://free-culture.cc/">Free Culture</a> av Lawrence Lessig
 810 som forklarte litt om problemstillingene.  Vi endte opp med å
 811 prioritere utvikling i
 812 <a href="http://www.skolelinux.org/">Skolelinux</a>-prosjektet i
 813 stedet, så den oversatte boken så aldri dagens lys.  Men i forrige uke
 814 ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
 815 bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
 816 sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
 817 fordel for forlag og store mediehus fortsatt trenger en annen vinkling
 818 i debatten.</p>
 819
 820 <p>Planen min er å oversette boka på dugnad, sette den opp for
 821 trykking med en av de mange
 822 <a href="http://no.wikipedia.org/wiki/Trykk_på_forespørsel">trykk på
 823 forespørsel</a>-tjenestene, skaffe sponsor til å finansiere trykking
 824 til stortingsrepresentantene og alle som har bidratt med
 825 oversettelser.  Kanskje vi også kan få en avtale med et forlag om
 826 publisering når boka er ferdig?  Kommentarene til
 827 <a href="http://newth.net/eirik/2011/04/01/e-selvpublisering/">Eirik
 828 Newth</a> og
 829 <a href="http://www.espen.com/norskblogg/archives/2008/09/erfaringer_med_publishing_on_demand.html">Espen
 830 Andersen</a> om erfaringene med selvpublisering og trykk på
 831 forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
 832 <a href="http://www.lulu.com/">Lulu</a> er en grei leverandør av
 833 trykketjenester til prosjektet.</p>
 834
 835 <p>Jeg har satt opp
 836 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">et
 837 Github-prosjekt</a> for a lage boken, basert på Docbook-utgaven jeg
 838 fant fra Hans Schou.  Skolelinux har hatt byggesystem for å lage
 839 oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
 840 kopiert og utvidet dette oppsettet.  Originalteksten er i Docbook, og
 841 oversettelsen gjøres i .po-filer med hjelp av vanlige
 842 oversetterverktøy brukt i fri programvareverden.  Dernest tar
 843 byggesystemet over og lager PDF og EPUB-utgave av den oversatte
 844 teksten.  Resultatet kan ses i Github-prosjektet.  For å komme raskt
 845 igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
 846 til norsk, noe som grovoversatte ca. 1300 av de ca. 1700 tekstbitene
 847 boken består av.  Jeg håper nå at flere kan bidra med å få
 848 oversettelsen på plass, slik at teksten kan være klar i løpet av
 849 høsten.  Når alt er oversatt må teksten gjennomgås for feil og
 850 konsistent språk.  Totalt er det nok mange timer som trengs for å
 851 gjennomføre oversettelsen.</p>
 852
 853 <p>Økonomien i dette er ikke avskrekkende.  169
 854 stortingsrepresentanter og nesten like mange varamedlemmer bør få
 855 bøker, og estimert produduksjonskostnad for hver bok er rundt 6 EURO i
 856 følge et raskt estimat fra Lulu.  Jeg vet ennå ikke hvor mange sider
 857 det blir i størrelsen 5,5" x 8.5" (det er ca. 140 sider i A4-format),
 858 så jeg gjettet på 400 sider.  Jeg tror originalutgaven har nesten 400
 859 sider.  For 169*2 eksemplarer snakker vi om en trykkekostnad på
 860 ca. 2000 EURO, dvs. ca 15 000 NOK.  Det burde være mulig å finne en
 861 sponsor for å dekke en slik sum.  I tillegg kommer distribusjon og
 862 porto, som antagelig kommer på like mye.</p>
 863
 864 <p>Kan du bidra med oversettelse og docbook-typesetting?  Ta kontakt
 865 og send patcher i github.  Jeg legger gjerne inn folk i prosjektet
 866 slik at du kan oppdatere direkte.</p>
 867
 868       </div>
 869       <div class="tags">
 870
 871
 872         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 873
 874
 875       </div>
 876     </div>
 877     <div class="padding"></div>
 878
 879     <p style="text-align: right;"><a href="freeculture.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
 880     <div id="sidebar">
 881
 882
 883
 884 <h2>Archive</h2>
 885 <ul>
 886
 887 <li>2014
 888 <ul>
 889
 890 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 891
 892 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 893
 894 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (5)</a></li>
 895
 896 </ul></li>
 897
 898 <li>2013
 899 <ul>
 900
 901 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 902
 903 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 904
 905 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 906
 907 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 908
 909 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 910
 911 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 912
 913 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 914
 915 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 916
 917 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 918
 919 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 920
 921 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 922
 923 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 924
 925 </ul></li>
 926
 927 <li>2012
 928 <ul>
 929
 930 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 931
 932 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 933
 934 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 935
 936 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 937
 938 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 939
 940 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 941
 942 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 943
 944 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 945
 946 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 947
 948 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 949
 950 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 951
 952 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 953
 954 </ul></li>
 955
 956 <li>2011
 957 <ul>
 958
 959 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 960
 961 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 962
 963 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 964
 965 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 966
 967 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 968
 969 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 970
 971 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 972
 973 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 974
 975 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 976
 977 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 978
 979 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 980
 981 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 982
 983 </ul></li>
 984
 985 <li>2010
 986 <ul>
 987
 988 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 989
 990 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 991
 992 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 993
 994 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 995
 996 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 997
 998 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 999
1000 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1001
1002 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1003
1004 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1005
1006 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1007
1008 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1009
1010 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1011
1012 </ul></li>
1013
1014 <li>2009
1015 <ul>
1016
1017 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1018
1019 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1020
1021 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1022
1023 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1024
1025 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1026
1027 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1028
1029 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1030
1031 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1032
1033 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1034
1035 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1036
1037 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1038
1039 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1040
1041 </ul></li>
1042
1043 <li>2008
1044 <ul>
1045
1046 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1047
1048 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1049
1050 </ul></li>
1051
1052 </ul>
1053
1054
1055
1056 <h2>Tags</h2>
1057 <ul>
1058
1059  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1060
1061  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1062
1063  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1064
1065  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
1068
1069  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
1070
1071  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1072
1073  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1074
1075  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (95)</a></li>
1076
1077  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (145)</a></li>
1078
1079  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1080
1081  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1082
1083  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1084
1085  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (239)</a></li>
1086
1087  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1088
1089  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1090
1091  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1092
1093  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (6)</a></li>
1094
1095  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1096
1097  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (39)</a></li>
1098
1099  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1100
1101  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1102
1103  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1104
1105  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (7)</a></li>
1106
1107  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1108
1109  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (7)</a></li>
1110
1111  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (26)</a></li>
1112
1113  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (242)</a></li>
1114
1115  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (162)</a></li>
1116
1117  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
1118
1119  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1120
1121  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (46)</a></li>
1122
1123  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (69)</a></li>
1124
1125  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1126
1127  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1128
1129  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1130
1131  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1132
1133  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1134
1135  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1136
1137  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1138
1139  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (35)</a></li>
1140
1141  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1142
1143  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1144
1145  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1146
1147  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1148
1149  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1150
1151  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (22)</a></li>
1152
1153  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1154
1155  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1156
1157  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (40)</a></li>
1158
1159  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1160
1161  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (29)</a></li>
1162
1163 </ul>
1164
1165
1166     </div>
1167     <p style="text-align: right">
1168  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1169 </p>
1170
1171   </body>
1172 </html>