Difference between revisions of "LRM po Support"
(→Example Project Definition File) |
(→Example Project Definition File) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 40: | Line 40: | ||
</pre> |
</pre> |
||
| − | == |
+ | == ''po'' parser type == |
| + | === valid po syntax === |
||
| + | Files that use the ''po'' parser are expected to have valid po syntax |
||
| + | === .po uses the ''po'' parser type=== |
||
| + | When defining a project containing LRM Standard .po resource files, there is no need to define a ''<parser-type>'' as the ''po'' parser will always be used. |
||
| + | |||
| + | === unique file extension needs to define ''json'' parser type === |
||
| + | If a unique file extension is a valid po file, then the ''<parser-type>'' should be ''po'' in the project definition file. |
||
| + | |||
| + | == Example of Project Definition for Resources == |
||
| + | The following is an example of po resource file definitions. See [[Supported_Resource_Bundles#Resource_Extensions| resource extensions]] for more information. |
||
| − | <?xml version="1.0" encoding="UTF-8"?> |
||
| − | <lrmconf> |
||
| − | <model-version>1.0.0</model-version> |
||
| − | <project-name>DemoPo</project-name> |
||
| − | <project-desc>This is a sample LRM Project definition file, configured to support po resource files</project-desc> |
||
| − | <group-name>acme</group-name> |
||
| − | <top-level-dir>C:\acme\source</top-level-dir> |
||
| − | <detect-errors> |
||
| − | <missed-trans-error>1</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-extensions> |
||
<resource-extension> |
<resource-extension> |
||
| + | '''<!-- parser-type not needed since .po is a standard LRM extension that maps to the po parser type -->''' |
||
'''<extension>po</extension>''' |
'''<extension>po</extension>''' |
||
'''<file-name-pattern>*-l_c_v</file-name-pattern>''' |
'''<file-name-pattern>*-l_c_v</file-name-pattern>''' |
||
| Line 73: | Line 65: | ||
</resource-extension> |
</resource-extension> |
||
<resource-extension> |
<resource-extension> |
||
| + | '''<!-- parser-type is required because .myext is not a standard LRM extension -->''' |
||
'''<extension>''myext''</extension>''' |
'''<extension>''myext''</extension>''' |
||
'''''<parser-type>po</parser-type>''''' |
'''''<parser-type>po</parser-type>''''' |
||
| Line 84: | Line 77: | ||
</resource-extension> |
</resource-extension> |
||
</resource-extensions> |
</resource-extensions> |
||
| − | <dirset> |
||
| − | <includes> |
||
| − | <include-dir-file>**/src/**</include-dir-file> |
||
| − | </includes> |
||
| − | <excludes> |
||
| − | <exclude-dir-file>**/src/test</exclude-dir-file> |
||
| − | </excludes> |
||
| − | </dirset> |
||
| − | </lrmconf> |
||
Latest revision as of 20:25, 18 September 2017
Contents
Example of .po files as well as file extensions using the po parser type
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-02-01 16:55-0700\n"
"PO-Revision-Date: 2017-02-01 16:55-0700\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
# SOURCE_FILE C:/Path/to/my/source/files/Matrix.js
msgid "ascending"
msgstr "ascending"
msgid "descending"
msgstr "descending"
msgid "Viewing rows {0} to {1} of {2}"
msgstr "Viewing rows {0} to {1} of {2}"
# SOURCE_FILE C:/Path/to/my/source/files/cache.js
msgid "You have made unsaved changes to the following cache document(s): <b>"
msgstr "You have made unsaved changes to the following cache document(s): <b>"
msgid "</b>. Procede with delete?"
msgstr "</b>. Procede with delete?"
msgid "//record[record]"
msgstr "//record[record]"
po parser type
valid po syntax
Files that use the po parser are expected to have valid po syntax
.po uses the po parser type
When defining a project containing LRM Standard .po resource files, there is no need to define a <parser-type> as the po parser will always be used.
unique file extension needs to define json parser type
If a unique file extension is a valid po file, then the <parser-type> should be po in the project definition file.
Example of Project Definition for Resources
The following is an example of po resource file definitions. See resource extensions for more information.
<resource-extensions>
<resource-extension>
<!-- parser-type not needed since .po is a standard LRM extension that maps to the po parser type -->
<extension>po</extension>
<file-name-pattern>*-l_c_v</file-name-pattern>
<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>
<file-location-pattern/>
<use-location-pattern-on-dflt-locale>0</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><![CDATA[%\d*[ds]|%\d+]]></parameter-regex-pattern>
</resource-extension>
<resource-extension>
<!-- parser-type is required because .myext is not a standard LRM extension -->
<extension>myext</extension>
<parser-type>po</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/>
<use-location-pattern-on-dflt-locale>0</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><![CDATA[%\d*[ds]|%\d+]]></parameter-regex-pattern>
</resource-extension>
</resource-extensions>
