irmtfan wrote:
I cannot see any problem. local functions in locale.php and translations in fa.php
Ah, I got it but... let me go back a little.
My first propose was 2 files per language:
1 - One file just for type casting (ex: XoopsLocale or ModuleLocale)
2 - One file to hold translations and methods (Ex: XoopsLocaleEn or ModuleLocaleEn)
Then I though you proposed 3 files per language
1 - One file for type casting
2 - One file for translations
3 - One file for methods
What you did propose however was using 2 files:
1 - One file for type casting and methods
2 - One file for translations
The only problem I see with your propose is that a pt_PT/XoopsLocale cannot extend a pt_BR/XoopsLocale and it would have to implement the methods with copy/paste. In my propose this could be done since the translation classes can extend other translation classes(they have different names).
Personally I think your propose is good/better. I think that all languages should extend just the english version. Full translations should be provided for pt_PT and for pt_BR and same goes for methods. You agree?