diff options
Diffstat (limited to 'doc/translations.txt')
| -rw-r--r-- | doc/translations.txt | 63 |
1 files changed, 30 insertions, 33 deletions
diff --git a/doc/translations.txt b/doc/translations.txt index f5910c290..83b55ac12 100644 --- a/doc/translations.txt +++ b/doc/translations.txt @@ -1,10 +1,12 @@ -Debian Installation Manual - notes for translation +Debian Installation Guide - notes for translation -------------------------------------------------- !!! Please note, that this file mostly documents xml-based !!! translations. But you can also translate this manual via po !!! files, if you want. This is documented in the file !!! translations_po.txt in this directory. +!!! And: using the po format is strongly recommended, using the +!!! xml format is deprecated! Note: if you happen to modify this file, please don't forget to update the trailing changelog @@ -12,10 +14,10 @@ Note: if you happen to modify this file, please don't forget to Where is the manual kept? ========================= -The manual is kept in a Subversion repository on svn.debian.org +The manual is kept in a git repository on salsa.debian.org as part of the Debian Installer (d-i) project. -The manual and its translations can be found in ./manual. +The manual and its translations can be found in ./installation-guide. How to join the translation effort for an existing translation ============================================================== @@ -31,7 +33,7 @@ translate and how to submit your translations. How to start a new translation ============================== -Starting a translation for a new language without write access to the d-i SVN +Starting a translation for a new language without write access to the d-i git repository really is not practical. See the section on getting SVN access below; you will also have to get a local working copy of the manual as described there. @@ -41,24 +43,24 @@ you will also have to get a local working copy of the manual as described there. base for your translation. This also ensures that your translation will be complete and can be built. A text that has not been translated yet, will be included in English. - - change directory to: ./manual/ + - change directory to: ./installation-guide/ - cp -R en/ <lang> (where <lang> is the ISO code for your language: xx or xx_XX) - - find <lang> -name .svn | xargs rm -Rf - (this removes all .svn subdirectories) + - find <lang> -name .git | xargs rm -Rf + (this removes all .git subdirectories) 2. Convert revision comments ---------------------------- This enables you to track changes in the original English documents. see 'Keeping your translation up to date' below for an explanation. - - change directory to: ./manual/ + - change directory to: ./installation-guide/ - ./scripts/rev-update <lang> - 3. Commit the changes to SVN + 3. Commit the changes to git ---------------------------- - - change directory to: ./manual/ - - svn add <lang> - - svn ci -m "Manual: creating new translation for <lang>" + - change directory to: ./installation-guide/ + - git add <lang>/* + - git commit -m "installation-guide: creating new translation for <lang>" One more change is needed to get your translation building automatically: <lang> needs to be added to the 'languages' variable in build/build.sh. @@ -216,46 +218,38 @@ You can also try to build the manual (create HTML pages) for a specific architecture for your language. See ./build/README for more information on building the manual. -How to get write access to the SVN repository +How to get write access to the git repository ============================================= - 1) Installing subversion + 1) Installing git ------------------------ You need to install subversion on your system. Just do - apt-get install subversion + apt install git - 2) Getting write access to the subversion repository + 2) Getting write access to the git repository ---------------------------------------------------- If you are not a Debian Developer, you first need to create a guest account - on http://alioth.debian.org/, than ask on debian-boot@lists.debian.org + on https://salsa.debian.org/, than ask on debian-boot@lists.debian.org for somebody to add your guest account to the debian-installer project. - 3) Using subversion to get files + 3) Using git to get files -------------------------------- Once your account is allowed to write to the project, you can retrieve the - full project using this: - svn co svn+ssh://<username>@svn.debian.org/svn/d-i/trunk - If you only want to work on the manual, you can retrieve the relevant part - of the repository using: - svn co svn+ssh://<username>@svn.debian.org/svn/d-i/trunk/manual + installation-guide using this: + git clone git@salsa.debian.org:installer-team/installation-guide.git - 4) Commit your changed translation files to SVN + 4) Commit your changed translation files to git ----------------------------------------------- After you have finished editing your translation, use - svn commit -m "Your comment about this commit" - to commit your changes to the SVN repository. + git add path-to-file(s) + git commit -m "Your comment about this commit" + git push + to commit your changes to the git repository. - Note: it's possible to do an anonymous checkout from the svn - (use svn co svn://svn.debian.org/d-i/trunk/manual). - However, from this local copy you aren't able to commit, it's readonly. - Use the commands listed under 3) if you plan to do commits in the future. - - -You can find a good manual for SVN at http://svnbook.red-bean.com/. How to get help =============== @@ -307,3 +301,6 @@ Changelog: 2017/04/12 Holger Wansing - Add hint on translations_po.txt + +2018/06/03 Holger Wansing + - Updating (most) content on git migration |