forked from extern/egroupware
cf19aae187
translation file (only those not translated in simplified Chinese).
This is because
1) most simplified Chinese readers can read traditional
Chinese. If some phrase doesn't have simplified Chinese translation,
egroupware better fall back to traditional Chinese then English.
2) Translation can be easier (just pick up the unfamiliar traditional
translation and change to simplified form)
The change is made by using
> find . -type d -name "setup" -exec /tmp/merge_tradition.sh {} \;
where merge_tradition.sh is:
#!/bin/sh
cd $1
if [ -f phpgw_zh.lang ] && [ -f phpgw_zt.lang ]; then
mv phpgw_zh.lang phpgw_zh.lang.old
join -a 1 -t " " phpgw_zt.lang phpgw_zh.lang.old | \
awk -F " " \
'{ OFS = FS; if (NF == 7) print $1, $5, $6, $7; else print $0 ;}' \
> phpgw_zh.lang
fi
Kiang if you like the idea you can merge my translation to your lang
file too. And it's even better if the language engine can be changed in
the way that, as a phrase has no translation for current language,
choose the nearest language before falling back to English. Say, when no
translation in zh, use zt before trying English.
Could it be better that this apply to pt too? (pt-br and pt)
|
||
|---|---|---|
| .. | ||
| default_records.inc.php | ||
| phpgw_da.lang | ||
| phpgw_de.lang | ||
| phpgw_en.lang | ||
| phpgw_es-ca.lang | ||
| phpgw_es-es.lang | ||
| phpgw_fr.lang | ||
| phpgw_nl.lang | ||
| phpgw_pl.lang | ||
| phpgw_pt-br.lang | ||
| phpgw_pt.lang | ||
| phpgw_sl.lang | ||
| phpgw_zh.lang | ||
| phpgw_zt.lang | ||
| setup.inc.php | ||
| tables_baseline.inc.php | ||
| tables_current.inc.php | ||
| tables_update.inc.php | ||