Update (14 September 2016): A month after I wrote this, RoboVM announced that they were winding down. I already had a (free) license, which is good until April 2017, but if you need a new one, you’re out of luck.
Update (14 September 2016): A month after I wrote this, RoboVM announced that they were winding down. I already had a (free) license, which is good until April 2017, but if you need a new one, you’re out of luck.
LibGDX has decent localization support
via a bundle of .properties files, for example:
== strings.properties ==
app_name=Confirmation App
confirmation=Are you sure?
== strings_en_UK.properties ==
confirmation=I'm terribly sorry to bother you, but would you please be so kind to confirm your certainty on this matter?
== strings_nl.properties ==
confirmation=Weet u het zeker?
However, LibGDX doesn’t help you to create those files. It can be onerous to
create them and keep them in sync. Both Eclipse and IntelliJ have features for
this, but of course your translators won’t be using either of these. This is
why I came up with a simple way to generate these .properties files from a
spreadsheet (via CSV export). The expected input format is very simple (just a
column per language) and is fully described in
the README.