Xoops Development::Proposal for a "universal language" system.
Quote:
I just thought it would be good standard to separate translations from functions (I should save the file contain translation in utf-8 without BOM but i can save the file contain functions in any standard format) but we can wrote translations and methods in fa.php as you proposed.
Quote:
yes. you are right.
I think it is possible with your proposal.(if we dont follow any standard and let users to do what they want)
Just i dont know what will happen on performance when we extend such a number of classes?
here:
1- en extends XoopsLocalAbstract
2- pt_BR extends en (translation + functions)
3- pt_PT extends pt_BR (translation + functions)
4- XoopsLocale extends pt_PT
about multilingual XOOPS:
Our only problem with the old system is the limited space in the field and we have this issue only in "title fields" not "text fields"
eg: i never run out of space in a news body/post body. i always have issues with news titles/ forum names/ categories,...
So I think nodes for text fields will not solve anything regarding multilingual unless you want to implement nodes for "any content" which i think is bad for performance and developing.
Quote:
What you did propose however was using 2 files:
1 - One file for type casting and methods
2 - One file for translations
I just thought it would be good standard to separate translations from functions (I should save the file contain translation in utf-8 without BOM but i can save the file contain functions in any standard format) but we can wrote translations and methods in fa.php as you proposed.
Quote:
The only problem I see with your propose is that a pt_PT/XoopsLocale cannot extend a pt_BR/XoopsLocale
yes. you are right.
I think it is possible with your proposal.(if we dont follow any standard and let users to do what they want)
Just i dont know what will happen on performance when we extend such a number of classes?
here:
1- en extends XoopsLocalAbstract
2- pt_BR extends en (translation + functions)
3- pt_PT extends pt_BR (translation + functions)
4- XoopsLocale extends pt_PT
about multilingual XOOPS:
Our only problem with the old system is the limited space in the field and we have this issue only in "title fields" not "text fields"
eg: i never run out of space in a news body/post body. i always have issues with news titles/ forum names/ categories,...
So I think nodes for text fields will not solve anything regarding multilingual unless you want to implement nodes for "any content" which i think is bad for performance and developing.