سلام، ظاهراً باید واژهنامه رو به جای جدیدی که برای این جور چیزها در نظر گرفتهاند منتقل کنیم. امیل جان، زحمتش رو میکشی؟
---------- Forwarded message ---------- From: Chusslove Illich <caslav.ilic@gmx....> Date: Wed, Jul 30, 2008 at 3:36 AM Subject: Created l10n-support, stuff moved (Pology, summits) To: kde-i18n-doc@kde....
As we discussed earlier, trunk/l10n-support has been created. From its README file:
----- 8< -----
Tools and data in support of the l10n process which are not directly linked to source code modules, i.e. not tracking stable/development code branches.
Each language team can create a subdirectory named by their language code, and use it for whatever fits the above purpose. For example, this would be a good place to store glossaries, style guides, checker scripts, etc.
----- 8< -----
Looking into current trunk/l10n-kde4/<lang>/internal directories, I'd say that almost all of their content would fit better into trunk/l10n-support/<lang>/. But this is just an observation, no team is forced to move anything.
Pology has been moved from trunk/l10n-kde4/scripts/pology to trunk/l10n-support/pology. Users should only adjust their PATH to reflect this (since some time ago setting PYTHONPATH is not necessary).
Summits have been moved from trunk/<lang>/internal/ to trunk/l10n-support/<lang>/sumit/. I have hopefully adjusted all paths accordingly; posummit.py is to be executed same as before, except that from now on within trunk/l10n-support/ directory.
-- Chusslove Illich (Часлав Илић) Serbian KDE translation team