14
Quote:
Any details on that? We had the discussion about xLanguage, and I was curious if this is an approach that we could use in the core?
A post long ago I was for the theory, that a multilingual functionality mostly has to be done at module level. There are parts of the core that have to be re-written anyway if multilang has to be in.
To test the multilang feature of debaser I installed xlanguage, because it is very simple to handle. The only thing debaser is now doing (if wanted), is to scan the installed languages and prepare the xoopsform with extra fields dynamically created from that information. So you can enter the language specific information. If the multilang feature is not used, the language used in xoopsconfig goes anyway to the database to make a switch later on easier. debaser has now an extra database table only for holding the text. I combined the table for files AND categories.
What I found extremely difficult was to use XOOPS standard functions for that purpose, which IS impossible. So I tweaked some of them. Some pros with more php experience will probably laugh at my code, but I did best as I can. In the best case it will inspire them, in the worst case give them a good laugh.
