Emulator Issues #491
closed
GUI language support
Added by psykauze over 15 years ago.
0%
Description
I request for a multi-langage-support. This will be an interresting
enhancement. I'll search files to be modified for this.
Updated by
Updated by Anonymous over 15 years ago
gnu gettext can be used with wxw, but i've heard that future versions of wxw will
make internationalization easier/better. Also, we really shouldn't bother until
activity on the gui settles a bit...
so maybe when a new version of wxw is out, and at least after the plugin revamping is
done.
But don't get your hopes up...
Updated by psykauze over 15 years ago
I think, you will need configure Wx::Locale in DolphinWX::main for gui translations.
Gettext is for commandline translations.
Updated by
Updated by lpfaint99 over 15 years ago
Issue 676 has been merged into this issue.
Updated by lpfaint99 almost 15 years ago
Issue 1507 has been merged into this issue.
Updated by beltza.nihongo over 13 years ago
Maybe we can use this solution for language support, everything is there :
http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/samples/internat/
I think its the fastest way to translate it without modify many things
example :
We have a sentence on mainMenu.cpp
file_menu->Append(wxID_ABOUT, _("&About..."));
On the language folder, specially french for example we have :
trunk/.../lang/fr/mainMenu.po
Inside we have
#: mainMenu.cpp:number_line
msgid "&About..."
msgstr "&A propos..."
mainMenu.cpp goes with mainMenu.po so it can be added easier.
maybe another issue must be added, for example creating a new option
Options>Configure...>General>Language> {choose here} > restart Dolphin Emu
Updated by BhaaL over 13 years ago
- Status changed from Questionable to Accepted
That sample app looks pretty easy, and since we have most strings in _(...) anyways, it probably wouldnt be much of a deal to add i18n stuff using the wx-way.
However, I see two ways of doing this: one thats quick in first place but requires more maintenance; and one that takes more time, but should be less resource-intense later on.
Both cases need the initialization stuff added, but in addition:
- Keep stuff as it is now, and translate based on the already present strings. Pro: Already in place, no(t much) work needed. Con: if a string changes (typo, or change in functionality; think of tooltips), we have to change both source and all translations.
- Replace strings in source with resource keys. Being a C# Guy, its natural to me, but it might not appeal to everyone. Pro: typos just affect the given language file, not everything. Cons: Takes time to rework, and if no fallback mechanism is im place (like, default is english, show that if nothing matches; I don't know if wx can do that) the GUI will look odd.
Any opinions on whether we should go with 1 and just screw the label changes, or whether we should choose 2 just to be on the safe side?
Updated by BhaaL over 13 years ago
- Status changed from Accepted to Work started
Seems easy enough, gonna give it a shot.
Updated by BhaaL over 13 years ago
- Status changed from Work started to Accepted
Aww crap, other than nakee's rants on IRC, we can't easily translate PanicAlert and such. On hold again =/
Updated by BhaaL over 13 years ago
You heard nakee on IRC and his issues with doing it.
The main problem to me is the fact that PanicAlert, PanicYesNo etc. are not using any wx infrastructure, so they cannot be translated as easily as the rest of the GUI.
Changing that fact is dependant on other stuff that has to be discussed internally.
Updated by beltza.nihongo over 13 years ago
I made another patch updates for r6726
built and work fine for me
- remplaced some wxT() and _T() to _()
- small cleaned up some comments
Thanks
Updated by nakeee over 13 years ago
Whoever submit this patch, please do it only if you are willing to invest the time and effort to maintain the language support. And to make sure it can work well on several languages (That might be quite some juggling even if you do not include bidi support)
Updated by beltza.nihongo over 13 years ago
Here is a small part of .po translated (french)
I didn't do whole cause i've soon to go working.
and yes i assume to invest my time and effort to maintain updated language files.
Updated by nakeee over 13 years ago
Thanks, But I was talking about the code not the translation per se. :)
Updated by skidau over 13 years ago
- Category set to ui
- Operating system N/A added
Here is some preliminary code that implements English and French. On my PC, there is a 5 second delay on opening the config dialog as the "catalog" of the locale is added. The delay can be made to occur once per session of Dolphin. I am not sure if there is a way to reduce or hide the delay. We could skip initializing language support if the default language (English) is selected, but the delay would still occur if other languages are chosen.
To install it, copy the "fr" directory to the dolphin installation directory, at the same level as Plugins, Sys and User. The .mo file is used by dolphin. The .po file is used by POEdit to add translations.
Updated by glennricster over 13 years ago
Here is another version. Probably similar to skidau's but I don't see the five second delay. May just be my computer.
Updated by zantezuken over 13 years ago
- No translation strings for
-> "Show About dialog"
-> "Quit this program"
-> "Slot A", "Slot B" etc on Gamecube tab
-> "Browse" on Patchs
-> "All GC/Wii images" (Browse on Patchs) or Open from File
-> "Browse, WINDOW TITLE" in MC manager dialog
-> "Name, Creater, Notes" in Cheats Manager (Gecjo). Tho, those strings DO exist in the POT. - No way to translate filetype drop-down menu in the Open dialog
- No way to translate pop-up messages (panicAlert and such.)
- "Size" column has fixed size and can't be properly translated
Updated by zantezuken over 13 years ago
Dolphin GCPad Configuration: many things can't be translated as well. The dialog window title, "Main stick, C-Stick, Pad %i", etc...
Updated by jackycola over 13 years ago
I expirimented with german translation (updated files in forum thread) and it seems as if the video plugin settings are not shown translated tough there are strings for those.
Updated by zantezuken over 13 years ago
The ISOProperties dialog has "Distance Alpha Pass" option. In Video plugins it's called as "Dest. Akpha pass" (destination?). Can someone correct all this stuff so it could be less confusing and translatable at last?
Updated by skidau over 13 years ago
- Status changed from Accepted to Work started
Updated by MofoMan2000 about 13 years ago
Yeah, this should be marked fixed, when I look at the Spanish translation there are a couple strings that still need to be translated but I think as long as it's maintained then this is working.
If those strings simply lack translation in the PO file itself I can probably pull that off too. If it's a deeper problem (PANIC! alerts were mentioned above) then it probably needs to be dealt with.
Updated by NeoBrainX about 13 years ago
- Status changed from Work started to Fixed
Updated by glennricster about 13 years ago
I am going to go ahead and mark this as fixed. The code aspect of things at least are pretty well set up. There are a few minor issues, but I think they already have their own issues. The quality of translations is not a reason to keep this issue open. That will be an eternal issue.