Difference between revisions of "LRM xhtml Support"
(→Examples of files that uses the xhtml parser type) |
(→Example of Project Definition for Resources) |
||
| Line 23: | Line 23: | ||
Since LRM is able to parse the text portion of ''xhtml'' parsed files, the files can be pseudo-localized and the number of words counted. |
Since LRM is able to parse the text portion of ''xhtml'' parsed files, the files can be pseudo-localized and the number of words counted. |
||
| − | == |
+ | == Setting up XHTML resource files definition == |
Revision as of 20:19, 8 July 2020
Contents
Examples of files that uses the xhtml parser type
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map id="component_CountryIdentifier" xml:lang="en">
<topicref href="ChapterIntroChange.dita">
<title></title>
</topicref>
</map>
xhtml parser type
A well-formed document in XML, such as .dita files, can be parsed by using the xhtml parser type. If there are well-defined keys/values, such as in a .resx or strings.xml file then the xml parser type should be used.
LRM interaction with xhtml parser type files
Number of keys in file is 1
All files that are parsed using the xhtml parser have only 1 key called key1. The value that corresponds to this key is the entire xhtml type file. Because there are no key/values pairs, xhtml parsed files cannot be instrumented (used in our InContext Reviewer/Translation product).
Prep kit files are always full file
If the checksum of the base file has changed then the file will be sent out in the next prep kit for all target locales. Since the file contains only 1 key, the entire file will be sent out for translation.
File can be pseudo-localized and number of words counted
Since LRM is able to parse the text portion of xhtml parsed files, the files can be pseudo-localized and the number of words counted.
