According to C99, Section 5.2.1, "Character sets"
Two sets of characters and their associated collating sequences shall be defined: the set in which source files are written (the source character set), and the set interpreted in the execution environment (the execution character set). Each set is further divided into a basic character set, whose contents are given by this subclause, and a set of zero or more locale-specific members (which are not members of the basic character set) called extended characters. The combined set is also called the extended character set. The values of the members of the execution character set are implementation-defined.
The character encoding defined by the ASCII standard is the following: code values are assigned to characters consecutively in the order in which the characters are listed as the table below: starting from 32 (assigned to space) and ending up with 126 (assigned to the tilde character ~). Positions 0 through 31 and 127 are reserved for control codes.
| ! | " | # | $ | % | & | ' | ( | ) | * | + | , | - | . | / | ||
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="cb3c55055695ca3f-9c55ed70-4da94f96-90418094-8dd3e875cc802d8605f1ccef"><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 | { | | | } | ~ |
...
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)
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"