Handle dynamic internationalisation across the ui. about mylibrelab HOT 7 CLOSED

I'll make a draft for the api and then we can decide whether it's worth our effort.

from mylibrelab.

Maybe I'm missing something here, but why wouldn't we just use the ResourceBundle class with properties files for the Strings?

from mylibrelab.

This issue is about how to handle dynamic locale changes during runtime. Resources will still be loaded using a ResourceBundle.

from mylibrelab.

Ah, I see. Apologies. I got a bit confused there 😄 .

from mylibrelab.

No problem. I have to admit I didn’t make it very clear that this is about dynamic changes in the first paragraph.

from mylibrelab.

I don't think we need to have dynamic locale changes, but I guess its neat.

I vote for the 3rd option.

from mylibrelab.

I'm guessing people aren't going to be changing language all that often. Would it not reduce the complexity to simply restart the application if the user changes language? I imagine this is something most people will only do once or twice anyway, as long as we remember their choice.

from mylibrelab.