...
| ! | " | # | $ | % | & | ' | ( | ) | * | + | , | - | . | / | ||
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="c59663b0ff51917f-3a56da85-4a6548d3-aea58057-e1ee4104b9af7dd9a4031c98"><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 | { | | | } | ~ |
| Wiki Markup |
|---|
There are several national variants of ASCII. Therefore, the original ASCII is often referred as *US-ASCII*. The international standard _ISO 646_ defines a character set similar to US-ASCII, but with code positions corresponding to US-ASCII characters {{@\[\]\{\|\}}} as "national use positions". It also gives some liberties with characters {{#$^`~}}. In _ISO 646_, several "national variants of ASCII" have been defined, assigning different letters and symbols to the "national use" positions. Thus, the characters that appear in those positions - including those in *US-ASCII* are somewhat "unsafe" in international data transfer. |
...
In Addition to the letters of the English alphabet ("A" to "Z" and "a" to "z"), the digits ("0" to "9") and the space , only the following characters can be regarded as really "safe" in data transmission:
| No Format |
|---|
! " % & ' ( ) * + , - . / : ; < = > ?
|
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 could result in data being lost or data mis-interpretation misinterpreted during data transmission. This can be a serious security issue. There are already solutions which address this issue pretty well. (See "Comments" section)
Reference
http://www.cl.cam.ac.uk/~mgk25/unicode.html
ISO/IEC 646, Information technology ? ISO 7-bit coded character set for information
interchange.
C99, Section 5.2.1, "Character sets"