Hallo. This is a first attempt to define a work-flow for sending Novell translations back to the upstream. What you download here? These files are preprocessed po-difference files comparing of Novell translation project translations and the latest upstream translation. They are intended to make upstreaming as straightforward as possible. Here are original unprocessed Novell translations: https://svn.berlios.de/svnroot/repos/opensuse-i18n/branches/SLE11/lcn/ Proposed work-flow for merging of Novell downstream translations ================================================================ If your language is in "new" and you are a package maintainer: -------------------------------------------------------------- 1) Download all po files in "new" directory. 2) Add translations to the repository and start upstream maintenance. 3) Do standard steps for adding a new language (LINGUAS/ALL_LINGUAS update). 4) Upload them to the upstream project. It can be done by the upstream maintainer. Particular language knowledge is not required. If your language is in "updates" and you are a translation maintainer: ---------------------------------------------------------------------- Suppose that your language is ${LNG} 1) Verify that you have msgcat utility installed (gettext-tools or gettext package). 2) Download your latest upstream ${LNG}.po file and Novell's ${LNG}_added.po, ${LNG}_changed.po, ${LNG}_changed_review.po and merge_tool script. 3) If ${LNG}_changed_review.po exists, open it in a text editor and review all changes. First item is your translation, second item is a translation proposed by Novell translators. 4) If you don't agree with some changes, edit ${LNG}_changed.po and remove corresponding strings. Please send us a feedback about your change. If you agree with all changes, go to step 6. 6) Download your latest po file, place it to the sane directory and perform the merge. If could be done in the shell by calling following command: sh ./merge_tool ${LNG} # replace ${LNG} by your language name, e. g. "de", "zh_CN" etc. or define LNG=de or so. 7) Review the new file and its header. 8) Upload the new file to the upstream project. It can be done only by the translation maintainer. Particular language knowledge is required to perform steps 3 and 4. If your language is in "updates" and you are a translation maintainer or ------------------------------------------------------------------------ package maintainer and ${LNG}_changed.po does not exist: -------------------------------------------------------- 1) You can do the above. The new translation will never be worse than the previous. It can be done by the upstream maintainer. Particular language knowledge is not required in this case.