Sayamindu Dasgupta wrote:
On Sat, 2005-09-03 at 15:35 +0530, Runa B wrote:
Hi Sayam,
Please find the files that i could update for 2.12 here :
http://runa.randomink.org/AnkurBangla/gnome2-12/. We have slipped down
un "unsupported" last week so perhaps this might help regain some of the
earlier position.
regards
runa
Umm.. I am going away to college tomorrow, and our college firewall
prevents CVS access.
Could you commit these files ?
I have submitted these files into the CVS. As of now we stand at ~65%.
Hopefully we can ensure >80% translated status for the next version. In
this regard I'd like to suggest a few things:
1. Let us not break the translation process for the files within the
HEAD as it is applicable to all the versions.
2. As suggested by Golam we can start clearing up the files in the
developer-libs section and also for the desktop. And for that as was
suggested by Sayam one can send in a mail to the original translator and
if he/she does not respond within the next 3 days the file can be safely
taken up.
3. This is a suggestion as regards the CVS-- the normal procedure
followed by Ankur is that once a file has been translated, it is posted
for RFC, revised and then committed to the CVS. Off-late a lot of files
have been posted for RFC but never made its way to the CVS as a result
of which precious time and effort of the translators was lost. And also
given the considerable time gap between the actual translation and the
time of CVS commit, the inconsistencies are too huge and compel the
merging and re-merging with the changed files in the CVS, thus defeating
the real purpose of a version control system. What I suggest is that
once a translator finishes translations... the work is immediately
merged with the version in the CVS and committed.. so that any changes
made by the developers can be easily incorporated with the latest
translated version. Also, the file is within easy reach of the
translator or other reviewers from the gnome-status site:
http://l10n-status.gnome.org/gnome-2.12/index.html from where it can be
d/led like any other file.
4. I would really like to stress the above for all the files under the
HEAD, as even if a package is branched out (for instance, evolution), we
will not be required to redo it completely, but the version from the
HEAD would automatically be moved into the branch. This is something
that happened for Evolution, which had to be submitted into the 2.8
branch, as a result of which it never made it automatically into the
2.10 version or 2.12. I had to merge it with the new .pot file and then
commit it into the 2.12 branch. Hence, perhaps with files of this
magnitude we ought ensure that it goes straight into the HEAD.
Comments and brickbats are welcome. :) Hopefully we can achieve the 100%
target for the next release.
thanks for listening
regards
Runa
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
http://www.bengalinux.org
Bengalinux-gnome-tran mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bengalinux-gnome-tran
