Content deleted Content added
Modernize it with Unicode material. The perspective was about a decade old. |
mNo edit summary |
||
Line 1:
Recent [[Microsoft]] products and APIs use [[Unicode]] internally, but many applications and APIs continue to use the default [[character encodings| encoding]] of the computer's ''locale'' when reading and writing text data to files, files or standard output.
Initially, computer systems and sytem programming languages did not make a distinction between characters and bytes. This has lead to many confusions subsequently. Microsoft software and systems from the 1980s will tend to use the IBM-derived OEM '''code pages'''. Software and systems from the 1990s (pre-Unicode [[Microsoft Windows]] applications) will tend to use extended versions of the national or international standard sets, so-called ANSI. Since the the late 1990s, software and systems are increasingly adopting more direct encodings of [[Unicode]], in particular UTF-8 and UTF-16; this trend has been improved by by the widespread adoption of [[XML]] which provides a more adequate mechanism for labelling the encoding used.
| |||