$LangSpc: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<p> | <p> | ||
<var>$LangSpc</var> returns a string containing the | <var>$LangSpc</var> returns a string containing the hexadecimal value of the specified character in the specified language. You can use <var>$LangSpc</var> to scan user input for a special character in a language independent manner. A printout or display of the returned value will be the character representation based on the language argument.</p> | ||
<p> | <p> | ||
You can also use the <var>$LangSpc</var> function to ensure that any special character that has a different hexadecimal code value or terminates with a language other | You can also use the <var>$LangSpc</var> function to ensure that any special character that has a different hexadecimal code value or terminates with a language other than U.S. English is displayed correctly.</p> | ||
==Syntax== | ==Syntax== | ||
| Line 76: | Line 76: | ||
The optional <var class="term">language</var> argument specifies which language to use to obtain the desired hexadecimal code for the specified character. The request is canceled with an error message if the name is not found in NLANG. The language argument is handled as follows:</p> | The optional <var class="term">language</var> argument specifies which language to use to obtain the desired hexadecimal code for the specified character. The request is canceled with an error message if the name is not found in NLANG. The language argument is handled as follows:</p> | ||
<ul> | <ul> | ||
<li>When you omit the <var class="term">language</var> argument, <var class="product">Model 204</var> performs the validation in U.S. English | <li>When you omit the <var class="term">language</var> argument, <var class="product">Model 204</var> performs the validation in U.S. English (even if the value of the <var>LANGUSER</var> parameter is not US) and lowercase characters are not recognized.</li> | ||
<li>An asterisk enclosed in quotation marks (<tt>'*'</tt>) instructs <var class="product">Model 204</var> to use the value of the <var>LANGUSER</var> parameter.</li> | <li>An asterisk enclosed in quotation marks (<tt>'*'</tt>) instructs <var class="product">Model 204</var> to use the value of the <var>LANGUSER</var> parameter.</li> | ||
<li>You can enter the name of a valid language enclosed in quotation marks or a %variable containing a valid language. If the value you enter is not supported, the request is canceled with an error message. </li> | <li>You can enter the name of a valid language enclosed in quotation marks or a %variable containing a valid language. If the value you enter is not supported, the request is canceled with an error message. See the <var>[[LANGUSER parameter|LANGUSER]]</var> parameter for valid values.</li> | ||
</ul> | </ul> | ||
Latest revision as of 18:57, 8 March 2016
$LangSpc returns a string containing the hexadecimal value of the specified character in the specified language. You can use $LangSpc to scan user input for a special character in a language independent manner. A printout or display of the returned value will be the character representation based on the language argument.
You can also use the $LangSpc function to ensure that any special character that has a different hexadecimal code value or terminates with a language other than U.S. English is displayed correctly.
Syntax
$LANGSPC('charname'[, langname])
Where:
The charname argument is a string containing one of the following values:
| Valid charname | Character | Description |
|---|---|---|
| AT | @ | At sign |
| BACKSLSH | \ | Backslash |
| DOLLAR | $ | Dollar sign |
| DQUOTE | " | Double quotation mark |
| EXCLAMAT | ! | Exclamation point |
| NOT | ¬ | Not sign |
| RBRACE | ] | Closing square brace or right square brace |
| SHARP | # | Number sign or pound sign |
| VERTICAL | | | Vertical bar |
The optional language argument specifies which language to use to obtain the desired hexadecimal code for the specified character. The request is canceled with an error message if the name is not found in NLANG. The language argument is handled as follows:
- When you omit the language argument, Model 204 performs the validation in U.S. English (even if the value of the LANGUSER parameter is not US) and lowercase characters are not recognized.
- An asterisk enclosed in quotation marks ('*') instructs Model 204 to use the value of the LANGUSER parameter.
- You can enter the name of a valid language enclosed in quotation marks or a %variable containing a valid language. If the value you enter is not supported, the request is canceled with an error message. See the LANGUSER parameter for valid values.
Example
In the following example, the %PATH variable (presumably supplied by the user from the terminal) is searched for the backslash character, regardless of its location in the user terminal's code table:
%BACKSLASH IS STRING LEN 1 %BACKSLASH = $LANGSPC('BACKSLSH','*') %DIR = $SUBSTR(%PATH, $INDEX(%PATH,%BACKSLASH)+1)