Version 4.5 will have better capability for localization. The key is being able to specify window text of a view widget without changing the name of the node, since flexscript logic will often use paths by name. So 4.5 will be able to do that for any type of widget. Once that is available, the task for localization is to create a user library that represents a "diff" from regular Flexsim to the localized version, or in other words, the user library would have some type of script that would go through a table of changes, and make those changes to the project/view. Then you would save off that project and view and create an install of that specific project and view. Even then, however, code changes that print messages, etc., would be more difficult. So you could get a long way with 4.5, probably 95% of the way there, but you wouldn't be able to do absolutely everything. The reason you would use a user library is because it minimizes the extra work required to update a new Flexsim release.
Right now Flexsim doesn't see it as economically viable to do a lot of localization, because of the small size of the simulation market. Localization, and subsequent maintenance of the localization, would therefore be the responsibility of the distributor, with our help of course.
I've talked with Jorge, our Mexican distributor, about localizing to spanish. Given that 4.32 doesn't have all the right capability, we decided that Jorge could simply change tooltips to be in spanish. This avoids the issues with sizing the localized text correctly, and it minimizes the work the Jorge has to do. I created a user library with a GUI that lets him quickly change tooltips of different widgets, and then saves those changes to a user library.
|
