[Francois]

Hi,

My App was supporting multi-language using the Qt way.

Since upgrade to 2.10.0, it’s not working anymore.

 

2 questions:

1/ It seems the ChickenOutbreak demo you provided is not correct. The only reference to “translation” is commented, and no other example to multi language logic. Is it normal ?

2/ I am making an App, not a Game. In your doc, you wrote “How to Make a Multi Language App or Game with Felgo”. Do I need to declare a GameWindow instead of App to get access to translation logic ?

 

Many Thanks for your help.

 

Best Regards.

 

F.

[Francois]

Hello,

Finally, I made it work again.

settings.language is also working with App ( Qt Creator doesn’t recognise it, but it works ).

My mistake was: before, I managed translation files using DEPLOYMENTFOLDERS.

Now, with the Felgo integrated system, I have to put the *.qm files in the QRC ressource system.

It’s not very clear in the doc, but it’s working as expected.

Best Regards.

 

F.

[AlexFelgo Team]

Hi Francois,

Glad you found a solution. We will add a hint to the documentation and to Qt Creator auto-completion that this also works with the App component. Regarding deployment folders, did you test that on macOS and iOS or only on one platform?

Thanks,

Alex

[Francois]

Hi Alex,

 

I tested it on MacOS and iOS.

If *.qm files are in the QRC, it’s working fine.

 

Best Regards.

 

F.

[GüntherFelgo Team]

Hi Francois!

We tested the translations again and they should work with both DEPLOYMENTFOLDERS and the QRC system.
It’s important that the translation files are placed in the qml/translations directory of your project though.

If you still experience this issue, can you prepare a minimum example with a setup similar to your project that produces the error?
Please send it to us at support@felgo.com then so we can have a look why DEPLOYMENTFOLDERS don’t work in that use-case.

Best,
Günther from Felgo

[Francois]

Hello Günther,

 

thanks for the tip.

Initially, my translation path wasn’t in qml/, that’s why DEPLOYMENTFOLDERS didn’t work.

Now, it’s working as expected.

Thanks again for your help.

Best,

F.