<?xml version="1.0" encoding="UTF-8"?>
<!-- name="generator" content="pyblosxom/1.4.1 7/27/2007" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
<channel>
<title>Блогчетање 14 Mar 2004</title>
<link>https://danilo.segan.org/blog</link>
<description>Данилово блогче</description>
<language>en</language>
<item>
  <title>xml2po 1.0.6</title>
  <link>https://danilo.segan.org/blog/gnome/xml2po-1-0-6</link>
  <description><![CDATA[
<p>I've just released another xml2po tarball from unstable development: <a href="http://kvota.net/hacks/xml2po/xml2po-1.0.6.tar.gz">version 1.0.6</a>. I'm pretty much satisfied with what I've got so far, and I think I'll probably stop adding features for a while, and concentrate on polishing it up. So, go try it <strong>NOW.</strong></p><p>
This is also a first version that features autoconf/automake install system and support for merging translator credits into output files for DocBook articles and Gnome Summaries.</p><p>
Auto* tools support proved to be easier than I thought (in part thanks to outdated <a href="http://sources.redhat.com/autobook/">Autobook</a>, and somewhat thanks to gnome-hello program.</p><p>
I've also introduced a couple of incompatible changes, in the hope that the program will be much clearer now.</p><p>
Shaun has already started a module gnome-doc-utils, and now we need to think of the best way to integrate xml2po into it, without making Python a hard dependency of gnome-doc-utils (because they contain stylesheets which are useful even if there's no Python in the system).  The catch here is that Yelp is going to depend on gnome-doc-utils, and since Yelp is a essential Gnome component, Gnome itself will depend on gnome-doc-utils.</p><p>
By extension, if gnome-doc-utils (with xml2po) starts depending on Python, entire Gnome would depend on Python as well. As you might guess, that's <em>not</em> going to happen (at least not soon).</p><p>
And all that brings a wild idea into my mind: rewrite intltool to use Python and libxml2, instead of the dreaded Perl and expat-based XML::Parser. With that move, we'd drop Perl as a dependency, and introduce Python. <strong>Lovely, isn't it?</strong></p>
]]></description>
</item>

</channel>
</rss>
