<div style="text-align: right;">سلام،<br>کسی این کار (که در زیر توضیح داده شده) رو روی فارسی انجام داده؟<br>باید قبل از شروع به ترجمهٔ ۴.۱ این کار رو می‌کردیم تا خروجی کارهامون روی ۴.۰ در ۴.۱ هم استفاده بشه.<br>می‌تونیم الان انجامش بدیم؟ یا کلاً ازش صرف نظر کنیم و از اول شروع کنیم؟ اگر بشه جوری این کار رو کرد که در عین انتقال ترجمه‌های ۴.۰ به ۴.۱، ترجمه‌های جدید توی ۴.۱ از دست نره خیلی خوبه.<br>
<span style="color: rgb(255, 255, 255);">؟</span><br></div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Chusslove Illich</b> <<a href="mailto:caslav.ilic@gmx.net">caslav.ilic@gmx.net</a>><br>
Date: Tue, Apr 22, 2008 at 6:30 PM<br>Subject: Re: KDE 4.1 warmup: Alpha1 translations<br>To: KDE i18n-doc <<a href="mailto:kde-i18n-doc@kde.org">kde-i18n-doc@kde.org</a>><br><br><br>> [: Māris Nartišs :]<br>
> [...] we where working on polishing and enhancing stable (4.0)<br>
> translations and we have not touched trunk [...] What are "best practice"<br>
<div class="Ih2E3d">> steps we should take to move our stable translations to next stable<br>
</div>> release? [...] Wait for a miracle to happen?<br>
<br>
I've just realized an interesting possible side-effect use of a, khm, yet-<br>
undocumented summit-workflow.<br>
<br>
First, if not so already (as it's anyway a good idea), you need to have an<br>
exact replica of the repository tree on your disk:<br>
<br>
$KDEREPO/<br>
trunk/<br>
l10n-kde4/<br>
scripts/<br>
templates/<br>
lv/<br>
branches/<br>
stable/<br>
l10n-kde4/<br>
scripts/<br>
templates/<br>
lv/<br>
<br>
with scripts/, templates/, and lv/ fully checked out.<br>
<br>
Then you do the following:<br>
<br>
$ cd $KDEREPO/trunk/l10n-kde4<br>
$ export PYTHONPATH=$PWD/scripts:$PYTHONPATH<br>
$ export PATH=$PWD/scripts/pology/scripts:$PATH<br>
$<br>
$ mkdir -p lv/internal<br>
$ echo "S.branches.reverse()" > lv/internal/messages.extras.summit<br>
$<br>
$ posummit.py scripts/messages.summit lv gather,merge --create --force<br>
(...go have your favorite beverage...)<br>
$ posummit.py scripts/messages.summit lv scatter trunk:<br>
(...some more favorite beverage...)<br>
<br>
After this you can just svn ci lv/messages -- all messages in trunk will be<br>
filled with existing translations in stable, all catalogs moved in trunk<br>
compared to stable will still get their translations, all catalogs present<br>
in stable but missing in trunk will be added and merged. You know, a bit of<br>
good old magic.<br>
<br>
The stuff created in the lv/internal in the process will also have been<br>
automatically added to version control, so to clean up:<br>
<br>
$ svn revert -R lv/internal<br>
$ rm -rf lv/internal/messages<br>
<br>
(And make sure to check out the fresh scripts/, as I've just committed few<br>
fixes after testing the above.)<br>
<br>
Since this procedure overwrites the translations in trunk with those from<br>
stable, it should be applied only when the intention is to switch from<br>
translating stable to (mostly) translating trunk.<br>
<br>
On the other hand, the stuff that got created in lv/internal/messages is in<br>
fact the union of stable and trunk, "the summit" of branches, where one can<br>
work on exclusively, never again caring about particular branches (only<br>
"scatter" into them from time to time). This is the summit-workflow, that<br>
I'm supposed to document sooner or later, for those who would bite the<br>
bullet :) (It has been tested for quite some time now on Serbian and<br>
Japanese translation.)<br>
<font color="#888888"><br>
--<br>
Chusslove Illich (Часлав Илић)<br>
Serbian KDE translation team<br>
</font></div><br><br clear="all"><br>-- <br> Mohammad Ebrahim Mohammadi Panah