...
| ! | " | # | $ | % | & | ' | ( | ) | * | + | , | - | . | / | ||
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 | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f7703522a9c62878-a5936fa4-4de740a8-b733bcea-d78c6623a5770e56743ca5ed"><ac:plain-text-body><![CDATA[ | P | Q | R | S | T | U | V | W | X | Y | Z | [ | \ | ] | ^ | _ | ]]></ac:plain-text-body></ac:structured-macro> |
' | 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 | { | | | } | ~ |
...
When naming files, variables, data files etc., it is often best to use only the characters listed above.
Comments
The way to resolve this issue is to use the corresponding codes strictly for US-ASCII meanings; national characters are handled otherwise, giving them their own, unique and universal code positions in character codes larger than ASCII. But certain old softwares and devices may still reflect various "national variants of ASCII".
Risk Assessment
This issue will result data lost or data mis-interpretation during data transmission. This can be a serious security issue. There are already solutions which address this issue pretty well. (See "Comments" section)
