1 | For language translation, please read these rules: |
---|
2 | |
---|
3 | |
---|
4 | Format of a lang file: |
---|
5 | |
---|
6 | {phrase}{TAB}{appname}{TAB}{LANG_CODE}{TAB}{translation} |
---|
7 | |
---|
8 | e.g: |
---|
9 | |
---|
10 | first name common en First Name |
---|
11 | first name common de Vorname |
---|
12 | |
---|
13 | |
---|
14 | Filenames: |
---|
15 | phpgw_{LANG_CODE}.lang |
---|
16 | |
---|
17 | e.g. |
---|
18 | English phpgw_en.lang |
---|
19 | German phpgw_de.lang |
---|
20 | |
---|
21 | Please look at the content of the 'languages' table for the correct |
---|
22 | setting of the {LANG_CODE}. |
---|
23 | |
---|
24 | |
---|
25 | Rules: |
---|
26 | |
---|
27 | 1. Phrases that are 'common' are loaded for all apps! This includes |
---|
28 | admin and preferences. |
---|
29 | |
---|
30 | 2. The appname 'common' is reserved for the API and for application names in |
---|
31 | each application. Please DO NOT place more than a few phrases in 'common'. |
---|
32 | These should be only enough for the appname to display correctly in the navbar |
---|
33 | for the most part. Please set the appname field to your application name. |
---|
34 | |
---|
35 | 3. Consult an API developer prior to adding or editing files in the |
---|
36 | phpgwapi/setup language files, and prior to adding a lot of phrases |
---|
37 | to 'common' within an application/setup dir. |
---|
38 | |
---|
39 | 4. TRANSLATION to other languages MUST be based upon the english language |
---|
40 | files (phpgw_en.lang in each app/setup directory). Since most of the |
---|
41 | developers are using English as their primary language, those should |
---|
42 | have the most complete list. |
---|
43 | |
---|
44 | 5. Language files for other than English should NOT have additional |
---|
45 | phrases. If some phrase needs to be added to the English file, please |
---|
46 | consult the API or application developer to let them know before you |
---|
47 | add missing phrases. |
---|
48 | |
---|
49 | 6. Please be careful not to conflict with or duplicate any lang entry. |
---|
50 | Conflicts should be checked for by using setup to load the language you are |
---|
51 | working with. Also, if more than a couple of apps are using the same or |
---|
52 | similar lang entry, it should most likely be moved to the API lang files. |
---|
53 | This is so that the size of the db is kept as small as possible. |
---|
54 | |
---|
55 | 7. Please do not have multiple copies of an entry for different apps when |
---|
56 | it can be avoided. e.g. the phrase 'add widget' set to 'preferences', |
---|
57 | 'admin', 'common' and the 'appname'. When in doubt use common, so that |
---|
58 | it will show in prefs/admin, etc. |
---|
59 | |
---|
60 | 8. Please sort the file when you add new entries. This makes it easier to |
---|
61 | read and will help to locate duplicates. |
---|