Path: csiph.com!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Jussi Piitulainen Newsgroups: comp.lang.python Subject: Re: Gmail eats Python Date: Sun, 26 Jul 2015 08:26:58 +0300 Organization: A noiseless patient Spider Lines: 20 Message-ID: References: <201507251634.t6PGYUvo028820@fido.openend.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="305c68510616a2e7ac08bcd2ff1598bd"; logging-data="2102"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19grRQPJBsTMvajNqkrlziH6xMrUTuZdG4=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:/VaGTokU2+4nXzOtCcdv4421Op4= sha1:reaR5usaAzV8w6JxYyLXqQW7lsw= Xref: csiph.com comp.lang.python:94592 Laura Creighton writes: > In a message of Sat, 25 Jul 2015 20:52:38 +0300, Jussi Piitulainen writes: >>Jussi Piitulainen writes: >>> Has the world adopted UTF-8 as the default charset now or what? >>> (I'll be only glad to hear that it has, if it has, but a reference >>> to some sort of internet standard would be nice.) > > I don't think so. Americans and other English speakers still love > ASCII. but the ISO charsets are rapidly going the way of the > buggywhip. :) > http://www.loc.gov/standards/iso639-2/php/English_list.php I thought the ISO-8859 sets are going away in favour of UTF-8, and I welcome that development. ASCII is still fine as a subset of UTF-8. What's not fine is the use of encoded characters outside ASCII without a corresponding declaration (possibly a default) of the encoding (or my mail reader failing to understand that the declaration is there). But how is that link to a set of language codes relevant?