Modula-2 Reloaded

A Modern Typesafe & Literate Programming Notation

Site Menu

Project

Specification

Implementation

Recommendations

Reference

Needs Updating

Work in Progress

Wastebasket

Wiki Manual

edit SideBar

Transliteration

Recommendations.Transliteration History

Hide minor edits - Show changes to output

2015-10-04 15:08 by trijezdci -
Changed line 39 from:
 [@"foo~bar" --> "foo" & ."?-" & "bar"@]
to:
 [@"foo~bar" <--> "foo" & ."?-" & "bar"@]
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:
 [@(* foo\bar *) --> ?(* foo?/bar *)@]
to:
 [@(* foo\bar *) <--> ?(* foo?/bar *)@]
Changed line 55 from:
 [@! foo\bar --> ?; foo?/bar@]
to:
 [@! foo\bar <--> ?; foo?/bar@]
Changed lines 64-65 from:
 [@CONST euro = 0u20AC; --> CONST euro = ?+0x9F; (*EBCDIC1047*)@]
 [@CONST copyright = CHR(169); --> CONST copyright = ?+180; (*EBCDIC500*)@]
to:
 [@CONST euro = 0u20AC; <--> CONST euro = ?+0x9F; (*EBCDIC1047*)@]
 [@CONST copyright = CHR(169); <--> CONST copyright = ?+180; (*EBCDIC500*)@]
Changed line 73 from:
 [@"foo's bar" --> 'foo' & .'?,' & 's bar'@]
to:
 [@"foo's bar" <--> 'foo' & .'?,' & 's bar'@]
Changed line 80 from:
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
to:
 [@"foo's||bar's" <--> ||foo's|| & '||' & ||bar's||@]
Changed line 88 from:
 [@setFoo --> (-)SET(+)F(-)OO@]
to:
 [@setFoo <--> (-)SET(+)F(-)OO@]
2015-09-20 11:32 by trijezdci -
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 [[CoreLanguage.LexicalEntities#UtilitySymbols|reserved]]:
2015-09-20 09:01 by trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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. Transliteration utilities must take care to insert the pragma where absent, or update the encoding in the pragma where present.
to:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an [[SyntaxDiagrams.Pragmas#charEncodingPragma|[@ENCODING@] pragma]]. Transliteration utilities must take care to insert the pragma where absent, or update the encoding in the pragma where present.
2015-09-20 08:23 by trijezdci -
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. Transliteration utilities must take care to insert the pragma where absent, or update the encoding where present.
to:
It is mandatory for any Modula-2 source file that is not ASCII encoded to record the character encoding using an [@ENCODING@] pragma. Transliteration utilities must take care to insert the pragma where absent, or update the encoding in the pragma where present.
2015-09-20 08:23 by trijezdci -
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 [@ENCODING@] pragma. Transliteration utilities must take care to insert the pragma where absent, or update the encoding where present.
2015-09-20 08:21 by trijezdci -
Changed lines 51-52 from:
Where transliteration is applied to line comments, it is recommended to use @@?;@@ in place of the opening @@!@@ line comment prefix.
to:
Where transliteration is applied to line comments, it is recommended to use [@?;@] in place of the opening [@!@]&nbsp;line comment prefix.
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 [@?+@] in place of character code literals and @@CHR@@ function invocations.
to:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with [@?+@] in place of character code literals and [@CHR@] function invocations.
Changed lines 69-70 from:
In the now unlikely event that the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation.
to:
In the now unlikely event that the legacy character set does not provide an encoding for [@"@], it is recommended to eliminate double quoted strings by factoring and concatenation.
Changed lines 76-77 from:
However, if the legacy character set provides an encoding for the vertical bar, one may use @@||@@ as a transliteration instead in which case only less likely occurrences of @@||@@ within the string would need to be factored out and concatenated.
to:
However, if the legacy character set provides an encoding for the vertical bar, one may use [@||@] as a transliteration instead in which case only less likely occurrences of [@||@] within the string would need to be factored out and concatenated.
Changed line 84 from:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use @@(+)@@ as a prefix to switch to uppercase and @@(-)@@ as a prefix to switch to lowercase.
to:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use [@(+)@] as a prefix to switch to uppercase and [@(-)@] as a prefix to switch to lowercase.
2015-09-20 08:18 by trijezdci -
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 trijezdci -
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 trijezdci -
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 [@ENCODING@] pragma.
2015-09-20 08:15 by trijezdci -
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 trijezdci -
Changed line 1 from:
!!! Legacy Character Set Transliterations
to:
!!! Encoding Modula-2 in Legacy Character Sets
2015-09-20 08:09 by trijezdci -
Changed lines 16-17 from:
|| @@#@@ || @@&@@ || @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ \
|| @@\@@ || @@^@@ || @@|@@ || @@~@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ || @@##@@ || [@@@@] || [@'@] || [@"@] || [@`@] ||
to:
|| [@#@] || [@&@] || [@{@] || [@}@] || [@[@] || [@]@] || [@<#@] || [@#>@] \
|| [@\@] || [@^@] || [@|@] || [@~@] || [@_@] || [@$@] || [@@@] || [@%@] || [@##@] || [@@@@] || [@'@] || [@"@] || [@`@] ||
Changed lines 19-20 from:
|| @@/=@@ || @@+>@@ || @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ \
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,,@] || [@?<@] ||
to:
|| [@/=@] || [@+>@] || [@(.@] || [@.)@] || [@(:@] || [@:)@] || [@(=@] || [@=)@] \
|| [@?/@] || [@?>@] || [@?!@] || [@?-@] || [@?.@] || [@?=@] || [@?*@] || [@?:@] || [@??@] || [@???@] || [@?,@] ||  [@?,,@] || [@?<@] ||
2015-09-20 08:05 by trijezdci -
Changed line 60 from:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with @@?+@@ in place of character code literals and @@CHR@@ function invocations.
to:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with [@?+@] in place of character code literals and @@CHR@@ function invocations.
2015-09-20 08:05 by trijezdci -
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 @@?+@@ in place of character code literals and @@CHR@@ function invocations.
to:
Where specific character code points are hardcoded in transliterated source text, it is recommended to prefix the character code with @@?+@@ in place of character code literals and @@CHR@@ function invocations.
2015-09-20 08:03 by trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
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 trijezdci -
Changed lines 6-7 from:
 [@.  ,  :  ;  +  -  *  /  =  <  >  (  )  '  !  ?@]
 [@
0 1 2 3 4 5 6 7 8 9@]
to:
 [@.  ,  :  ;  +  -  *  /  =  <  >  (  )  '  !  ?  0 1 2 3 4 5 6 7 8 9@]
2015-09-20 07:37 by trijezdci -
Deleted line 5:
'''Minimal Required Characters'''
2015-09-20 07:37 by trijezdci -
Changed line 6 from:
'''Minimal Required Characters''
to:
'''Minimal Required Characters'''
2015-09-20 07:37 by trijezdci -
Changed line 6 from:
'''Minimal Required Character Set'''
to:
'''Minimal Required Characters''
2015-09-20 07:36 by trijezdci -
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 trijezdci -
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:

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Minimal Required Character Set'''
 [@.  ,  :  ;  +  -  *  /  =  <  >  (  )  '  !  ?@]
 [@0 1 2 3 4 5 6 7 8 9@]
 [@A B C D E F G H I J K L M N O P Q R S T U V W X Y Z@]
>><<

!!!! Recommended Transliterations
2015-09-20 06:51 by trijezdci -
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 switch to uppercase and @@(-)@@ to switch to lowercase.
to:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use @@(+)@@ as a prefix to switch to uppercase and @@(-)@@ as a prefix to switch to lowercase.
2015-09-20 06:49 by trijezdci -
Changed line 42 from:
Where transliteration is applied to line comments, it is recommended to use transliteration @@?;@@ in place of the opening @@!@@ line comment prefix.
to:
Where transliteration is applied to line comments, it is recommended to use @@?;@@ in place of the opening @@!@@ line comment prefix.
2015-09-20 06:49 by trijezdci -
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 @@?;@@ in place of the opening @@!@@ line comment prefix.
to:
Where transliteration is applied to line comments, it is recommended to use transliteration @@?;@@ in place of the opening @@!@@ line comment prefix.
2015-09-20 06:45 by trijezdci -
Changed line 19 from:
 [@<*ENCODING="EBDIC500"*> (* Transliterated Modula-2 Source Text *)@]
to:
 [@<*ENCODING="EBCDIC500"*> (* Transliterated Modula-2 Source Text *)@]
2015-09-20 06:44 by trijezdci -
Changed line 13 from:
!!!! Recording the Encoding in the Source
to:
!!!!! Recording the Encoding in the Source
2015-09-20 06:43 by trijezdci -
Added lines 12-22:

!!!! Recording the Encoding in the Source

It is mandatory to record the character encoding scheme within transliterated source files using an ENCODING pragma.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@<*ENCODING="EBDIC500"*> (* Transliterated Modula-2 Source Text *)@]
 [@DEFINITION MODULE Foobar;@]
 [@...@]
>><<
2015-09-20 06:15 by trijezdci -
Changed lines 40-41 from:
Where specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration @@?+@@ in place of character code literals and @@CHR@@ function invocations.
to:
Where specific character code points are to be hardcoded in transliterated source text, it is recommended to prefix the character code with @@?+@@ in place of character code literals and @@CHR@@ function invocations.
Changed lines 43-44 from:
'''Example:'''
to:
'''Examples:'''
 [@CONST euro = 0u20AC; --> CONST euro = ?+0x9F; (*EBCDIC1047*)@]
2015-09-20 06:10 by trijezdci -
Changed lines 38-40 from:
!!!!! Transliteration of Hardcoded Code Points

Where
specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration @@?+@@ in place of a CHR function invocation.
to:
!!!!! Transliteration of Character Codes

Where
specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration @@?+@@ in place of character code literals and @@CHR@@ function invocations.
2015-09-20 06:09 by trijezdci -
Added lines 36-44:
>><<

!!!!! Transliteration of Hardcoded Code Points

Where specific character code points are to be hardcoded in transliterated source text, it is recommended to use transliteration @@?+@@ in place of a CHR function invocation.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@CONST copyright = CHR(169); --> CONST copyright = ?+180; (*EBCDIC500*)@]
2015-09-20 05:57 by trijezdci -
Changed line 11 from:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,,@] || [@?+@] ||
to:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,,@] || [@?<@] ||
2015-09-20 05:52 by trijezdci -
Changed lines 39-40 from:
In the unlikely event that the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation.
to:
In the now unlikely event that the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation.
Changed line 54 from:
In the unlikely event that the legacy character set does not support case sensitivity, it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
to:
In the now unlikely event that the legacy character set does not support case sensitivity, it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
2015-09-20 05:50 by trijezdci -
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 @@?;@@ in place of the opening @@!@@ comment delimiter.
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 @@?;@@ in place of the opening @@!@@ line comment prefix.
2015-09-20 05:49 by trijezdci -
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 @@?;@@ in place of the opening @@!@@ comment delimiter.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@! foo\bar --> ?; foo?/bar@]
2015-09-20 05:29 by trijezdci -
Changed line 11 from:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,,@] || [@?'@] ||
to:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,,@] || [@?+@] ||
2015-09-20 05:27 by trijezdci -
2015-09-20 05:25 by trijezdci -
Changed line 11 from:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,@] || [@?'@] ||
to:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,,@] || [@?'@] ||
2015-09-20 05:24 by trijezdci -
Changed line 8 from:
|| @@\@@ || @@^@@ || @@|@@ || @@~@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ || @@##@@ || [@@@@] || [@'@] || [@"@] ||
to:
|| @@\@@ || @@^@@ || @@|@@ || @@~@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ || @@##@@ || [@@@@] || [@'@] || [@"@] || [@`@] ||
Changed line 11 from:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] || [@?,,@] ||
to:
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] ||  [@?,@] || [@?'@] ||
2015-09-20 05:23 by trijezdci -
Changed lines 7-8 from:
|| @@#@@ || @@&@@ || @@\@@ || @@^@@ || @@|@@ || @@~@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ \
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ || @@##@@ || [@@@@] || [@'@] || [@"@] ||
to:
|| @@#@@ || @@&@@ || @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ \
|| @@\@@ || @@^@@ || @@|@@ || @@~@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ || @@##@@ || [@@@@] || [@'@] || [@"@] ||
Changed lines 10-11 from:
|| @@/=@@ || @@+>@@ || @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ \
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ || @@???@@ || [@?,@] || [@?,,@] ||
to:
|| @@/=@@ || @@+>@@ || @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ \
|| @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ || @@??@@ || @@???@@ || [@?,@] || [@?,,@] ||
2015-09-20 05:16 by trijezdci -
Changed line 43 from:
 [@"foo's||bar's" --> ||foo's|| & .'||' & ||bar's||@]
to:
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
2015-09-20 05:16 by trijezdci -
Changed line 43 from:
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
to:
 [@"foo's||bar's" --> ||foo's|| & .'||' & ||bar's||@]
2015-09-20 04:42 by trijezdci -
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 trijezdci -
Changed line 28 from:
 [@(* foo\bar *) --> ?(* foo\bar *)@]
to:
 [@(* foo\bar *) --> ?(* foo?/bar *)@]
2015-09-20 04:40 by trijezdci -
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:
 [@(* foo\bar *) --> .(* foo\bar *)@]
to:
 [@(* foo\bar *) --> ?(* foo\bar *)@]
2015-09-20 04:39 by trijezdci -
Added lines 20-28:
>><<

!!!!! Transliteration Within Comments

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.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@(* foo\bar *) --> .(* foo\bar *)@]
2015-09-20 04:29 by trijezdci -
Changed line 27 from:
 [@"foo's bar" --> 'foo' & .'?,,' & 's bar'@]
to:
 [@"foo's bar" --> 'foo' & .'?,' & 's bar'@]
2015-09-20 04:28 by trijezdci -
Changed line 27 from:
 [@"foo's bar" --> 'foo' & CHR(39) & 's bar'@]
to:
 [@"foo's bar" --> 'foo' & .'?,,' & 's bar'@]
2015-09-20 04:27 by trijezdci -
Changed line 8 from:
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ || @@##@@ || [@@@@] ||
to:
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ || @@##@@ || [@@@@] || [@'@] || [@"@] ||
Changed line 11 from:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ || @@???@@ ||
to:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ || @@???@@ || [@?,@] || [@?,,@] ||
2015-09-20 04:19 by trijezdci -
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 trijezdci -
Changed line 19 from:
 [@"foo~bar" --> "foo" & ."?-" & "s bar"@]
to:
 [@"foo~bar" --> "foo" & ."?-" & "bar"@]
2015-09-20 04:15 by trijezdci -
Changed lines 13-15 from:
!!!!!Double Quotation Mark
In the unlikely event that the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation
.
to:
!!!!! Transliteration Within Quoted Literals

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
.
Changed line 19 from:
 [@"foo's bar" --> 'foo' & CHR(39) & 's bar'@]
to:
 [@"foo~bar" --> "foo" & ."?-" & "s bar"@]
Changed lines 22-23 from:
However, if the legacy character set provides an encoding for the vertical bar, one may use @@||@@ as a transliteration instead in which case only less likely occurrences of @@||@@ within the string would need to be factored out and concatenated.
to:
!!!!! Double Quotation Mark
In the unlikely event that the legacy character set does not provide an encoding for
@@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation.
Changed line 27 from:
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
to:
 [@"foo's bar" --> 'foo' & CHR(39) & 's bar'@]
Changed lines 30-37 from:
!!!!!Case Sensitivity
to:
However, if the legacy character set provides an encoding for the vertical bar, one may use @@||@@ as a transliteration instead in which case only less likely occurrences of @@||@@ within the string would need to be factored out and concatenated.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
>><<

!!!!!
Case Sensitivity
2015-09-20 04:00 by trijezdci -
Changed line 11 from:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ || @@&&@@ ||
to:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ || @@???@@ ||
2015-09-20 03:58 by trijezdci -
Changed line 8 from:
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ || @@##@@ ||
to:
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ || @@##@@ || [@@@@] ||
Changed line 11 from:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ ||
to:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ || @@&&@@ ||
2015-09-20 03:53 by trijezdci -
Changed line 8 from:
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ ||
to:
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ || @@##@@ ||
Changed line 11 from:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ ||
to:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ || @@??@@ ||
2015-09-20 03:44 by trijezdci -
Changed line 7 from:
|| @@#@@ || @@&@@ || @@\@@ || @@^@@ || @@~@@ || @@|@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ \
to:
|| @@#@@ || @@&@@ || @@\@@ || @@^@@ || @@|@@ || @@~@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ \
Changed line 10 from:
|| @@/=@@ || @@+>@@ || @@?/@@ || @@?>@@ || @@?-@@ || @@?!@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ \
to:
|| @@/=@@ || @@+>@@ || @@?/@@ || @@?>@@ || @@?!@@ || @@?-@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ \
2015-09-20 03:38 by trijezdci -
Changed line 10 from:
|| @@/=@@ || @@+>@@ || @@/<@@ || @@?>@@ || @@?-@@ || @@?!@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ \
to:
|| @@/=@@ || @@+>@@ || @@?/@@ || @@?>@@ || @@?-@@ || @@?!@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ \
2015-09-20 03:36 by trijezdci -
Deleted lines 11-29:

|| class=headrow border=1 cellspacing=0
||!Original Symbol ||!Transliteration||
|| @@#@@ || @@/=@@ ||
|| @@&@@ || @@+>@@ ||
|| @@\@@ || @@/<@@ ||
|| @@^@@ || @@?>@@ ||
|| @@~@@ || @@?-@@ ||
|| @@|@@ || @@?!@@ ||
|| @@_@@ || @@?.@@ ||
|| @@$@@ || @@?=@@ ||
|| @@@@@ || @@?*@@ ||
|| @@%@@ || @@?:@@ ||
|| @@{@@ || @@(.@@ ||
|| @@}@@ || @@.)@@ ||
|| [@[@] || @@(:@@ ||
|| [@]@] || @@:)@@ ||
|| @@<#@@ || @@(=@@ ||
|| @@#>@@ || @@=)@@ ||
2015-09-20 03:36 by trijezdci -
Changed line 11 from:
|| @@(.@@ | @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ ||
to:
|| @@(.@@ || @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ ||
2015-09-20 03:34 by trijezdci -
Added lines 4-11:

|| class=headrow border=1 cellspacing=0
||!Original Symbol \
|| @@#@@ || @@&@@ || @@\@@ || @@^@@ || @@~@@ || @@|@@ || @@_@@ || @@$@@ || @@@@@ || @@%@@ \
|| @@{@@ || @@}@@ || [@[@] || [@]@] || @@<#@@ || @@#>@@ ||
||!Transliteration \
|| @@/=@@ || @@+>@@ || @@/<@@ || @@?>@@ || @@?-@@ || @@?!@@ || @@?.@@ || @@?=@@ || @@?*@@ || @@?:@@ \
|| @@(.@@ | @@.)@@ || @@(:@@ || @@:)@@ || @@(=@@ || @@=)@@ ||
2015-09-19 15:38 by trijezdci -
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 trijezdci -
Changed lines 25-26 from:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation.
to:
In the unlikely event that the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation.
Changed line 40 from:
In the unlikely event that the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
to:
In the unlikely event that the legacy character set does not support case sensitivity, it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
2015-09-19 15:34 by trijezdci -
Changed line 40 from:
If the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
to:
In the unlikely event that the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
2015-09-19 15:30 by trijezdci -
Changed line 29 from:
 [@"foo's bar" --> 'foo' & CHR(39); & 's bar'@]
to:
 [@"foo's bar" --> 'foo' & CHR(39) & 's bar'@]
2015-09-19 15:30 by trijezdci -
Changed lines 29-30 from:
 [@(*?XLAT INSERT*) CONST apo = CHR(39); (*?INSERT END*)@]
 [@"foo's bar" --> 'foo' & apo
& 's bar'@]
to:
 [@"foo's bar" --> 'foo' & CHR(39); & 's bar'@]
Changed lines 36-37 from:
 [@(*?XLAT INSERT*) CONST doubleBar = '||'; (*?INSERT END*)@]
 [@"foo
's||bar's" --> ||foo's|| & doubleBar & ||bar's||@]
to:
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
Deleted lines 37-38:

To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags [@(*?XLAT INSERT*)@] and [@(*?INSERT END*)@] so that the inserts can be automatically identified and removed when the source text is transliterated back to ASCII.
2015-09-19 15:26 by trijezdci -
Changed line 41 from:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags [@(*?XLAT INSERT*)@] and [@(*?INSERT END*)@] so that the inserts can be identified and removed when the source text is transliterated back to ASCII.
to:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags [@(*?XLAT INSERT*)@] and [@(*?INSERT END*)@] so that the inserts can be automatically identified and removed when the source text is transliterated back to ASCII.
2015-09-19 15:25 by trijezdci -
Changed line 37 from:
 [@(*?XLAT INSERT*) CONST doubleBar = '||'; (*?XLAT INSERT*)@]
to:
 [@(*?XLAT INSERT*) CONST doubleBar = '||'; (*?INSERT END*)@]
Changed line 41 from:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags [@(*?XLAT INSERT*)@] and [@(*?XLAT INSERT*)@] so that the inserts can be identified and removed when the source text is transliterated back to ASCII.
to:
To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags [@(*?XLAT INSERT*)@] and [@(*?INSERT END*)@] so that the inserts can be identified and removed when the source text is transliterated back to ASCII.
2015-09-19 15:24 by trijezdci -
Added lines 40-41:

To ensure reversibility of transliteration, it is recommended that transliteration utilities will enclose any ancillary inserts in special comment tags [@(*?XLAT INSERT*)@] and [@(*?XLAT INSERT*)@] so that the inserts can be identified and removed when the source text is transliterated back to ASCII.
2015-09-19 15:21 by trijezdci -
Changed line 37 from:
 [@(*INSERT BY XLAT*) CONST doubleBar = '||'; (*INSERT END*)@]
to:
 [@(*?XLAT INSERT*) CONST doubleBar = '||'; (*?XLAT INSERT*)@]
2015-09-19 15:21 by trijezdci -
Changed line 29 from:
 [@(*INSERT BY XLAT*) CONST apo = CHR(39); (*INSERT END*)@]
to:
 [@(*?XLAT INSERT*) CONST apo = CHR(39); (*?INSERT END*)@]
2015-09-19 15:17 by trijezdci -
Changed line 29 from:
 [@CONST apo = CHR(39);@]
to:
 [@(*INSERT BY XLAT*) CONST apo = CHR(39); (*INSERT END*)@]
Changed line 37 from:
 [@CONST doubleBar = '||';@]
to:
 [@(*INSERT BY XLAT*) CONST doubleBar = '||'; (*INSERT END*)@]
Changed line 47 from:
>><<
to:
>><<
2015-09-19 15:09 by trijezdci -
Changed lines 37-38 from:
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
to:
 [@CONST doubleBar = '||';@]
 [@"
foo's||bar's" --> ||foo's|| & doubleBar & ||bar's||@]
2015-09-19 15:07 by trijezdci -
Changed line 33 from:
However, if the legacy character set provides an encoding for the vertical bar, one may use @@||@@ as a transliteration instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
to:
However, if the legacy character set provides an encoding for the vertical bar, one may use @@||@@ as a transliteration instead in which case only less likely occurrences of @@||@@ within the string would need to be factored out and concatenated.
2015-09-19 15:06 by trijezdci -
Changed line 33 from:
However, if the vertical bar is available, one may use @@||@@ as a transliteration instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
to:
However, if the legacy character set provides an encoding for the vertical bar, one may use @@||@@ as a transliteration instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
2015-09-19 15:05 by trijezdci -
Changed line 33 from:
However, if the vertical bar is available, one may use transliteration @@||@@ instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
to:
However, if the vertical bar is available, one may use @@||@@ as a transliteration instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
2015-09-19 15:04 by trijezdci -
Changed line 33 from:
However, if the vertical bar is available, one may use @@||@@ instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
to:
However, if the vertical bar is available, one may use transliteration @@||@@ instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
2015-09-19 15:02 by trijezdci -
Changed lines 25-26 from:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation. However, if the vertical bar is available, one may use @@||@@ instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
to:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@CONST apo = CHR(39);
@]
 [
@"foo's bar" --> 'foo' & apo & 's bar'@]
>><<

However, if
the vertical bar is available, one may use @@||@@ instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
2015-09-19 14:53 by trijezdci -
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 trijezdci -
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 trijezdci -
Changed line 25 from:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to avoid double quoted strings altogether. However, if the vertical bar is available, one may use @@||@@ instead in which case any occurrences of @@||@@ within the string will need to be factored out and concatenated.
to:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to eliminate double quoted strings by factoring and concatenation. However, if the vertical bar is available, one may use @@||@@ instead in which case only occurrences of @@||@@ within the string would need to be factored out and concatenated.
2015-09-19 14:37 by trijezdci -
Changed lines 33-38 from:
If the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
to:
If the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@setFoo --> (-)SET(+)F(-)OO@]
>><<
2015-09-19 14:36 by trijezdci -
Changed lines 25-30 from:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to avoid double quoted strings altogether. However, if the vertical bar is available, one may use @@||@@ instead but occurrences of @@||@@ within the string will need to be factored out.
to:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to avoid double quoted strings altogether. However, if the vertical bar is available, one may use @@||@@ instead in which case any occurrences of @@||@@ within the string will need to be factored out and concatenated.

>>background-color:#f4f4f4 padding:0.5em border:'thin solid gray' whitespace:pre<<
'''Example:'''
 [@"foo's||bar's" --> ||foo's|| & '||' & ||bar's||@]
>><<
2015-09-19 14:26 by trijezdci -
Changed line 25 from:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to use @@(')@@ instead.
to:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to avoid double quoted strings altogether. However, if the vertical bar is available, one may use @@||@@ instead but occurrences of @@||@@ within the string will need to be factored out.
2015-09-19 14:19 by trijezdci -
Changed line 20 from:
|| [ @]@] || @@:)@@ ||
to:
|| [@]@] || @@:)@@ ||
2015-09-19 14:19 by trijezdci -
Changed lines 7-22 from:
||@@#@@ ||@@/=@@ ||
||@@&@@ ||@@+>@@ ||
||@@\@@ ||@@/<@@ ||
||@@^@@ ||@@?>@@ ||
||@@~@@ ||@@?-@@ ||
||@@|@@ ||@@?!@@ ||
||@@_@@ ||@@?.@@ ||
||@@$@@ ||@@?=@@ ||
||@@@@@ ||@@?*@@ ||
||@@%@@ ||@@?:@@ ||
||@@{@@ ||@@(.@@ ||
||@@}@@ ||@@.)@@ ||
||[@[@] ||@@(:@@ ||
||[@]@] ||@@:)@@ ||
||@@<#@@ ||@@(=@@ ||
||@@#>@@ ||@@=)@@ ||
to:
|| @@#@@ || @@/=@@ ||
|| @@&@@ || @@+>@@ ||
|| @@\@@ || @@/<@@ ||
|| @@^@@ || @@?>@@ ||
|| @@~@@ || @@?-@@ ||
|| @@|@@ || @@?!@@ ||
|| @@_@@ || @@?.@@ ||
|| @@$@@ || @@?=@@ ||
|| @@@@@ || @@?*@@ ||
|| @@%@@ || @@?:@@ ||
|| @@{@@ || @@(.@@ ||
|| @@}@@ || @@.)@@ ||
|| [@[@] || @@(:@@ ||
|| [ @]@] || @@:)@@ ||
|| @@<#@@ || @@(=@@ ||
|| @@#>@@ || @@=)@@ ||
2015-09-19 14:18 by trijezdci -
Changed lines 19-20 from:
||@@[@@ ||@@(:@@ ||
||@@]@@ ||@@:)@@ ||
to:
||[@[@] ||@@(:@@ ||
||[@]@] ||@@:)@@ ||
2015-09-19 14:17 by trijezdci -
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:

!!!!! Backslash
If the legacy character set does not provide an encoding for
@@\@@, it is recommended to use [@/<@] instead.

!!!!! Octothorpe
If the legacy character set does not provide an encoding for
@@#@@, it is recommended to use [@/=@] instead.

!!!!! Ampersand
If the legacy character set does not provide an encoding for
@@&@@, it is recommended to use [@+>@] instead.

!!!!! Tilde
If the legacy character set does not provide an encoding for @@~@@, it is recommended to use [@.-@] instead.

!!!!! Vertical Bar
If the legacy character set does not provide an encoding for @@
|@@, it is recommended to use [@?!@] instead.

!!!!! Caret
If the legacy character set does not provide an encoding for @@^@@, it is recommended to use [@?>@] instead.

!!!!! Lowline
If the legacy character set does not provide an encoding for @@_@@, it is recommended to use [@?-@] instead.

!!!!! Dollar Sign
If the legacy character set does not provide an encoding for @@$@@, it is recommended to use [@?=@] instead.

!!!!! At Sign
If the legacy character set does not provide an encoding for @@@@@, it is recommended to use [@?.@] instead.

!!!!! Percent Sign
If the legacy character set does not provide an encoding for @@%@@, it is recommended to use [@?:@] instead.

!!!!! Curly Braces
If the legacy character set does not provide encodings for curly braces, it is recommended to use [@(.@] for [@{@] and [@.)@] for [@}@] instead.

!!!!! Square Brackets
If the legacy character set does not provide encodings for square brackets, it is recommended to use [@(!@] or [@(/@] for [@[@] and [@!)@] or [@/)@] for [@]@] instead.

!!!!! Angular Brackets With Octothorpe
If the legacy character set does not provide an encoding for @@#@@, it is recommended to use [@(=@]  for [@<#@] and [@=)@] for [@#>@] instead.
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:

|| class=headrow border=1 cellspacing=0
||!Original Symbol ||!Transliteration||
||@@#@@ ||@@/=@@ ||
||@@&@@ ||
@@+>@@ ||
||@@\@@ ||
@@/<@@ ||
||@@^@@ ||@@?>@@ ||
||@@~@@ ||@@?-@@ ||
||@@|@@ ||@@?!@@ ||
||@@_@@ ||
@@?.@@ ||
||@@$@@ ||
@@?=@@ ||
||@@@@@ ||@@?*@@ ||
||@@%@@ ||@@?:@@ ||
||@@{@@ ||@@(.@@ ||
||@@}@@ ||
@@.)@@ ||
||@@[@@ ||
@@(:@@ ||
||@@]@@ ||@@:)@@ ||
||@@<#@@ ||@@(=@@ ||
||@@#>@@ ||@@=)@@
||
2015-09-19 13:55 by trijezdci -
Deleted lines 16-24:
!!!!! Curly Braces
If the legacy character set does not provide encodings for curly braces, it is recommended to use [@(.@] for [@{@] and [@.)@] for [@}@] instead.

!!!!! Square Brackets
If the legacy character set does not provide encodings for square brackets, it is recommended to use [@(!@] or [@(/@] for [@[@] and [@!)@] or [@/)@] for [@]@] instead.

!!!!! Angular Brackets With Octothorpe
If the legacy character set does not provide an encoding for @@#@@, it is recommended to use [@(=@]  for [@<#@] and [@=)@] for [@#>@] instead.

Added lines 34-42:

!!!!! Curly Braces
If the legacy character set does not provide encodings for curly braces, it is recommended to use [@(.@] for [@{@] and [@.)@] for [@}@] instead.

!!!!! Square Brackets
If the legacy character set does not provide encodings for square brackets, it is recommended to use [@(!@] or [@(/@] for [@[@] and [@!)@] or [@/)@] for [@]@] instead.

!!!!! Angular Brackets With Octothorpe
If the legacy character set does not provide an encoding for @@#@@, it is recommended to use [@(=@]  for [@<#@] and [@=)@] for [@#>@] instead.
2015-09-19 13:54 by trijezdci -
Deleted lines 13-15:
!!!!! Vertical Bar
If the legacy character set does not provide an encoding for @@|@@, it is recommended to use [@./@] instead.

Added lines 25-27:

!!!!! Vertical Bar
If the legacy character set does not provide an encoding for @@|@@, it is recommended to use [@?!@] instead.
2015-09-19 13:48 by trijezdci -
Deleted lines 10-12:
!!!!! Caret
If the legacy character set does not provide an encoding for @@^@@, it is recommended to use [@=>@] instead.

Added lines 28-30:

!!!!! Caret
If the legacy character set does not provide an encoding for @@^@@, it is recommended to use [@?>@] instead.
2015-09-19 11:02 by trijezdci -
Changed line 42 from:
If the legacy character set does not provide an encoding for @@@@@, it is recommended to use [@?:@] instead.
to:
If the legacy character set does not provide an encoding for @@%@@, it is recommended to use [@?:@] instead.
2015-09-19 11:01 by trijezdci -
Changed line 48 from:
If the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-) to switch to lowercase.
to:
If the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-)@@ to switch to lowercase.
2015-09-19 11:01 by trijezdci -
Changed lines 1-15 from:
!!! === This page needs updating ===

!!! 6-bit Character Set Transliterations

Implementors may choose to use whichever digraph or trigraph translations they see fit provided that the translations are reversible. The following translations are recommended:

!!!!!Curly braces
If the 6-bit character set does not provide encodings for curly braces, it is recommended to use [@(.@] for [@{@] and [@.)@] for [@}@] instead.

!!!!!Square brackets
If the 6-bit character set does not provide encodings for square brackets, it is recommended to use [@(!@] or [@(/@] for [@[@] and [@!)@] or [@/)@] for [@]@] instead.

!!!!!Angular brackets
If the 6-bit character set does not provide encodings for angular brackets, it is recommended to use [@%GT%@] for [@>@], [@%GE%@] for [@>=@], [@%LT%@] for [@<@] and [@%LE%@] for [@<=@] instead.

to:
!!! Legacy Character Set Transliterations

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:

!!!!! Backslash
If the legacy character set does not provide an encoding for @@\@@, it is recommended to use [@/<@] instead.

!!!!! Octothorpe
If the legacy character set does not provide an encoding for @@#@@, it is recommended to use [@/=@] instead.

!!!!! Caret
If the legacy character set does not provide an encoding for @@^@@, it is recommended to use [@=>@] instead.

!!!!! Ampersand
If the legacy character set does not provide an encoding for @@&@@, it is recommended to use [@+>@] instead.

!!!!! Vertical Bar
If the legacy character set does not provide an encoding for @@|@@, it is recommended to use [@./@] instead.

!!!!! Tilde
If the legacy character set does not provide an encoding for @@~@@, it is recommended to use [@.-@] instead.

!!!!! Curly Braces
If the legacy character set does not provide encodings for curly braces, it is recommended to use [@(.@] for [@{@] and [@.)@] for [@}@] instead.

!!!!! Square Brackets
If the legacy character set does not provide encodings for square brackets, it is recommended to use [@(!@] or [@(/@] for [@[@] and [@!)@] or [@/)@] for [@]@] instead.

!!!!! Angular Brackets With Octothorpe
If the legacy character set does not provide an encoding for @@#@@, it is recommended to use [@(=@]  for [@<#@] and [@=)@] for [@#>@] instead.

!!!!! Lowline
If the legacy character set does not provide an encoding for @@_@@, it is recommended to use [@?-@] instead.

!!!!! Dollar Sign
If the legacy character set does not provide an encoding for @@$@@, it is recommended to use [@?=@] instead.

!!!!! At Sign
If the legacy character set does not provide an encoding for @@@@@, it is recommended to use [@?.@] instead.

!!!!! Percent Sign
If the legacy character set does not provide an encoding for @@@@@, it is recommended to use [@?:@] instead.

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 [@<<@] for the opening [@"@] and [@>>@] for the closing [@"@] instead. If angular brackets are not available, it is recommended to use [@%'@] for [@"@] instead.

!!!!!Lowline
If the 6-bit character set does not provide an encoding for the lowline or underscore symbol [@_@], it is recommended to use [@!.@] or [@/.@] instead.

!!!!!Dollar sign
If the 6-bit character set does not provide an encoding for the dollar sign [@$@], it is recommended to use the available currency symbol instead.

!!!!!Octothorpe
If the 6-bit character set does not provide an encoding for the octothorpe or hash symbol [@#@], it is recommended to use [@!=@] or [@/=@] instead.

!!!!!Vertical bar
If the 6-bit character set does not provide an encoding for the vertical bar symbol [@|@], it is recommended to use [@!@] or [@/:@] instead.

!!!!!Backslash
If the 6-bit character set does not provide an encoding for the backslash symbol [@\@], it is recommended to use [@.!@] or [@./@] instead.

!!!!!Caret
If the 6-bit character set does not provide an encoding for the caret symbol  [@^@], it is recommended to use [@->@] instead. If angular brackets are not available, it is recommended to use [@%DREF%@] instead.

!!!!!Tilde
If the 6-bit character set does not provide an encoding for the tilde symbol  [@~@], it is recommended to use [@NOT@] instead.

!!!!!Ampersand
If the 6-bit character set does not provide an encoding for the ampersand symbol  [@&@], it is recommended to use [@AND@] instead.

!!!!!At sign
If the 6-bit character set does not provide an encoding for the at sign [@@@] used by the Modula-2 template utility to tag placeholders, it is recommended to use [@**@] or [@&&@] for [@@@@] instead.

!!!!!Percent sign
If the 6-bit character set does not provide an encoding for the percent sign [@%@] used by the Modula-2 template utility to mark template comments, it is recommended to use [@==@] for [@%%@] instead.

!!!!!Equal sign
If the 6-bit character set does not provide an encoding for the equal sign  [@=@], it is recommended to use [@%EQ%@] for [@=@] and [@%ASSIGN%@] for [@:=@] instead.

to:
If the legacy character set does not provide an encoding for @@"@@, it is recommended to use @@(')@@ instead.
Changed lines 48-49 from:
In support of case sensitivity it is recommended to use the control codes [@SI@] and [@SO@] to switch between uppercase and lowercase.
to:
If the legacy character set does not support case sensitivity it is recommended to use @@(+)@@ to switch to uppercase and @@(-) to switch to lowercase.
2015-09-17 17:57 by trijezdci -
Added lines 1-54:
!!! === This page needs updating ===

!!! 6-bit Character Set Transliterations

Implementors may choose to use whichever digraph or trigraph translations they see fit provided that the translations are reversible. The following translations are recommended:

!!!!!Curly braces
If the 6-bit character set does not provide encodings for curly braces, it is recommended to use [@(.@] for [@{@] and [@.)@] for [@}@] instead.

!!!!!Square brackets
If the 6-bit character set does not provide encodings for square brackets, it is recommended to use [@(!@] or [@(/@] for [@[@] and [@!)@] or [@/)@] for [@]@] instead.

!!!!!Angular brackets
If the 6-bit character set does not provide encodings for angular brackets, it is recommended to use [@%GT%@] for [@>@], [@%GE%@] for [@>=@], [@%LT%@] for [@<@] and [@%LE%@] for [@<=@] instead.

!!!!!Double Quotation Mark
If the 6-bit character set does not provide an encoding for the double quotation mark symbol, it is recommended to use [@<<@] for the opening [@"@] and [@>>@] for the closing [@"@] instead. If angular brackets are not available, it is recommended to use [@%'@] for [@"@] instead.

!!!!!Lowline
If the 6-bit character set does not provide an encoding for the lowline or underscore symbol [@_@], it is recommended to use [@!.@] or [@/.@] instead.

!!!!!Dollar sign
If the 6-bit character set does not provide an encoding for the dollar sign [@$@], it is recommended to use the available currency symbol instead.

!!!!!Octothorpe
If the 6-bit character set does not provide an encoding for the octothorpe or hash symbol [@#@], it is recommended to use [@!=@] or [@/=@] instead.

!!!!!Vertical bar
If the 6-bit character set does not provide an encoding for the vertical bar symbol [@|@], it is recommended to use [@!@] or [@/:@] instead.

!!!!!Backslash
If the 6-bit character set does not provide an encoding for the backslash symbol [@\@], it is recommended to use [@.!@] or [@./@] instead.

!!!!!Caret
If the 6-bit character set does not provide an encoding for the caret symbol  [@^@], it is recommended to use [@->@] instead. If angular brackets are not available, it is recommended to use [@%DREF%@] instead.

!!!!!Tilde
If the 6-bit character set does not provide an encoding for the tilde symbol  [@~@], it is recommended to use [@NOT@] instead.

!!!!!Ampersand
If the 6-bit character set does not provide an encoding for the ampersand symbol  [@&@], it is recommended to use [@AND@] instead.

!!!!!At sign
If the 6-bit character set does not provide an encoding for the at sign [@@@] used by the Modula-2 template utility to tag placeholders, it is recommended to use [@**@] or [@&&@] for [@@@@] instead.

!!!!!Percent sign
If the 6-bit character set does not provide an encoding for the percent sign [@%@] used by the Modula-2 template utility to mark template comments, it is recommended to use [@==@] for [@%%@] instead.

!!!!!Equal sign
If the 6-bit character set does not provide an encoding for the equal sign  [@=@], it is recommended to use [@%EQ%@] for [@=@] and [@%ASSIGN%@] for [@:=@] instead.

!!!!!Case Sensitivity
In support of case sensitivity it is recommended to use the control codes [@SI@] and [@SO@] to switch between uppercase and lowercase.