“translate scheme”

Sure, that's the translation of the picture content. Thank you very much for your help! /Users/hututu/Downloads/IMG_E6E06923A6AB-1.jpeg

Actually, just grabbed Xcode 9.3 beta 2 and the export includes the translated Localizable.string entries. So, I guess it was a bug and has been fixed.

Lo and behold today I tried Xcode's export/import for the first time and used Xliffie for the external translating. Very convenient but a lot of crashes in XLiffie and Xcode. I got around the n issue by putting those strings in their own strings file with a unique table name. I only had three. I used NSLocalizedString(fooEnglish, tableName fooTable, comment:fooComment). It seems that straight-out-of-the-box Xcode's export/import function ignores uniquely named strings files and only export/imports the Localizable.strings file along with the Storyboard files. This works for me in this case because I am translating into two languages that I happen to know. However, if I was sending this out for professional translation, it would be an additional chore and expense to deal with these exceptions.

One difficulty I always run into is the order of the elementary transformations when one of them is translation, because then they're no longer commutative and the order matters. Apple isn't very clear about the order (there are equivalent pre- and post-multiplication forms of the transform arithmetic, and you need to know which you're doing). On top of that, there may be a invisible coordinate flip transform (depending on whether the y coordinates increase from the top or the bottom), as well as a possible origin translation due to the semantics of the video frame geometry.Try doing just a single translation (ignoring size and rotation) and see if you can get rational placement. If so, trying adding in a small second transform again, and see if it's clear how it interacts with the translation.It ain't fun.

Hello and thanks for your question and interest in the Translation API. These APIs do only work from SwiftUI, but it's not necessary to rewrite your app if you're using UIKit or AppKit. You can use a UIHostingController in the spot where you want to trigger translation, and keep the rest of your app as-is. There's a bit more detail in this reply on another post: https://developer.apple.com/forums/thread/756837?answerId=791116022#791116022

Great example! Just note that this will gimble in all directions whereas `buttonLockup` only translates left and right.

I just double-clicked the .ips file in Finder and it opened, converted and displayed in Console with Translated Report at the top.

I believe you have to create localizable.strings resource file in FR locale. The String.init and runtime do not do the magic translation work.

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.

It looks like I'm going to have to apply all of the translations manually, which is quite a pain. Better to just give the .stringsdict file itself to the translators, rather than using the XLIFF until Apple fixes this.Did you file a bug about this? If so, what’s the number?Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Just applying the translation component of the result transform should give you want. How is your toIdentity() method implemented, is it possible that you accidentally apply a rotation in there? As an alternative to the simd types, you could work with RealityKit's Transform type (https://developer.apple.com/documentation/realitykit/transform). This makes it easier to access and set the translation, rotation, and scale components separately (which may also help with your second question regarding aligning the rotation of multiple objects).

My Device is iPad Pro 2020. About 1mm with LiDAR,0.5mm with front True Depth Camera. This reply was translated.

Me too. I was downloading offline translation and it was taking too long and I could not see how to stop the download. Then I uninstalled it. Would like to reinstall it.

Becuase I'm so new with app development, Objective-C translation to Swift is very hard for me. I appreciate the information to research. Thank you!