1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/' xmlns:
atom=
"http://www.w3.org/2005/Atom">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>Free software forced Microsoft to open Office (and don
't forget Officeshots)
</title>
11 <link>http://people.skolelinux.org/pere/blog/Free_software_forced_Microsoft_to_open_Office__and_don_t_forget_Officeshots_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Free_software_forced_Microsoft_to_open_Office__and_don_t_forget_Officeshots_.html
</guid>
13 <pubDate>Thu,
23 Aug
2012 14:
20:
00 +
0200</pubDate>
14 <description><p
>I came across a great comment from Simon Phipps today, about how
15 <a href=
"http://www.infoworld.com/d/open-source-software/how-microsoft-was-forced-open-office-
200233">Microsoft
16 have been forced to open Office
</a
>, and it made me remember and
17 revisit the great site
18 <a href=
"http://www.officeshots.org/
">officeshots
</a
> which allow you
19 to check out how different programs present the ODF file format. I
20 recommend both to those of my readers interested in ODF. :)
</p
>
25 <title>Half way there with translated docbook version of Free Culture
</title>
26 <link>http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</link>
27 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html
</guid>
28 <pubDate>Fri,
17 Aug
2012 21:
50:
00 +
0200</pubDate>
29 <description><p
>In my spare time, I currently work on a Norwegian
30 <a href=
"http://www.docbook.org/
">docbook
</a
> version of the
2004 book
31 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig,
32 to get a Norwegian text explaining the problems with the copyright law
33 I can give to my parents and others that are reluctant to read an
34 English book. It is a marvellous set of examples on how the ever
35 expanding copyright regulations hurt culture and society. When the
36 translation is done, I hope to find funding to print and ship a copy
37 to all the members of the Norwegian parliament, before they sit down
38 to debate the latest revisions to the Norwegian copyright law. This
40 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">called
41 for volunteers
</a
> to help me, and I have been able to secure the
42 valuable contribution from at least one other Norwegian.
</p
>
44 <p
>Two days ago, we finally broke the
50% mark. Then more than
50% of
45 the number of strings to translate (normally paragraphs, but also
46 titles and index entries are also counted). All parts from the
47 beginning up to and including chapter four is translated. So is
48 chapters six, seven and the conclusion. I created a graph to show the
51 <img width=
"80%
" align=
"center
" src=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png
">
53 <p
>The number of strings to translate increase as I insert the index
54 entries into the docbook. They were missing with the docbook version
55 I initially started with. There are still quite a few index entries
56 missing, but everyone starting with A, B, O, Z and Y are done. I
57 currently focus on completing the index entries, to get a complete
58 english version of the docbook source.
</p
>
60 <p
>There is still need for translators and people with docbook
61 knowledge, to be able to get a good looking book (I still struggle
62 with dblatex, xmlto and docbook-xsl) as well as to do the draft
63 translation and proof reading. And I would like the figures to be
64 redrawn as SVGs to make it easy to translate them. Any SVG master
65 around? I am sure there are some legal terms that are unfamiliar to
66 me. If you want to help, please get in touch, and check out the
67 project files currently available from
<a
68 href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
70 <p
>If you are curious what the translated book currently look like,
72 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true
">PDF
</a
>
74 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true
">EPUB
</a
>
75 are published on github. The HTML version is published as well, but
76 github hand it out with MIME type text/plain, confusing browsers, so I
77 saw no point in linking to that version.
</p
>
82 <title>Gratulerer med
19-årsdagen, Debian!
</title>
83 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
84 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
85 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
86 <description><p
>I dag fyller
87 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
88 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
89 si gratulerer med dagen, Debian!
</p
>
94 <title>Gladoppslag om Skolelinux i avisen Fremover
</title>
95 <link>http://people.skolelinux.org/pere/blog/Gladoppslag_om_Skolelinux_i_avisen_Fremover.html
</link>
96 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gladoppslag_om_Skolelinux_i_avisen_Fremover.html
</guid>
97 <pubDate>Wed,
15 Aug
2012 10:
20:
00 +
0200</pubDate>
98 <description><p
>I sommer hadde avisen
<a href=
"http://www.fremover.no/
">Fremover
</a
>
99 et flott oppslag om bruken av
100 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> på alle skolene
101 der. Artikkelen var på trykk på side
4 og
5 i papirutgaven
102 2012-
07-
23, men mangler dessverre i nettutgaven av avisen. Mine
103 henvendelser til avisen for å få artikkelen på nett har så langt ikke
104 vært vellykket.
</p
>
106 <p
>Artikkelen med tittelen
"Narvik kommune bruker gratisprogram i
107 skolen - Har spart millioner
", forteller om hvordan bruken av
108 Skolelinux er en stor suksess i Narvik siden det ble tatt i bruk i
109 2004. Her er noen fine sitater:
</p
>
112 "- Skolelinux har spart kommunen for store pengesummer, millionbeløp,
113 som de heller kan bruke på andre ting, sier IKT-konsulent Viggo
117 <p
>Avisen forteller at de har fått tilgang til beregninger som viser
118 at Narvik kommune har spart noe mellom
10 og
20 millioner kroner de
119 siste
8 årene på å bruke Skolelinux, og fortsetter:
</p
>
123 "Regnestykket tar høyde for sparte kostnader til lisenser som medfølger
124 de alternative operativsystemene, lavere driftskostnader og lengre
125 levetid på datautstyret. Totalt har Narvikskolen en maskinpark på
126 1600 maskiner fordelt på de
11 skolene fra Skjomen i sør til Bjerkvik
131 <p
>Viggo Fedreheim sier dette om hvor noe av gevinsten kommer fra:
</p
>
134 "- Vi kan gjenbruke gamle maskiner i skolen som er for dårlig andre
135 steder i kommunen der de ikke bruker Skolelinux. Levetiden på en
136 datamaskin blir
3-
5 år lenger med Skolelinux. Vi kaller det for
137 grønn IT, miljøvennlig IT.
"
140 <p
>Her er det mulighet for flere kommuner å få et godt IT-system på
141 skolene, hvis de er villige til å forsøke. De som ikke har kompetanse
142 innomhus kan kjøpe det fra en av de kommersielle leverandørene av
143 Skolelinux-tjenester, som
<a href=
"http://www.slxdrift.no/
">Skolelinux
144 Drift AS
</a
> (der jeg er styremedlem). Komplett liste er tilgjengelig
146 <a href=
"http://wiki.debian.org/DebianEdu/Help/ProfessionalHelp
">wikien
</a
>.
</p
>
148 <p
>Update
2012-
08-
16: Today I was allowed by Fremover to put the PDF I
149 received from them with a copy of the article on the Internet. It is
150 <a href=
"http://ftp.skolelinux.org/skolelinux/press/
2012-
07-
23-fremover-narvik.pdf
">now
151 available
</a
> in the Skolelinux press archive.
</p
>
156 <title>Notes on language codes for Norwegian docbook processing...
</title>
157 <link>http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</link>
158 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html
</guid>
159 <pubDate>Fri,
10 Aug
2012 21:
00:
00 +
0200</pubDate>
160 <description><p
>In
<a href=
"http://www.docbook.org/
">docbook
</a
> one can specify
161 the language used at the top, and the processing pipeline will use
162 this information to pick the correct translations for
'chapter
',
'see
163 also
',
'index
' etc. And for most languages used with docbook, I guess
164 this work just fine. For example a German user can start the document
165 with
&lt;book lang=
"de
"&gt;, and the document will show up with the
166 correct content with any of the docbook processors. This is not the
167 case for the language
168 <a href=
"http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
">I
169 am working with at the moment
</a
>, Norwegian Bokmål.
</p
>
171 <p
>For a while, I was confused about which language code to use,
172 because I was unable to find any language code that would work across
173 all tools. I am currently testing dblatex, xmlto, docbook-xsl, and
174 dbtoepub, and they do not handle Norwegian Bokmål the same way. Some
175 of them do not handle it at all.
</p
>
177 <p
>A bit of background information is probably needed to understand
178 this mess. Norwegian is not one, but two written variants. The
179 variants are Norwegian Nynorsk and Norwegian Bokmål. There are three
180 two letter language codes associated with these languages, Norwegian
181 is
'no
', Norwegian Nynorsk is
'nn
' and Norwegian Bokmål is
'nb
'.
182 Historically the
'no
' language code was used for Norwegian Bokmål, but
183 many years ago this was found to be å bad idea, and the recommendation
184 is to use the most specific language code instead, to avoid confusion.
185 In the transition period it is a good idea to make sure
'no
' was an
186 alias for
'nb
'.
</p
>
188 <p
>Back to docbook processing tools in Debian. The dblatex tool only
189 understand
'nn
'. There are translations for
'no
', but not
'nb
' (BTS
190 <a href=
"http://bugs.debian.org/
684391">#
684391</a
>), but due to a bug
191 (BTS
<a href=
"http://bugs.debian.org/
682936">#
682936</a
>) the
'no
'
192 language code is not recognised. The docbook-xsl tool chain only
193 recognise
'nn
' and
'nb
', but not
'no
'. The xmlto tool only recognise
194 'nn
' and
'nb
', but not
'no
'. The end result that there is no language
195 code I can use to get the docbook file working with all of these tools
196 at the same time. :(
</p
>
198 <p
>The correct solution is to use
&lt;book lang=
"nb
"&gt;, but it will
199 take time before that will work with all the free software docbook
200 processors. :(
</p
>
202 <p
>Oh, the joy of well integrated tools. :/
</p
>
207 <title>Best way to create a docbook book?
</title>
208 <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</link>
209 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html
</guid>
210 <pubDate>Tue,
31 Jul
2012 22:
00:
00 +
0200</pubDate>
211 <description><p
>I tried to send this text to the
212 <a href=
"https://lists.oasis-open.org/archives/docbook-apps/
">docbook-apps
213 mailing list at lists.oasis-open.org
</a
>, but it only accept messages
214 from subscribers and rejected my post, and I completely lack the
215 bandwidth required to subscribe to another mailing list, so instead I
216 try to post my message here and hope my blog readers can help me
219 <p
>I am quite new to docbook processing, and am climbing a steep
220 learning curve at the moment.
</p
>
222 <p
>To give you some background, I am working on a Norwegian
223 translation of the book Free Culture by Lawrence Lessig, and I use
224 docbook to handle the process. The files to build the book are
226 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
227 The book got around
400 pages with parts, images, footnotes, tables,
228 index entries etc, which has proven to be a challenge for the free
229 software docbook processors. My build platform is Debian GNU/Linux
232 <p
>I want to build PDF, EPUB and HTML version of the book, and have
233 tried different tool chains to do the conversion from docbook to these
234 formats. I am currently focusing on the PDF version, and have a few
239 <li
>Using dblatex, the
&lt;part
&gt; handling is not the way I want to,
240 as
&lt;/part
&gt; do not really end the
&lt;part
&gt;. (See
241 <a href=
"http://bugs.debian.org/
683166">BTS report #
683166</a
>), the
242 xetex backend (needed to process UTF-
8) give incorrect hyphens in
243 index references spanning several pages (See
244 <a href=
"http://bugs.debian.org/
682901">BTS report #
682901</a
>), and
245 I am unable to get the norwegian template texts (See
246 <a href=
"http://bugs.debian.org/
682936">BTS report #
682936</a
>).
</li
>
248 <li
>Using straight xmlto fail with some latex error (See
249 <a href=
"http://bugs.debian.org/
683163">BTS report
250 #
683163</a
>).
</li
>
252 <li
>Using xmlto with the fop backend fail to handle images (do not
253 show up in the PDF), fail to handle a long footnote (overlap
254 footnote and text body, see
255 <a href=
"http://bugs.debian.org/
683197">BTS report #
683197</a
>), and
256 fail to create a correct index (some lack page ref, and the page
257 refs listed are not right).
</li
>
259 <li
>Using xmlto with the dblatex backend behave like dblatex.
</li
>
261 <li
>Using docbook-xls with xsltproc + fop have the same footnote and
262 index problems the xmlto + fop processing.
</li
>
266 <p
>So I wonder, what would be the best way to create the PDF version
267 of this book? Are some of the bugs found above solved in new or
268 experimental versions of some docbook tool chain?
</p
>
270 <p
>What about HTML and EPUB versions?
</p
>
275 <title>OOXML og standardisering
</title>
276 <link>http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html
</link>
277 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html
</guid>
278 <pubDate>Wed,
25 Jul
2012 21:
10:
00 +
0200</pubDate>
279 <description><p
>DIFI har
280 <a href=
"http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html
">en
281 høring gående
</a
> om ny versjon av statens standardkatalog, med frist
282 2012-
09-
30, der det foreslås å fjerne ODF fra katalogen og ta inn ISO
283 OOXML. I den anledning minnes jeg
284 <a href=
"http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf
">notatet
285 FAD skrev
</a
> da versjon
2 av standardkatalogen var under
286 utarbeidelse, da FAD og DIFI fortsatt forsto poenget med og verdien av
287 frie og åpne standarder.
</p
>
289 <p
>Det er mange som tror at OOXML er ett spesifikt format, men det
290 brukes ofte som fellesbetegnelse for både formatet spesifisert av
291 ECMA, ISO, og formatet produsert av Microsoft Office (aka docx), som
292 dessverre ikke er det samme formatet. Fra en av de som implementerte
293 støtte for docx-formatet i KDE fikk jeg høre at ISO-spesifikasjonen
294 var en nyttig referanse, men at det var mange avvik som gjorde at en
295 ikke kunne gå ut ifra at Microsoft Office produserte dokumenter i
296 henhold til ISO-spesifikasjonen.
</p
>
298 <p
>ISOs OOXML-spesifikasjon har (eller hadde, usikker på om
299 kommentaren er oppdatert) i følge
300 <a href=
"http://surguy.net/articles/ooxml-validation-and-technical-review.xml
">Inigo
301 Surguy
</a
> feil i mer enn
10% av eksemplene, noe som i tillegg gjør
302 det vanskelig å bruke spesifikasjonen til å implementere støtte for
303 ISO OOXML. Jeg har ingen erfaring med å validere OOXML-dokumenter
305 <a href=
"http://www.microsoft.com/en-us/download/details.aspx?id=
5124">Microsoft
306 har laget en validator
</a
> som jeg ikke kan teste da den kun er
307 tilgjengelig på MS Windows. Finner også en annen kalt
308 <a href=
"http://code.google.com/p/officeotron/
">Office-O-Tron
</A
> som
309 er oppdatert i fjor. Lurer på om de validerer at dokumenter er i
310 formatet til Microsoft office, eller om de validerer at de er i
311 henhold til formatene spesifisert av ECMA og ISO. Det hadde også vært
312 interessant å se om docx-dokumentene publisert av det offentlige er
313 gyldige ISO OOXML-dokumenter.
</p
>
318 <title>Free Culture in Norwegian -
5 chapters done,
74 percent left to do
</title>
319 <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</link>
320 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html
</guid>
321 <pubDate>Sat,
21 Jul
2012 20:
00:
00 +
0200</pubDate>
322 <description><p
>I reported earlier that I am working on
323 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">a
324 norwegian version
</a
> of the book
325 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig.
326 Progress is good, and yesterday I got a major contribution from Anders
327 Hagen Jarmund completing chapter six. The source files as well as a
328 PDF and EPUB version of this book are available from
329 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
331 <p
>I am happy to report that the draft for the first two chapters
332 (preface, introduction) is complete, and three other chapters are also
333 completely translated. This completes
26 percent of the number of
334 strings (equivalent to paragraphs) in the book, and there is thus
74
335 percent left to translate. A graph of the progress is present at the
336 bottom of the github project page. There is still room for more
337 contributors. Get in touch or send github pull requests with fixes if
338 you got time and are willing to help make this book make it to
341 <p
>The book translation framework could also be a good basis for other
342 translations, if you want the book to be available in your
348 <title>Tips for å bli med i Skolelinux-prosjektet (som faktisk er aktivt)
</title>
349 <link>http://people.skolelinux.org/pere/blog/Tips_for___bli_med_i_Skolelinux_prosjektet__som_faktisk_er_aktivt_.html
</link>
350 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Tips_for___bli_med_i_Skolelinux_prosjektet__som_faktisk_er_aktivt_.html
</guid>
351 <pubDate>Thu,
19 Jul
2012 20:
30:
00 +
0200</pubDate>
352 <description><p
>Jeg fikk nettopp spørsmål på epost om Skolelinux-prosjektet lever
353 fra en som var interessert i å bidra, og måtte jo konstatere at i og
354 med at spørsmålet ble stilt har prosjektet ikke lyktes med å formidle
355 sin aktivitet. Her er det jeg svarte:
</p
>
357 <p
><blockquote
>
358 <p
>Jada,
<a href=
"http://www.skolelinux.org/
">Skolelinux-prosjektet
</a
>
359 lever, men det meste av utvikling foregår nå under paraplyen
360 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> som er det
361 internasjonale navnet på prosjektet. Dugnaden i Norge organiseres av
363 <a href=
"http://www.friprogramvareiskolen.no/
">Fri programvare i
364 Skolen
</a
>, og det finnes minst ett selskap som selger kommersiell
365 support på løsningen (
<a href=
"http://www.slxdrift.no/
">Skolelinux
366 Drift AS
</a
>, der jeg er styremedlem). Anbefaler at du melder deg på
368 <a href=
"http://lists.debian.org/debian-edu/
">debian-edu@lists.debian.org
</a
>
369 (og debian-edu-announce) og
370 <a href=
"http://medlem.friprogramvareiskolen.no/
">melder deg inn i
371 foreningen
</a
> for å få beskjed om aktivitet som planlegges. Det
373 <a href=
"http://www.friprogramvareiskolen.no/Gathering
">utviklersamlinger
374 i august
</a
> og utover høsten.
</p
>
376 <p
>Bidra gjerne med å spre ordet om Skolelinux. Det er alt for få som
377 bidrar til pressedekning, bloggposter, twittermeldinger, etc. :)
</p
>
379 <p
>Jeg antar du har funnet
380 <a href=
"http://people.skolelinux.org/pere/blog/tags/intervju/
">bloggserien
381 min med intervjuer
</a
>. Det er antagelig også interessant for deg å
382 følge med på
<a href=
"http://planet.skolelinux.org/
">Planet
383 Skolelinux
</a
>.
</p
>
385 <p
>Hm, jeg burde vel blogge alle disse lenkene slik at de blir enklere
387 </blockquote
></p
>
388 <p
>Herved gjort. :)
</p
>
393 <title>Call for help from docbook expert to tag Free Culture by Lawrence Lessig
</title>
394 <link>http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</link>
395 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html
</guid>
396 <pubDate>Mon,
16 Jul
2012 22:
50:
00 +
0200</pubDate>
397 <description><p
>I am currently working on a
398 <a href=
"http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html
">project
399 to translate
</a
> the book
400 <a href=
"http://free-culture.cc/
">Free Culture
</a
> by Lawrence Lessig
401 to Norwegian. And the source we base our translation on is the
402 <a href=
"http://en.wikipedia.org/wiki/DocBook
">docbook
</a
> version, to
403 allow us to use po4a and .po files to handle the translation, and for
404 this to work well the docbook source document need to be properly
405 tagged. The source files of this project is available from
406 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">github
</a
>.
</p
>
408 <p
>The problem is that the docbook source have flaws, and we have
409 no-one involved in the project that is a docbook expert. Is there a
410 docbook expert somewhere that is interested in helping us create a
411 well tagged docbook version of the book, and adjust our build process
412 for the PDF, EPUB and HTML version of the book? This will provide a
413 well tagged English version (our source document), and make it a lot
414 easier for us to create a good Norwegian version. If you can and want
415 to help, please get in touch with me or fork the github project and
416 send pull requests with fixes. :)
</p
>