diff options
Diffstat (limited to 'doc/translations.txt')
| -rw-r--r-- | doc/translations.txt | 18 |
1 files changed, 11 insertions, 7 deletions
diff --git a/doc/translations.txt b/doc/translations.txt index 83b55ac12..e2b81a5ad 100644 --- a/doc/translations.txt +++ b/doc/translations.txt @@ -34,7 +34,7 @@ How to start a new translation ============================== 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; +repository really is not practical. See the section on getting GIT access below; you will also have to get a local working copy of the manual as described there. 1. Create a new directory structure for your translation @@ -138,22 +138,23 @@ scripts should be run from this directory. The procedure below can be used for relatively simple changes. If there have been major reorganizations in the English documents, you may have to do additional checks to find out exactly what changes have been made. -Use 'svn st -u' before you start this procedure to check the status of +Use 'git status' before you start this procedure to check the status of your working copy. - 1. Update your local working copy from SVN + 1. Update your local working copy from GIT ------------------------------------------ - change directory to: ./manual/ - - svn up + - git pull 2. Copy new files (if any) -------------------------- - If there are any new files (marked 'A' in the output from 'svn up'), + If there are any new files (appearing with "create mode" in the output from + 'git pull'), copy them to the directory for your translation and then: - ./scripts/rev-update <lang> This will change the revision comment in the copied file to: <!-- original version: ##### untranslated --> - You will also have to run 'svn add' for the new documents. + You will also have to run 'git add' for the new documents. 3. Check for other changes -------------------------- @@ -174,7 +175,7 @@ your working copy. after you updated a translation. The revision number should be the same as the revision number in the new version of the English document. You should run './scripts/doc-check <lang>' again after you finish all updates - and before you commit your changes to SVN; there should be no output. + and before you commit your changes to GIT; there should be no output. Other uses of the scripts ------------------------- @@ -266,6 +267,9 @@ are probably errors. Please fix it if you find errors. -------------------------------------------------------------------------- Changelog: +2018-06-03 Samuel Thibault + - migrate to git + 2010-05-01 Tapio Lehtonen - Typo fixes |