“translate scheme”

when I add a translation for ln, the result for 0.5 [ln] looks correct: But do I want to add localizations for the arithmetic function symbols? Are there specific arabic rtl versions in unicode for those too? I guess calligraphically it would make sense.

Thanks to both of you for putting me in the right direction.Sadly, my knowledge of the C langage is not deep enough to translate the code in swift.Is there a way to inplement the EvenBetterAuthorizationSample inside an application written in Swift? Is it possible to mix the code between C and Swift?

Please, may I ask you how can you say:we can only provide one app per client (translated, developer account)?Is there an offical Apple declaration for that or is all about your experience?Because am not sure about it at all 😢

Not sure.When you have multiple languages and need to export to xliff to give it to translate, it is much better to have a format as:Hello World = Hello World;andHello World = Bonjour;To know exactly what is to be translated.Anyway, could file an enhancement request.

Your app should have translate capabilities automatically if you use standard system views and controls. Otherwise, you have to be very careful with other companies' apps and services. You might not be legally allowed to use those services or data inside your own app.

The recommended approach here is to have separate InfoPlist.xcstrings files per target. Otherwise you would not be able to effectively translate the app name without every target having the same name. There is no setting for disabling extraction of CFBundleDisplayName from the Info.plist. Even if it wasn't in the String Catalog, Xcode would generate it again when exporting localizations to allow translators to translate it. The naming convention of InfoPlist.xcstrings is as follows: The Info.plist file (if you have one) should not be added to any targets but referenced by the Info.plist File build setting in the relevant target. The corresponding .xcstrings file should be added to the target. InfoPlist.xcstrings always works to refer to the strings for the Info plist (regardless of the name of the Info plist file and even if it is fully generated at build time). If a target's Info plist file is named CustomName.plist, then the xcstrings file may be named CustomName-InfoPlist.xcstrin

you can try with online translator, but it should be easy to do it by yourself.I am not on XCode presently, so I can just give you hints by translating line line by line, but cannot check it, so I am not completely sure of some syntax. But that should give you an idea.Start withvar formatter : NSNumberFormatterType:func textField(Autocompletion should let you find the appropriate method with shouldChangeCharactersInRange, with the parameters aTextField and stringvar TextFieldValue = aTextField.text + stringif range.length > 0 { textFieldValue = aTextField.text.substringToIndex(range.location) // check how substringToImndex must be called}if textFieldValue == { self.formattedLabel.text = } else { let newValue = NSDecimalNumber(textFieldValue) if formatter == nil { formatter = NSNumberFormatter() formatter.numberStyle = NSNumberFormatterDecimalStyle self.formattedLabel.text = formatter.stringFromNumber(newValue). // check how stringFromNumber must be called}return true}

Hi @The Eskimo, Thank you for your reply. To clearly our issue in the NAT64 LTE environment: After we connected to the IPv4 VPN connection, we are able to ping the domain host domain.com, so we think the DNS works okay. However, we are not able to ping its IP address: 192.168.1.134, and it translates the IPv4 IP address to an IPv6 IP address. (attached in the reply) The iOS device under the WiFi environment can ping both of them okay. We are not sure why it translates the IPv4 IP address to an IPv6, so we guess the NAT64 does it before sending the traffic to the tunnel. Our thought is like the flow chart we made, and we want to confirm our thought is correct. Thanks, Ken

We wonder if NAT64 translation is done before or after iOS decides which network interface to use. There is no “NAT64 translation” being done on the device. Rather, an app running on the device resolves a DNS name to a set of IPv4 and IPv6 addresses, and it just happens to be that, in a NAT64 environment, this set only contains IPv6 addresses. When you think about it this way, it makes sense that a tunnel that only supports IPv4 address won’t ‘see’ these connections. For more background on this, see Supporting IPv6 DNS64/NAT64 Networks. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi @DTS Engineer , We have a similar issue in our app. Officially, we support the Croatian language only, so there are no .lproj folders for other languages as we don't want to falsely advertise supported languages on the App Store as the app is translated only to Croatian. When we set the device to Croatian, the button is in Croatian. When we set it to any other language, the button is in English (developer language / CFBundleDevelopmentRegion). So, would you say that that's the expected and okay behavior? We don't have to add .lproj for all 30+ languages iOS support, just to have that one button translated to system language, if we don't want to support all those languages in the app? Thnx!

I'm the same person who posted the other question and 2 previous answer. This is what I came up with for both landscapeRight and landscapeLeft videos func turnHorizontalVideoToPortraitVideo(asset: AVURLAsset) -> AVVideoComposition { let track = asset.tracks(withMediaType: AVMediaType.video)[0] let renderSize = CGSize(width: 720, height: 1280) let t = track.preferredTransform if (t.a == 1.0 && t.b == 0 && t.c == 0 && t.d == 1.0) { print(landscapeRight) } var isLandscapeLeft = false if (t.a == -1.0 && t.b == 0 && t.c == 0 && t.d == -1.0) { print(landscapeLeft) isLandscapeLeft = true } var transform1 = t transform1 = transform1.concatenating(CGAffineTransform(rotationAngle: CGFloat(90.0 * .pi / 180))) transform1 = transform1.concatenating(CGAffineTransform(translationX: track.naturalSize.width, y: 0)) let transform2 = CGAffineTransform(translationX: track.naturalSize.height, y: (track.naturalSize.width - track.naturalSize.height) / 2) var p = Double.pi/2 if isLa

I will test on this basis. Thanks.EDITED.I tested and it works without any change to the app.What has changed is the way schemes are organized.Before, there was an IOS scheme and a Watch scheme, the watch scheme including both targets : iPhone and APpleWatch.Nos, there are 2 schemes, but the watch scheme includes only the watch.However, when compiling, it creates both (and opens the 2 simulators).

The setting is in privacy-----> location services ------> Apple watch faces and i changed it to Never. That's how you find it and turn it off. My phone is on swedish so i translated the words but I hope you will find it 🙂 If not i will post a link with screenshots to guide you.

Thank you for sharing this. I'm finding it's incrediable how little to no documentation exists on how to translate existing basic AR concepts Apple used in ARKit in UIKit applications to RealityKit. I'll post here if I make any progress