Post not yet marked as solved
I tested again, the issue is about multiple targets instead of frameworks (although I wanted to ask something about internal frameworks too) I am adopting Mac Catalyst in our project. For reasons to include different frameworks between iOS and macOS apps, I setup one target for each. So this is where the issue starts... 1) Main app (iOS) exports to {Project}/en.lproj/Common.strings 2) Mac Catalyst exports to en.lproj/Common.strings I confirmed by removing the Mac Catalyst target to export.
Post not yet marked as solved
You have a few options. First, from your subprojects, you can pass the bundle argument to NSLocalizedString and pass the correct bundle ID. That will ensure it doesn't try to use the app's main bundle. You could simplify this by creating your own LocalizedString function/macro that automatically does this correctly. /// NSLocalizedString replacement for MyFramework. func MyFrameworkLocalizedString(_ key: StaticString, comment: StaticString) -> String { return Bundle(identifier: com.me.MyFramework)!.localizedString(forKey: (key), value: nil, table: nil) } If you go this route and define your own function, you'll need to add that function name to the Localized String Macro Names build setting. You can also specify custom table arguments to either NSLocalizedString or Bundle if you wish in order to customize the strings file that your string appears in, even within a single bundle.
Post not yet marked as solved
Hello. I have just localised my app into two new languages. This is my first attempt at localising, and from what I read, I should expect at least the same or greater amount of downloads/impressions. Everything regarding the app has been localised, such as screenshots, keywords, the main app etc. It's been three days since, and the impressions for unique devices has dropped to about a 1/3 the daily average. I don't understand why this would happen. The app has been localised by a native speaker, so the keywords should be alright, and even so, the app should be ranked normally with the English keywords. Has anyone else experienced something similar?
Post not yet marked as solved
The best-practice we recommend here is: Have your framework export a new macro / function ex: FWLocalizedString that calls NSLocalizedStringFromTableInBundle (Objective-C) or the sets the bundle argument in NSLocalizedString (Swift) to your framework bundle Use FWLocalizedString for all localized strings within your framework In your framework target, add FWLocalizedString to the Localized String Macro Names build setting Now, when you export for localization all FWLocalizedString calls will be extracted in the framework target—but not from the application or widget target.
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?
Post not yet marked as solved
I have my app localized for many languages, but I'd like to limit the available app languages to only a subset of those, because the content is not ready for all of them. So in fact the app is not yet localised in those languages. A better practice would be to only add a language when it is readily available. And release a new version. Did I miss something ?
Post not yet marked as solved
I have my app localized for many languages, but I'd like to limit the available app languages to only a subset of those, because the content is not ready for all of them. I don't want to delete localization files, because they contain some useful translations that I will use in the future. The only thing I was able to find and try out is this piece of code: class AppDelegate: NSObject, UIApplicationDelegate { func application( _ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? ) -> Bool { UserDefaults.standard.set([Base, pl, de, ru], forKey: AppleLanguages) UserDefaults.standard.synchronize() ApplicationDelegate.shared.application( application, didFinishLaunchingWithOptions: launchOptions ) return true } } but unfortunately it does not work. When I launch Settings of my app, I can still choose from about 20-30 languages that I have already some translations for.
Post not yet marked as solved
Hello! To be able to effectively analyze this problem, we’ll need to know what the Language & Region settings are for your users who encounter this problem. Can you ask them for that information, e.g. a screenshot of Settings > General > Language & Region (iOS) or System Preferences > Language & Region (macOS)?
Post not yet marked as solved
Hello, For some rare users, our app is only available in English, no matter what settings they used for their language (general settings and app settings). It seems to be for some random users, and we cannot reproduce it. We never had this issue before (the app is localized in 12 languages) We would love to have a clue or advice on this! Thanks
Post not yet marked as solved
Hi, what keyboard language would you be interested in? You can tell us by filling a request using the Feedback Assistant app on your phone when running a pre-release version of iOS, visit the website at https://feedbackassistant.apple.com , or on our website https://www.apple.com/feedback/
Post not yet marked as solved
Thanks. Is that documented somewhere?
Post not yet marked as solved
Indeed it's very annoying. Trying to solve this same issue for a few days already. Apparently the only solution is fall back to the old approach reacting on keyboard related notifications etc.
Post not yet marked as solved
When I try to convert date to Arabic language with below code & ar_AE language code, it does not work. let dateFormatter = DateFormatter() dateFormatter.dateStyle = .medium dateFormatter.locale = Locale.init(identifier: ar_AE) lblDate.text = dateFormatter.string(from: Date()) when we change the language code to _ar_OM_ or ar_SD or any other Arabic countries it works in iOS. let dateFormatter = DateFormatter() dateFormatter.dateStyle = .medium dateFormatter.locale = Locale.init(identifier: ar_OM) lblDate.text = dateFormatter.string(from: Date()) Tested on iOS 15.5 & 13.3, there is nothing related to iOS version. Request someone to help me to understand the reason why ar_AE code is not working while if I provide identifier ar it works perfectly & that would be great help if we can resolve this.
Post not yet marked as solved
Slushy snow. What Wikipedia refers to as Rain and snow mixed.
Post not yet marked as solved
Crikey, what have they done with our good old English Sleet?!
