<?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>Using gnome-doc-utils for documentation translation</title>
  <link>https://danilo.segan.org/blog/gnome/shaunize</link>
  <description><![CDATA[
<p>I've finally gotten around to porting one module to
gnome-doc-utils (<a href="http://gnome.org/~shaunm/blog/">Shaun's</a>
<em>awesome</em> build system for documentation).  The chosen module
was (surprisingly) gnome-hello.  I haven't committed anything yet, but
I've generated a  
<a href="http://kvota.net/hacks/shaunize/gnome-hello-2.0.3.tar.gz">tarball</a>  
(with Serbian documentation as well — figures are not yet installed
due to bug in gnome-doc-utils; copy them over manually for now).</p>

<p>I've also posted a <a
href="http://kvota.net/hacks/shaunize/guide.html">preliminary
instructions</a> for gdu-enabling your modules (there're also some
missing features from gnome-doc-utils, which are described there as
well).  Until all of this is committed (updates to gnome-doc-utils,
gnome-hello), you can follow these manual steps to enable
documentation translation with PO files for any of your modules.</p>

<p>When gdu-enabled, your translators will need only to put
translated .PO file into <code>help/<em>LANG</em>/<em>LANG</em>.po</code>.</p>

<p>And for those unaware, this process has a new name as well:</p>
<center><strong>SHAUNIZE!</strong></center>

]]></description>
</item>

</channel>
</rss>
