<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 14px;" lang="x-unicode">Please see my comments below
<br>
<br>
27.02.2014 1:08, Stephen Kelly пишет:
<br>
<blockquote type="cite" style="color: #000000;">Anatoly Shirokov
wrote:
<br>
<br>
<blockquote type="cite" style="color: #000000;">The translation
file is usual source file, it is not binary artifact.
<br>
</blockquote>
I didn't say it was a binary artifact. It's a buildsystem
artifact created
<br>
by your buildsystem.
<br>
</blockquote>
This is source which can be updated by build system. But initially
this is source file was made by myself for each supported
languages and put it to repository.
<br>
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">The only
difference is that I have to support them in up to date state
<br>
with the lupdate utility.
<br>
</blockquote>
Yes.
<br>
<br>
<blockquote type="cite" style="color: #000000;">I want to invoke
lupdate automatically during
<br>
build and after that commit updated translation files to use
them by
<br>
translator group.
<br>
</blockquote>
That seems fine.
<br>
<br>
<blockquote type="cite" style="color: #000000;">What's wrong
with such approach?
<br>
</blockquote>
Maybe the details of your approach are too simple. If you commit
the
<br>
translation files resulting from your build to your repo, then
how did you
<br>
lose work?
<br>
</blockquote>
1. get sources
<br>
2. update sources
<br>
3. build to update translation files
<br>
4. translate new items extracted during the last build (we can
translate to several languages ourself)
<br>
5. make clean to build whole system (and I lose all translated
items)
<br>
6. commit
<br>
...
<br>
N. get sources
<br>
N+1. ops, where are my translated items?
<br>
<br>
Actually it was several times.
<br>
<br>
BR,
<br>
Anatoly Shirokov
<br>
<br>
</div>
</body>
</html>