jimw Mon Mar 12 11:17:56 2001 EDT
Modified files:
/phpdoc README.translations
Log:
clean this up, add link to iso language codes
Index: phpdoc/README.translations
diff -u phpdoc/README.translations:1.2 phpdoc/README.translations:1.3
--- phpdoc/README.translations:1.2 Sat Jan 13 14:03:50 2001
+++ phpdoc/README.translations Mon Mar 12 11:17:55 2001
@@ -3,21 +3,25 @@
Starting a new language translation comes down to these simple steps
now:
-0) Consult the phpdoc list to see if the translation is already
- in progress... if one is, disregard the following.
+0) Consult the [EMAIL PROTECTED] list to see if the translation
+ is already in progress... if it is, disregard the following and
+ coordinate with the other translators on the list.
-1) Create a sudirectory with the appropriate language code
+1) Create a sudirectory with the appropriate language code (one
+ list is at:
+ http://www.unicode.org/unicode/onlinedat/languages.html)
-2) copy en/language-defs.ent to the new directory
+2) Copy en/language-defs.ent to the new directory and translate
+ the contents.
-3) copy over files from the english tree and start to work on them,
- (do not copy/checkin untranslated files) and rerun configure each
- time you add a file
+3) Copy over files from the English tree and start to work on them,
+ (do not check in untranslated files) and rerun configure each
+ time you add a file.
-Some important issues to consider when requesting building a new
-translation:
+Some important issues to consider when building a new translation:
+
a) Can you set up and compile the manual yourself? If not, can
you set up a team to work on the language?
-b) Have you made sure that your language or glyph (lettering,
-font, or characters) are using a format compatible with docbook?
+b) Have you made sure that your language or glyph (lettering, font,
+or characters) is supported by the docbook stylesheets?
