Difference between revisions of "LRM strings Support"
(Created page with "== Example .strings file == <pre> →Class = "IBUILabel"; text = "or"; ObjectID = "DTz-P6-Y3D";: "DTz-P6-Y3D.text" = "or"; /* Class = "IBUITextField"; placeholder = "Usern...") |
|||
Line 101: | Line 101: | ||
</dirset> |
</dirset> |
||
</lrmconf> |
</lrmconf> |
||
+ | |||
+ | == Why don't Bad iOS Comments Trigger Errors?== |
||
+ | If an IOS file has a comment that is <b>not ended properly</b>, no error is thrown. |
||
+ | For example, if a comment doesn't have an ending '''*/''', such as '''/*Bad comment''' |
||
+ | no errors are found. |
||
+ | |||
+ | This is due to the formatting of iOS. This type of bad comments would typically be created on the base files. |
||
+ | |||
+ | <b>Note</b> ''key/value'' pairs are not effected. Noticed when '''LRM_RESEND''' tag was added, |
||
+ | the info in the Changed Key values included '''LRM_RESEND'''. |
Revision as of 18:12, 2 February 2017
Example .strings file
/* Class = "IBUILabel"; text = "or"; ObjectID = "DTz-P6-Y3D"; */ "DTz-P6-Y3D.text" = "or"; /* Class = "IBUITextField"; placeholder = "Username"; ObjectID = "FiC-Ph-wbo"; */ "FiC-Ph-wbo.placeholder" = "Username"; /* Class = "IBUILabel"; text = "The username or password was incorrect."; ObjectID = "tDx-oc-GBE"; */ "tDx-oc-GBE.text" = "The username or \"password\" was incorrect.";
Example Project Definition File
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <lrmconf> <model-version>2.0.11</model-version> <project-name>DemoIOS</project-name> <project-desc>This is a sample LRM Project definition file, configured for IOS 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-extension> <extension>strings</extension> <file-name-pattern/> <use-pattern-on-dflt-locale>1</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><![CDATA[(%([dsf]|(\d+\$[dsf@])|(\.\d+f)|@))|%\{\w+\}]]></parameter-regex-pattern> </resource-extension> </resource-extensions> <dirset> <includes> <include-dir>**/**</include-dir> </includes> <excludes> </excludes> </dirset> </lrmconf>
Why don't Bad iOS Comments Trigger Errors?
If an IOS file has a comment that is not ended properly, no error is thrown. For example, if a comment doesn't have an ending */, such as /*Bad comment no errors are found.
This is due to the formatting of iOS. This type of bad comments would typically be created on the base files.
Note key/value pairs are not effected. Noticed when LRM_RESEND tag was added, the info in the Changed Key values included LRM_RESEND.