Apple iOS Localization
LingoHub supports iOS .strings files for translation of your iOS and Mac applications.
LingoHub offers a tight coupling between Apple iOS and Android projects to speed up your multi mobile development. You just have to create one of these projects and export the translated resource files in the other format.
- Key-value pairs are delimited with the equal character (=), and terminated by a semicolon (;). The key and the value have to be quoted.
- Newlines can be either written directly in a quoted string or escaped by using “\n”.
- Double quotes have to be escaped using “\””.
- Single-line comments start with “//”.
- Multi-line comments are surrounded by “/* … */”.
- On export, single-line comments are exported using single-line syntax, and multi-line comments using multi-line syntax.
- Information about placeholders can be found here: String Format Specifiers
- LingoHub will assign a comment to the next key-value pair. These comments will be used as translations descriptions and may include LingoChecks information.
- The recommended character encoding for these files is UTF-16LE. But LingoHub allows you to use other common encodings.
Additional example files can be accessed here.
In your Xcode project the file does not need to have any locale
information in the filename (a typical name is
Localizable.strings). The locale information can be found in the
path. For that reason we always recommend to use our SCM integration to
synchronize your repository with LingoHub.
Otherwise you always have to specify the language in an additional step while importing this file. See Supported Technologies.
For Xcode projects you can use ‘Base.lproj’ in your path as locale information. If LingoHub detects this information (and no other locale is given in the path), it will associate these files to the source language of the project.
The most seen approach how .strings files are used is to have your source language content as key. As LingoHub offers support to manage Android and iOS resources in a single project, we always recommend to use the same “generic keys” in both – the .strings files and the Android resource files.