svn: /phpdoc/he/trunk/ TRANSLATE-INFO Translators

--cbcc5d9d28b65e7902d9e6c8d56f05d220852e11
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

superb                                   Sat, 07 May 2011 14:12:53 +0000

Revision: http://svn.php.net/viewvc?view=revision&revision=310824

Log:
Rename Translators to TRANSLATE-INFO. Translators should be used in a different way, as per:
https://doc.php.net/php/dochowto/translation-revtrack.php

Changed paths:
    A + phpdoc/he/trunk/TRANSLATE-INFO
        (from phpdoc/he/trunk/Translators:r310823)
    D   phpdoc/he/trunk/Translators

Copied: phpdoc/he/trunk/TRANSLATE-INFO (from rev 310823, phpdoc/he/trunk/Translators)
===================================================================
--- phpdoc/he/trunk/TRANSLATE-INFO	                        (rev 0)
+++ phpdoc/he/trunk/TRANSLATE-INFO	2011-05-07 14:12:53 UTC (rev 310824)
@@ -0,0 +1,43 @@
+Translation Rules:
+
+1. general rules:
+1.1 Treat PHP as a lady. translate "php enables" to "php me'afsheret" (and not to "php me'afsher")
+
+1.2 Avoid translating technical words, like 'operator', 'compile' (lekampel), and others
+
+1.3 Avoid translating "you" to "ata" or "at". you should -> 'kedai' or 'nitan'
+
+1.4 when u r not sure how to translate a term, try:
+http://moshe.i-com-it.com/phpdoc-he/index.php?action=articles&cmd=show&id=15
+if the entry is not exists, discuss it the on the group.
+
+
+2. hebrew and english mixing:
+2.1. Avoid transtale the function prototypes.
+
+2.2. Transtale NOTHING between <term> tags.
+
+3.3. where varibles or functions mixed with regular text without special tages capsulating them,
+u should capsulate them with <varname> to avoid rtl problems (just if appear),
+otherwise don't try costumizing the code (including adding &nbsp), since it just confusing me
+while tring doing it automatically during the the build process.
+
+3.3.1. "problems" with the align (where trems joining to the follow text) that can be solve using whitespace (not &nbsp;),
+are not problems, just feel free to add spaces.
+
+3.3.2 avoid this format of sentence: 'ôåð÷öééú äPHP date_sunset()' coz the the bidi engine always flip all the english direction
+(copy this sentence to bidi editor to c the effect) mean, the hebrew 'ä' will follow the 'date_sunset()' and not the 'PHP'.
+the solution have to be take playing with the translation.
+e.g, droping the PHP word: 'äôåð÷öéä date_sunset()'
+
+3.4 dont translate what between <type> tags (e.g, integer=>'shalem'') at all,
+since the build process use the description to link to types page.
+
+
+3. Co-working and maintaining:
+3.1 updating the file named 'translation.xml' every time you start working on
+a translation.
+
+3.2. use a revision tag similar to the one used in the file '/language/variables.xml'.
+
+

Deleted: phpdoc/he/trunk/Translators
===================================================================
--- phpdoc/he/trunk/Translators	2011-05-07 14:04:31 UTC (rev 310823)
+++ phpdoc/he/trunk/Translators	2011-05-07 14:12:53 UTC (rev 310824)
@@ -1,43 +0,0 @@
-Translation Rules:
-
-1. general rules:
-1.1 Treat PHP as a lady. translate "php enables" to "php me'afsheret" (and not to "php me'afsher")
-
-1.2 Avoid translating technical words, like 'operator', 'compile' (lekampel), and others
-
-1.3 Avoid translating "you" to "ata" or "at". you should -> 'kedai' or 'nitan'
-
-1.4 when u r not sure how to translate a term, try:
-http://moshe.i-com-it.com/phpdoc-he/index.php?action=articles&cmd=show&id=15
-if the entry is not exists, discuss it the on the group.
-
-
-2. hebrew and english mixing:
-2.1. Avoid transtale the function prototypes.
-
-2.2. Transtale NOTHING between <term> tags.
-
-3.3. where varibles or functions mixed with regular text without special tages capsulating them,
-u should capsulate them with <varname> to avoid rtl problems (just if appear),
-otherwise don't try costumizing the code (including adding &nbsp), since it just confusing me
-while tring doing it automatically during the the build process.
-
-3.3.1. "problems" with the align (where trems joining to the follow text) that can be solve using whitespace (not &nbsp;),
-are not problems, just feel free to add spaces.
-
-3.3.2 avoid this format of sentence: 'ôåð÷öééú äPHP date_sunset()' coz the the bidi engine always flip all the english direction
-(copy this sentence to bidi editor to c the effect) mean, the hebrew 'ä' will follow the 'date_sunset()' and not the 'PHP'.
-the solution have to be take playing with the translation.
-e.g, droping the PHP word: 'äôåð÷öéä date_sunset()'
-
-3.4 dont translate what between <type> tags (e.g, integer=>'shalem'') at all,
-since the build process use the description to link to types page.
-
-
-3. Co-working and maintaining:
-3.1 updating the file named 'translation.xml' every time you start working on
-a translation.
-
-3.2. use a revision tag similar to the one used in the file '/language/variables.xml'.
-
-

--cbcc5d9d28b65e7902d9e6c8d56f05d220852e11--