![]() If this directive is not set, pseudo translations are 30 percent longer than the original strings.ĭownloaded pseudo translations will increase the length of original strings by 80 percent.Ĭontrol trans-unit level HTML parsing. Sets the percentage by which original strings are inflated when downloading pseudo translations. See Placeholders in Resource Files for more on placeholders.Īny characters surrounded by curly brackets, e.g.,, will be treated as a placeholder. Any text in your file matching the regular expression you provide will be captured as a placeholder. NONE - disables any current custom placeholders.Specifies iOS-style placeholders for the file. Used to specify a standard placeholder format. 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 &, ', <, >.This does not affect source content at all - so using it will not result in new strings. 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. Numerical entities are not considered at all with this directive, and are treated normally. 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. 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. ![]() When the translated file is downloaded, the translated string will be escaped as: Here are examples of supported directives for XLIFF: Directive nameĬontrols whether base characters ( > & " example string4īy default, using the "auto" setting, we will assume this is HTML from the tag. ![]() Directives are specified in comments within the files, in the following format: Inline File Format Character (character name)įile directives are supported, both inline and via our API. You can control this by using the entity_escaping directive. The following XML character are always escaped. 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. You must translate XLIFF 1.2 and choose the articulate option for translations to be compatible with Articulate import. xml files that use the XML Localization Interchange File Format (XLIFF).Īrticulate XLIFF 1.2 is supported, meaning you can upload a translation XLIFF 1.2 file to Articulate Storyline. Click here to download example file with common directives
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |