It would be nice to hook together the built in vBulletin language system with vBET. This way there is more control over the phrase translations, some things don't have to be run through Google to be translated, and more human translations will exist and be more accurate.
So for example, if a user selects the Spanish language, all posts and other text are run through vBET and all other phrases, if they exist, are handled by the Spanish vBulletin language pack.


Reply With Quote
We also already thought about it - just vBET 4.x consumes most of time right now. But we will release next vBET 4.x soon and go back to full support of booth vBET 3.x and 4.x lines. We where already thinking about it and we have even possible solution (not tested). This solution is to change value of vB parameter holding language code for translated pages. This will make vB taking already translated phrases. One issue - we will have to change all phrases from other lanuages than forum language and put it inside of not translated area. And this should be done inside of Database. So this is theoretical solution. Which is on our TODO list
