Lines Matching refs:ASCII

29 Plan 9 from Bell Labs has recently been converted from ASCII
30 to an ASCII-compatible variant of the Unicode Standard,
46 are based on English and ASCII.
142 into and out of Plan 9 between ASCII and Unicode, which cannot be done.
153 needed an ASCII-compatible textual
169 a byte in the ASCII range 0-127 represents
171 Thus UTF is backward compatible with ASCII.
176 ASCII control characters appear in the byte stream
202 Their proposal would allow all 7-bit ASCII characters
251 to find ways to include non-ASCII symbols in our text;
256 and data that contain non-ASCII characters; our browser for the
285 source character set to be ASCII.
286 Since UTF is backward compatible with ASCII,
290 Since 7-bit ASCII characters can represent only
296 character with a value outside of the ASCII range as
447 All programs in Plan 9 now read and write text as UTF, not ASCII.
472 are equivalent to null-terminated ASCII strings for most purposes
602 unless searching for a 7-bit ASCII character, that is, a character
661 the fact that UTF preserves ASCII characters in the byte stream.
767 plain ASCII text grows when converted to runes; UTF-encoded Japanese
890 We wrote a trivial program to look for non-ASCII bytes in
1046 Latin-1 (or even just ASCII) characters and the International
1096 For plain ASCII-like text it naturally stays around 128 images.
1133 We selected an unused key on our ASCII keyboards