Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

!

"

#

$

%

&

'

(

)

*

+

,

-

.

/

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="433c62d1c7ee5ef6-9c74cb82-44864b87-abe7883f-c4b5ac306abfeaf8eb6343c8"><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 standarstandard _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.

...

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