Loco support for Android XML strings files
Loco translations are plain text by default. You don't need to enter specially escaped text into Loco, just type your translations normally and the export process will create a valid
These strings are suitable for use with Android's
getString, which will return the text literally to your application.
- If you're using Android's built-in HTML styles, use the HTML asset type instead.
- If you need to embed XML markup (such as CDATA or XLIFF tags) use the XML asset type.
To work with Android's built-in HTML styles, the corresponding Loco asset must be of the HTML type. Click the :cog icon: from the main management view to change the asset type. This is suitable if you're using
getText which will retain any rich text styling applied to the string.
Note that only
<u> tags are supported in HTML assets, as per the Android documentation.
To add unsupported formatting tags use a plain text asset but call
getString instead of
getText in your application.
If you notice Loco's HTML editor adding the wrong kind of markup, don't worry, the export process will fix the HTML to ensure it's valid for Android. For example:
<p><em>foo</em></p> will become
If your exported
<string> tags need to contain XML child nodes, the corresponding Loco asset must be of the XML type. Click the :cog icon: from the main management view to change the asset type. This is suitable if you have special processing rules such as XLIFF inline markup.
Note that this type of asset is exported to XML files as is. Loco will warn you if a translation is invalid XML, but it will still be saved in your project.
A note about CDATA
CDATA in imported files is treated as plain text. It's not treated as XML unless there is other markup present in the string. This is a feature, not a bug. The most common use of CDATA in translation files is just to wrap plain text, often when not even necessary.
The following are equivalent:
<string name="a"><![CDATA[Foo & Bar]]></string> <string name="b">Foo & Bar</string>
Likewise at export. Loco escapes plain text as in the second example. If you must have CDATA in your export, change the asset type to XML and enter the markup exactly as you need it.
In addition to regular XML escaping, Loco performs Android-specific escaping of string values at export. Escaped characters include line breaks, quotes and tabs; plus handling of multiple spaces and other characters that have special meaning such as
Don't add escape sequences into your asset translations, or you will get double escaping. For example
"foo" will be exported as
\"foo\", but if you were to escape your own translation this way you would end up with
Android pluralized strings are supported by Loco at both export and import. Plurals are managed in the main Loco interface the same way for all platforms. Read more about plural forms in Loco.
Example: Create an asset called
apple and another called
apples. Bind them together as plurals and Loco will export their translations with the singular form's asset ID, as follows:
<plurals name="apple"> <item quantity="one">An apple</item> <item quantity="other">%d apples</item> </plurals>
The quantity attributes
"other" come from your project locale settings. The two strings come from the individual asset translations.
Loco supports the
<string-array> element at import and export. If you're creating strings manually within Loco you can group them into arrays using the context field available in the asset properties.
Example: Create an asset called
"apple" with context
"fruit", and an asset called
"banana" with the context
"fruit". This will export the following:
<string-array name="fruit"> <item name="apple">apple</item> <item name="banana">banana</item> </string-array>
Java formatting substitutions
Loco will automatically detect string formatting when you import entries containing valid printf-style syntax like this:
<string name="result">You scored %1$d / %2$d</string>
After importing this string, it will be identified as being in Java format and any translations made from it will be validated to ensure they match.
If you have string that is not intended to be formatted, you can disable the feature with the
formatted="false" attribute, as follows:
<string name="sale" formatted="false">Now 20% off!</string>
It's common to share translations between iOS and Android, but the syntax of the Android Formatter is quite different to the Objective C implementation. Loco recognizes both styles of formatting and can convert between the two in most common cases.
Read more on Loco's support for cross-platform string formatting.
Java-safe string names
Your asset IDs are taken as Android string names in the default XML export, so avoid using characters that are invalid as Java variable names.
The only substitutions performed on your custom IDs are the replacement of hyphens with underscores (so
foo_bar), but if you index your export by source text Loco will convert the text to a valid Java variable.