“translate scheme”

I understand that API returns Strings (in some cases) and you want to translate those Strings.Did you test cloud translation ?You would pass it the String returned by API, with the original language (that you should know) and the destination language.Have a look here:h ttps://cloud.google.com/translate/docs/translating-text

The intended flow for working with translators is to use .strings (or the new .xcstrings) files within Xcode to specify/organize which strings need to be translated, then use Product > Export Localizations in the menu bar to get a Localization Catalog for a given language. This .xcloc file can then be sent to your translators and they can edit it in any translation tool of their choice that understands .xcloc or .xliff files. Then at some later point when they've finished translating, you can import the .xcloc file back into Xcode using Product > Import Localizations and the translations will be merged back into the .xc/strings files.

As a child of parentEntity, entity should appear to be scaled, rotated, and translated when parentEntity is scaled, rotated, and translated.

Hi, I have had the same problem you can achieve a string without a numerical specifier when editing the source code of the xcstrings file. right click .xcstrings > Open As > Source Code add this to strings object and edit this as your want: %lld day : { localizations : { de : { stringUnit : { state : translated, value : %#@day@ }, substitutions : { day : { formatSpecifier : lld, variations : { plural : { one : { stringUnit : { state : translated, value : Tag } }, other : { stringUnit : { state : translated, value : Tage } } } } } } }, en : { stringUnit : { state : translated, value : %#@day@ }, substitutions : { day : { formatSpecifier : lld, variations : { plural : { one : { stringUnit : { state : translated, value : day } }, other : { stringUnit : { state : translated, value : days } } } } } } } } }, note: %lld day is translated in German Its sad that we need to this every time manual by adding it to the source code.

i just find that enter translate:// in safari will show the open in translate prompt, but will not actually open the app.

My understanding of that Lock dropdown is meant to lock the control while translation is in progress. So you can Lock Localizable Properties to ensure they are not changed while you are waiting on translations to come back. Locking Non-localizable properties ensures you cannot edit other properties of the control.The problem with just using comments is that they appear as part of the larger note generated for that item. Its already a note full of technical details a translator is just going to ignore. For example here is the exported XLIFF output of a UILabel with placeholder text and a Do Not Translate comment added in storyboard:<trans-unit id=1cv-zx-pu2.text> <source>Today 3:31pm</source> <note>Class = UILabel; text = Today 3:31pm; ObjectID = 1cv-zx-pu2; Note = Do Not Translate;</note></trans-unit>It requires extra manual work to determine if it should be translated or not. It is not a standardized way to skip translations

The Korean and Chinese translations of The Swift Programming Language book are provided by community members. There does seem to be a Spanish translation, according to https://www.swift.org/documentation/#translations - maybe you could chat on the Swift Forums about it? There's a link to the appropriate subforum on that page i linked.