HiThe app under test is localized and internationalized. So when device language is changed, strings displayed on the app are changed.I am trying to write test cases that work independent of the current language, in order to achieve this some of the static text/button labels have to be localized for the element query to work correctly.How can we achieve this? If I try to have all the strings in an external file, the bundle created for UITesting for some reason does NOT include this strings file.Can someone please shed light on how to include non-code files into UI Testing bundle?I tried having the file named as .json, .strings. It does not work.ThanksNaveen

Hello or Iranqarahte-e in Ainu of Japan Aynu itah -itaq-k = language Those who use Japanese and Kotoeri there is a icon in the text menu in screen shot below.Ainu is written in Katakana アaイiヌnu　イiタtaㇰk = Aynu itah/itaq/k　or Roman =Aynu itah -itaq-k when using this setting you press A, i ,n ,u , keys it will convert into Katakana some Japanese prefer Katakana others prefer Roman the problem with Katakana it does not represent final letter and must use a special small letter or syllable kaカ , kiキ ,ku ク,ke ケ,ko コ.　i イ is ok and ta タ,but final ku ク is not ㇰk is used ,hence the conversion itah q are variations. that is the only support Apple has for Ainu.At present some Japanese and Ainu are trying to get J apanese I ndustrial S tandards to get it into the platforms then we need Apple i/OS/X dictionaries ,Siri, predictive writing text,Grammar spell checker Google translate,Google ermersion. there is a lot of Ainu ( mostly roman script ) written online mixed with Japanese ,this is mostly historical text and some blogs and dictionaries ( Ihave spent years researching books and online material )now we have an online dictionary http://ainutopic.ninjal.ac.jp/en/,but does not work on iOS. The main problem is the various dialects, syntax ,words ,spelling, pronunciation and natives speakers of Ainu language , now only a handful of bi-lingual Japanese and Ainu native speakers,they are very old most thousands of Ainu speak Japanese as first language and some a little Ainu are a few , Some book dictionaries and text ,bible written by Batchelor a near native speaker 60 years. last century. with the argument Apple may not support i/OS/X dictionaries ,Siri, predictive writing text,Grammar spell checker. Iaim to go further and like to have Ainu i/O S /X bi-lingual interface or Help tags on icons emoji and text on menu ,we point our mouse pointer and a yellow help tag pops up and shows the word in the bi -lingual ( if it is icon only) language of our choice. all text can be linked to an Apple bi- directional dictionary Japanese ( with furigana ) Ainu ( sometimes Ido not know the criteria for Help tags ,some are obvious Reader Show reader ! some icons + do not have help tags and where is the explanation ? and you can make the cursur big and you can not see the tags! so is that a solution ? apart from computer terms Ainu does not have language terms , as well we need to translate the teaching of code into Ainu code to protect the Ainu langauge in the future Ainu needs to be written on computer and collected as raw data for making a Google translate and dictionary and teaching writing and then Siri or speech software to do dictation and some way to read all the written ainu on the web. the biggest challenge is the Ainu grammar for a software writer- Ainu itah /eywanqe an ro . a simple sentence Let's use /speak Ainu !

Greetings allI have an app whose development language is French, which is also its base localization. I also localise it to English.The app makes use of both location services and the calendar.I have created an InfoPlist.strings file and localized both NSCalendarsUsageDescription and NSLocationWhenInUseUsageDescription.My problem is that, although the Base localization (French) of NSCalendarsUsageDescription is correctly used when requesting permission, I can only ever see the French text for NSLocationWhenInUseUsageDescription if I remove the key from the English version of InfoPlist.strings.Many thanks for any help you can give me.

Hi. iOS 10 has a new setting 'Temperature Unit'. Users can choose a temperature unit, independent of their Locale/Region.I had found this blog post, which explained how to get it's value: http://blog.timac.org/?tag=nslocaletemperatureunit. And it works great. I modified it a little bit so that it would be backwards compatible from iOS8 up to iOS10.However... When I submitted my app to Testflight, the app was rejected for the reason: "The app references non-public symbols in [app-name]: _NSLocaleTemperatureUnit"That's rather disappointing, because I know of no other way to find out what the user entered for this setting. I am 100% sure that users WILL change this setting, and then be disappointed that my app only looks at the region to determine if Celcius or Fahenrheit should be used.Is there any official solution for this predicament?Please check here what I did: http://stackoverflow.com/questions/39727075/determine-users-temperature-unit-setting-on-ios-10-celsius-fahrenheit

i used this link https://medium.com/if-let-swift-programming/working-with-localization-in-swift-4a87f0d393a4but dosen't work for everything like googlemaps and menui tried to use Localize-Swift but it didn't localized my storyboard

Hi everyone!I`m having an odd problem with localization. I localized my app to English and Brazilian Portuguese. They both work fine, except for the launch screen.It ignores completely my localization in Pt-Br. I have just a label on it with a loading message. I've tried both strings and storyboards files with no use. Only the english is loaded. Do you guys have any idea why this is happening?Thanks!Danilo

Does anyone from Apple read this thread?I wrote about missing CRH language code in Xcode in Bug Reporter a long time ago, which is not supported anymore.I've downloaded the beta of Xcode 11 but there is no changes compare with v10.Any ideas of why there is still no Crimean Tatar language among languages available for localisation?https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes

We format times in a localized way using the DateFormatter APIs.DateFormatter.localizedString(from: date, dateStyle: .none, timeStyle: .short)However if the result of this localization is say "22:00" VoiceOver just reads this out as "22". The VoiceOver user is given no indication that this numeric value is a time of the day.I've read online that one approach is to use DateComponentsFormatter and the spellOut unitsStyle e.g.let hourComponents = Calendar.current.dateComponents([.hour, .minute], from: date) cell.accessibilityLabel = DateComponentsFormatter.localizedString(from: hourComponents, unitsStyle: .spellOut)But again for a time "22:00" this reads out "22 hours". Sure if gives more context that this is related to time but it doesn't really indicate it is a time of the day i.e. it could be an interval (22 hours until something happens).We've trawled through the Apple documenation but we can't find anything that covers this.The best possible workaround we've found would be to force the accessibility label to be read out in 12 hour time i.e.let dateFormatter = DateFormatter() dateFormatter.setLocalizedDateFormatFromTemplate("hh:mm") accessibilityLabel =dateFormatter.string(from: date)that way it is clear to the user that it is a time of the day. Although this approach has the downside that ignores the user's preference of a 24 hour or 12 hour time display.The VoiceOver readout is handled perfectly in the Calendar app. It reads out "10 o'clock" and "22 hundred hours" in English and it is fully localized so for example it reads out "midi" for 12:00pm in French. It is possible that this is being done with private APIs though.So my question is, what is the recommended approach for formatting times for VoiceOver?

Hi there, The Call Directory Extension in Settings wasn't localized since iOS 13, and getting even worse in iOS 14 beta. In iOS 13, though not localized, the custom extension name was display as expected. In iOS 14, it showed only the bundle name which made no sense to general users. This is important to us to introduce our app to foreign countries. I also fired a feedback in Feedback Assistance but don't know when it will get fixed, so just raise the attention here.

I have a in-house framework that I share between the main app and the widget. The framework contains some localized strings. These strings show up in correct language in the main app but on the widget they only show up in English. I'm guessing the localized strings from the framework are not getting bundled in the widget extension. Anybody with the same problem?

When we try to add localized info (what's new, description, etc.) we get a whole bunch of errors: Japanese The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. Japanese Description couldn’t be saved because another field in this localization is invalid. Japanese Keywords couldn’t be saved because another field in this localization is invalid. Japanese Marketing URL couldn’t be saved because another field in this localization is invalid. Japanese Promotional Text couldn’t be saved because another field in this localization is invalid. Japanese Support URL couldn’t be saved because another field in this localization is invalid. Japanese What's New in This Version couldn’t be saved because another field in this localization is invalid. We have 2 versions of the app on the store, iOS & macOS. Both have the same name, because they're the same app. They predate the ability to add Universal versions of iOS/macOS apps. Could this be the cause of the error? We really don't want to have to change the name of either of them.

We noticed that all our new in-app purchases were approved (green dot) but not the localization content (yellow dot). So the customers are seeing the wrong name when managing subscription. Those items were approved more than a week ago but the localizations are still in review. Is anyone facing this issue?

I have an app in the app store which is free to download but has a few In-App Purchases. I am not allowed to sell in China and because of the In-App Purchases it doesn't appear in the Chinese app store. I would like to offer it for free there. Is there a way to do this with the same bundle-ID or do I have to create a separate app without any In-App Purchases for China?

We are developing application for Ios using Unity and struggling with adding localization for info.plist usage descriptions(NSCameraUsageDescription, NSMicrophoneUsageDescription, NSPhotoLibraryUsageDescription). Localization is added accordingly to the guide outlined here https://developer.apple.com/documentation/xcode/adding-support-for-languages-and-regions, but it doesn't work for us. On device with system language in Ukrainian we getting English localization. In project we added localization for Ukrainian and Russian. Any recommendations on resolving this issue?

Hi all ;-) I'm using SPM to create various libraries. So far, I only had to localize strings, so I added a Resources folder, some .lproj data and a defaultLocalization in my Package.swift file. Now I'd like to localize some images in the XCAsset catalog, but when I click on "localize" on my image, the only localization that is proposed is the defaultLocalization from my Package.swift file (if I change "en" to "fr", I now get a "French" localize option, but English has gone). How can I make Xcode aware of the supported localization inside my package ? Thanks.

I have translated my app into Bulgarian bg_BG and I am seeing that the 'д' character always shows up as 'g' as well as the 'т' character always showing up as 'm'. Both of these characters show up properly in the Russian ru_RU translation of the app. Does iOS show a different Cyrillic alphabet for Bulgarian?

Hi. I'm looking forward to using the new localization features as shown in 10221. Is there a version of String(localized: ) that uses a key that is separate from the user-facing string? This is my preferred approach even with short strings but becomes really important for long strings like what you might see for an explanation in a table view footer. And is there support for multi-line strings? Again, with a key? Many thanks.

How do I add a complete Gaelic dictionary without adding individual custom words? Thank you.

I am developing a SwiftUI based app (https://github.com/rsyncOSX/RsyncUI) which is localized to two languages, German and Norwegian. The development language is English. Running the app on a Norwegian macOS Montery works OK, the app shows the correct localization. Executing the app on an English macOS setup picks the German localization, and not the base localization which is English. And I don't know what causes the app to pick another language than English on a default English macOS setup.... I am experience this on macOS Monterey and Xcode 13, but also on macOS Big Sur and Xcode 12.5.1