[homepage.git] / blog / tags / docbook / docbook.rss

<?xml version="1.0" encoding="utf-8"?>
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
        <channel>
                <title>Petter Reinholdtsen - Entries tagged docbook</title>
                <description>Entries tagged docbook</description>
                <link>http://people.skolelinux.org/pere/blog/</link>

        
        <item>
                <title>Typesetting DocBook footnotes as endnotes with dblatex</title>
                <link>http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html</guid>
                <pubDate>Thu, 16 Jul 2015 18:10:00 +0200</pubDate>
                <description>&lt;p&gt;I&#39;m still working on the Norwegian version of the
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture book by Lawrence
Lessig&lt;/a&gt;, and is now working on the final typesetting and layout.
One of the features I want to get the structure similar to the
original book is to typeset the footnotes as endnotes in the notes
chapter.  Based on the
&lt;a href=&quot;https://bugs.debian.org/685063&quot;&gt;feedback from the Debian
maintainer and the dblatex developer&lt;/a&gt;, I came up with this recipe I
would like to share with you.  The proposal was to create a new LaTeX
class file and add the LaTeX code there, but this is not always
practical, when I want to be able to replace the class using a make
file variable.  So my proposal misuses the latex.begindocument XSL
parameter value, to get a small fragment into the correct location in
the generated LaTeX File.&lt;/p&gt;

&lt;p&gt;First, decide where in the DocBook document to place the endnotes,
and add this text there:&lt;/p&gt;

&lt;pre&gt;
&amp;lt;?latex \theendnotes ?&amp;gt;
&lt;/pre&gt;

&lt;p&gt;Next, create a xsl stylesheet file dblatex-endnotes.xsl to add the
code needed to add the endnote instructions in the preamble of the
generated LaTeX document, with content like this:&lt;/p&gt;

&lt;pre&gt;
&amp;lt;?xml version=&#39;1.0&#39;?&amp;gt;
&amp;lt;xsl:stylesheet xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot; version=&#39;1.0&#39;&amp;gt;
  &amp;lt;xsl:param name=&quot;latex.begindocument&quot;&amp;gt;
    &amp;lt;xsl:text&amp;gt;
\usepackage{endnotes}
\let\footnote=\endnote
\def\enoteheading{\mbox{}\par\vskip-\baselineskip }
\begin{document}
    &amp;lt;/xsl:text&amp;gt;
  &amp;lt;/xsl:param&amp;gt;
&amp;lt;/xsl:stylesheet&amp;gt;
&lt;/pre&gt;

&lt;p&gt;Finally, load this xsl file when running dblatex, for example like
this:&lt;/p&gt;

&lt;pre&gt;
dblatex --xsl-user=dblatex-endnotes.xsl freeculture.nb.xml
&lt;/pre&gt;

&lt;p&gt;The end result can be seen on github, where
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;my
book project&lt;/a&gt; is located.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Proof reading the Norwegian translation of Free Culture by Lessig</title>
                <link>http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html</guid>
                <pubDate>Sat, 4 Apr 2015 09:30:00 +0200</pubDate>
                <description>&lt;p&gt;During eastern I had some time to continue working on the Norwegian
&lt;a href=&quot;http://www.docbook.org/&quot;&gt;docbook&lt;/a&gt; version of the 2004 book
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig.
At the moment I am proof reading the finished text, looking for typos,
inconsistent wordings and sentences that do not flow as they should.
I&#39;m more than two thirds done with the text, and welcome others to
check the text up to chapter 13.  The current status is available on the
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;
project pages.  You can also check out the 
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true&quot;&gt;PDF&lt;/a&gt;,
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true&quot;&gt;EPUB&lt;/a&gt;
and HTML version available in the
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive&quot;&gt;archive
directory&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Please report typos, bugs and improvements to the github project if
you find any.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>98.6 percent done with the Norwegian draft translation of Free Culture</title>
                <link>http://people.skolelinux.org/pere/blog/98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/98_6_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html</guid>
                <pubDate>Wed, 23 Jul 2014 22:40:00 +0200</pubDate>
                <description>&lt;p&gt;This summer I finally had time to continue working on the Norwegian
&lt;a href=&quot;http://www.docbook.org/&quot;&gt;docbook&lt;/a&gt; version of the 2004 book
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig,
to get a Norwegian text explaining the problems with todays copyright
law.  Yesterday, I finally completed translated the book text.  There
are still some foot/end notes left to translate, the colophon page
need to be rewritten, and a few words and phrases still need to be
translated, but the Norwegian text is ready for the first proof
reading. :) More spell checking is needed, and several illustrations
need to be cleaned up.  The work stopped up because I had to give
priority to other projects the last year, and the progress graph of
the translation show this very well:&lt;/p&gt;

&lt;p&gt;&lt;img width=&quot;80%&quot; align=&quot;center&quot; src=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png&quot;&gt;&lt;/p&gt;

&lt;p&gt;If you want to read the result, check out the 
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;
project pages and the
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true&quot;&gt;PDF&lt;/a&gt;,
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true&quot;&gt;EPUB&lt;/a&gt;
and HTML version available in the
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive&quot;&gt;archive
directory&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Please report typos, bugs and improvements to the github project if
you find any.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>From English wiki to translated PDF and epub via Docbook</title>
                <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
                <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
                <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
project&lt;/a&gt; provide an instruction manual for teachers, system
administrators and other users that contain useful tips for setting up
and maintaining a Debian Edu installation.  This text is about how the
text processing of this manual is handled in the project.&lt;/p&gt;

&lt;p&gt;One goal of the project is to provide information in the native
language of its users, and for this we need to handle translations.
But we also want to make sure each language contain the same
information, so for this we need a good way to keep the translations
in sync.  And we want it to be easy for our users to improve the
documentation, avoiding the need to learn special formats or tools to
contribute, and the obvious way to do this is to make it possible to
edit the documentation using a web browser.  We also want it to be
easy for translators to keep the translation up to date, and give them
help in figuring out what need to be translated. Here is the list of
tools and the process we have found trying to reach all these
goals.&lt;/p&gt;

&lt;p&gt;We maintain the authoritative source of our manual in the
&lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
wiki&lt;/a&gt;, as several wiki pages written in English.  It consist of one
front page with references to the different chapters, several pages
for each chapter, and finally one &quot;collection page&quot; gluing all the
chapters together into one large web page (aka
&lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
AllInOne page&lt;/a&gt;).  The AllInOne page is the one used for further
processing and translations.  Thanks to the fact that the
&lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
wiki.debian.org support exporting pages in
&lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
the list of pages to export using the raw version of the AllInOne
page, loop over each of them to generate a Docbook XML version of the
manual.  This process also download images and transform image
references to use the locally downloaded images.  The generated
Docbook XML files are slightly broken, so some post-processing is done
using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
a handfull of images.  The XML file can now be used to generate PDF, HTML
and epub versions of the English manual.  This is the basic step of
our process, making PDF (using dblatex), HTML (using xsltproc) and
epub (using dbtoepub) version from Docbook XML, and the resulting files
are placed in the debian-edu-doc-en binary package.&lt;/p&gt;

&lt;p&gt;But English documentation is not enough for us.  We want translated
documentation too, and we want to make it easy for translators to
track the English original.  For this we use the
&lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
which allow us to transform the English Docbook XML file into a
translation file (a .pot file), usable with the normal gettext based
translation tools used by those translating free software.  The pot
file is used to create and maintain translation files (several .po
files), which the translations update with the native language
translations of all titles, paragraphs and blocks of text in the
original.  The next step is combining the original English Docbook XML
and the translation file (say debian-edu-wheezy-manual.nb.po), to
create a translated Docbook XML file (in this case
debian-edu-wheezy-manual.nb.xml).  This translated (or partly
translated, if the translation is not complete) Docbook XML file can
then be used like the original to create a PDF, HTML and epub version
of the documentation.&lt;/p&gt;

&lt;p&gt;The translators use different tools to edit the .po files.  We
recommend using
&lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
while some use emacs and vi, others can use web based editors like
&lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
&lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;.  All we care about
is where the .po file end up, in our git repository.  Updated
translations can either be committed directly to git, or submitted as
&lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;One challenge is images, which both might need to be translated (if
they show translated user applications), and are needed in different
formats when creating PDF and HTML versions (epub is a HTML version in
this regard).  For this we transform the original PNG images to the
needed density and format during build, and have a way to provide
translated images by storing translated versions in
images/$LANGUAGECODE/.  I am a bit unsure about the details here.  The
package maintainers know more.&lt;/p&gt;

&lt;p&gt;If you wonder what the result look like, we provide
&lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
of the documentation packages on the web&lt;/a&gt;.  See for example the
&lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
PDF version&lt;/a&gt; or the
&lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
HTML version&lt;/a&gt;.  We do not yet build the epub version by default,
but perhaps it will be done in the future.&lt;/p&gt;

&lt;p&gt;To learn more, check out
&lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
debian-edu-doc package&lt;/a&gt;,
&lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
manual on the wiki&lt;/a&gt; and
&lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>90 percent done with the Norwegian draft translation of Free Culture</title>
                <link>http://people.skolelinux.org/pere/blog/90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html</guid>
                <pubDate>Fri, 2 Aug 2013 10:40:00 +0200</pubDate>
                <description>&lt;p&gt;It has been a while since my last update.  Since last summer, I
have worked on a Norwegian
&lt;a href=&quot;http://www.docbook.org/&quot;&gt;docbook&lt;/a&gt; version of the 2004 book
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig,
to get a Norwegian text explaining the problems with the copyright
law.  Yesterday, I finally broken the 90% mark, when counting the
number of strings to translate.  Due to real life constraints, I have
not had time to work on it since March, but when the summer broke out,
I found time to work on it again.  Still lots of work left, but the
first draft is nearing completion.  I created a graph to show the
progress of the translation:&lt;/p&gt;

&lt;p&gt;&lt;img width=&quot;80%&quot; align=&quot;center&quot; src=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png&quot;&gt;&lt;/p&gt;

&lt;p&gt;When the first draft is done, the translated text need to be
proof read, and the remaining formatting problems with images and SVG
drawings need to be fixed.  There are probably also some index entries
missing that need to be added.  This can be done by comparing the
index entries listed in the SiSU version of the book, or comparing the
English docbook version with the paper version.  Last, the colophon
page with ISBN numbers etc need to be wrapped up before the release is
done.  I should also figure out how to get correct Norwegian sorting
of the index pages.  All docbook tools I have tried so far (xmlto,
docbook-xsl, dblatex) get the order of symbols and the special
Norwegian letters ÆØÅ wrong.&lt;/p&gt;

&lt;p&gt;There is still need for translators and people with docbook
knowledge, to be able to get a good looking book (I still struggle
with dblatex, xmlto and docbook-xsl) as well as to do the draft
translation and proof reading.  And I would like the figures to be
redrawn as SVGs to make it easy to translate them.  Any SVG master
around?  There are also some legal terms that are unfamiliar to me.
If you want to help, please get in touch with me, and check out the
project files currently available from
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are curious what the translated book currently look like,
the updated
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true&quot;&gt;PDF&lt;/a&gt;
and
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true&quot;&gt;EPUB&lt;/a&gt;
are published on github.  The HTML version is published as well, but
github hand it out with MIME type text/plain, confusing browsers, so I
saw no point in linking to that version.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>EFN nyutgir novellen Kodémus av Tor Åge Bringsværd</title>
                <link>http://people.skolelinux.org/pere/blog/EFN_nyutgir_novellen_Kod_mus_av_Tor__ge_Bringsv_rd.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/EFN_nyutgir_novellen_Kod_mus_av_Tor__ge_Bringsv_rd.html</guid>
                <pubDate>Wed, 27 Mar 2013 09:50:00 +0100</pubDate>
                <description>&lt;p&gt;For noen dager siden nevnte jeg at vi jobbet med å typesette en
novelle med &lt;a href=&quot;http://www.docbook.org/&quot;&gt;DocBook&lt;/a&gt;.  I dag ble
utgivelsen annonsert med følgende pressemelding fra Elektronisk
Forpost Norge), som jeg gjengir i sin helhet:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;

&lt;p&gt;&lt;strong&gt;EFN nyutgir Kodémus:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tor Åge Bringsværd-novelle om IT og overvåkning fra
informasjonsteknologiens spedbarndom får nytt liv&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Elektronisk Forpost Norge (EFN) er veldig glad for anledningen til
å nyutgi Tor Åge Bringsværds novelle Kodémus i digitalt format for nye
(og gamle) generasjoner. Novellen ble skrevet så tidlig som vinteren
1968, og første gang trykt i novellesamlingen Probok på Gyldendal
samme år.&lt;/p&gt;

&lt;p&gt;Informasjonsteknologi spiller en sentral rolle i Kodémus, og det er
spennende å sammenligne beskrivelsen av IT fra 1968 med dagens IT i
2013. Forskjellene er mange -- men det er jammen likhetene også. Ikke
minst det at idag går jo nesten alle rundt med lillebrødre på seg!&lt;/p&gt;

&lt;p&gt;&quot;Riktignok er det ikke påbudt å ha mobil,&quot; sier Thomas Gramstad,
leder i EFN. &quot;Men vi holder på å lage et samfunn der det blir så
upraktisk eller tungvint å ikke ha det, at man i praksis ikke slipper
unna. Og disse lillebrødrene sladrer hele tiden til staten (og til
mange andre) om hvor vi er, hva vi gjør, hva vi bryr oss om, hva vi
liker...&quot;&lt;/p&gt;

&lt;p&gt;Det at Kodémus åpenbart er skrevet i en annen tid med en annen type
IT og likevel virker så relevant idag, er i seg selv et hardtslående
tankekors.&lt;/p&gt;

&lt;p&gt;Tross sitt IT-tema fantes ikke Kodémus i elektronisk form, og
frivillige i EFN har skannet inn, OCR-tolket og korrekturlest
novellen, og deretter kodet den i en rekke digitale formater.&lt;/p&gt;

&lt;p&gt;Forfatteren har gitt tillatelse til publisering av Kodémus under ny
lisens, og novellen utgis av EFN med en Creative Commons (CC)
fribrukslisens (nærmere bestemt lisensen CC-BY-NC-ND). For leserne
eller brukerne innebærer dette at de får en klar og standardisert
beskjed om hvilke rettigheter de har til å dele novellen videre med
andre. For forfatteren innebærer dette økt synlighet og
tilgjengelighet for verket, slik at det ikke blir glemt, da
søkemotorer og nettlesere inneholder egne søkevalg for CC-lisenser, og
mange brukere søker etter verk som de vet de kan dele og bruke på
lovlig vis.&lt;/p&gt;

&lt;p&gt;EFN oppfordrer andre forfattere om å gi ut sine gamle tekster med
en fribrukslisens, slik at tekstene ikke blir glemt og for å stimulere
lovlig deling på nettet. EFN kan være behjelpelig med digitalisering
og utlegging på nett, i den grad det finnes kapasitet blant EFNs
medlemmer til dette. Vi mener at nyutgivelser av tekster under frie
lisenser kan øke interessen rundt forfatterskapet, og vil gjerne bidra
til dette.&lt;/p&gt;

&lt;p&gt;EFN utgir og deler med dette en novelle fra den digitale
informasjonsteknologiens tidligste barndom. En novelle som fortsatt er
full av vitalitet og aktualitet, og som derfor kan bidra til, og gi
ettertanke i dagens debatter om IT, personvern, overvåkning og
individets frihet og integritet.&lt;/p&gt;

&lt;p&gt;Du finner novellen her:
&lt;br&gt;&lt;a href=&quot;http://efn.no/kodemus/&quot;&gt;http://efn.no/kodemus/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;i flere forskjellige formater, for ulike plattformer. Per idag
finnes novellen i disse formatene: EPUB, MOBI, XML, HTML, PDF og
txt. Det kan bli flere formater senere, og evt. frivillige
bidragsytere til dette er velkommen.&lt;/p&gt;

&lt;p&gt;Kontaktperson for denne pressemeldingen,&lt;/p&gt;

&lt;p&gt;Thomas Gramstad
&lt;br&gt;thomas@efn.no
&lt;br&gt;4817 6875&lt;/p&gt;

&lt;hr&gt;

&lt;p&gt;EFN arbeider for dine borgerrettigheter i IT-samfunnet, for
nettverks- og delingskultur, personvern og frihet fra overvåkning,
åpne standarder, brukerstyrt programvare, retten til å kopiere, og
styrking av det digitale sivilsamfunnet m.m.
&lt;br&gt;&lt;a href=&quot;http://efn.no/&quot;&gt;www.efn.no&lt;/a&gt;&lt;/p&gt;

&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;Jeg håper flere forfattere ser verdien av å gjøre kulturen
tilgjengelig for flere, og slår følge med Hr. Bringsværd i å gi ut
sine verker med bruksvilkår med færre bruksbegrensinger enn
opphavsretten legger opp til.  Selv om jeg gjerne skulle sett at han
hadde brukt en Creative Commons-lisens som tillot avledede verker og
kommersiell bruk.&lt;/p&gt;
</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>&lt;p&gt;A few days ago, during a discussion in
&lt;a href=&quot;http://www.efn.no/&quot;&gt;EFN&lt;/a&gt; about interesting books to read
about copyright and the data retention directive, a suggestion to read
the 1968 short story Kodémus by
&lt;a href=&quot;http://web2.gyldendal.no/toraage/&quot;&gt;Tore Åge Bringsværd&lt;/a&gt;
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 &lt;a href=&quot;http://www.creativecommons.org/&quot;&gt;Creative
Commons&lt;/a&gt; license.  The text was quickly scanned and OCR-ed, and we
were ready to start on the editing and typesetting.&lt;/p&gt;

&lt;p&gt;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
&lt;a href=&quot;http://www.docbook.org/&quot;&gt;DocBook&lt;/a&gt; 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, &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;, so
all I had to do was to use the
&lt;a href=&quot;http://dblatex.sourceforge.net/&quot;&gt;dblatex&lt;/a&gt;,
&lt;a href=&quot;http://docbook.sourceforge.net/release/xsl/current/epub/README&quot;&gt;dbtoepub&lt;/a&gt;
and &lt;a href=&quot;https://fedorahosted.org/xmlto/&quot;&gt;xmlto&lt;/a&gt; tools to do the
conversion.  After a few days, we decided to replace dblatex with
xsltproc/fop (aka
&lt;a href=&quot;http://wiki.docbook.org/DocBookXslStylesheets&quot;&gt;docbook-xsl&lt;/a&gt;),
to get the copyright information to show up in the PDF and to get a
nicer &amp;lt;variablelist&amp;gt; typesetting, but that is just a minor
technical detail.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;I initially solved the first challenge by using a paragraph with a
single star in it, ie &amp;lt;para&amp;gt;*&amp;lt;/para&amp;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 &amp;lt;?newscene?&amp;gt;, mapping to &quot;&amp;lt;hr/&amp;gt;&quot;
for HTML and &quot;&amp;lt;fo:block text-align=&quot;center&quot;&amp;gt;&amp;lt;fo:leader
leader-pattern=&quot;rule&quot; rule-thickness=&quot;0.5pt&quot;/&amp;gt;&amp;lt;/fo:block&amp;gt;&quot;
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:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
&amp;lt;?xml version=&#39;1.0&#39;?&amp;gt; 
&amp;lt;xsl:stylesheet xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot; version=&#39;1.0&#39;&amp;gt;
  &amp;lt;xsl:template match=&quot;processing-instruction(&#39;newscene&#39;)&quot;&amp;gt;
    &amp;lt;hr/&amp;gt;
  &amp;lt;/xsl:template&amp;gt;
&amp;lt;/xsl:stylesheet&amp;gt; 
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;And the FO/PDF XSL file looked like this:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
&amp;lt;?xml version=&#39;1.0&#39;?&amp;gt; 
&amp;lt;xsl:stylesheet xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot; version=&#39;1.0&#39;&amp;gt;
  &amp;lt;xsl:template match=&quot;processing-instruction(&#39;newscene&#39;)&quot;&amp;gt;
    &amp;lt;fo:block text-align=&quot;center&quot;&amp;gt;
      &amp;lt;fo:leader leader-pattern=&quot;rule&quot; rule-thickness=&quot;0.5pt&quot;/&amp;gt;
    &amp;lt;/fo:block&amp;gt;
  &amp;lt;/xsl:template&amp;gt;
&amp;lt;/xsl:stylesheet&amp;gt; 
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;Finally, I came across the &amp;lt;bridgehead&amp;gt; tag, which seem to be
a good fit for the task at hand, and I replaced &amp;lt;?newscene?&amp;gt;
with &amp;lt;bridgehead&amp;gt;*&amp;lt;/bridgehead&amp;gt;.  It isn&#39;t centred, but we
can fix it with some XSL rule if the current visual layout isn&#39;t
enough.&lt;/p&gt;

&lt;p&gt;I did not find a good DocBook compliant way to solve the
linebreak/paragraph challenge, so I ended up creating a new processor
directive &amp;lt;?linebreak?&amp;gt;, mapping to &amp;lt;br/&amp;gt; in HTML, and
&amp;lt;fo:block/&amp;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:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
&amp;lt;?xml version=&#39;1.0&#39;?&amp;gt; 
&amp;lt;xsl:stylesheet xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot; version=&#39;1.0&#39;&amp;gt;
  &amp;lt;xsl:template match=&quot;processing-instruction(&#39;linebreak)&quot;&amp;gt;
    &amp;lt;br/&amp;gt;
  &amp;lt;/xsl:template&amp;gt;
&amp;lt;/xsl:stylesheet&amp;gt; 
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;And the FO/PDF XSL file looked like this:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
&amp;lt;?xml version=&#39;1.0&#39;?&amp;gt; 
&amp;lt;xsl:stylesheet xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot; version=&#39;1.0&#39;
  xmlns:fo=&quot;http://www.w3.org/1999/XSL/Format&quot;&amp;gt;
  &amp;lt;xsl:template match=&quot;processing-instruction(&#39;linebreak)&quot;&amp;gt;
    &amp;lt;fo:block/&amp;gt;
  &amp;lt;/xsl:template&amp;gt;
&amp;lt;/xsl:stylesheet&amp;gt; 
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;If you want to check out the finished result, check out the
&lt;a href=&quot;https://github.com/sickel/kodemus&quot;&gt;source repository at
github&lt;/a&gt;
(&lt;a href=&quot;https://github.com/EFN/kodemus&quot;&gt;future/new/official
repository&lt;/a&gt;).  We expect it to be ready and announced in a few
days.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Seventy percent done with Norwegian docbook version of Free Culture</title>
                <link>http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Seventy_percent_done_with_Norwegian_docbook_version_of_Free_Culture.html</guid>
                <pubDate>Sun, 23 Sep 2012 09:30:00 +0200</pubDate>
                <description>&lt;p&gt;Since this summer, I have worked in my spare time on a Norwegian &lt;a
href=&quot;http://www.docbook.org/&quot;&gt;docbook&lt;/a&gt; version of the 2004 book &lt;a
href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig.
The reason is that this book is a great primer on what problems exist
in the current copyright laws, and I want it to be available also for
those that are reluctant do read an English book.

When I started, I 
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html&quot;&gt;called
for volunteers&lt;/a&gt; to help me, but too few have volunteered so far,
and progress is a bit slow.  Anyway, today I broken the 70 percent
mark for the first rough translation.  At the moment, less than 700
strings (paragraphs, index terms, titles) are left to translate.  With
my current progress of 10-20 strings per day, it will take a while to
complete the translation.  This graph show the updated progress:&lt;/p&gt;

&lt;img width=&quot;80%&quot; align=&quot;center&quot; src=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png&quot;&gt;

&lt;p&gt;Progress have slowed down lately due to family and work
commitments.  If you want to help, please get in touch, and check out
the project files currently available from
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are curious what the translated book currently look like,
the updated
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true&quot;&gt;PDF&lt;/a&gt;
and
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true&quot;&gt;EPUB&lt;/a&gt;
are published on github.  The HTML version is published as well, but
github hand it out with MIME type text/plain, confusing browsers, so I
saw no point in linking to that version.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Half way there with translated docbook version of Free Culture</title>
                <link>http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Half_way_there_with_translated_docbook_version_of_Free_Culture.html</guid>
                <pubDate>Fri, 17 Aug 2012 21:50:00 +0200</pubDate>
                <description>&lt;p&gt;In my spare time, I currently work on a Norwegian
&lt;a href=&quot;http://www.docbook.org/&quot;&gt;docbook&lt;/a&gt; version of the 2004 book
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig,
to get a Norwegian text explaining the problems with the copyright law
I can give to my parents and others that are reluctant to read an
English book.  It is a marvellous set of examples on how the ever
expanding copyright regulations hurt culture and society.  When the
translation is done, I hope to find funding to print and ship a copy
to all the members of the Norwegian parliament, before they sit down
to debate the latest revisions to the Norwegian copyright law.  This
summer I
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html&quot;&gt;called
for volunteers&lt;/a&gt; to help me, and I have been able to secure the
valuable contribution from at least one other Norwegian.&lt;/p&gt;

&lt;p&gt;Two days ago, we finally broke the 50% mark.  Then more than 50% of
the number of strings to translate (normally paragraphs, but also
titles and index entries are also counted).  All parts from the
beginning up to and including chapter four is translated.  So is
chapters six, seven and the conclusion.  I created a graph to show the
progress:&lt;/p&gt;

&lt;img width=&quot;80%&quot; align=&quot;center&quot; src=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/progress.png&quot;&gt;

&lt;p&gt;The number of strings to translate increase as I insert the index
entries into the docbook.  They were missing with the docbook version
I initially started with.  There are still quite a few index entries
missing, but everyone starting with A, B, O, Z and Y are done.  I
currently focus on completing the index entries, to get a complete
english version of the docbook source.&lt;/p&gt;

&lt;p&gt;There is still need for translators and people with docbook
knowledge, to be able to get a good looking book (I still struggle
with dblatex, xmlto and docbook-xsl) as well as to do the draft
translation and proof reading.  And I would like the figures to be
redrawn as SVGs to make it easy to translate them.  Any SVG master
around?  I am sure there are some legal terms that are unfamiliar to
me.  If you want to help, please get in touch, and check out the
project files currently available from &lt;a
href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are curious what the translated book currently look like,
the updated
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true&quot;&gt;PDF&lt;/a&gt;
and
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true&quot;&gt;EPUB&lt;/a&gt;
are published on github.  The HTML version is published as well, but
github hand it out with MIME type text/plain, confusing browsers, so I
saw no point in linking to that version.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Notes on language codes for Norwegian docbook processing...</title>
                <link>http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Notes_on_language_codes_for_Norwegian_docbook_processing___.html</guid>
                <pubDate>Fri, 10 Aug 2012 21:00:00 +0200</pubDate>
                <description>&lt;p&gt;In &lt;a href=&quot;http://www.docbook.org/&quot;&gt;docbook&lt;/a&gt; one can specify
the language used at the top, and the processing pipeline will use
this information to pick the correct translations for &#39;chapter&#39;, &#39;see
also&#39;, &#39;index&#39; etc.  And for most languages used with docbook, I guess
this work just fine.  For example a German user can start the document
with &amp;lt;book lang=&quot;de&quot;&amp;gt;, and the document will show up with the
correct content with any of the docbook processors.  This is not the
case for the language
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html&quot;&gt;I
am working with at the moment&lt;/a&gt;, Norwegian Bokmål.&lt;/p&gt;

&lt;p&gt;For a while, I was confused about which language code to use,
because I was unable to find any language code that would work across
all tools.  I am currently testing dblatex, xmlto, docbook-xsl, and
dbtoepub, and they do not handle Norwegian Bokmål the same way.  Some
of them do not handle it at all.&lt;/p&gt;

&lt;p&gt;A bit of background information is probably needed to understand
this mess.  Norwegian is not one, but two written variants.  The
variants are Norwegian Nynorsk and Norwegian Bokmål.  There are three
two letter language codes associated with these languages, Norwegian
is &#39;no&#39;, Norwegian Nynorsk is &#39;nn&#39; and Norwegian Bokmål is &#39;nb&#39;.
Historically the &#39;no&#39; language code was used for Norwegian Bokmål, but
many years ago this was found to be å bad idea, and the recommendation
is to use the most specific language code instead, to avoid confusion.
In the transition period it is a good idea to make sure &#39;no&#39; was an
alias for &#39;nb&#39;.&lt;/p&gt;

&lt;p&gt;Back to docbook processing tools in Debian.  The dblatex tool only
understand &#39;nn&#39;.  There are translations for &#39;no&#39;, but not &#39;nb&#39; (BTS
&lt;a href=&quot;http://bugs.debian.org/684391&quot;&gt;#684391&lt;/a&gt;), but due to a bug
(BTS &lt;a href=&quot;http://bugs.debian.org/682936&quot;&gt;#682936&lt;/a&gt;) the &#39;no&#39;
language code is not recognised.  The docbook-xsl tool chain only
recognise &#39;nn&#39; and &#39;nb&#39;, but not &#39;no&#39;.  The xmlto tool only recognise
&#39;nn&#39; and &#39;nb&#39;, but not &#39;no&#39;.  The end result that there is no language
code I can use to get the docbook file working with all of these tools
at the same time. :(&lt;/p&gt;

&lt;p&gt;The correct solution is to use &amp;lt;book lang=&quot;nb&quot;&amp;gt;, but it will
take time before that will work with all the free software docbook
processors. :(&lt;/p&gt;

&lt;p&gt;Oh, the joy of well integrated tools. :/&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Best way to create a docbook book?</title>
                <link>http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Best_way_to_create_a_docbook_book_.html</guid>
                <pubDate>Tue, 31 Jul 2012 22:00:00 +0200</pubDate>
                <description>&lt;p&gt;I tried to send this text to the
&lt;a href=&quot;https://lists.oasis-open.org/archives/docbook-apps/&quot;&gt;docbook-apps
mailing list at lists.oasis-open.org&lt;/a&gt;, but it only accept messages
from subscribers and rejected my post, and I completely lack the
bandwidth required to subscribe to another mailing list, so instead I
try to post my message here and hope my blog readers can help me
out.&lt;/p&gt;

&lt;p&gt;I am quite new to docbook processing, and am climbing a steep
learning curve at the moment.&lt;/p&gt;

&lt;p&gt;To give you some background, I am working on a Norwegian
translation of the book Free Culture by Lawrence Lessig, and I use
docbook to handle the process.  The files to build the book are
available from
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.
The book got around 400 pages with parts, images, footnotes, tables,
index entries etc, which has proven to be a challenge for the free
software docbook processors.  My build platform is Debian GNU/Linux
Squeeze.&lt;/p&gt;

&lt;p&gt;I want to build PDF, EPUB and HTML version of the book, and have
tried different tool chains to do the conversion from docbook to these
formats.  I am currently focusing on the PDF version, and have a few
problems.&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;Using dblatex, the &amp;lt;part&amp;gt; handling is not the way I want to,
   as &amp;lt;/part&amp;gt; do not really end the &amp;lt;part&amp;gt;. (See
   &lt;a href=&quot;http://bugs.debian.org/683166&quot;&gt;BTS report #683166&lt;/a&gt;), the
   xetex backend (needed to process UTF-8) give incorrect hyphens in
   index references spanning several pages (See
   &lt;a href=&quot;http://bugs.debian.org/682901&quot;&gt;BTS report #682901&lt;/a&gt;), and
   I am unable to get the norwegian template texts (See
   &lt;a href=&quot;http://bugs.debian.org/682936&quot;&gt;BTS report #682936&lt;/a&gt;).&lt;/li&gt;

&lt;li&gt;Using straight xmlto fail with some latex error (See
   &lt;a href=&quot;http://bugs.debian.org/683163&quot;&gt;BTS report
   #683163&lt;/a&gt;).&lt;/li&gt;

&lt;li&gt;Using xmlto with the fop backend fail to handle images (do not
   show up in the PDF), fail to handle a long footnote (overlap
   footnote and text body, see
   &lt;a href=&quot;http://bugs.debian.org/683197&quot;&gt;BTS report #683197&lt;/a&gt;), and
   fail to create a correct index (some lack page ref, and the page
   refs listed are not right).&lt;/li&gt;

&lt;li&gt;Using xmlto with the dblatex backend behave like dblatex.&lt;/li&gt;

&lt;li&gt;Using docbook-xls with xsltproc + fop have the same footnote and
   index problems the xmlto + fop processing.&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;So I wonder, what would be the best way to create the PDF version
of this book?  Are some of the bugs found above solved in new or
experimental versions of some docbook tool chain?&lt;/p&gt;

&lt;p&gt;What about HTML and EPUB versions?&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Free Culture in Norwegian - 5 chapters done, 74 percent left to do</title>
                <link>http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Free_Culture_in_Norwegian___5_chapters_done__74_percent_left_to_do.html</guid>
                <pubDate>Sat, 21 Jul 2012 20:00:00 +0200</pubDate>
                <description>&lt;p&gt;I reported earlier that I am working on
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html&quot;&gt;a
norwegian version&lt;/a&gt; of the book
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig.
Progress is good, and yesterday I got a major contribution from Anders
Hagen Jarmund completing chapter six.  The source files as well as a
PDF and EPUB version of this book are available from
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I am happy to report that the draft for the first two chapters
(preface, introduction) is complete, and three other chapters are also
completely translated.  This completes 26 percent of the number of
strings (equivalent to paragraphs) in the book, and there is thus 74
percent left to translate.  A graph of the progress is present at the
bottom of the github project page.  There is still room for more
contributors.  Get in touch or send github pull requests with fixes if
you got time and are willing to help make this book make it to
print. :)&lt;/p&gt;

&lt;p&gt;The book translation framework could also be a good basis for other
translations, if you want the book to be available in your
language.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Call for help from docbook expert to tag Free Culture by Lawrence Lessig</title>
                <link>http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Call_for_help_from_docbook_expert_to_tag_Free_Culture_by_Lawrence_Lessig.html</guid>
                <pubDate>Mon, 16 Jul 2012 22:50:00 +0200</pubDate>
                <description>&lt;p&gt;I am currently working on a
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html&quot;&gt;project
to translate&lt;/a&gt; the book
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; by Lawrence Lessig
to Norwegian.  And the source we base our translation on is the
&lt;a href=&quot;http://en.wikipedia.org/wiki/DocBook&quot;&gt;docbook&lt;/a&gt; version, to
allow us to use po4a and .po files to handle the translation, and for
this to work well the docbook source document need to be properly
tagged.  The source files of this project is available from
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The problem is that the docbook source have flaws, and we have
no-one involved in the project that is a docbook expert.  Is there a
docbook expert somewhere that is interested in helping us create a
well tagged docbook version of the book, and adjust our build process
for the PDF, EPUB and HTML version of the book?  This will provide a
well tagged English version (our source document), and make it a lot
easier for us to create a good Norwegian version.  If you can and want
to help, please get in touch with me or fork the github project and
send pull requests with fixes. :)&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Dugnad for å sende norsk versjon av Free Culture til stortingets representanter!</title>
                <link>http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Dugnad_for___sende_norsk_versjon_av_Free_Culture_til_stortingets_representanter_.html</guid>
                <pubDate>Wed, 11 Jul 2012 09:00:00 +0200</pubDate>
                <description>&lt;p&gt;Da opphavsrettsloven ble revidert i forrige runde rundt 2005, var
det skummelt å se hvor lite stortingsrepresentantene forsto hvordan
Internet påvirket folks forhold til kulturuttrykk, og min venn Vidar
og jeg spekulert på at det hadde kanskje vært fornuftig om samtlige
representanter fikk en norsk utgave av boken
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt; av Lawrence Lessig
som forklarte litt om problemstillingene.  Vi endte opp med å
prioritere utvikling i
&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;-prosjektet i
stedet, så den oversatte boken så aldri dagens lys.  Men i forrige uke
ble jeg inspirert til å ta opp tråden og se om det er mulig å få til
bokprosjektet denne gang, da det er tydelig at kulturdepartementet i
sitt nye forsøk på å gjøre opphavsrettsloven enda mer ubalansert til
fordel for forlag og store mediehus fortsatt trenger en annen vinkling
i debatten.&lt;/p&gt;

&lt;p&gt;Planen min er å oversette boka på dugnad, sette den opp for
trykking med en av de mange
&lt;a href=&quot;http://no.wikipedia.org/wiki/Trykk_på_forespørsel&quot;&gt;trykk på
forespørsel&lt;/a&gt;-tjenestene, skaffe sponsor til å finansiere trykking
til stortingsrepresentantene og alle som har bidratt med
oversettelser.  Kanskje vi også kan få en avtale med et forlag om
publisering når boka er ferdig?  Kommentarene til
&lt;a href=&quot;http://newth.net/eirik/2011/04/01/e-selvpublisering/&quot;&gt;Eirik
Newth&lt;/a&gt; og
&lt;a href=&quot;http://www.espen.com/norskblogg/archives/2008/09/erfaringer_med_publishing_on_demand.html&quot;&gt;Espen
Andersen&lt;/a&gt; om erfaringene med selvpublisering og trykk på
forespørsel er interessante og ikke avskrekkende, og jeg mistenker at
&lt;a href=&quot;http://www.lulu.com/&quot;&gt;Lulu&lt;/a&gt; er en grei leverandør av
trykketjenester til prosjektet.&lt;/p&gt;

&lt;p&gt;Jeg har satt opp
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;et
Github-prosjekt&lt;/a&gt; for a lage boken, basert på Docbook-utgaven jeg
fant fra Hans Schou.  Skolelinux har hatt byggesystem for å lage
oversatt HTML og PDF-utgave av Docbook-bøker i en årrekke, så jeg har
kopiert og utvidet dette oppsettet.  Originalteksten er i Docbook, og
oversettelsen gjøres i .po-filer med hjelp av vanlige
oversetterverktøy brukt i fri programvareverden.  Dernest tar
byggesystemet over og lager PDF og EPUB-utgave av den oversatte
teksten.  Resultatet kan ses i Github-prosjektet.  For å komme raskt
igang har jeg brukt maskinoversettelse av alle tekstbitene fra engelsk
til norsk, noe som grovoversatte ca. 1300 av de ca. 1700 tekstbitene
boken består av.  Jeg håper nå at flere kan bidra med å få
oversettelsen på plass, slik at teksten kan være klar i løpet av
høsten.  Når alt er oversatt må teksten gjennomgås for feil og
konsistent språk.  Totalt er det nok mange timer som trengs for å
gjennomføre oversettelsen.&lt;/p&gt;

&lt;p&gt;Økonomien i dette er ikke avskrekkende.  169
stortingsrepresentanter og nesten like mange varamedlemmer bør få
bøker, og estimert produduksjonskostnad for hver bok er rundt 6 EURO i
følge et raskt estimat fra Lulu.  Jeg vet ennå ikke hvor mange sider
det blir i størrelsen 5,5&quot; x 8.5&quot; (det er ca. 140 sider i A4-format),
så jeg gjettet på 400 sider.  Jeg tror originalutgaven har nesten 400
sider.  For 169*2 eksemplarer snakker vi om en trykkekostnad på
ca. 2000 EURO, dvs. ca 15 000 NOK.  Det burde være mulig å finne en
sponsor for å dekke en slik sum.  I tillegg kommer distribusjon og
porto, som antagelig kommer på like mye.&lt;/p&gt;

&lt;p&gt;Kan du bidra med oversettelse og docbook-typesetting?  Ta kontakt
og send patcher i github.  Jeg legger gjerne inn folk i prosjektet
slik at du kan oppdatere direkte.&lt;/p&gt;
</description>
        </item>
        
        </channel>
</rss>