+ <title>Change the font, save the world (and save some money in the process)</title>
+ <link>http://people.skolelinux.org/pere/blog/Change_the_font__save_the_world__and_save_some_money_in_the_process_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Change_the_font__save_the_world__and_save_some_money_in_the_process_.html</guid>
+ <pubDate>Tue, 26 Mar 2013 15:10:00 +0100</pubDate>
+ <description><p>Would you like to help the environment and save money at the same
+time, without much sacrifice? A small step could be to change the
+font you use when printing.</p>
+
+<p>Three years ago,
+<a href="http://arstechnica.com/business/2010/04/last-year-printer-comparison-website/">Ars
+Technica</a> reported how the University of Wisconsin-Green Bay
+changed their default front from
+<a href="http://en.wikipedia.org/wiki/Arial">Arial</a> to
+<a href="http://en.wikipedia.org/wiki/Century_Gothic">Century
+Gothic</a> to save money. The Century Gothic font uses 30% less toner
+than Arial to print the same text. In other word, you could cut your
+toner costs by 30% (or actually, increase your toner supply life time
+by more than 30%), by simply changing the default font used in your
+prints.</p>
+
+<p>But it is not quite obvious how much one will safe by switching.
+The University of Wisconsin-Green Bay said it used $100,000 per year
+on ink and toner cartridges, according to
+<a href="http://www.twincities.com/ci_14833097">a report from
+TwinCities.com</a>, and expected to save between $5,000 and $10,000
+per year by asking staff and students to use a different font. Not
+all PDFs and documents are created internally, and those from external
+sources will most likely still use a different font. Also, the
+Century Gothic font is slightly wider than Arial, and thus might use
+more sheets of paper to print the same text, so the total saving
+depend on the documents printed.</p>
+
+<p>But it is definitely something to consider, if you want to reduce
+the amount of trash, decrease the amount of toner used in the world,
+and save some money in the process.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Typesetting a short story using docbook for PDF, HTML and EPUB</title>
+ <link>http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Typesetting_a_short_story_using_docbook_for_PDF__HTML_and_EPUB.html</guid>
+ <pubDate>Sun, 24 Mar 2013 17:30:00 +0100</pubDate>
+ <description><p>A few days ago, during a discussion in
+<a href="http://www.efn.no/">EFN</a> about interesting books to read
+about copyright and the data retention directive, a suggestion to read
+the 1968 short story Kodémus by
+<a href="http://web2.gyldendal.no/toraage/">Tore Åge Bringsværd</a>
+came up. The text was only available in old paper books, and thus not
+easily available for current and future generations. Some of the
+people participating in the discussion contacted the author, and
+reported back 2013-03-19 that the author was OK with releasing the
+short story using a <a href="http://www.creativecommons.org/">Creative
+Commons</a> license. The text was quickly scanned and OCR-ed, and we
+were ready to start on the editing and typesetting.</p>
+
+<p>As I already had some experience formatting text in my project to
+provide a Norwegian version of the Free Culture book by Lawrence
+Lessig, I chipped in and set up a
+<a href="http://www.docbook.org/">DocBook</a> processing framework to
+generate PDF, HTML and EPUB version of the short story. The tools to
+transform DocBook to different formats are already in my Linux
+distribution of choice, <a href="http://www.debian.org/">Debian</a>, so
+all I had to do was to use the
+<a href="http://dblatex.sourceforge.net/">dblatex</a>,
+<a href="http://docbook.sourceforge.net/release/xsl/current/epub/README">dbtoepub</a>
+and <a href="https://fedorahosted.org/xmlto/">xmlto</a> tools to do the
+conversion. After a few days, we decided to replace dblatex with
+xsltproc/fop (aka
+<a href="http://wiki.docbook.org/DocBookXslStylesheets">docbook-xsl</a>),
+to get the copyright information to show up in the PDF and to get a
+nicer &lt;variablelist&gt; typesetting, but that is just a minor
+technical detail.</p>
+
+<p>There were a few challenges, of course. We want to typeset the
+short story to look like the original, and that require fairly good
+control over the layout. The original short story have three
+parts/scenes separated by a single horizontally centred star (*), and
+the paragraphs do not contain only flowing text, but dialogs and text
+that started on a new line in the middle of the paragraph.</p>
+
+<p>I initially solved the first challenge by using a paragraph with a
+single star in it, ie &lt;para&gt;*&lt;/para&gt;, but it made sure a
+placeholder indicated where the scene shifted. This did not look too
+good without the centring. The next approach was to create a new
+preprocessor directive &lt;?newscene?&gt;, mapping to "&lt;hr/&gt;"
+for HTML and "&lt;fo:block text-align="center"&gt;&lt;fo:leader
+leader-pattern="rule" rule-thickness="0.5pt"/&gt;&lt;/fo:block&gt;"
+for FO/PDF output (did not try to implement this in dblatex, as we had
+switched at this time). The HTML XSL file looked like this:</p>
+
+<p><blockquote><pre>
+&lt;?xml version='1.0'?&gt;
+&lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'&gt;
+ &lt;xsl:template match="processing-instruction('newscene')"&gt;
+ &lt;hr/&gt;
+ &lt;/xsl:template&gt;
+&lt;/xsl:stylesheet&gt;
+</pre></blockquote></p>
+
+<p>And the FO/PDF XSL file looked like this:</p>
+
+<p><blockquote><pre>
+&lt;?xml version='1.0'?&gt;
+&lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'&gt;
+ &lt;xsl:template match="processing-instruction('newscene')"&gt;
+ &lt;fo:block text-align="center"&gt;
+ &lt;fo:leader leader-pattern="rule" rule-thickness="0.5pt"/&gt;
+ &lt;/fo:block&gt;
+ &lt;/xsl:template&gt;
+&lt;/xsl:stylesheet&gt;
+</pre></blockquote></p>
+
+<p>Finally, I came across the &lt;bridgehead&gt; tag, which seem to be
+a good fit for the task at hand, and I replaced &lt;?newscene?&gt;
+with &lt;bridgehead&gt;*&lt;/bridgehead&gt;. It isn't centred, but we
+can fix it with some XSL rule if the current visual layout isn't
+enough.</p>
+
+<p>I did not find a good DocBook compliant way to solve the
+linebreak/paragraph challenge, so I ended up creating a new processor
+directive &lt;?linebreak?&gt;, mapping to &lt;br/&gt; in HTML, and
+&lt;fo:block/&gt; in FO/PDF. I suspect there are better ways to do
+this, and welcome ideas and patches on github. The HTML XSL file now
+look like this:</p>
+
+<p><blockquote><pre>
+&lt;?xml version='1.0'?&gt;
+&lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'&gt;
+ &lt;xsl:template match="processing-instruction('linebreak)"&gt;
+ &lt;br/&gt;
+ &lt;/xsl:template&gt;
+&lt;/xsl:stylesheet&gt;
+</pre></blockquote></p>
+
+<p>And the FO/PDF XSL file looked like this:</p>
+
+<p><blockquote><pre>
+&lt;?xml version='1.0'?&gt;
+&lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'
+ xmlns:fo="http://www.w3.org/1999/XSL/Format"&gt;
+ &lt;xsl:template match="processing-instruction('linebreak)"&gt;
+ &lt;fo:block/&gt;
+ &lt;/xsl:template&gt;
+&lt;/xsl:stylesheet&gt;
+</pre></blockquote></p>
+
+<p>One unsolved challenge is our wish to expose different ISBN numbers
+per publication format, while keeping all of them in some conditional
+structure in the DocBook source. No idea how to do this, so we ended
+up listing all the ISBN numbers next to their format in the colophon
+page.</p>
+
+<p>If you want to check out the finished result, check out the
+<a href="https://github.com/sickel/kodemus">source repository at
+github</a>
+(<a href="https://github.com/EFN/kodemus">future/new/official
+repository</a>). We expect it to be ready and announced in a few
+days.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Regjeringen, FAD og DIFI går inn for å fjerne ODF som obligatorisk standard i det offentlige</title>
+ <link>http://people.skolelinux.org/pere/blog/Regjeringen__FAD_og_DIFI_g_r_inn_for___fjerne_ODF_som_obligatorisk_standard_i_det_offentlige.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Regjeringen__FAD_og_DIFI_g_r_inn_for___fjerne_ODF_som_obligatorisk_standard_i_det_offentlige.html</guid>
+ <pubDate>Mon, 18 Mar 2013 21:10:00 +0100</pubDate>
+ <description><p>I
+<a href="http://standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning">siste
+høring</a> om
+<a href="http://standard.difi.no/forvaltningsstandarder">referansekatalogen
+for IT-standarder i offentlig sektor</a>, med høringsfrist 2012-09-30
+(DIFI-sak 2012/498), ble det foreslått å fjerne ODF som obligatorisk
+standard når en publiserte dokumenter som skulle kunne redigeres
+videre av mottaker. NUUG og andre protesterte på forslaget, som er et
+langt steg tilbake når det gjelder å sikre like rettigheter for alle
+når en kommuniserer med det offentlige. For noen dager siden ble jeg
+oppmerksom på at Direktoratet for forvaltning og IKT (DIFI) og
+Fornyings-,administrasjons- og kirkedepartementet (FAD) har
+konkludert, og oversendt forslag til regjeringen i saken. FADs
+dokument
+<a href="http://www.oep.no/search/result.html?period=none&descType=both&caseNumber=2012%2F2168&senderType=both&documentType=all&list2=94&searchType=advanced&Search=S%C3%B8k+i+journaler">2012/2168</a>-8,
+«Utkast til endring av standardiseringsforskriften» datert 2013-02-06
+har følgende triste oppsummering fra høringen i saken:</p>
+
+<p><blockquote>
+Det kom noen innvendinger på forslaget om å fjerne ODF som
+obligatorisk standard for redigerbare dokumenter. Innvendingene har
+ikke blitt ilagt avgjørende vekt.
+</blockquote></p>
+
+<p>Ved å fjerne ODF som obligatorisk format ved publisering av
+redigerbare dokumenter setter en Norge tiår tilbake. Det som vil skje
+er at offentlige etater går tilbake til kun å publisere dokumenter på
+et av de mange formatene til Microsoft Office, og alle som ikke
+aksepterer bruksvilkårene til Microsoft eller ikke har råd til å bruke
+penger på å få tilgang til Microsoft Office må igjen basere seg på
+verktøy fra utviklerne som er avhengig av å reversutvikle disse
+formatene. I og med at ISO-spesifikasjonen for OOXML ikke komplett og
+korrekt spesifiserer formatene til MS Office (men er nyttige å titte i
+når en reversutvikler), er en tilbake til en situasjon der en ikke har
+<a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">en
+fri og åpen standard</a> å forholde seg til, men i stedet må springe
+etter Microsoft. Alle andre leverandører enn Microsoft vil dermed ha
+en seriøs ulempe. Det er som å fjerne krav om bruk av meter som
+måleenhet, og heretter aksepterer alle måleenheter som like gyldige,
+når en vet at den mest brukte enheten vil være armlengden til Steve
+Ballmer slik Microsoft måler den.</p>
+
+<p>Jeg er ikke sikker på om forslaget er vedtatt av regjeringen ennå.
+Kristian Bergem hos DIFI nevnte på et møte forrige tirsdag at han
+trodde det var vedtatt i statsråd 8. mars, men jeg har ikke klart å
+finne en skriftlig kilde på regjeringen.no som bekrefter dette.
+Kanskje det ennå ikke er for sent...</p>
+
+<p>Jeg ba i forrige uke om innsyn i dokument 6, 7 og 8 i FAD-saken, og
+har i dag fått innsyn i dokument 7 og 8. Ble nektet innsyn i
+dokumentet med tittelen «Oppsummering av høring om endringer i
+forskrift om IT-standarder i offentlig forvaltning» med hjemmel i
+off. lovens §15.1, så det er vanskelig å vite hvordan argumentene fra
+høringen ble mottatt og forstått av saksbehandleren hos DIFI. Lurer
+på hvordan jeg kan klage på at jeg ikke fikk se oppsummeringen. Fikk
+tre PDFer tilsendt fra FAD,
+<a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/20130115%20Notat%20FAD%20-%20EHF.pdf%20(L)(889185).pdf">Endring av underversjon i EHF</a>,
+<a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/Bakgrunnsnotat%20knyttet%20til%20versjon%20av%20EHF%20standarden%20i%20Forskrift%20om%20IT-standarder%20i%20offentlig%20sektor.pdf">Bakgrunnsnotat knyttet til versjon av EHF standarden i Forskrift om IT-standarder i offentlig sektor</a> og
+<a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/Utkast%20Kongelig%20resolusjon.docx%20(L)(898064).pdf">Utkast til endring av standardiseringsforskriften</a>, hvis du vil ta en titt.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Skolelinux 6 got a video review from Pcwizz</title>
+ <link>http://people.skolelinux.org/pere/blog/Skolelinux_6_got_a_video_review_from_Pcwizz.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Skolelinux_6_got_a_video_review_from_Pcwizz.html</guid>
+ <pubDate>Sun, 17 Mar 2013 10:30:00 +0100</pubDate>
+ <description><p>Via
+<a href="https://twitter.com/pcwizz/status/313044373262716930">twitter</a>
+I just discovered that <a href="http://pcwizz.net/">Pcwizz</a> have
+done a <a href="http://www.youtube.com/watch?v=wPzTZ61Pcuc">video
+review</a> on Youtube of <a href="http://www.skolelinux.org/">Skolelinux
+/ Debian Edu</a> version 6. He installed the standalone profile and
+the video show a walk-through of of the menu content, demonstration of
+a few programs and his view of our distribution.</p>
+
+<p>There is also some really nice quotes (transcribed by me, might
+have heard wrong). While looking thought the Graphics menu:</p>
projects / homepage.git / blobdiff