11 Replies
      Latest reply: Jan 10, 2017 1:03 PM by eskimo RSS
      jobvite_bhavik Level 1 Level 1 (0 points)

        Hi All,

         

        We are in process of localizing our application and we wanted to perform some pseudolangugae testing on device. Xcode currently provides a way to test "Double Length Pseudolanguage" and "Show non-localized strings" options under a scheme. And these options work perfectly when I run the application in simulator. Is it possible to have this enabled on the app running on device?

         

        We are using these settings from Scheme --> Edit Scheme --> Run --> Options --> Application language and Localization Debugging. But these setting seem to work only when we run the application in simulator. Is there a way to enable these on device?

         

        Regards,

        Bhavik

        • Re: Double Length Pseudolanguage and Non-localized string on device
          KMT Level 8 Level 8 (7,670 points)

          It's just meant to be a stress test, and I think it's hit/miss when targetting a device, so in this this case, you may need to settle for sim testing only.

          • Re: Double Length Pseudolanguage and Non-localized string on device
            eskimo Apple Staff Apple Staff (6,470 points)

            Let’s split this up.  Are you having problems with:

            • Show non-localized strings

            • Double Length Pseudolanguage

            • The combination of both

            I just did a quick test of Double Length Pseudolanguage and it worked on my device.  It was a really simple test:

            1. Xcode 8.2 on macOS 10.12.2 targeting iOS 10.1.1.

            2. Created a new project from the Single View Application template.

            3. Added a label in the UI and then constrained it to the centre, leaving the text as the default “Label”.

            4. Editing the scheme to Double Length Pseudolanguage.

            5. Ran it on my device.

            The label displays as “Label Label”.

            One thing I missed pointing out was that I am compiling and building the application through command line and not through Xcode. Does it matter? I guess it would, right?

            If you’re building it from the command line, how are you installing it?  These options don’t affect the built code, but rather set environment variables to enable the feature.  Thus, if you run from outside of Xcode you won’t get the feature.

            Share and Enjoy

            Quinn “The Eskimo!”
            Apple Developer Relations, Developer Technical Support, Core OS/Hardware
            let myEmail = "eskimo" + "1" + "@apple.com"

              • Re: Double Length Pseudolanguage and Non-localized string on device
                jobvite_bhavik Level 1 Level 1 (0 points)

                Thanks Quinn and KMT. I understand the problem better now. I was trying to build the application using command line and install it using over the air installation or manually using iTunes. Since I was specifying these parameters inside a scheme and I was building a scheme I assumed that these parameters will be available when I install and run the application on device. But it is not the case since these parameters are environment variables injected by Xcode.

                 

                I was trying to setup a pseduo locale testing build (combination of Double Length Pseudolanguage and Show non-localized strings) on my Jenkins CI that my QA team can use to test different localization issues such as layouts, missing strings etc. And hence I was trying to build from command line and not via Xcode. But I guess that there is no way to enable these parameters when running application outside of Xcode.

                 

                Regards,

                Bhavik

                  • Re: Double Length Pseudolanguage and Non-localized string on device
                    eskimo Apple Staff Apple Staff (6,470 points)

                    But I guess that there is no way to enable these parameters when running application outside of Xcode.

                    You can do this if you’re prepared to build your app differently.  The basic strategy is:

                    1. Run your app from Xcode with the debug options you want.

                    2. In your app, dump the environment variables that got set by Xcode.  You can use the standard C environ global variable for this.

                    3. Modify your app so that, right at the start of main, you set those same environment variables using setenv.

                    There’s two things to watch out for:

                    • You must set the environment variables before anything uses Foundation.  For most apps the start of main is fine.  However, if your app has code that runs at load time (the most common examples are C++ static initialises and framework init functions), things get trickier.

                    • In many cases these environment variables are not documented API.  It’s fine to use this approach as part of a debug build you ship to testers, but don’t use it for code you distribute to users.

                    Share and Enjoy

                    Quinn “The Eskimo!”
                    Apple Developer Relations, Developer Technical Support, Core OS/Hardware
                    let myEmail = "eskimo" + "1" + "@apple.com"

                      • Re: Double Length Pseudolanguage and Non-localized string on device
                        jobvite_bhavik Level 1 Level 1 (0 points)

                        Thanks Quinn for the reply. I would use a bow emoticon if there was one.

                         

                        Regards,

                        Bhavik

                        • Re: Double Length Pseudolanguage and Non-localized string on device
                          SunnyLlama Level 1 Level 1 (0 points)

                          I have the same issue- but I need/want to be able to send a debug build out via TestFlight. XCode has no ability to use/create an imaginary language. So for example I can't use Klingon for a test language, or insert my own .strings file for a language that show "**KEYNAME**" for a strings key, instead of the actual translated phrase. My translation team is asking for this kind of functionality (we are a global company). We can make sure all the layouts are properly translated this way.

                          We have added some debug code to override the system language (it's a little hacky, sure) but with it we could debug all of our strings easily, if there was a way to even include a fake language. But we cannot.

                          I realize this is a bug report, but wanted to add my comment to this topic.

                            • Re: Double Length Pseudolanguage and Non-localized string on device
                              eskimo Apple Staff Apple Staff (6,470 points)

                              I’m a bit confused as to what you’re trying to do here.  If you’re trying to engage the double length pseudolanguage mode in a TestFlight build, I recommend you try the the approach I outlined in my post of 28 Dec.  OTOH, if you just want to create a dummy localisation that happens to be very long, it seems like you could do that by picking an obscure language (one that none of your testers use) and putting your dummy localisation there.

                              Share and Enjoy

                              Quinn “The Eskimo!”
                              Apple Developer Relations, Developer Technical Support, Core OS/Hardware
                              let myEmail = "eskimo" + "1" + "@apple.com"