Poll:Translation system
From DeSmuME
Revision as of 21:06, 7 April 2009 by 92.128.43.76 (Talk)
We need to decide what system we'll use for translating the Win32 port of DeSmuME.
Don't forget to add your name when voting! :P
Contents |
Multilingual resource file (current system)
Pros
- doesn't require making all the static textboxes dynamic in dialogs
Cons
- adding a new dialog or making a new translation is a pain
* your vote here
Gettext (like PCSX2)
Pros
- portable
- simple (you just have tu use gettext("string") instead of "string"
Cons
- dealing with the language names can be a pain
* your vote here
Resource DLLs (like iDeaS)
Pros
Cons
- same as the current system
* your vote here
Mini18n (by Guillaume)
Pros
- made to be portable: works on both linux and windows and should be easy to port to other systems
- made to be easily embeddable as a static library
- use somehow the same interface than gettext, translating a string is just a matter of using _("some string") instead of "some string"
- provide UTF-16 on windows with the _16 macro
Cons
- doesn't provide a way to translate resource files, so we would have to either find a way to handle the resource files or build the whole GUI "dynamicaly" instead of reading it from resource files
Votes
- Of course, I give my vote to my own system :) [Guillaume]
* your vote here
Other
* your vote here, alongside a description of your idea
Thank you for voting! :)
- <zeromus> one point: we may want to try and port some simple config windows to gtk. If we decide we like that, then we will want to have chosen a translation system that can work with it. I will try and do the gtk experiment soon. - <Luigi__> good luck then! :) btw, we shouldn't take this for an IRC channel :P