summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorTapio Lehtonen <tale@debian.org>2010-05-01 09:32:29 +0000
committerTapio Lehtonen <tale@debian.org>2010-05-01 09:32:29 +0000
commitedc71be22eef19cd5c112296c072b378e94a1fe7 (patch)
tree266bc706df07f0c3ef2795594d7c799e2dd71f8c /doc
parent246e3ab67843111e7ea68fca83904b89f6e43598 (diff)
downloadinstallation-guide-edc71be22eef19cd5c112296c072b378e94a1fe7.zip
Typo fixes
Diffstat (limited to 'doc')
-rw-r--r--doc/translations.txt19
-rw-r--r--doc/translations_po.txt18
2 files changed, 22 insertions, 15 deletions
diff --git a/doc/translations.txt b/doc/translations.txt
index f6d32e862..56717467f 100644
--- a/doc/translations.txt
+++ b/doc/translations.txt
@@ -34,7 +34,7 @@ you will also have to get a local working copy of the manual as described there.
--------------------------------------------------------
Use the following commands to create a copy of the English documents as a
base for your translation. This also ensures that your translation will be
- complete and can be build. A text that has not be translated yet, will be
+ complete and can be built. A text that has not been translated yet, will be
included in English.
- change directory to: ./manual/
- cp -R en/ <lang>
@@ -44,7 +44,7 @@ you will also have to get a local working copy of the manual as described there.
2. Convert revision comments
----------------------------
- This enables you to track changes is the original English documents.
+ 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/
- ./scripts/rev-update <lang>
@@ -55,7 +55,7 @@ you will also have to get a local working copy of the manual as described there.
- svn add <lang>
- svn ci -m "Manual: creating new translation for <lang>"
-One more change is needed to get your translation build automatically:
+One more change is needed to get your translation building automatically:
<lang> needs to be added to the 'languages' variable in build/build.sh.
However, this is only usefull after you have translated your first couple
of chapters. Please send a request to the debian-boot mail list for your
@@ -92,7 +92,7 @@ Suggested translation order:
- ./boot-new/*.xml
- ./boot-new/modules/*.xml
-Note that currently (may 10, 2004) it look like there will be a fairly major
+Note that currently (may 10, 2004) it looks like there will be a fairly major
reorganization of parts of the manual in the next month(s).
Keeping your translation up to date
@@ -107,7 +107,7 @@ An original English file contains something like:
<!-- $Id: preface.xml 12756 2004-04-06 22:23:56Z some-user $ -->
The second line is important. It contains the filename, the revision number,
-the date and time the last revision was committed, the user that committed
+the date and time the last revision was committed and the user that committed
the last revision. The string '$Id:' is necessary for SVN to automatically
update this line each time the file is committed.
@@ -188,7 +188,7 @@ both in English and your own language.
As strings and their translations in the installer may change, you may have
to perform an installation once in a while to check if there have been
important changes (the main burden to check for changes in strings falls on
-the maintainers of the English original, but is you spot inconsistencies,
+the maintainers of the English original, but if you spot inconsistencies,
please report them to the debian-boot list).
You can also use the xx(_XX).po files for packages (including d-i) to see
@@ -244,10 +244,10 @@ How to get write access to the SVN repository
svn commit -m "Your comment about this commit"
to commit your changes to the SVN repository.
- Note: it's possible, to do an anonymous checkout from the svn
+ 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.
+ 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/.
@@ -267,6 +267,9 @@ are probably errors. Please fix it if you find errors.
--------------------------------------------------------------------------
Changelog:
+2010-05-01 Tapio Lehtonen
+ - Typo fixes
+
2006-07-14 Frans Pop
- Correct and update information on subversion checkout
diff --git a/doc/translations_po.txt b/doc/translations_po.txt
index 543cc3a45..f90ee80f8 100644
--- a/doc/translations_po.txt
+++ b/doc/translations_po.txt
@@ -20,7 +20,7 @@ The downside of the poxml tools is that they require the .xml files to be
original are not proper XML, we've had to "integrate" the files per chapter.
This means that instead of translating about 160 small files, you will be
-translating about 15 large files.
+translating about 18 large files.
Current limitations
===================
@@ -95,11 +95,12 @@ to check what you are committing before you run the 'svn ci' command.
Updating your translation
=========================
-The PO files for your language and the templates for the manual are updated
-regularly when there are changes in the original English XML files.
-This is done during the "daily" builds (currently done by Frans Pop); you
-should not have to update your PO files yourself.
-Changed strings will be marked 'fuzzy' and new strings will be untranslated.
+The PO files for your language and the templates for the manual are
+updated regularly when there are changes in the original English XML
+files. This is done during the "daily" builds (currently done by
+Frans Pop); you should not have to update your PO files yourself, but
+rather get the updates using 'svn up'. Changed strings will be marked
+'fuzzy' and new strings will be untranslated.
After this your PO files in the ./po directory should be updated and you can
update the translation with your favorite PO file editor. To commit the
@@ -148,7 +149,7 @@ It is possible to convert an existing translation of the manual (where the
individual XML files have been translated) to using PO files.
There are two important conditions:
- the translation must be up-to-date with the English XML files;
-- the translation must have same structure as the English XML files (i.e.
+- the translation must have the same structure as the English XML files (i.e.
the translation must have the same chapters, sections, paragraphs, tables,
examples, etc; you can have no 'extra' paragraphs in your translation).
@@ -168,6 +169,9 @@ If you find any errors in this file, please fix them.
--------------------------------------------------------------------------
Changelog:
+2010-05-01 Tapio Lehtonen
+ - Typo fixes
+
2007-07-31 Frans Pop
- Add link to full conversion instructions