Internationalisation Topic is solved

If you are using the main C++ distribution of wxWidgets, Feel free to ask any question related to wxWidgets development here. This means questions regarding to C++ and wxWidgets, not compile problems.
gtafan
Earned some good credits
Earned some good credits
Posts: 143
Joined: Wed Mar 29, 2017 9:52 am

Re: Internationalisation

Post by gtafan » Tue Nov 06, 2018 2:38 pm

ONEEYEMAN wrote:Hi,

Can you do that or you have trouble finding where it is being done?

Thank you.
That´s exactly what I am tallking about all the time. I need to find where it is done.

ONEEYEMAN
Part Of The Furniture
Part Of The Furniture
Posts: 3276
Joined: Sat Apr 16, 2005 7:22 am
Location: USA, Ukraine

Re: Internationalisation

Post by ONEEYEMAN » Tue Nov 06, 2018 3:29 pm

Hi,
Run the samplpe thru the debugger and see where it is initialized.

Thank you.

gtafan
Earned some good credits
Earned some good credits
Posts: 143
Joined: Wed Mar 29, 2017 9:52 am

Re: Internationalisation

Post by gtafan » Wed Nov 07, 2018 12:56 pm

ONEEYEMAN wrote:Hi,
Run the samplpe thru the debugger and see where it is initialized.

Thank you.
Sory, but this makes everything even more complicated, have no idea about that debugger stuff. I din´t even have the debug version ofwxWidgets.

ONEEYEMAN
Part Of The Furniture
Part Of The Furniture
Posts: 3276
Joined: Sat Apr 16, 2005 7:22 am
Location: USA, Ukraine

Re: Internationalisation

Post by ONEEYEMAN » Wed Nov 07, 2018 3:36 pm

Hi,
This is a complete failure on your side.
Especially if you just starting - always start with the debug build.

Now you will have to waste extra time and create a debug build of the library.

Thank you.

gtafan
Earned some good credits
Earned some good credits
Posts: 143
Joined: Wed Mar 29, 2017 9:52 am

Re: Internationalisation

Post by gtafan » Thu Nov 08, 2018 3:08 pm

ONEEYEMAN wrote:Hi,
This is a complete failure on your side.
Especially if you just starting - always start with the debug build.

Now you will have to waste extra time and create a debug build of the library.

Thank you.
Not going to create that debug stuff, as it´s complete useles for me. It´s easier to write my own translation frameworck, then that anoing and complicated debug stuff.
I know, that writing own translation frameworck is really not easy, but wanted to show the complexity of that debug stuff.

ONEEYEMAN
Part Of The Furniture
Part Of The Furniture
Posts: 3276
Joined: Sat Apr 16, 2005 7:22 am
Location: USA, Ukraine

Re: Internationalisation

Post by ONEEYEMAN » Thu Nov 08, 2018 3:34 pm

Hi,
Out of curiosity - is you program build in Debug or Release mode?

Thank you.

gtafan
Earned some good credits
Earned some good credits
Posts: 143
Joined: Wed Mar 29, 2017 9:52 am

Re: Internationalisation

Post by gtafan » Fri Nov 09, 2018 11:47 am

ONEEYEMAN wrote:Hi,
Out of curiosity - is you program build in Debug or Release mode?

Thank you.
Release, what else. Always using Release only.

gtafan
Earned some good credits
Earned some good credits
Posts: 143
Joined: Wed Mar 29, 2017 9:52 am

Re: Internationalisation

Post by gtafan » Fri Nov 09, 2018 12:59 pm

After hours of reading documentation and triing diferent stuff, looks like I finaly solve the problem:

Code: Select all

wxTranslations *t=new wxTranslations();
t->SetLanguage(lng);
wxLocale::AddCatalogLookupPathPrefix(".");
t->AddCatalog("translations");
wxTranslations::Set(t);
lng is the int value of the language. This code I use at the begining of MyApp::OnInit().

Post Reply