Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: markspace <-@.>
Newsgroups: comp.lang.java.programmer
Subject: Re: A proposal to handle file encodings
Date: Thu, 22 Nov 2012 17:20:11 -0800
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <k8mj0d$2m2$1@dont-email.me>
References: <lb6ta81u9imfdtlpuesoc8slncju0ehsnm@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 23 Nov 2012 01:20:13 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="61282af8d6595e8d991edb5ac03d6e00"; logging-data="2754"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18v780toGLmgvhrp7FqD4Wp89HwHznUUdI="
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
In-Reply-To: <lb6ta81u9imfdtlpuesoc8slncju0ehsnm@4ax.com>
Cancel-Lock: sha1:w5AkxV9e21hsNNRzCLiYk7aXxnQ=
Xref: csiph.com comp.lang.java.programmer:19858

On 11/22/2012 1:36 PM, Roedy Green wrote:
> The problem with encodings is they are not attached in any way or
> embedded in any way in a file. You are just supposed to know how a
> file is encoded.
>
> Here is my idea to solve the problem.
>
> We invent a new encoding.


http://xkcd.com/927/