Model 204 language support - Revision history

JAL: link repair

2016-12-20T14:55:50Z

link repair

← Older revision		Revision as of 14:55, 20 December 2016
Line 241:		Line 241:
	<P CLASS="syntax">FIND [ALL] RECORDS {FOR WHICH \| WITH} <span class="term">fieldname</span>		<P CLASS="syntax">FIND [ALL] RECORDS {FOR WHICH \| WITH} <span class="term">fieldname</span>
	IS [NOT] LANGLIKE '<span class="term">pattern</span>'</p>		IS [NOT] LANGLIKE '<span class="term">pattern</span>'</p>
	~~<b>where~~:~~</b>~~		Where:
	<p>		<p>
	The LANGLIKE keyword indicates that <var class="term">pattern</var> is the set of characters to match, using LANGUSER and LANGFILE as previously described.</p>		The LANGLIKE keyword indicates that <var class="term">pattern</var> is the set of characters to match, using LANGUSER and LANGFILE as previously described.</p>
Line 323:		Line 323:

	==Control characters==		==Control characters==
	For a list of the control characters found in IBM computers and the sequence in which they are sorted, see [[Control characters]].		For a list of the control characters found in IBM computers and the sequence in which they are sorted, see [[Control characters and Model 204 language support]].

	==Special characters==		==Special characters==

ELowell at 23:37, 6 December 2016

2016-12-06T23:37:46Z

← Older revision		Revision as of 23:37, 6 December 2016
Line 1:		Line 1:
	<div class="toclimit-3">__TOC__</div>		<div class="toclimit-3">__TOC__</div>

	Model 204 contains a language support feature for customers who sort and display Model 204 data using single-byte character sets other than U.S. English or Japanese double-byte character set (DBCS).		Model 204 contains a language support feature for customers who sort and display Model 204 data using single-byte character sets other than U.S. English or Japanese double-byte character set (DBCS).

ELowell at 23:24, 6 December 2016

2016-12-06T23:24:03Z

← Older revision		Revision as of 23:24, 6 December 2016
Line 76:		Line 76:
	<table>		<table>
	<caption>Character sets supported in Model 204</caption>		<caption>Character sets supported in Model 204</caption>
	<tr class="~~bold~~">		<tr class="head">
	<th>Written language</th>		<th>Written language</th>
	<th>Parameter value</th>		<th>Parameter value</th>
Line 126:		Line 126:
	<table>		<table>
	<caption>Valid character sets</caption>		<caption>Valid character sets</caption>
	<tr class="~~bold~~">		<tr class="head">
	<th>Written language</th>		<th>Written language</th>
	<th>Model 204 LANGFILE value</th>		<th>Model 204 LANGFILE value</th>
Line 170:		Line 170:
	<table>		<table>
	<caption>Valid languages for a thread's I/O device</caption>		<caption>Valid languages for a thread's I/O device</caption>
	<tr class="~~bold~~">		<tr class="head">
	<th>Written language</th>		<th>Written language</th>
	<th>Model 204 LANGUSER value</th>		<th>Model 204 LANGUSER value</th>
Line 242:		Line 242:
	<P CLASS="syntax">FIND [ALL] RECORDS {FOR WHICH \| WITH} <span class="term">fieldname</span>		<P CLASS="syntax">FIND [ALL] RECORDS {FOR WHICH \| WITH} <span class="term">fieldname</span>
	IS [NOT] LANGLIKE '<span class="term">pattern</span>'</p>		IS [NOT] LANGLIKE '<span class="term">pattern</span>'</p>
	~~====Where====~~		<b>where:</b>
	<p>		<p>
	The LANGLIKE keyword indicates that <var class="term">pattern</var> is the set of characters to match, using LANGUSER and LANGFILE as previously described.</p>		The LANGLIKE keyword indicates that <var class="term">pattern</var> is the set of characters to match, using LANGUSER and LANGFILE as previously described.</p>
Line 252:		Line 252:
	<table>		<table>
	<caption>$Functions for language-specific processing</caption>		<caption>$Functions for language-specific processing</caption>
	<tr class="~~bold~~">		<tr class="head">
	<th>$function</th>		<th>$function</th>
	<th>Description</th>		<th>Description</th>

ELowell: deleted $Upcase description; linked to $Upcase page instead

2016-03-09T01:10:02Z

deleted $Upcase description; linked to $Upcase page instead

@@ Line 289: / Line 289: @@
 </tr>
 <tr>
-<td>[[#$UPCASE|$UPCASE]]</td>
+<td>[[$Upcase|$Upcase]]</td>
 <td>Translates a lowercase or mixed-case string into an uppercase string.</td>
 </tr>
 </table>
 ==Terminal interface requirements==

ELowell: deleted $Lowcase description; linked to $Lowcase page instead

2016-03-08T23:40:42Z

deleted $Lowcase description; linked to $Lowcase page instead

@@ Line 285: / Line 285: @@
 </tr>
 <tr>
-<td>[[#$LOWCASE|$LOWCASE]]</td>
+<td>[[$Lowcase|$Lowcase]]</td>
 <td>Translates an uppercase case or mixed-case string into a lowercase string.</td>
 </tr>
@@ Line 293: / Line 293: @@
 </tr>
 </table>
 ===$UPCASE===

ELowell: deleted $LIKE description; linked to $LIKE page instead

2016-03-08T23:32:45Z

deleted $LIKE description; linked to $LIKE page instead

@@ Line 281: / Line 281: @@
 </tr>
 <tr>
-<td>[[#$LIKE|$LIKE]]</td>
+<td>[[$LIKE|$LIKE]]</td>
 <td>Controls parsing and evaluation languages used in pattern matching.</td>
 </tr>
@@ Line 293: / Line 293: @@
 </tr>
 </table>
 ===$LOWCASE===

ELowell: deleted $LangUst description; linked to $LangUst page instead

2016-03-08T23:15:37Z

deleted $LangUst description; linked to $LangUst page instead

@@ Line 277: / Line 277: @@
 </tr>
 <tr>
-<td>[[#$LANGUST|$LANGUST]]</td>
+<td>[[$LangUst|$LangUst]]</td>
 <td>Restores a transformed string back to its original value.</td>
 </tr>
@@ Line 293: / Line 293: @@
 </tr>
 </table>
 ===$LIKE===

ELowell: deleted $LangSrt description; linked to $LangSrt page instead

2016-03-08T22:51:01Z

deleted $LangSrt description; linked to $LangSrt page instead

← Older revision		Revision as of 22:51, 8 March 2016
Line 273:		Line 273:
	</tr>		</tr>
	<tr>		<tr>
	<td>[[#$~~LANGSRT~~\|$~~LANGSRT~~]]</td>		<td>[[$LangSrt\|$LangSrt]]</td>
	<td>Transforms a string into a language-specific sequence value.</td>		<td>Transforms a string into a language-specific sequence value.</td>
	</tr>		</tr>

ELowell: /* $LANGSRT */

2016-03-08T22:49:48Z

$LANGSRT

@@ Line 293: / Line 293: @@
 </tr>
 </table>
 ===$LANGUST===

ELowell: deleted $LangSpc description; linked to $LangSpc page instead

2016-03-08T19:00:09Z

deleted $LangSpc description; linked to $LangSpc page instead

@@ Line 269: / Line 269: @@
 </tr>
 <tr>
-<td>[[#$LANGSPC|$LANGSPC]]</td>
+<td>[[$LangSpc|$LangSpc]]</td>
 <td>Returns a string containing the language-specific hexadecimal value of a special character on a particular terminal.</td>
 </tr>
@@ Line 293: / Line 293: @@
 </tr>
 </table>
 ===$LANGSRT===