Localization doesn't work on iOS device.

Solar2D General Questions/Discussion
#21

It returns “en” for me.   What device are you on?  Do you have any locales added to your build.settings?  Are you  building for Android or iOS?  What version of Corona SDK are you running?

#22

Hi Rob. Here are the answers:

  • iPhone 4 (6.1 firmware)

  • Windows 7 64bits

  • Corona 2013.1076 (2013.4.3).

  • iOS target.

  • Yes. I have both “en” and “es” added to the build.settings.

The best thing is that the same code works like a charm in my OSX… Weird thing…  :wacko:

Thanks in advice.

#23

I have a couple of things… How are you building for iOS on Windows?  I think you have to spell out the names in your build.settings.  Can you post it?

#24

First of all, apologise for that misunderstanding. I am not building for iOS on Windows. I mean, I started to develop the app on Windows and then I load that code into my Mac for the iOS build.  :slight_smile:

Secondly, I have this configured in my build.settings:

CFBundleLocalizations = { "es", "en" },

And this is the configuration for the localized texts (localized.lua):

local localized = { ["Menu"] = { ["es"] = "Menu Principal", ["en"] = "Main Menu" }, } return localized

Lastly, this is the way I load every localized text:

local localized = require("localized") language = system.getPreference( "ui", "language" ) [...] local message = localized["Menu"][language] [...] local t = display.newText(message, img.x + 20, img.y - 14, font, 22)

Thanks,

Cristian.

#25

You have to spell out the names:

         CFBundleLocalizations =
         {
            “English”,
            “French”,
            “German”,
            “Italian”,
            “Spanish”,
            “Hebrew”,
            “Hindi”,
            “Chinese”,
            “Portugese”
         },

#26

Still doesn’t work on Windows… I don’t know what I’m doing wrong.  :frowning:

Here’s all the code just in case (is not organized and not optimized, etc, etc, just for testing purposes).

bit.ly/14IfoRX

Thanks in advice. Anyway is working 100% ok on OSX.

#27

I don’t know how you’re trying to build for device on Windows for iOS.  You have to be on a Mac with XCode.   This localization is iOS only, 

#28

No, no, I am testing in the Simulator on Windows (obvioulsy) and building for iOS on my home’s macBook. Anyway, don’t worry and thanks for the help.

Regards. 

#29

Well the build.settings iphone section only applies to apple devices, not the simulator.  I guess that those functions should return something, but because windows is windows, that feature might not be available.  Let me ask the engineers about this.  Maybe it’s something we can add but there are just some operating system differences that may prevent this from working.

#30

Hi, 

Great tutorial, I also followed the link and everything works but one thing…

I don’t know if it’s a new change in the API or something but now the line:

language = system.getPreference( "locale", "language" )

returns ‘1033’ (insted of ‘en’).

Any suggestions? Is there any way to get ‘en’ instead of Country codes?  :huh:

Thanks,

Cristian.

#31

It returns “en” for me.   What device are you on?  Do you have any locales added to your build.settings?  Are you  building for Android or iOS?  What version of Corona SDK are you running?

#32

Hi Rob. Here are the answers:

  • iPhone 4 (6.1 firmware)

  • Windows 7 64bits

  • Corona 2013.1076 (2013.4.3).

  • iOS target.

  • Yes. I have both “en” and “es” added to the build.settings.

The best thing is that the same code works like a charm in my OSX… Weird thing…  :wacko:

Thanks in advice.

#33

I have a couple of things… How are you building for iOS on Windows?  I think you have to spell out the names in your build.settings.  Can you post it?

#34

First of all, apologise for that misunderstanding. I am not building for iOS on Windows. I mean, I started to develop the app on Windows and then I load that code into my Mac for the iOS build.  :slight_smile:

Secondly, I have this configured in my build.settings:

CFBundleLocalizations = { "es", "en" },

And this is the configuration for the localized texts (localized.lua):

local localized = { ["Menu"] = { ["es"] = "Menu Principal", ["en"] = "Main Menu" }, } return localized

Lastly, this is the way I load every localized text:

local localized = require("localized") language = system.getPreference( "ui", "language" ) [...] local message = localized["Menu"][language] [...] local t = display.newText(message, img.x + 20, img.y - 14, font, 22)

Thanks,

Cristian.

#35

You have to spell out the names:

         CFBundleLocalizations =
         {
            “English”,
            “French”,
            “German”,
            “Italian”,
            “Spanish”,
            “Hebrew”,
            “Hindi”,
            “Chinese”,
            “Portugese”
         },

#36

Still doesn’t work on Windows… I don’t know what I’m doing wrong.  :frowning:

Here’s all the code just in case (is not organized and not optimized, etc, etc, just for testing purposes).

bit.ly/14IfoRX

Thanks in advice. Anyway is working 100% ok on OSX.

#37

I don’t know how you’re trying to build for device on Windows for iOS.  You have to be on a Mac with XCode.   This localization is iOS only, 

#38

No, no, I am testing in the Simulator on Windows (obvioulsy) and building for iOS on my home’s macBook. Anyway, don’t worry and thanks for the help.

Regards. 

#39

Well the build.settings iphone section only applies to apple devices, not the simulator.  I guess that those functions should return something, but because windows is windows, that feature might not be available.  Let me ask the engineers about this.  Maybe it’s something we can add but there are just some operating system differences that may prevent this from working.