Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Unknown Newsgroups: comp.lang.forth Subject: Do 4thers also replace 7bitQuoteChar by 24bits? Date: Sun, 26 Jun 2016 07:17:14 -0000 (UTC) Organization: A noiseless patient Spider Lines: 27 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 26 Jun 2016 07:17:14 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="f461b4d92b27f73caf7fa295738a0b8c"; logging-data="13039"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18aYpn6sqA5IuudDWsVRo3M7aSBycRf26Q=" User-Agent: Pan/0.133 (House of Butterflies) Cancel-Lock: sha1:kCWigxA85kJ4FWxgJhQFCLw0Z6E= Xref: csiph.com comp.lang.forth:48530 Yes, it may be nice to be able to write in Chinese and Arabic instead of just ASCII. But did we cancel "walking" when we got the jet-plane. What was insufficient about the single & double quote chars, that needed them to be replaced by 3 bytes? Investigating what was sent to show the 3 chars: "e" # grep example /root/ORS.htm | hexdump -C | head -3 00000000 49 6e 20 79 6f 75 72 20 65 78 61 6d 70 6c 65 20 |In your example | 00000010 e2 80 9e 65 22 20 69 73 20 35 20 28 3d 20 e2 80 |â..e" is 5 (= â.| 00000020 9e 31 30 31 e2 80 9c 20 69 6e 20 62 69 6e 61 72 |.101â.. in binar| shows e2 80 9e = " 65 = e 22 = " So it's not even consistent. Or double-quote maps to multiple possibilities.