<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Il 27/09/2014 21:58, Vincent Snijders
ha scritto:<br>
</div>
<blockquote
cite="mid:CAMDhvckjiFDz70EaX9S=NZY-kU0WtyYD-H8bmDu2n5Hd_jHTXA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-09-27 17:59 GMT+02:00 Bart <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:bartjunk64@gmail.com" target="_blank">bartjunk64@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On 9/27/14, Giuliano Colla <<a
moz-do-not-send="true"
href="mailto:giuliano.colla@fastwebnet.it">giuliano.colla@fastwebnet.it</a>>
wrote:<br>
<br>
> Do you mean the procedures in /ide/idetranslations
and /lcl/translations<br>
> or what?<br>
<br>
</span>Maybe he means in the updatepofiles tool
($Lazarus)/tools/updatepofiles.lpi ?<br>
<span class="HOEnZb"></span><br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">That is the one I meant, but I guess
the IDE uses the same routines nowadays.<br>
<br>
</div>
</div>
</blockquote>
<br>
Yes, I checked, and currently updatepofiles in ($Lazarus)/tools is
little more than a wrapper around the Translations unit, the same
unit used by the IDE to manage translations.<br>
<br>
To summarize, for translations currently there's a number of
scattered tools, providing each one a limited number of functions,
with some amount of overlap and with some functions missing.<br>
<br>
In an ideal world<br>
<ol>
<li>a maintainer would have a tool to quickly verify the state of
the translations of the project he maintains, in order to
possibly alert translators.</li>
<li>a translator would have a tool which quickly shows him the
state of the translations he's responsible of, and is capable to
perform a clean up, to edit the translations and to validate
them, without being obliged to jump from one tool to another.<br>
</li>
</ol>
Pochecker provides point 1. Nothing at the moment provides point 2.
This can be achieved either extending Pochecker functions, or by
creating a new tool, which could take advantage for a large extent
of existing units and components, but assembling them having in mind
translator needs.<br>
<br>
If Bart, who is the author and rightful "owner" of Pochecker,
doesn't like the idea of making it too bloated, then creating a new
tool becomes an option to be considered.<br>
<br>
Giuliano<br>
<pre class="moz-signature" cols="72">--
Giuliano Colla
Project planning question: when it's 90% done, are we halfway or not yet?</pre>
</body>
</html>