“translate scheme”

How do I translate the following Objective-C code into Swift?- (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification{

I've been working on an app that uses the new RoomPlan API and I'm looking for a way to translate the Scan Guidance or User Instructions that are overlayed on the RoomCaptureView when the user is scanning a room. Instructions like Move device to start and Move further away are in English but I'd like them to be in Dutch in my case. I can't seem to find a way to provide translations to these instructions myself and setting the device region or language doesn't seem to change anything. Is this even possible currently?

How will I be able to translate location purpose strings? Will it use InfoPlist.strings, or Localizable.strings? I assume that the purpose key will not be shown to the user. If I have my Info.plist set up as such: <key>NSLocationTemporaryUsageDescriptionDictionary</key> <dict> <key>Purpose1</key> <string>Purpose1TranslatedPhrase</string> <key>Purpose2</key> <string>Purpose2TranslatedPhrase</string> </dict> Should my InfoPlistStrings file look like?: Purpose1TranslatedPhrase = We use your location to do a thing; Purpose2TranslatedPhrase = We use your location to do something very different; Thanks

Every time I submit a new iOS build, I need to switch to each supported language and paste an update about what's new. This takes so long! Is there any way to speed up the process? Google Play translates everything automatically; why doesn't Apple do that? I hate to completely remove support for most languages but I feel like I must sacrifice user experience due to App Store Connect design.

We developed a Default Translation App following the guide: https://developer.apple.com/documentation/translationuiprovider/preparing-your-app-to-be-the-default-translation-app. However, when submitting to App Store Connect, we encountered the following error: No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found in extension Info.plist . When we attempt to add this key to the Extension's Info.plist, Xcode displays an error: xxx defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.public.translation-ui-provider .

I came across a useful repo on GitHub: https://github.com/GianniCarlo/DirectoryWatcher/blob/master/Sources/DirectoryWatcher/DirectoryWatcher.swift self.queue = DispatchQueue.global() self.source = DispatchSource.makeFileSystemObjectSource(fileDescriptor: descriptor, eventMask: .write, queue: self.queue) self.source?.setEventHandler { [weak self] in self?.directoryDidChange() } self.source?.setCancelHandler() { close(descriptor) } self.source?.resume() How do I translate this to OC version? I have an app that was written in OC and I plan to incorporate this directory watcher into the project.

Is there a built-in CLI program capable of listing all processes on an M1 device with an indicator showing which are running translated x86_64 binaries (Rosetta 2) vs. native arm64? I'd prefer something I can do from the command line, but I don't see anything obvious in the man pages for top or ps. Activity Monitor does have an Architecture column, but I end up spending a lot of time in terminals and would like something I can access easily from there. Alternatively, a CLI program capable of determining whether any given PID is translated would be sufficient for quick troubleshooting.

Returns NSView but constructed as NSTextField ... How does this translate into Swift ? ...https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/TableView/PopulatingView-TablesProgrammatically/PopulatingView-TablesProgrammatically.html- (NSView *)tableView:(NSTableView *)tableView viewForTableColumn:(NSTableColumn *)tableColumn row:(NSInteger)row { // Get an existing cell with the MyView identifier if it exists NSTextField *result = [tableView makeViewWithIdentifier:@MyView owner:self]; // There is no existing cell to reuse so create a new one if (result == nil) { // Create the new NSTextField with a frame of the {0,0} with the width of the table. // Note that the height of the frame is not really relevant, because the row height will modify the height. result = [[NSTextField alloc] initWithFrame:...]; // The identifier of the NSTextField instance is set to MyView. // This allows the cell to be reused. result.identifier = @MyView; } // result is now guaranteed to be valid, either

If I apply a translate transform inside a RealityKit.System update function - then in subsequent calls to update the value of the translation, SIMD3 has changed somehow. Why does it change? func update(context: SceneUpdateContext) { entity.move(to: Transform(translation: SIMD3(0, 0, -2)), relativeTo: nil) Next frame in update and print(😬 (entity.transform.translation)) Displays: translation: SIMD3(0.0, 0.2, -0.79999995) I'm missing something, hopefully obvious!

Hello, everybody. I'm Mauricio Paternina, an aspiring iOS Developer from Colombia. I have a strong interest in translating the Apple Developer Documentation into Spanish for two reasons: on one hand, I'd be able to dive deeper into the documentation itself and cement my knowledge, and on another hand, non-English speakers will be able to navigate and consume the contents of the Documentation, thus, reaching a wider audience. I'm currently the owner/maintainer of an ongoing effort to translate The Swift Programming Language book into Spanish as well. You can check the live site at https://swiftbook.es/. The site has been accepted by The Swift.org Working Development Group as the official Spanish translation and it's currently linked on their website. Back to my initial point, I'd tried reaching out to all possible channels to get guidance on how to request or proceed with this, or at least to know if this is even possible/allowed by Apple and I've found myself with no other clue than

I have an application that binds a menu item to trigger on ⌘]. When I set the US input source, I press ⌘] in order to trigger that item. However, when I switch the input source to QWERTZ (German), the trigger changes to ⌘Ä automatically by the OS. It seems to translate keystrokes for different input sources. The problem is that I also render the keybindings in a window in my application, and my application is not aware of this translation. Furthermore, I have other key shortcuts in my application which are not bound to menu items, and I want to make sure those get translated too. Does AppKit expose a way to lookup what a keystroke will be when MacOS translates it, i.e. lookup ⌘Ä from ⌘] when the current layout is QWERTZ? I can't find anything in Apple's docs. I tried converting a character to virtual key code based on the US layout and then mapping it back to a character based on the QWERTZ layout. That doesn't seem to be the same b/c that ends up converting ] to + instead

Hello I've been trying to build our existing iOS 14 app using Xcode 13 beta 5, and though it was working perfectly before, when trying to display some of the views on our main page this exception is consistently raised when trying to apply a snapshot on a UITableViewDiffableDataSource: Must translate autoresizing mask into constraints. looking online it seems that in previous Xcode betas have had this issue in relation to table view cells. Has anyone else been seeing this when trying to build with iOS 15? Thanks

I'm not sure if this is user error, if there's something else happening here, or if this is the expected behavior.I've got an app that we've translated into Japanese. The in-code localized strings are handled using the NSLocalizedString(_ key:, value:, comment:) function without a base langauge version of Localizable.strings.The XLIFF we submitted had the synthesized Localizable.strings values and the translated version we received back was fully popuplated. Importing that XLIFF created the Japanese version of Localizable.strings (this is our only translation at this point, so this is the only version of the file we've got.Now, when I try re-exporting the Japanese translation (to pick up new strings, etc), the exported XLIFF doesn't contain the existing translations for Japanese. Every entry in the Localizable.strings section is untranslated. As far as I can tell, evey other file's section contains the current translations.I wasn't expecting that and it seems like

We developed a Default Translation App following the guide: https://developer.apple.com/documentation/translationuiprovider/preparing-your-app-to-be-the-default-translation-app. I have already configured everything that needs to be configured according to the document, but there is still this problem

My app has the Text views that display the value of variables. Below are two sample pieces of code and the String Catalog (Localizable.xcstrings) entries created when app builds: (1) Code: Text([ (var1) ]) Key: [ %@ ] Default: [ %@ ] Spanish: [ %@ ] (2) Code: Text((var2) - (var3) - (var4)) Key: %@ / %@ / %@ Default: %1$@ / %2$@ / %3$@ Spanish: %1$@ / %2$@ / %3$@ Each of the 4 vars have a discrete number of known possible values. How do I enter the possible var values and their associated Spanish translations in the String Catalog?