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

superb Sat, 14 May 2011 20:45:47 +0000 Revision: http://svn.php.net/viewvc?view=revision&revision=311022 Log: Update some of the information for translators. Changed paths: U phpdoc/he/trunk/TRANSLATE-INFO Modified: phpdoc/he/trunk/TRANSLATE-INFO =================================================================== --- phpdoc/he/trunk/TRANSLATE-INFO 2011-05-14 20:38:47 UTC (rev 311021) +++ phpdoc/he/trunk/TRANSLATE-INFO 2011-05-14 20:45:47 UTC (rev 311022) @@ -6,10 +6,12 @@ 2. התייחסו למילה "PHP" כנקבה. דמיינו שכתוב "שפת PHP". דוגמה: "PHP מאפשרת". -3. אל תתרגמו מילים בין הטאגים <term>. +3. אל תתרגמו מחרוזות בין הטאגים <term> ו-<type>. 4. שמרו את הקבצים כ-UTF-8 (עם או בלי BOM). לא כ-Windows-1255. +5. אל תתרגמו שמות או הגדרות פונקציות. + ----------------------------------------------------------------------- מידע ישן. צריך לתרגם או להסיר אם כבר לא רלוונטי. ----------------------------------------------------------------------- @@ -17,22 +19,9 @@ 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 @@ -46,12 +35,6 @@ 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'. \ No newline at end of file +a translation. \ No newline at end of file