<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comentários sobre: How to use msggrep to apply new terminology on previous translation</title>
	<atom:link href="http://leonardof.org/2008/08/03/how-to-use-msggrep-to-apply-new-terminology-on-previous-translation/feed/" rel="self" type="application/rss+xml" />
	<link>http://leonardof.org/2008/08/03/how-to-use-msggrep-to-apply-new-terminology-on-previous-translation/</link>
	<description>Tradutor do GNOME para o português do Brasil</description>
	<lastBuildDate>Tue, 24 Jan 2012 22:29:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Por: Chusslove Illich</title>
		<link>http://leonardof.org/2008/08/03/how-to-use-msggrep-to-apply-new-terminology-on-previous-translation/#comment-2384</link>
		<dc:creator>Chusslove Illich</dc:creator>
		<pubDate>Mon, 04 Aug 2008 23:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://leonardof.org/?p=190#comment-2384</guid>
		<description>I personally am not happy with eyeballing/editing matched messages on their own, out of their PO files; for proper context, I frequently want to look at messages just above or below, or elsewhere in the same PO. So instead of extracting them, I prefer that matched messages get flagged in place, in their POs; then I can search for those flags in the editor, check the message, possibly edit, remove flag.

&lt;code&gt;
$ alias posieve-fmm=&apos;posieve.py find-messages -smark -saccel:_ -m /tmp/fmm.out&apos;
$
$ posieve-fmm -smsgid:&apos;\bprint(er&#124;s&#124;ing)?&#124;\bimag(e&#124;ing&#124;es)&apos; po_files_root/
! po_files_root/alpha.po
! po_files_root/subdir/bravo.po
$
$ cat /tmp/fmm.out
po_files_root/alpha.po
po_files_root/subdir/bravo.po
$
$ kate `cat /tmp/fmm.out`
&lt;/code&gt;

where &lt;a href=&quot;http://nedohodnik.dyndns.org/pology-doc/pology.scripts.posieve-module.html&quot; rel=&quot;nofollow&quot;&gt;posieve.py&lt;/a&gt; is a part of &lt;a href=&quot;http://nedohodnik.dyndns.org/pology-doc/&quot; rel=&quot;nofollow&quot;&gt;Pology&lt;/a&gt;, a collection of PO tools that we are brewing in KDE&apos;s repository.</description>
		<content:encoded><![CDATA[<p>I personally am not happy with eyeballing/editing matched messages on their own, out of their PO files; for proper context, I frequently want to look at messages just above or below, or elsewhere in the same PO. So instead of extracting them, I prefer that matched messages get flagged in place, in their POs; then I can search for those flags in the editor, check the message, possibly edit, remove flag.</p>
<p><code><br />
$ alias posieve-fmm=&apos;posieve.py find-messages -smark -saccel:_ -m /tmp/fmm.out&apos;<br />
$<br />
$ posieve-fmm -smsgid:&apos;\bprint(er|s|ing)?|\bimag(e|ing|es)&apos; po_files_root/<br />
! po_files_root/alpha.po<br />
! po_files_root/subdir/bravo.po<br />
$<br />
$ cat /tmp/fmm.out<br />
po_files_root/alpha.po<br />
po_files_root/subdir/bravo.po<br />
$<br />
$ kate `cat /tmp/fmm.out`<br />
</code></p>
<p>where <a href="http://nedohodnik.dyndns.org/pology-doc/pology.scripts.posieve-module.html" rel="nofollow">posieve.py</a> is a part of <a href="http://nedohodnik.dyndns.org/pology-doc/" rel="nofollow">Pology</a>, a collection of PO tools that we are brewing in KDE&apos;s repository.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Por: Leonardo Fontenelle</title>
		<link>http://leonardof.org/2008/08/03/how-to-use-msggrep-to-apply-new-terminology-on-previous-translation/#comment-2380</link>
		<dc:creator>Leonardo Fontenelle</dc:creator>
		<pubDate>Mon, 04 Aug 2008 01:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://leonardof.org/?p=190#comment-2380</guid>
		<description>What if the message catalogs are located at different directories, e. g. gedit/po/pt_BR.po?</description>
		<content:encoded><![CDATA[<p>What if the message catalogs are located at different directories, e. g. gedit/po/pt_BR.po?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Por: Dwayne Bailey</title>
		<link>http://leonardof.org/2008/08/03/how-to-use-msggrep-to-apply-new-terminology-on-previous-translation/#comment-2379</link>
		<dc:creator>Dwayne Bailey</dc:creator>
		<pubDate>Mon, 04 Aug 2008 01:31:45 +0000</pubDate>
		<guid isPermaLink="false">http://leonardof.org/?p=190#comment-2379</guid>
		<description>If you are doing cleanups of terminology I would also suggest the following approaches from the &lt;a href=&quot;http://translate.sourceforge.net/wiki/toolkit/index&quot; rel=&quot;nofollow&quot;&gt;Translate Toolkit&lt;/a&gt;:

You can use &lt;a href=&quot;http://translate.sourceforge.net/wiki/toolkit/pogrep&quot; rel=&quot;nofollow&quot;&gt;pogrep&lt;/a&gt; to traverse one or multiple files, regex queries accepted (--regex), accelerator characters can be ignored(--accelerators), and various sections searchable:

&lt;blockquote&gt;pogrep image po/ po-grepped/
# Edit the files
pomerge -t po po-grepped po  # merges all of your changes back again
&lt;/blockquote&gt;

If you want to check terminology or create terminology then you can use the &lt;a href=&quot;http://translate.sourceforge.net/wiki/toolkit/poterminology&quot; rel=&quot;nofollow&quot;&gt;poterminology&lt;/a&gt; tool.  This won&#039;t fix the terminology for you but will identify problem areas. If there are conflicts then it will display both conflicting entries.  You could use this then to execute a pogrep search.  The advantage of this approach is that it will highlight words of terminology that you also might not yet have defined.  But you probably want to use the next tool for a good cleanup.

Lastly, if you are checking consistency you want to use &lt;a href=&quot;http://translate.sourceforge.net/wiki/toolkit/poconflicts&quot; rel=&quot;nofollow&quot;&gt;poconflicts&lt;/a&gt;.  This will find areas in your translations that are using different translations for the same English source text (note that not all occurrences are incorrect as your language might use different words for English words that have multiple meanings):

&lt;blockquote&gt;poconflicts po/ po-conflicts/&lt;/blockquote&gt;

You now have a directory of PO files, one for each word or phrase in conflict.  The advantage of this is that if the word in conflict is &#039;image&#039; then we will extract every entry that contains the word image into a file called image.po.  While you might lose context you will see the context of the word across the whole project.  Try ignoring case to identify more conflicts.

Once you have cleaned up the conflicts we use &lt;a href=&quot;http://translate.sourceforge.net/wiki/toolkit/porestructure&quot; rel=&quot;nofollow&quot;&gt;porestructure&lt;/a&gt; and &lt;a href=&quot;http://translate.sourceforge.net/wiki/toolkit/pomerge&quot; rel=&quot;nofollow&quot;&gt;pomerge&lt;/a&gt; to get your corrections back into the original files:

&lt;blockquote&gt;porestructure po-conflicts/ po-restructured/  # This converts the PO files back into the original layout of the original PO files
pomerge -t po/ po-restructured/ po/
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>If you are doing cleanups of terminology I would also suggest the following approaches from the <a href="http://translate.sourceforge.net/wiki/toolkit/index" rel="nofollow">Translate Toolkit</a>:</p>
<p>You can use <a href="http://translate.sourceforge.net/wiki/toolkit/pogrep" rel="nofollow">pogrep</a> to traverse one or multiple files, regex queries accepted (&#8211;regex), accelerator characters can be ignored(&#8211;accelerators), and various sections searchable:</p>
<blockquote><p>pogrep image po/ po-grepped/<br />
# Edit the files<br />
pomerge -t po po-grepped po  # merges all of your changes back again
</p></blockquote>
<p>If you want to check terminology or create terminology then you can use the <a href="http://translate.sourceforge.net/wiki/toolkit/poterminology" rel="nofollow">poterminology</a> tool.  This won&#8217;t fix the terminology for you but will identify problem areas. If there are conflicts then it will display both conflicting entries.  You could use this then to execute a pogrep search.  The advantage of this approach is that it will highlight words of terminology that you also might not yet have defined.  But you probably want to use the next tool for a good cleanup.</p>
<p>Lastly, if you are checking consistency you want to use <a href="http://translate.sourceforge.net/wiki/toolkit/poconflicts" rel="nofollow">poconflicts</a>.  This will find areas in your translations that are using different translations for the same English source text (note that not all occurrences are incorrect as your language might use different words for English words that have multiple meanings):</p>
<blockquote><p>poconflicts po/ po-conflicts/</p></blockquote>
<p>You now have a directory of PO files, one for each word or phrase in conflict.  The advantage of this is that if the word in conflict is &#8216;image&#8217; then we will extract every entry that contains the word image into a file called image.po.  While you might lose context you will see the context of the word across the whole project.  Try ignoring case to identify more conflicts.</p>
<p>Once you have cleaned up the conflicts we use <a href="http://translate.sourceforge.net/wiki/toolkit/porestructure" rel="nofollow">porestructure</a> and <a href="http://translate.sourceforge.net/wiki/toolkit/pomerge" rel="nofollow">pomerge</a> to get your corrections back into the original files:</p>
<blockquote><p>porestructure po-conflicts/ po-restructured/  # This converts the PO files back into the original layout of the original PO files<br />
pomerge -t po/ po-restructured/ po/
</p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
