Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index c74f8a3c9e159040eef2d55dbab26371ea7360b1..bb18ddde2a2ee85696d373fc26b25966527c0ebf 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,30 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        

+       <item>
+               <title>Naturvernforbundet i Oslo bruker OpenStreetmap i sin kalender</title>
+               <link>http://people.skolelinux.org/pere/blog/Naturvernforbundet_i_Oslo_bruker_OpenStreetmap_i_sin_kalender.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Naturvernforbundet_i_Oslo_bruker_OpenStreetmap_i_sin_kalender.html</guid>
+                <pubDate>Sun, 16 Sep 2012 12:00:00 +0200</pubDate>
+               <description>&lt;p&gt;Veldig morsomt å se at
+&lt;a href=&quot;http://naturvernforbundet.no/noa/&quot;&gt;Naturvernforbundet Oslo og
+Akershus&lt;/a&gt; bruker kart fra
+&lt;a href=&quot;http://www.openstreetmap.no/&quot;&gt;OpenStreetmap.org&lt;a/&gt; i
+&lt;a href=&quot;http://naturvernforbundet.no/noa/bestill-markakalenderen-2013-article24039-1939.html&quot;&gt;sine
+kalendere&lt;/a&gt;.  Vidar Gundersen i kartgruppa
+&lt;a href=&quot;http://lists.nuug.no/pipermail/kart/2012-September/003696.html&quot;&gt;forteller
+på den norske epostlisten&lt;/a&gt; til prosjektet at hvert blad i
+kalenderen har et turforslag på baksiden, med kart fra OpenStreetmap.
+Tidligere kjøpte de visst kart fra kartverket, men nå slipper de
+det.&lt;/p&gt;
+
+&lt;p&gt;Denne nyheten synes jeg er fantastisk bra, og jeg håper de får
+følge av flere, slik at det potensielle og fryktede inntektstapet for
+kartverket ved frigjøring av kartdata blir mindre, og forhåpentligvis
+til slutt så lite at frykten for å frigjøre data overvinnes.&lt;/p&gt;
+</description>
+       </item>
+       

        <item>
                <title>IETF activity to standardise video codec</title>
                <link>http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</link>
        <item>
                <title>IETF activity to standardise video codec</title>
                <link>http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</link>


@@ -568,56 +592,5 @@ available&lt;/a&gt; in the Skolelinux press archive.&lt;/p&gt;
 </description>
        </item>
        
 </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>
-       

         </channel>
 </rss>
         </channel>
 </rss>