Site Menu Project Specification Implementation Recommendations Reference Needs Updating Work in Progress Wastebasket Wiki Manual |
TransliterationRecommendations.Transliteration HistoryHide minor edits - Show changes to markup 2015-10-04 15:08
by -
Changed line 39 from:
to:
Changed lines 44-45 from:
Where transliteration is applied to block comments, it is recommended to prefix the comment with a question mark. As with string literals, it is recommended to separate and isolate transliterated symbols from the remaining comment by splitting the comment into several comments to make it visible exactly which part of the original comment has been transliterated. to:
Where transliteration is applied to block comments, it is recommended to prefix the comment with a question mark. As with string literals, it is recommended to separate and isolate transliterated symbols from the remaining comment by splitting the comment into several comments to make it visible exactly which part of the comment has been transliterated. Changed line 48 from:
to:
Changed line 55 from:
to:
Changed lines 64-65 from:
to:
Changed line 73 from:
to:
Changed line 80 from:
to:
Changed line 88 from:
to:
2015-09-20 11:32
by -
Changed line 12 from:
Implementors of transliteration utilities may choose whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended as their digraphs have been reserved: to:
Implementors of transliteration utilities may choose whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended as their digraphs have been reserved: 2015-09-20 09:01
by -
Changed line 44 from:
Where transliteration is applied to block comments, it is recommended to prefix the comment with a question mark. to:
Where transliteration is applied to block comments, it is recommended to prefix the comment with a question mark. As with string literals, it is recommended to separate and isolate transliterated symbols from the remaining comment by splitting the comment into several comments to make it visible exactly which part of the original comment has been transliterated. 2015-09-20 08:57
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a period. It is further recommended to separate transliterated symbols from the remaining string literal by factoring and concatenation. This way it becomes visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a period. It is further recommended to separate transliterated symbols from the remaining string literal by factoring and concatenation. This way it becomes visible in the transliterated source text exactly which part of a string literal has been transliterated, avoiding accidental transliterations. 2015-09-20 08:56
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a period. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it becomes visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a period. It is further recommended to separate transliterated symbols from the remaining string literal by factoring and concatenation. This way it becomes visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. 2015-09-20 08:56
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it becomes visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a period. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it becomes visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. 2015-09-20 08:54
by -
Changed line 24 from:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an to:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an 2015-09-20 08:23
by -
Changed line 24 from:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an to:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an 2015-09-20 08:23
by -
Changed line 24 from:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an to:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an 2015-09-20 08:21
by -
Changed lines 51-52 from:
Where transliteration is applied to line comments, it is recommended to use to:
Where transliteration is applied to line comments, it is recommended to use Changed lines 60-61 from:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with to:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with Changed lines 69-70 from:
In the now unlikely event that the legacy character set does not provide an encoding for to:
In the now unlikely event that the legacy character set does not provide an encoding for Changed lines 76-77 from:
However, if the legacy character set provides an encoding for the vertical bar, one may use to:
However, if the legacy character set provides an encoding for the vertical bar, one may use Changed line 84 from:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use to:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use 2015-09-20 08:18
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it becomes visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. 2015-09-20 08:18
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is clearly visible in the transliterated source text which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is visible in the transliterated source text exactly which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. 2015-09-20 08:17
by -
Changed line 24 from:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an ENCODING pragma. to:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an 2015-09-20 08:15
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is clearly visible in the transliterated source text which part of a string literal has been transliterated and accidental transliterations are avoided. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is clearly visible in the transliterated source text which part of a string literal has been transliterated. Accidental transliterations can thus be avoided. 2015-09-20 08:10
by -
Changed line 1 from:
Legacy Character Set Transliterationsto:
Encoding Modula-2 in Legacy Character Sets2015-09-20 08:09
by -
Changed lines 16-17 from:
to:
Changed lines 19-20 from:
to:
2015-09-20 08:05
by -
Changed line 60 from:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with to:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with 2015-09-20 08:05
by -
Changed line 60 from:
Where specific character code points are to be hardcoded in transliterated source text, it is recommended to prefix the character code with to:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with 2015-09-20 08:03
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is clearly visible in the transliterated source text which part of a string literal has been transliterated. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is clearly visible in the transliterated source text which part of a string literal has been transliterated and accidental transliterations are avoided. 2015-09-20 07:59
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, care has been taken to allow reversible transliteration to and from legacy character sets via source code transliteration utilities to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: to:
Modula-2 syntax is based on the ASCII character set. Nevertheless, care has been taken to allow reversible transliteration to and from legacy character sets via source code transliteration utilities to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: 2015-09-20 07:54
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. This way it is clearly visible in the transliterated source text which part of a string literal has been transliterated. 2015-09-20 07:51
by -
Changed line 35 from:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate symbols to be transliterated by factoring and concatenation. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate transliterated symbols by factoring and concatenation. 2015-09-20 07:50
by -
Changed line 24 from:
It is mandatory to record the character encoding scheme within transliterated source files using an ENCODING pragma. to:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an ENCODING pragma. 2015-09-20 07:47
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, care has been taken to allow reversible transliteration to and from legacy character sets via source code transliteration utilities in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: to:
Modula-2 syntax is based on the ASCII character set. However, care has been taken to allow reversible transliteration to and from legacy character sets via source code transliteration utilities to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: 2015-09-20 07:46
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, care has been taken to allow reversible transliteration to and from legacy character sets via transliteration utilities in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: to:
Modula-2 syntax is based on the ASCII character set. However, care has been taken to allow reversible transliteration to and from legacy character sets via source code transliteration utilities in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: 2015-09-20 07:45
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets via transliteration utilities in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: to:
Modula-2 syntax is based on the ASCII character set. However, care has been taken to allow reversible transliteration to and from legacy character sets via transliteration utilities in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: 2015-09-20 07:44
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here accommodate any character set which contains at minimum the printable characters below: to:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets via transliteration utilities in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here require at minimum the availability of the following printable characters: 2015-09-20 07:41
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described below accommodate any character set which contains at minimum the printable characters below: to:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described here accommodate any character set which contains at minimum the printable characters below: 2015-09-20 07:40
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not use ASCII or Unicode. The recommendations described below accommodate any character set which contains at minimum the printable characters below: to:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not support ASCII or Unicode. The recommendations described below accommodate any character set which contains at minimum the printable characters below: 2015-09-20 07:40
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not use ASCII or Unicode. The recommendations described below accommodate any character set which contains at least the following 52 printable characters: to:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not use ASCII or Unicode. The recommendations described below accommodate any character set which contains at minimum the printable characters below: 2015-09-20 07:38
by -
Changed lines 6-7 from:
to:
2015-09-20 07:37
by -
Changed line 6 from:
'Minimal Required Characters to:
Minimal Required Characters 2015-09-20 07:37
by -
Changed line 6 from:
Minimal Required Character Set to:
'Minimal Required Characters 2015-09-20 07:36
by -
Changed line 3 from:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not use ASCII or Unicode. The transliteration recommendations described below accommodate any character set which contains at least the following 52 printable characters: to:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not use ASCII or Unicode. The recommendations described below accommodate any character set which contains at least the following 52 printable characters: 2015-09-20 07:35
by -
Added lines 2-12:
Modula-2 syntax is based on the ASCII character set. However, much care has been taken to allow reversible transliteration to and from legacy character sets in order to accommodate Modula-2 on computer systems that do not use ASCII or Unicode. The transliteration recommendations described below accommodate any character set which contains at least the following 52 printable characters: Minimal Required Character Set
Recommended Transliterations2015-09-20 06:51
by -
Changed line 75 from:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use to:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use 2015-09-20 06:49
by -
Changed line 42 from:
Where transliteration is applied to line comments, it is recommended to use transliteration to:
Where transliteration is applied to line comments, it is recommended to use 2015-09-20 06:49
by -
Changed line 42 from:
It is further recommended not to apply transliteration to line comments. However, if transliteration is to be applied to line comments, it is recommended to use transliteration to:
Where transliteration is applied to line comments, it is recommended to use transliteration 2015-09-20 06:45
by -
Changed line 19 from:
to:
2015-09-20 06:44
by -
Changed line 13 from:
Recording the Encoding in the Sourceto:
Recording the Encoding in the Source2015-09-20 06:43
by -
Added lines 12-22:
Recording the Encoding in the SourceIt is mandatory to record the character encoding scheme within transliterated source files using an ENCODING pragma. Example:
2015-09-20 06:15
by -
Changed lines 40-41 from:
Where specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration to:
Where specific character code points are to be hardcoded in transliterated source text, it is recommended to prefix the character code with Changed lines 43-44 from:
Example: to:
Examples:
2015-09-20 06:10
by -
Changed lines 38-40 from:
Transliteration of Hardcoded Code PointsWhere specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration to:
Transliteration of Character CodesWhere specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration 2015-09-20 06:09
by -
Added lines 36-44:
Transliteration of Hardcoded Code PointsWhere specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration Example: 2015-09-20 05:57
by -
Changed line 11 from:
to:
2015-09-20 05:52
by -
Changed lines 39-40 from:
In the unlikely event that the legacy character set does not provide an encoding for to:
In the now unlikely event that the legacy character set does not provide an encoding for Changed line 54 from:
In the unlikely event that the legacy character set does not support case sensitivity, it is recommended to use to:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use 2015-09-20 05:50
by -
Changed line 31 from:
It is further recommended not to apply transliteration to line comments. However, if transliteration is to be applied to line comments, it is recommended to use transliteration to:
It is further recommended not to apply transliteration to line comments. However, if transliteration is to be applied to line comments, it is recommended to use transliteration 2015-09-20 05:49
by -
Changed lines 24-25 from:
Where transliteration is applied to block comments, it is recommended to prefix the comment with a question mark. It is further recommended never to apply transliteration to line comments. to:
Where transliteration is applied to block comments, it is recommended to prefix the comment with a question mark. Added lines 29-35:
It is further recommended not to apply transliteration to line comments. However, if transliteration is to be applied to line comments, it is recommended to use transliteration Example: 2015-09-20 05:29
by -
Changed line 11 from:
to:
2015-09-20 05:27
by - 2015-09-20 05:25
by -
Changed line 11 from:
to:
2015-09-20 05:24
by -
Changed line 8 from:
to:
Changed line 11 from:
to:
2015-09-20 05:23
by -
Changed lines 7-8 from:
to:
Changed lines 10-11 from:
to:
2015-09-20 05:16
by -
Changed line 43 from:
to:
2015-09-20 05:16
by -
Changed line 43 from:
to:
2015-09-20 04:42
by -
Changed lines 15-16 from:
Where transliteration is desired to occur within within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate symbols to be transliterated by factoring and concatenation. to:
Where transliteration is applied within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate symbols to be transliterated by factoring and concatenation. Changed line 24 from:
Where transliteration is desired to occur within within block comments, it is recommended to prefix the comment with a question mark. It is further recommended never to apply transliteration to line comments. to:
Where transliteration is applied to block comments, it is recommended to prefix the comment with a question mark. It is further recommended never to apply transliteration to line comments. 2015-09-20 04:40
by -
Changed line 28 from:
to:
2015-09-20 04:40
by -
Changed lines 24-25 from:
Where transliteration is desired to occur within within block comments, it is recommended to prefix the comment with a dot. It is further recommended never to apply transliteration to line comments. to:
Where transliteration is desired to occur within within block comments, it is recommended to prefix the comment with a question mark. It is further recommended never to apply transliteration to line comments. Changed line 28 from:
to:
2015-09-20 04:39
by -
Added lines 20-28:
Transliteration Within CommentsWhere transliteration is desired to occur within within block comments, it is recommended to prefix the comment with a dot. It is further recommended never to apply transliteration to line comments. Example: 2015-09-20 04:29
by -
Changed line 27 from:
to:
2015-09-20 04:28
by -
Changed line 27 from:
to:
2015-09-20 04:27
by -
Changed line 8 from:
to:
Changed line 11 from:
to:
2015-09-20 04:19
by -
Changed line 15 from:
Where transliteration is desired to occur within within quoted string literals, it is recommended to prefix the string literal with a dot. Furthermore, symbols to be transliterated should be factored out and concatenated. to:
Where transliteration is desired to occur within within quoted string literals, it is recommended to prefix the string literal with a dot. It is further recommended to separate symbols to be transliterated by factoring and concatenation. 2015-09-20 04:15
by -
Changed line 19 from:
to:
2015-09-20 04:15
by -
Changed lines 13-15 from:
Double Quotation MarkIn the unlikely event that the legacy character set does not provide an encoding for to:
Transliteration Within Quoted LiteralsWhere transliteration is desired to occur within within quoted string literals, it is recommended to prefix the string literal with a dot. Furthermore, symbols to be transliterated should be factored out and concatenated. Changed line 19 from:
to:
Changed lines 22-23 from:
However, if the legacy character set provides an encoding for the vertical bar, one may use to:
Double Quotation MarkIn the unlikely event that the legacy character set does not provide an encoding for Changed line 27 from:
to:
Changed lines 30-37 from:
Case Sensitivityto:
However, if the legacy character set provides an encoding for the vertical bar, one may use Example: Case Sensitivity2015-09-20 03:58
by -
Changed line 8 from:
to:
Changed line 11 from:
to:
2015-09-20 03:53
by -
Changed line 8 from:
to:
Changed line 11 from:
to:
2015-09-20 03:44
by -
Changed line 7 from:
to:
Changed line 10 from:
to:
2015-09-20 03:36
by -
Deleted lines 11-29:
2015-09-20 03:34
by -
Added lines 4-11:
2015-09-19 15:38
by -
Changed line 3 from:
Implementors of transliteration utilities may choose whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended: to:
Implementors of transliteration utilities may choose whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended as their digraphs have been reserved: 2015-09-19 15:35
by -
Changed lines 25-26 from:
If the legacy character set does not provide an encoding for to:
In the unlikely event that the legacy character set does not provide an encoding for Changed line 40 from:
In the unlikely event that the legacy character set does not support case sensitivity it is recommended to use to:
In the unlikely event that the legacy character set does not support case sensitivity, it is recommended to use 2015-09-19 15:34
by -
Changed line 40 from:
If the legacy character set does not support case sensitivity it is recommended to use to:
In the unlikely event that the legacy character set does not support case sensitivity it is recommended to use 2015-09-19 15:30
by -
Changed line 29 from:
to:
2015-09-19 15:30
by -
Changed lines 29-30 from:
to:
Changed lines 36-37 from:
to:
Deleted lines 37-38:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags 2015-09-19 15:26
by -
Changed line 41 from:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags to:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags 2015-09-19 15:25
by -
Changed line 37 from:
to:
Changed line 41 from:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags to:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags 2015-09-19 15:24
by -
Added lines 40-41:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags 2015-09-19 15:21
by -
Changed line 37 from:
to:
2015-09-19 15:21
by -
Changed line 29 from:
to:
2015-09-19 15:17
by -
Changed line 29 from:
to:
Changed line 37 from:
to:
Changed line 47 from:
to:
2015-09-19 15:09
by -
Changed lines 37-38 from:
to:
2015-09-19 15:07
by -
Changed line 33 from:
However, if the legacy character set provides an encoding for the vertical bar, one may use to:
However, if the legacy character set provides an encoding for the vertical bar, one may use 2015-09-19 15:06
by -
Changed line 33 from:
However, if the vertical bar is available, one may use to:
However, if the legacy character set provides an encoding for the vertical bar, one may use 2015-09-19 15:05
by -
Changed line 33 from:
However, if the vertical bar is available, one may use transliteration to:
However, if the vertical bar is available, one may use 2015-09-19 15:04
by -
Changed line 33 from:
However, if the vertical bar is available, one may use to:
However, if the vertical bar is available, one may use transliteration 2015-09-19 15:02
by -
Changed lines 25-26 from:
If the legacy character set does not provide an encoding for to:
If the legacy character set does not provide an encoding for Example:
However, if the vertical bar is available, one may use 2015-09-19 14:53
by -
Changed line 3 from:
Implementors of transliteration utilities may choose to use whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended: to:
Implementors of transliteration utilities may choose whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended: 2015-09-19 14:51
by -
Changed line 3 from:
Implementors may choose to use whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended: to:
Implementors of transliteration utilities may choose to use whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended: 2015-09-19 14:42
by -
Changed line 25 from:
If the legacy character set does not provide an encoding for to:
If the legacy character set does not provide an encoding for 2015-09-19 14:37
by -
Changed lines 33-38 from:
If the legacy character set does not support case sensitivity it is recommended to use to:
If the legacy character set does not support case sensitivity it is recommended to use Example: 2015-09-19 14:36
by -
Changed lines 25-30 from:
If the legacy character set does not provide an encoding for to:
If the legacy character set does not provide an encoding for Example: 2015-09-19 14:26
by -
Changed line 25 from:
If the legacy character set does not provide an encoding for to:
If the legacy character set does not provide an encoding for 2015-09-19 14:19
by -
Changed lines 7-22 from:
to:
2015-09-19 14:17
by -
Changed lines 3-42 from:
Implementors may choose to use whichever digraph or trigraph translations they see fit provided that the translations are reversible. However, the following translations are recommended: BackslashIf the legacy character set does not provide an encoding for OctothorpeIf the legacy character set does not provide an encoding for AmpersandIf the legacy character set does not provide an encoding for TildeIf the legacy character set does not provide an encoding for Vertical BarIf the legacy character set does not provide an encoding for CaretIf the legacy character set does not provide an encoding for LowlineIf the legacy character set does not provide an encoding for Dollar SignIf the legacy character set does not provide an encoding for At SignIf the legacy character set does not provide an encoding for Percent SignIf the legacy character set does not provide an encoding for Curly BracesIf the legacy character set does not provide encodings for curly braces, it is recommended to use Square BracketsIf the legacy character set does not provide encodings for square brackets, it is recommended to use Angular Brackets With OctothorpeIf the legacy character set does not provide an encoding for to:
Implementors may choose to use whichever digraph or trigraph transliterations they see fit provided that the transliterations are reversible. However, the following transliterations are recommended:
2015-09-19 13:55
by -
Deleted lines 16-24:
Curly BracesIf the legacy character set does not provide encodings for curly braces, it is recommended to use Square BracketsIf the legacy character set does not provide encodings for square brackets, it is recommended to use Angular Brackets With OctothorpeIf the legacy character set does not provide an encoding for Added lines 34-42:
Curly BracesIf the legacy character set does not provide encodings for curly braces, it is recommended to use Square BracketsIf the legacy character set does not provide encodings for square brackets, it is recommended to use Angular Brackets With OctothorpeIf the legacy character set does not provide an encoding for 2015-09-19 13:54
by -
Deleted lines 13-15:
Vertical BarIf the legacy character set does not provide an encoding for Added lines 25-27:
Vertical BarIf the legacy character set does not provide an encoding for 2015-09-19 13:48
by -
Deleted lines 10-12:
CaretIf the legacy character set does not provide an encoding for Added lines 28-30:
CaretIf the legacy character set does not provide an encoding for 2015-09-19 11:02
by -
Changed line 42 from:
If the legacy character set does not provide an encoding for to:
If the legacy character set does not provide an encoding for 2015-09-19 11:01
by -
Changed line 48 from:
If the legacy character set does not support case sensitivity it is recommended to use to:
If the legacy character set does not support case sensitivity it is recommended to use 2015-09-19 11:01
by -
Changed lines 1-15 from:
=== This page needs updating ===6-bit Character Set TransliterationsImplementors may choose to use whichever digraph or trigraph translations they see fit provided that the translations are reversible. The following translations are recommended: Curly bracesIf the 6-bit character set does not provide encodings for curly braces, it is recommended to use Square bracketsIf the 6-bit character set does not provide encodings for square brackets, it is recommended to use Angular bracketsIf the 6-bit character set does not provide encodings for angular brackets, it is recommended to use to:
Legacy Character Set TransliterationsImplementors may choose to use whichever digraph or trigraph translations they see fit provided that the translations are reversible. However, the following translations are recommended: BackslashIf the legacy character set does not provide an encoding for OctothorpeIf the legacy character set does not provide an encoding for CaretIf the legacy character set does not provide an encoding for AmpersandIf the legacy character set does not provide an encoding for Vertical BarIf the legacy character set does not provide an encoding for TildeIf the legacy character set does not provide an encoding for Curly BracesIf the legacy character set does not provide encodings for curly braces, it is recommended to use Square BracketsIf the legacy character set does not provide encodings for square brackets, it is recommended to use Angular Brackets With OctothorpeIf the legacy character set does not provide an encoding for LowlineIf the legacy character set does not provide an encoding for Dollar SignIf the legacy character set does not provide an encoding for At SignIf the legacy character set does not provide an encoding for Percent SignIf the legacy character set does not provide an encoding for Changed lines 45-79 from:
If the 6-bit character set does not provide an encoding for the double quotation mark symbol, it is recommended to use LowlineIf the 6-bit character set does not provide an encoding for the lowline or underscore symbol Dollar signIf the 6-bit character set does not provide an encoding for the dollar sign OctothorpeIf the 6-bit character set does not provide an encoding for the octothorpe or hash symbol Vertical barIf the 6-bit character set does not provide an encoding for the vertical bar symbol BackslashIf the 6-bit character set does not provide an encoding for the backslash symbol CaretIf the 6-bit character set does not provide an encoding for the caret symbol TildeIf the 6-bit character set does not provide an encoding for the tilde symbol AmpersandIf the 6-bit character set does not provide an encoding for the ampersand symbol At signIf the 6-bit character set does not provide an encoding for the at sign Percent signIf the 6-bit character set does not provide an encoding for the percent sign Equal signIf the 6-bit character set does not provide an encoding for the equal sign to:
If the legacy character set does not provide an encoding for Changed lines 48-49 from:
In support of case sensitivity it is recommended to use the control codes to:
If the legacy character set does not support case sensitivity it is recommended to use 2015-09-17 17:57
by -
Added lines 1-54:
=== This page needs updating ===6-bit Character Set TransliterationsImplementors may choose to use whichever digraph or trigraph translations they see fit provided that the translations are reversible. The following translations are recommended: Curly bracesIf the 6-bit character set does not provide encodings for curly braces, it is recommended to use Square bracketsIf the 6-bit character set does not provide encodings for square brackets, it is recommended to use Angular bracketsIf the 6-bit character set does not provide encodings for angular brackets, it is recommended to use Double Quotation MarkIf the 6-bit character set does not provide an encoding for the double quotation mark symbol, it is recommended to use LowlineIf the 6-bit character set does not provide an encoding for the lowline or underscore symbol Dollar signIf the 6-bit character set does not provide an encoding for the dollar sign OctothorpeIf the 6-bit character set does not provide an encoding for the octothorpe or hash symbol Vertical barIf the 6-bit character set does not provide an encoding for the vertical bar symbol BackslashIf the 6-bit character set does not provide an encoding for the backslash symbol CaretIf the 6-bit character set does not provide an encoding for the caret symbol TildeIf the 6-bit character set does not provide an encoding for the tilde symbol AmpersandIf the 6-bit character set does not provide an encoding for the ampersand symbol At signIf the 6-bit character set does not provide an encoding for the at sign Percent signIf the 6-bit character set does not provide an encoding for the percent sign Equal signIf the 6-bit character set does not provide an encoding for the equal sign Case SensitivityIn support of case sensitivity it is recommended to use the control codes |