#Add xlif file to xbench update

This directive can be placed inline, in the API or in a template (consult your SA about configuring directive templates). However, if there are a different number of characters in the translation where the translation process removed or added some and the escaping is inconsistent among them, propagate will escape all entities for that character. If the same character is both escaped and unescaped in the same string propagate will return the characters in the translation escaped in the same order as they were in the source. Base entities continue to be controlled by HTML detection and the entity_escaping directive.

Propagate will only affect non-base entities - all named entities except &, ', <, >.

The default is none which is the current behavior, which recognizes HTML4 entities only - if HTML5 entities are required as well, you must use the entity_escaping_type=propagate directive. For each entity character we'll check to see if it was escaped in the source and try to match (propagate) it in the target.

#Add xlif file to xbench update

For example normally we turn © into © but if we use this new directive the translation will automatically update to use escaping from the source. Used to retain entity escaping for all non-base entities. When this directive is set to html5, all html5 entities will be unescaped as well.

XML Characters (always escaped) Character (name)īy default, all html4 entities are unescaped, except the basic set: < > & '.

Using will allow This is an & ' example string4 to appear unescaped. When the translated file is downloaded, the translated string will be escaped as: Valuesįor example, your translation might look like this:īy default, using the 'auto' setting, we will assume this is HTML from the tag. entity_escapingĮxact delivery depends on file type. Here are some examples of, along with example values or paths.

Directives are specified in comments within the files, in the following format: Inline File Format ĪPI Parameter smartling. Directivesįile directives are supported, both inline and via our API. See Placeholders in Resource Files for more on placeholders. Please refer to the Apple documentation for the file format, which uses the standard CLDR forms. This is still true regardless if the app uses. IOS apps using plural functions store the strings in the Stringsdict file format. See XLIFF Resource Documentation for details on the translate attribute. To exclude a string from translation, set translate=no. To exclude content from translation, you can use XLIFF’s translate attribute. Smartling automatically captures XLIFF notes and makes them translator instructions. xml files that use the XML Localization Interchange File Format (XLIFF).