<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>IETF activity to standardise video codec</title>
+ <link>http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IETF_activity_to_standardise_video_codec.html</guid>
+ <pubDate>Sat, 15 Sep 2012 20:00:00 +0200</pubDate>
+ <description><p>After the
+<a href="http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html">Opus
+codec made</a> it into <a href="http://www.ietf.org/">IETF</a> as
+<a href="http://tools.ietf.org/html/rfc6716">RFC 6716</a>, I had a look
+to see if there is any activity in IETF to standardise a video codec
+too, and I was happy to discover that there is some activity in this
+area. A non-"working group" mailing list
+<a href="https://www.ietf.org/mailman/listinfo/video-codec">video-codec</a>
+was
+<a href="http://ietf.10.n7.nabble.com/New-Non-WG-Mailing-List-video-codec-Video-codec-BoF-discussion-list-td119548.html">created 2012-08-20</a>. It is intended to discuss the topic and if a
+formal working group should be formed.</p>
+
+<p>I look forward to see how this plays out. There is already
+<a href="http://www.ietf.org/mail-archive/web/video-codec/current/msg00003.html">an
+email from someone</a> in the MPEG group at ISO asking people to
+participate in the ISO group. Given how ISO failed with OOXML and given
+that it so far (as far as I can remember) only have produced
+multimedia formats in the past requiring royalty payments, I suspect
+joining the ISO group would be a complete waste of time, but I am not
+involved in any codec work and my opinion will not matter much.</p>
+
+<p>If one of my readers is involved with codec work, I hope she will
+join this work to standardise a royalty free video codec within
+IETF.</p>
+</description>
+ </item>
+
<item>
<title>IETF standardize its first multimedia codec: Opus</title>
<link>http://people.skolelinux.org/pere/blog/IETF_standardize_its_first_multimedia_codec__Opus.html</link>
</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><p>I tried to send this text to the
-<a href="https://lists.oasis-open.org/archives/docbook-apps/">docbook-apps
-mailing list at lists.oasis-open.org</a>, 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.</p>
-
-<p>I am quite new to docbook processing, and am climbing a steep
-learning curve at the moment.</p>
-
-<p>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
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>.
-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.</p>
-
-<p>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.</p>
-
-<ul>
-
-<li>Using dblatex, the &lt;part&gt; handling is not the way I want to,
- as &lt;/part&gt; do not really end the &lt;part&gt;. (See
- <a href="http://bugs.debian.org/683166">BTS report #683166</a>), the
- xetex backend (needed to process UTF-8) give incorrect hyphens in
- index references spanning several pages (See
- <a href="http://bugs.debian.org/682901">BTS report #682901</a>), and
- I am unable to get the norwegian template texts (See
- <a href="http://bugs.debian.org/682936">BTS report #682936</a>).</li>
-
-<li>Using straight xmlto fail with some latex error (See
- <a href="http://bugs.debian.org/683163">BTS report
- #683163</a>).</li>
-
-<li>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
- <a href="http://bugs.debian.org/683197">BTS report #683197</a>), and
- fail to create a correct index (some lack page ref, and the page
- refs listed are not right).</li>
-
-<li>Using xmlto with the dblatex backend behave like dblatex.</li>
-
-<li>Using docbook-xls with xsltproc + fop have the same footnote and
- index problems the xmlto + fop processing.</li>
-
-</ul>
-
-<p>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?</p>
-
-<p>What about HTML and EPUB versions?</p>
-</description>
- </item>
-
</channel>
</rss>
projects / homepage.git / blobdiff