blog/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</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="http://people.skolelinux.org/pere/blog/index.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
  22     <div class="entry">
  23       <div class="title"><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></div>
  24       <div class="date">10th August 2012</div>
  25       <div class="body"><p>In <a href="http://www.docbook.org/">docbook</a> one can specify
  26 the language used at the top, and the processing pipeline will use
  27 this information to pick the correct translations for 'chapter', 'see
  28 also', 'index' etc.  And for most languages used with docbook, I guess
  29 this work just fine.  For example a German user can start the document
  30 with &lt;book lang="de"&gt;, and the document will show up with the
  31 correct content with any of the docbook processors.  This is not the
  32 case for the language
  33 <a href="http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html">I
  34 am working with at the moment</a>, Norwegian Bokmål.</p>
  35
  36 <p>For a while, I was confused about which language code to use,
  37 because I was unable to find any language code that would work across
  38 all tools.  I am currently testing dblatex, xmlto, docbook-xsl, and
  39 dbtoepub, and they do not handle Norwegian Bokmål the same way.  Some
  40 of them do not handle it at all.</p>
  41
  42 <p>A bit of background information is probably needed to understand
  43 this mess.  Norwegian is not one, but two written variants.  The
  44 variants are Norwegian Nynorsk and Norwegian Bokmål.  There are three
  45 two letter language codes associated with these languages, Norwegian
  46 is 'no', Norwegian Nynorsk is 'nn' and Norwegian Bokmål is 'nb'.
  47 Historically the 'no' language code was used for Norwegian Bokmål, but
  48 many years ago this was found to be å bad idea, and the recommendation
  49 is to use the most specific language code instead, to avoid confusion.
  50 In the transition period it is a good idea to make sure 'no' was an
  51 alias for 'nb'.</p>
  52
  53 <p>Back to docbook processing tools in Debian.  The dblatex tool only
  54 understand 'nn'.  There are translations for 'no', but not 'nb' (BTS
  55 <a href="http://bugs.debian.org/684391">#684391</a>), but due to a bug
  56 (BTS <a href="http://bugs.debian.org/682936">#682936</a>) the 'no'
  57 language code is not recognised.  The docbook-xsl tool chain only
  58 recognise 'nn' and 'nb', but not 'no'.  The xmlto tool only recognise
  59 'nn' and 'nb', but not 'no'.  The end result that there is no language
  60 code I can use to get the docbook file working with all of these tools
  61 at the same time. :(</p>
  62
  63 <p>The correct solution is to use &lt;book lang="nb"&gt;, but it will
  64 take time before that will work with all the free software docbook
  65 processors. :(</p>
  66
  67 <p>Oh, the joy of well integrated tools. :/</p>
  68 </div>
  69       <div class="tags">
  70
  71
  72         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
  73
  74
  75       </div>
  76     </div>
  77     <div class="padding"></div>
  78
  79     <div class="entry">
  80       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html">Best way to create a docbook book?</a></div>
  81       <div class="date">31st July 2012</div>
  82       <div class="body"><p>I tried to send this text to the
  83 <a href="https://lists.oasis-open.org/archives/docbook-apps/">docbook-apps
  84 mailing list at lists.oasis-open.org</a>, but it only accept messages
  85 from subscribers and rejected my post, and I completely lack the
  86 bandwidth required to subscribe to another mailing list, so instead I
  87 try to post my message here and hope my blog readers can help me
  88 out.</p>
  89
  90 <p>I am quite new to docbook processing, and am climbing a steep
  91 learning curve at the moment.</p>
  92
  93 <p>To give you some background, I am working on a Norwegian
  94 translation of the book Free Culture by Lawrence Lessig, and I use
  95 docbook to handle the process.  The files to build the book are
  96 available from
  97 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.
  98 The book got around 400 pages with parts, images, footnotes, tables,
  99 index entries etc, which has proven to be a challenge for the free
 100 software docbook processors.  My build platform is Debian GNU/Linux
 101 Squeeze.</p>
 102
 103 <p>I want to build PDF, EPUB and HTML version of the book, and have
 104 tried different tool chains to do the conversion from docbook to these
 105 formats.  I am currently focusing on the PDF version, and have a few
 106 problems.</p>
 107
 108 <ul>
 109
 110 <li>Using dblatex, the &lt;part&gt; handling is not the way I want to,
 111    as &lt;/part&gt; do not really end the &lt;part&gt;. (See
 112    <a href="http://bugs.debian.org/683166">BTS report #683166</a>), the
 113    xetex backend (needed to process UTF-8) give incorrect hyphens in
 114    index references spanning several pages (See
 115    <a href="http://bugs.debian.org/682901">BTS report #682901</a>), and
 116    I am unable to get the norwegian template texts (See
 117    <a href="http://bugs.debian.org/682936">BTS report #682936</a>).</li>
 118
 119 <li>Using straight xmlto fail with some latex error (See
 120    <a href="http://bugs.debian.org/683163">BTS report
 121    #683163</a>).</li>
 122
 123 <li>Using xmlto with the fop backend fail to handle images (do not
 124    show up in the PDF), fail to handle a long footnote (overlap
 125    footnote and text body, see
 126    <a href="http://bugs.debian.org/683197">BTS report #683197</a>), and
 127    fail to create a correct index (some lack page ref, and the page
 128    refs listed are not right).</li>
 129
 130 <li>Using xmlto with the dblatex backend behave like dblatex.</li>
 131
 132 <li>Using docbook-xls with xsltproc + fop have the same footnote and
 133    index problems the xmlto + fop processing.</li>
 134
 135 </ul>
 136
 137 <p>So I wonder, what would be the best way to create the PDF version
 138 of this book?  Are some of the bugs found above solved in new or
 139 experimental versions of some docbook tool chain?</p>
 140
 141 <p>What about HTML and EPUB versions?</p>
 142 </div>
 143       <div class="tags">
 144
 145
 146         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 147
 148
 149       </div>
 150     </div>
 151     <div class="padding"></div>
 152
 153     <div class="entry">
 154       <div class="title"><a href="http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html">OOXML og standardisering</a></div>
 155       <div class="date">25th July 2012</div>
 156       <div class="body"><p>DIFI har
 157 <a href="http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html">en
 158 høring gående</a> om ny versjon av statens standardkatalog, med frist
 159 2012-09-30, der det foreslås å fjerne ODF fra katalogen og ta inn ISO
 160 OOXML.  I den anledning minnes jeg
 161 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">notatet
 162 FAD skrev</a> da versjon 2 av standardkatalogen var under
 163 utarbeidelse, da FAD og DIFI fortsatt forsto poenget med og verdien av
 164 frie og åpne standarder.</p>
 165
 166 <p>Det er mange som tror at OOXML er ett spesifikt format, men det
 167 brukes ofte som fellesbetegnelse for både formatet spesifisert av
 168 ECMA, ISO, og formatet produsert av Microsoft Office (aka docx), som
 169 dessverre ikke er det samme formatet.  Fra en av de som implementerte
 170 støtte for docx-formatet i KDE fikk jeg høre at ISO-spesifikasjonen
 171 var en nyttig referanse, men at det var mange avvik som gjorde at en
 172 ikke kunne gå ut ifra at Microsoft Office produserte dokumenter i
 173 henhold til ISO-spesifikasjonen.</p>
 174
 175 <p>ISOs OOXML-spesifikasjon har (eller hadde, usikker på om
 176 kommentaren er oppdatert) i følge
 177 <a href="http://surguy.net/articles/ooxml-validation-and-technical-review.xml">Inigo
 178 Surguy</a> feil i mer enn 10% av eksemplene, noe som i tillegg gjør
 179 det vanskelig å bruke spesifikasjonen til å implementere støtte for
 180 ISO OOXML.  Jeg har ingen erfaring med å validere OOXML-dokumenter
 181 selv, men ser at
 182 <a href="http://www.microsoft.com/en-us/download/details.aspx?id=5124">Microsoft
 183 har laget en validator</a> som jeg ikke kan teste da den kun er
 184 tilgjengelig på MS Windows.  Finner også en annen kalt
 185 <a href="http://code.google.com/p/officeotron/">Office-O-Tron</A> som
 186 er oppdatert i fjor.  Lurer på om de validerer at dokumenter er i
 187 formatet til Microsoft office, eller om de validerer at de er i
 188 henhold til formatene spesifisert av ECMA og ISO. Det hadde også vært
 189 interessant å se om docx-dokumentene publisert av det offentlige er
 190 gyldige ISO OOXML-dokumenter.</p>
 191 </div>
 192       <div class="tags">
 193
 194
 195         Tags: <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/standard">standard</a>.
 196
 197
 198       </div>
 199     </div>
 200     <div class="padding"></div>
 201
 202     <div class="entry">
 203       <div class="title"><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></div>
 204       <div class="date">21st July 2012</div>
 205       <div class="body"><p>I reported earlier that I am working on
 206 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">a
 207 norwegian version</a> of the book
 208 <a href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig.
 209 Progress is good, and yesterday I got a major contribution from Anders
 210 Hagen Jarmund completing chapter six.  The source files as well as a
 211 PDF and EPUB version of this book are available from
 212 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.</p>
 213
 214 <p>I am happy to report that the draft for the first two chapters
 215 (preface, introduction) is complete, and three other chapters are also
 216 completely translated.  This completes 26 percent of the number of
 217 strings (equivalent to paragraphs) in the book, and there is thus 74
 218 percent left to translate.  A graph of the progress is present at the
 219 bottom of the github project page.  There is still room for more
 220 contributors.  Get in touch or send github pull requests with fixes if
 221 you got time and are willing to help make this book make it to
 222 print. :)</p>
 223
 224 <p>The book translation framework could also be a good basis for other
 225 translations, if you want the book to be available in your
 226 language.</p>
 227 </div>
 228       <div class="tags">
 229
 230
 231         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</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>.
 232
 233
 234       </div>
 235     </div>
 236     <div class="padding"></div>
 237
 238     <div class="entry">
 239       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Tips_for___bli_med_i_Skolelinux_prosjektet__som_faktisk_er_aktivt_.html">Tips for å bli med i Skolelinux-prosjektet (som faktisk er aktivt)</a></div>
 240       <div class="date">19th July 2012</div>
 241       <div class="body"><p>Jeg fikk nettopp spørsmål på epost om Skolelinux-prosjektet lever
 242 fra en som var interessert i å bidra, og måtte jo konstatere at i og
 243 med at spørsmålet ble stilt har prosjektet ikke lyktes med å formidle
 244 sin aktivitet.  Her er det jeg svarte:</p>
 245
 246 <p><blockquote>
 247 <p>Jada, <a href="http://www.skolelinux.org/">Skolelinux-prosjektet</a>
 248 lever, men det meste av utvikling foregår nå under paraplyen
 249 <a href="http://wiki.debian.org/DebianEdu/">Debian Edu</a> som er det
 250 internasjonale navnet på prosjektet.  Dugnaden i Norge organiseres av
 251 medlemsforeningen
 252 <a href="http://www.friprogramvareiskolen.no/">Fri programvare i
 253 Skolen</a>, og det finnes minst ett selskap som selger kommersiell
 254 support på løsningen (<a href="http://www.slxdrift.no/">Skolelinux
 255 Drift AS</a>, der jeg er styremedlem).  Anbefaler at du melder deg på
 256 epostlisten
 257 <a href="http://lists.debian.org/debian-edu/">debian-edu@lists.debian.org</a>
 258 (og debian-edu-announce) og
 259 <a href="http://medlem.friprogramvareiskolen.no/">melder deg inn i
 260 foreningen</a> for å få beskjed om aktivitet som planlegges.  Det
 261 planlegges
 262 <a href="http://www.friprogramvareiskolen.no/Gathering">utviklersamlinger
 263 i august</a> og utover høsten.</p>
 264
 265 <p>Bidra gjerne med å spre ordet om Skolelinux.  Det er alt for få som
 266 bidrar til pressedekning, bloggposter, twittermeldinger, etc. :)</p>
 267
 268 <p>Jeg antar du har funnet
 269 <a href="http://people.skolelinux.org/pere/blog/tags/intervju/">bloggserien
 270 min med intervjuer</a>.  Det er antagelig også interessant for deg å
 271 følge med på <a href="http://planet.skolelinux.org/">Planet
 272 Skolelinux</a>.</p>
 273
 274 <p>Hm, jeg burde vel blogge alle disse lenkene slik at de blir enklere
 275 å finne...</p>
 276 </blockquote></p>
 277 <p>Herved gjort. :)</p>
 278 </div>
 279       <div class="tags">
 280
 281
 282         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
 283
 284
 285       </div>
 286     </div>
 287     <div class="padding"></div>
 288
 289     <div class="entry">
 290       <div class="title"><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></div>
 291       <div class="date">16th July 2012</div>
 292       <div class="body"><p>I am currently working on a
 293 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">project
 294 to translate</a> the book
 295 <a href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig
 296 to Norwegian.  And the source we base our translation on is the
 297 <a href="http://en.wikipedia.org/wiki/DocBook">docbook</a> version, to
 298 allow us to use po4a and .po files to handle the translation, and for
 299 this to work well the docbook source document need to be properly
 300 tagged.  The source files of this project is available from
 301 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.</p>
 302
 303 <p>The problem is that the docbook source have flaws, and we have
 304 no-one involved in the project that is a docbook expert.  Is there a
 305 docbook expert somewhere that is interested in helping us create a
 306 well tagged docbook version of the book, and adjust our build process
 307 for the PDF, EPUB and HTML version of the book?  This will provide a
 308 well tagged English version (our source document), and make it a lot
 309 easier for us to create a good Norwegian version.  If you can and want
 310 to help, please get in touch with me or fork the github project and
 311 send pull requests with fixes. :)</p>
 312 </div>
 313       <div class="tags">
 314
 315
 316         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</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>.
 317
 318
 319       </div>
 320     </div>
 321     <div class="padding"></div>
 322
 323     <div class="entry">
 324       <div class="title"><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></div>
 325       <div class="date">15th July 2012</div>
 326       <div class="body"><p>Et ofte brukt sitat i fri programvareverden er Stallman-sitatet
 327 «<a href="http://www.gnu.org/philosophy/free-sw.html.en">Free Software,
 328 "free" as in "free speech", not as in "free beer"</a>».  Men det er
 329 ikke direkte overførbart til norsk, da det baserer seg på koblingen
 330 gratis/fri på engelsk.  En direkte oversettelse ville være «Fri
 331 programvare, "fri" som i "talefrihet", ikke som "gratis øl"», og det
 332 går jo glipp av poenget.  I forbindelse med at vi er
 333 <a href="http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html">igang
 334 med å oversette</a> <a href="http://free-culture.cc/">Free Culture</a>
 335 av Lawrence Lessig, måtte jeg forsøke a finne en bedre
 336 oversettelse.</p>
 337
 338 <p>Mitt forslag til oversettelse blir dermed å droppe ølet, og heller
 339 fokusere på det kjente norske uttrykket "fri bar".  Dermed blir
 340 oversettelsen «Fri programvare - "fri" som i "talefrihet", ikke som i
 341 "fri bar"».</p>
 342
 343 <p>Noen som har bedre forslag?</p>
 344
 345 <p>Forøvrig bruker jeg fri programvare som et samlebegrep på norsk for
 346 begge de engelske uttrykkene Free Software og Open Source, jamfør
 347 <a href="http://www.nuug.no/dokumenter/folder-friprogramvare.pdf">NUUGs
 348 lille folder om temaet</a>.</p>
 349 </div>
 350       <div class="tags">
 351
 352
 353         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 354
 355
 356       </div>
 357     </div>
 358     <div class="padding"></div>
 359
 360     <div class="entry">
 361       <div class="title"><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></div>
 362       <div class="date">11th July 2012</div>
 363       <div class="body"><p>Da opphavsrettsloven ble revidert i forrige runde rundt 2005, var
 364 det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
 365 Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
 366 og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
 367 representanter fikk en norsk utgave av boken
 368 <a href="http://free-culture.cc/">Free Culture</a> av Lawrence Lessig
 369 som forklarte litt om problemstillingene.  Vi endte opp med å
 370 prioritere utvikling i
 371 <a href="http://www.skolelinux.org/">Skolelinux</a>-prosjektet i
 372 stedet, så den oversatte boken så aldri dagens lys.  Men i forrige uke
 373 ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
 374 bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
 375 sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
 376 fordel for forlag og store mediehus fortsatt trenger en annen vinkling
 377 i debatten.</p>
 378
 379 <p>Planen min er å oversette boka på dugnad, sette den opp for
 380 trykking med en av de mange
 381 <a href="http://no.wikipedia.org/wiki/Trykk_på_forespørsel">trykk på
 382 forespørsel</a>-tjenestene, skaffe sponsor til å finansiere trykking
 383 til stortingsrepresentantene og alle som har bidratt med
 384 oversettelser.  Kanskje vi også kan få en avtale med et forlag om
 385 publisering når boka er ferdig?  Kommentarene til
 386 <a href="http://newth.net/eirik/2011/04/01/e-selvpublisering/">Eirik
 387 Newth</a> og
 388 <a href="http://www.espen.com/norskblogg/archives/2008/09/erfaringer_med_publishing_on_demand.html">Espen
 389 Andersen</a> om erfaringene med selvpublisering og trykk på
 390 forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
 391 <a href="http://www.lulu.com/">Lulu</a> er en grei leverandør av
 392 trykketjenester til prosjektet.</p>
 393
 394 <p>Jeg har satt opp
 395 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">et
 396 Github-prosjekt</a> for a lage boken, basert på Docbook-utgaven jeg
 397 fant fra Hans Schou.  Skolelinux har hatt byggesystem for å lage
 398 oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
 399 kopiert og utvidet dette oppsettet.  Originalteksten er i Docbook, og
 400 oversettelsen gjøres i .po-filer med hjelp av vanlige
 401 oversetterverktøy brukt i fri programvareverden.  Dernest tar
 402 byggesystemet over og lager PDF og EPUB-utgave av den oversatte
 403 teksten.  Resultatet kan ses i Github-prosjektet.  For å komme raskt
 404 igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
 405 til norsk, noe som grovoversatte ca. 1300 av de ca. 1700 tekstbitene
 406 boken består av.  Jeg håper nå at flere kan bidra med å få
 407 oversettelsen på plass, slik at teksten kan være klar i løpet av
 408 høsten.  Når alt er oversatt må teksten gjennomgås for feil og
 409 konsistent språk.  Totalt er det nok mange timer som trengs for å
 410 gjennomføre oversettelsen.</p>
 411
 412 <p>Økonomien i dette er ikke avskrekkende.  169
 413 stortingsrepresentanter og nesten like mange varamedlemmer bør få
 414 bøker, og estimert produduksjonskostnad for hver bok er rundt 6 EURO i
 415 følge et raskt estimat fra Lulu.  Jeg vet ennå ikke hvor mange sider
 416 det blir i størrelsen 5,5" x 8.5" (det er ca. 140 sider i A4-format),
 417 så jeg gjettet på 400 sider.  Jeg tror originalutgaven har nesten 400
 418 sider.  For 169*2 eksemplarer snakker vi om en trykkekostnad på
 419 ca. 2000 EURO, dvs. ca 15 000 NOK.  Det burde være mulig å finne en
 420 sponsor for å dekke en slik sum.  I tillegg kommer distribusjon og
 421 porto, som antagelig kommer på like mye.</p>
 422
 423 <p>Kan du bidra med oversettelse og docbook-typesetting?  Ta kontakt
 424 og send patcher i github.  Jeg legger gjerne inn folk i prosjektet
 425 slik at du kan oppdatere direkte.</p>
 426 </div>
 427       <div class="tags">
 428
 429
 430         Tags: <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>.
 431
 432
 433       </div>
 434     </div>
 435     <div class="padding"></div>
 436
 437     <div class="entry">
 438       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__George_Bredberg.html">Debian Edu interview: George Bredberg</a></div>
 439       <div class="date"> 9th July 2012</div>
 440       <div class="body"><p>The <a href="http://www.skolelinux.org/">Debian Edu /
 441 Skolelinux</a> project have users all over the globe, but until
 442 recently we have not known about any users in Norway's neighbour
 443 country Sweden.  This changed when George Bredberg showed up in March
 444 this year on the mailing list, asking interesting questions about how
 445 to adjust and scale the just released
 446 <a href="http://www.debian.org/News/2012/20120311.html">Debian Edu
 447 Wheezy</a> setup to his liking.  He granted me an interview, and I am
 448 happy to share his answers with you here.</p>
 449
 450 <p><strong>Who are you, and how do you spend your days?</strong></p>
 451
 452 <p>I'm a 44 year old country guy that have been working 12 years at
 453 the same school as 50% IT-manager and 50% Teacher. My educational
 454 background is fil.kand in history and religious beliefs, an exam as a
 455 "folkhighschool" teacher, that is, for teaching grownups.  In
 456 Norwegian I believe it's called "Vuxenupplaring". I also have a master
 457 in "Technology and social change". So I'm not really a tech guy, I
 458 just like to study how humans and technology interact and that is my
 459 perspective when working with IT.</p>
 460
 461 <p><strong>How did you get in contact with the Skolelinux/Debian Edu
 462 project?</strong></p>
 463
 464 I have followed the Skolelinux project for quite some time by
 465 now. Earlier I tested out the K12-LTSP project, which we used for some
 466 time, but I really like the idea of having a distribution aimed to be
 467 a complete solution for schools with necessary tools integrated. When
 468 K12-LTSP abandoned that idea some years ago, I started to look more
 469 seriously into Skolelinux instead.
 470
 471 <p><strong>What do you see as the advantages of Skolelinux/Debian
 472 Edu?</strong></p>
 473
 474 The big point of Skolelinux to me is that it is a complete
 475 distribution, ready to install. It has LDAP-support, MS Windows
 476 integration tools and so forth already configured, saving an
 477 administrator a lot of time and headache. We were using another Linux
 478 based thin-client system called Thinlinc, that has served us very
 479 well. But that Skolelinux is based on VNC and LTSP, to me, is better
 480 when it comes to the kind of multimedia used in schools. That is
 481 showing videos from Youtube or educational TV. It is also easier to
 482 mix thin clients with workstations, since the user settings will be the
 483 same. In our VNC-based solution you had to "beat around the bush" by
 484 setting up a second, hidden, home-directory for user settings for the
 485 workstations, because they will be different from the ones used on the
 486 thin clients. Skolelinux support for diskless workstations are very
 487 convenient since a school today often need to use a class room
 488 projector showing videos in full screen. That is easily done with a
 489 small integrated media computer running as a diskless workstation. You
 490 have only two installs to update and configure. One for the thin
 491 clients and one for the workstations. Also saving a lot of time.  Our
 492 old system was also based on Redhat and CentOS. They are both very
 493 nice distributions, but they are sometimes painfully slow when it
 494 comes to updating multimedia support and multimedia programs (even
 495 such as Gimp), leaving us with a bit "oldish" applications. Debian is
 496 quicker to update.
 497
 498 <p><strong>What do you see as the disadvantages of Skolelinux/Debian
 499 Edu?</strong></p>
 500
 501 <p>Debian is a bit too quick when it comes to updating. As an example
 502 we use old HP terminals as thinclients, and two times already this
 503 year (2012) the updates you get from the repositories has stopped
 504 sound from working with them.  It's a kernel/ALSA issue. So you have
 505 to be more careful properly testing the updates before you run them in
 506 a production environment. This has never happened with CentOS.</p>
 507
 508 <p>I also would like to be able to set my own domain-settings at
 509 install time.  In Skolelinux they are kind of hard coded into the
 510 distribution, when it comes to LDAP and at least samba integration.
 511 That is more a cosmetic/translation issue, and not a real problem.
 512 Running MS Windows applications within the Skolelinux environment needs
 513 to be better supported. That is, running them seamlessly via RDP, and
 514 support for single-sign on.  That will make the transition to free
 515 software easier, because you can keep the applications you really
 516 need.  No support will make it impossible if you work in a school where
 517 some applications can't be open source. As for us we really need to
 518 run Adobe InDesign in our journalist classes.  We run a journalist
 519 education, and is one of the very few non university ones that is ok:d
 520 by Svenska journalistförbundet (Swedish journalist association).  Our
 521 education gives the pupils the right of membership there, once they
 522 are done.  This is important if you want to get a job.</p>
 523
 524 <p>Adobe InDesign is the program most commonly used in newspapers and
 525 magazines.  We used Quark Express before, but they seem to loose there
 526 market to Adobe. The only "equivalent" to InDesign in the opensource
 527 world is Scribus, and its not advanced enough. At least not according
 528 to the teacher. I think it would be possible to use it, because they
 529 are not supposed to learn a program, they are supposed to learn how to
 530 edit and compile a newspaper.  But politically at our school we are not
 531 there yet.  And Scribus lacks a lot of things you find i InDesign.</p>
 532
 533 <p>We used even a windows program for sound editing when it comes to
 534 the radio-journalist part. The year to come we are going to try
 535 Audacity. That software has the same kind of limitations compared to
 536 Adobe Audition, but that teacher is a bit more open minded. We have
 537 tried Ardour also, but that instead is more like a music studio
 538 program, not intended for the kind of editing taking place in a radio
 539 studio. Its way to complex and the GUI is to scattered when you only
 540 want to cut, make pass-overs, add extra channels and normalise.  Those
 541 things you can do in Audacity, but its not as easy as in Audition. You
 542 have to do more things manually with envelopes, and that is a bit old
 543 fashion and timewasting. Its also harder to cut and move sound from
 544 one channel to another, which is a thing that you do frequently
 545 because you often find yourself needing to rearrange parts of the
 546 sound file.</p>
 547
 548 <p>So, I am not sure we will succeed in replacing even Audition, but we
 549 will try.  The problem is the students have certain expectations when
 550 they start an education towards a profession.  So the programs has to
 551 look and feel professional.  Good thing with radio, there are many
 552 programs out there, that radio studios use, so its not as standardised
 553 as Newspaper editing. That means, it does not really matter what
 554 program they learn, because once they start working they still have to
 555 learn the program the studio uses, so instead focus has to be to learn
 556 the editing part without to much focus on a specific software.</p>
 557
 558 <p><strong>Which free software do you use daily?</strong></p>
 559
 560 <p>Myself I'm running Linux Mint, or Ubuntu these days.  I use almost
 561 only open source software, and preferably Linux based. When it comes
 562 to most used applications its OpenOffice, and Firefox (of course ;)
 563 )</p>
 564
 565 <p><strong>Which strategy do you believe is the right one to use to
 566 get schools to use free software?</strong></p>
 567
 568 <p>To get schools to use free software there has to be good open
 569 source software that are windows based, to ease the transition. But
 570 it's also very important that the multimedia support is working
 571 flawlessly.  The problems with Youtube, Twitter, Facebook and whatever
 572 will create problems when it comes to both teachers and
 573 students. Economy are also important for schools, so using thin
 574 clients, as long as they have good multimedia support, is a very good
 575 idea. It's also important that the open source software works even for
 576 the administration.  It's hard to convince the teachers to stick with
 577 open source, if the principal has to run Windows.  It also creates a
 578 problem if some classes has to use Windows for there tasks, since that
 579 will create a difference in "status" between classes, so a good
 580 support for running windows applications via the thin client (Linux)
 581 desktop is essential.  At least at our school, where we have mixed
 582 level of educations, from high-school to journalist-school.</p>
 583
 584 <p>Update 2012-07-09 08:30: Paul Wise tipped me on IRC about three
 585 useful sources related to Free Software for radio stations: the LWN
 586 article <a href="https://lwn.net/Articles/481607/">Radio station
 587 management with Airtime</a>,
 588 <a href="http://www.sourcefabric.org/en/airtime/">Airtime</a> which
 589 claim to be a Free open source radio automation software and
 590 <a href="http://www.rivendellaudio.org/">Rivendell</a> which claim to
 591 be complete radio broadcast automation solution.  All of them seem
 592 useful to the aspiring radio producer.</p>
 593 </div>
 594       <div class="tags">
 595
 596
 597         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju</a>.
 598
 599
 600       </div>
 601     </div>
 602     <div class="padding"></div>
 603
 604     <div class="entry">
 605       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Why_do_schools_waste_money_on_IT_.html">Why do schools waste money on IT?</a></div>
 606       <div class="date"> 8th July 2012</div>
 607       <div class="body"><p>In the Debian Edu / Skolelinux project, we have realised that one
 608 of the major blockers for the project success is the purchasing skills
 609 in schools and municipalities.  We provide what the happy users of
 610 Debian Edu / Skolelinux say they need and to a lower cost than the
 611 alternatives, and yet so few schools decide to use our solution.  I
 612 was pleased to discover the same observation done by mySociety and Tom
 613 Steinberg in his blog post
 614 "<a href="http://www.mysociety.org/2012/06/19/can-you-recognize-the-million-pound-chair/">Can
 615 you recognize the million pound chair?</a>".  Read it and weep for the
 616 spending of your tax money.</p>
 617
 618 <p>Of course there are other factors involved as well, like our
 619 projects bad marketing skills and the Linux community fragmentation
 620 causing worry with the people on the outside, so we as a project need
 621 to keep working hard to gain users, but it is a up-hill battle when
 622 public decision makers are unable to understand computer system
 623 purchases.</p>
 624 </div>
 625       <div class="tags">
 626
 627
 628         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 629
 630
 631       </div>
 632     </div>
 633     <div class="padding"></div>
 634
 635     <p style="text-align: right;"><a href="index.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
 636     <div id="sidebar">
 637
 638
 639
 640 <h2>Archive</h2>
 641 <ul>
 642
 643 <li>2012
 644 <ul>
 645
 646 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 647
 648 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 649
 650 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 651
 652 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 653
 654 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 655
 656 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 657
 658 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 659
 660 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (1)</a></li>
 661
 662 </ul></li>
 663
 664 <li>2011
 665 <ul>
 666
 667 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 668
 669 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 670
 671 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 672
 673 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 674
 675 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 676
 677 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 678
 679 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 680
 681 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 682
 683 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 684
 685 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 686
 687 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 688
 689 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 690
 691 </ul></li>
 692
 693 <li>2010
 694 <ul>
 695
 696 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 697
 698 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 699
 700 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 701
 702 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 703
 704 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 705
 706 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 707
 708 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 709
 710 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 711
 712 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 713
 714 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 715
 716 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 717
 718 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 719
 720 </ul></li>
 721
 722 <li>2009
 723 <ul>
 724
 725 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 726
 727 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 728
 729 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 730
 731 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 732
 733 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 734
 735 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 736
 737 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 738
 739 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 740
 741 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 742
 743 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 744
 745 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 746
 747 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 748
 749 </ul></li>
 750
 751 <li>2008
 752 <ul>
 753
 754 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 755
 756 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 757
 758 </ul></li>
 759
 760 </ul>
 761
 762
 763
 764 <h2>Tags</h2>
 765 <ul>
 766
 767  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 768
 769  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 770
 771  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 772
 773  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
 774
 775  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
 776
 777  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 778
 779  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (55)</a></li>
 780
 781  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (110)</a></li>
 782
 783  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (9)</a></li>
 784
 785  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 786
 787  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (145)</a></li>
 788
 789  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (17)</a></li>
 790
 791  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 792
 793  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (6)</a></li>
 794
 795  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (30)</a></li>
 796
 797  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (16)</a></li>
 798
 799  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
 800
 801  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
 802
 803  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 804
 805  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (22)</a></li>
 806
 807  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (190)</a></li>
 808
 809  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (142)</a></li>
 810
 811  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (4)</a></li>
 812
 813  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 814
 815  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (34)</a></li>
 816
 817  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (48)</a></li>
 818
 819  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
 820
 821  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
 822
 823  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
 824
 825  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
 826
 827  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 828
 829  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
 830
 831  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
 832
 833  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
 834
 835  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 836
 837  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (1)</a></li>
 838
 839  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (36)</a></li>
 840
 841  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
 842
 843  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (4)</a></li>
 844
 845  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (10)</a></li>
 846
 847  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
 848
 849  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (32)</a></li>
 850
 851  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
 852
 853  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (25)</a></li>
 854
 855 </ul>
 856
 857
 858     </div>
 859     <p style="text-align: right">
 860  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
 861 </p>
 862
 863   </body>
 864 </html>