Difference between revisions of "LRM html Support"
(→html parser type) |
(→valid html syntax) |
||
| Line 7: | Line 7: | ||
== ''html'' parser type == |
== ''html'' parser type == |
||
=== valid html syntax === |
=== valid html syntax === |
||
| − | Files that use the ''html'' are expected to have valid html syntax |
+ | Files that use the ''html'' parser are expected to have valid html syntax |
| + | |||
=== htm/html uses the ''html'' parser type=== |
=== htm/html uses the ''html'' parser type=== |
||
When defining a project with .html or .htm extension, there is no need to define a ''<parser-type>'' as the ''html'' parser will always be used. |
When defining a project with .html or .htm extension, there is no need to define a ''<parser-type>'' as the ''html'' parser will always be used. |
||
Revision as of 23:20, 31 August 2017
Contents
Example .html or .htm File or a file extension that uses the html parser type
<html> <p>This is some text in an html file</p> </html>
html parser type
valid html syntax
Files that use the html parser are expected to have valid html syntax
htm/html uses the html parser type
When defining a project with .html or .htm extension, there is no need to define a <parser-type> as the html parser will always be used.
unique file extension needs to define html parser type
If a unique file extension is a valid html file, then the <parser-type> should be html in the project definition file.
LRM interaction with html parser type files
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.
Number of keys in file is 1
All files that are parsed using the html parser have only 1 key called key1. The value that corresponds to this key is the entire html type file.
Example Project Definition File
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<lrmconf>
<model-version>2.0.11</model-version>
<project-name>DemoRxml</project-name>
<project-desc>This is a sample LRM Project definition file, configured for Globalyzer Rxml resource files</project-desc>
<group-name>acme</group-name>
<top-level-dir>C:\acme\source</top-level-dir>
<detect-errors>
<missed-trans-error>0</missed-trans-error>
<parameter-mismatch-error>1</parameter-mismatch-error>
</detect-errors>
<track-back-locale>br</track-back-locale>
<pseudo-locale>eo</pseudo-locale>
<target-locales>
<locale>es_MX</locale>
<locale>fr_CA</locale>
<locale>fr_FR</locale>
</target-locales>
<default-locale>en_US</default-locale>
<resource-extensions>
<resource-extension>
<!-- parser-type not needed since .html is a standard LRM extension that maps to the html parser type -->
<extension>html</extension>
<file-name-pattern>*-l_c_v</file-name-pattern>
<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>
<file-location-pattern>l_c_v</file-location-pattern>
<use-location-pattern-on-dflt-locale>1</use-location-pattern-on-dflt-locale>
<base-file-encoding>UTF-8</base-file-encoding>
<localized-file-encoding>UTF-8</localized-file-encoding>
<parameter-regex-pattern></parameter-regex-pattern>
</resource-extension>
<resource-extension>
<!-- parser-type not needed since .htm is a standard LRM extension that maps to the html parser type -->
<extension>htm</extension>
<file-name-pattern>*-l_c_v</file-name-pattern>
<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>
<file-location-pattern>l_c_v</file-location-pattern>
<use-location-pattern-on-dflt-locale>1</use-location-pattern-on-dflt-locale>
<base-file-encoding>UTF-8</base-file-encoding>
<localized-file-encoding>UTF-8</localized-file-encoding>
<parameter-regex-pattern></parameter-regex-pattern>
</resource-extension>
<resource-extension>
<!-- parser-type is required because .myext is not a standard LRM extension -->
<extension>myext</extension>
<parser-type>html</parser-type>
<file-name-pattern>*-l_c_v</file-name-pattern>
<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>
<file-location-pattern>l_c_v</file-location-pattern>
<use-location-pattern-on-dflt-locale>1</use-location-pattern-on-dflt-locale>
<base-file-encoding>UTF-8</base-file-encoding>
<localized-file-encoding>UTF-8</localized-file-encoding>
<parameter-regex-pattern></parameter-regex-pattern>
</resource-extension>
</resource-extensions>
<dirset>
<includes>
<include-dir-file>**/**</include-dir-file>
</includes>
<excludes>
<exclude-dir-file>**/source/bin/**</exclude-dir-file>
</excludes>
</dirset>
</lrmconf>
