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. Using will allow is above string to appear unescaped. When the translated file is downloaded, the translated string will be escaped as: Here are examples of supported directives for MadCap Lingo: 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. Non-XLIFF files in the archive are excluded from processing.ĭirectory structure and non-XLIFF files are preserved when downloading the translated archive. zip file, not the individual XLIFF files. Translated strings in the archive will be associated with the. Smartling supports Madcap Lingo version 10.Ī MadCap package is a ZIP-archive with one or more XLIFF files, optionally organized in directories.Ī MadCap archive is treated as a single file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |