<?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>Блогчетање   </title>
<link>https://danilo.segan.org/blog</link>
<description>Данилово блогче</description>
<language>en</language>
<item>
  <title>More xml2po bug-fixing: call for test cases</title>
  <link>https://danilo.segan.org/blog/gnome/more-xml2po-bugfixing</link>
  <description><![CDATA[
<p>I've fixed all known xml2po bugs (at least all bugs reported in <a
href="http://bugzilla.gnome.org/buglist.cgi?product=xml2po&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED">Bugzilla</a>;
I know of at least one other bug [look at TODO] which I only partially
fixed :).</p>

<p>But, this would be no good if I didn't actually start developing
regression tests.  I'm not planning on distributing them, but I've put
them in 
<a href="http://cvs.gnome.org/viewcvs/gnome-doc-utils/xml2po/tests">CVS</a>
so anyone can look at them and try them.</p>

<p>Since it's sometimes hard to come up with decent examples, I'd like
to have a couple of more complex XML (preferably DocBook) files, which
will push xml2po to it's limits.  Of course, it's better if they're
smaller, but I won't mind even large, very complex documents,
but only <strong>if</strong> you provide me with a translated PO file
as well (so I can test both extraction and merging).</p>

<p><em>Now, off to cleaning the bathroom. :)</em></p>

]]></description>
</item>

</channel>
</rss>
