With gnu gpl licensed gettext, there would be the possibility for other languages.
Because of the structure with po and mo files, translation and help by users is quite sure.
Logged In: YES
From reading the gettext docs I am left with the impression that GNU's gettext functionality does not suit MS rc files (which burns in the strings and the text position & length details at compile time). As the vast majority of VW's interface (and therefore translation work) is in the rc files I don't see what gettext would do without have to completely change the gui interface to a different toolkit.
Have I missed something?
Give that MS rc files support multiple locals why would I not simply use MS's own solution to this problem?
Logged In: YES
MS rc-files are possible and usefully, if most of the strings are already there.
Whatever way is chosen, language support would be an usefully, kind of simple feature, which would make it possible to have more users.
I think it's easier for non-programmers to translate po-files (for example with poedit) then rc-files, but I'm not sure about that.
Having said that I don't know what MS's own solution is - this is an area that none of the current VW developers have any experience in which is why no progress is being made on this issue...
Given the cronic shortage of available development time I think we will need a windows developer with this skill set to come on board to create the foundation of multi-language support in VW. Any takers?
Log in to post a comment.