Typos und Formulierungen in doc-Files und Lokalisierung

[kivitendo-erp.git] / doc / languages_howto.txt

diff --git a/doc/languages_howto.txt b/doc/languages_howto.txt
index cb4a188..defff69 100644 (file)
--- a/doc/languages_howto.txt
+++ b/doc/languages_howto.txt
@@ -27,7 +27,7 @@ File Structure
 
 The structure of locales in Lx-Office is:
 
-  lx-office/locale/<lnagcode>/
+  lx-office/locale/<langcode>/
 
 where <langcode> stands for an abbreviation of the language package. The builtin
 packages use two letter ISO 639-1 codes, but the actual name is not relevant for
@@ -72,7 +72,7 @@ The central translation file. It is essentially an inline perlscript
 autogenerated by locales.pl. To generate it, generate the directory and the two
 files mentioned above, and execute
 
-  scripts/locaes.pl <langcode>
+  scripts/locales.pl <langcode>
 
 or simply copy one of the other languages. You will be told how many are missing
 like this:
@@ -81,14 +81,12 @@ like this:
 
   English - 0.6% - 2015/2028 missing
 
-A "missing" file will be generated and can be edited. You can also edit the all
-directly. Edit all that sounds differently in your language, and execute
+A "missing" file will be generated and can be edited. You can also edit the "all" file
+directly. Edit everything you like to fit the target language, and execute
 locales.pl again. See how the missing words get fewer.
 
 
 
-
-
 These three files are necessary for a localization to be working. Other files
 are optional, but will have special effects:
 
@@ -98,7 +96,7 @@ Num2text (optional)
 
 Legacy code from sql ledger. It provides a means for numbers to be converted
 into natural language, like 1523 => one thousand five hundred twenty three. If
-you want to provide it, it must be inlinable perl code which privdes a num2text
+you want to provide it, it must be inlinable perl code which provides a num2text
 sub. If an init sub exists, it will be executed first.
 
 Only used in the check and receipt printing module.
@@ -108,12 +106,12 @@ special_chars
 
 Lx-Office comes with a lot of interfaces to different formats, some of which are
 rather picky with their accepted charset. The special_chars file contains a
-listing of chars not suited for diefferent file format, and provides
+listing of chars not suited for different file format, and provides
 substitutions. It is written in "Simple Ini" style, containing a block for every
 file format.
 
 First entry should be the order of substitution for entries as a whitespace
-separated list. all entries are interpolated, so \n, \x20 and \\ all work.
+separated list. All entries are interpolated, so \n, \x20 and \\ all work.
 
 After that every entry is a special char that should be translated when writing
 text into such a file.
@@ -127,7 +125,7 @@ Example:
   >=&gt;
   \n=<br>
 
-Note how in this example the order is important. Substituting < and > befor &
+Note the importance of the order in this example. Substituting < and > befor &
 would lead to $gt; become &amp;gt;
 
 For a list of valid formats, see the german special_chars entry. As of this
@@ -144,7 +142,7 @@ writing the following are recognized:
 
 The last of which is very machine dependant. Remember that a lot of characters
 are forbidden by some filesystems, for exmaple MS Windows doesn't like ':' in
-its files where linux doesn't mind that. If you want the files created with your
+its files where Linux doesn't mind that. If you want the files created with your
 language pack to be portable, find all chars that could cause trouble.
 
 
@@ -153,7 +151,7 @@ missing (not part of language package)
 
 This is a file generated by scripts/locales.pl while processing your locales.
 It's only to have the missing entries singled out and does not belong to a
-languge package.
+language package.
 
 
 lost (not part of language package)