RE: texteditors that can process and save in different encodings

From: Doug Ewell <>
Date: Fri, 19 Oct 2012 14:04:05 -0700

Philippe Verdy <verdy underscore p at wanadoo dot fr> wrote:

>>> ASCII,
>> A strict subset of UTF-8, so no need to support this separately.
> Not really. If the file to save does not need any character which is
> found in an 8-bit extended character set (there are many of them),
> saving them as ASCII (i.e. saving this charset information in the
> metadata) still preserves the compatibility of the encoded text with
> all these other extended charsets (notably all ISO 8859-* codepages as
> well as UTF-8).

Which metadata is that? I was sure we were talking about editors for
plain-text files, which don't have any sort of metadata declaring the
character encoding or anything else.

In Stephan's original post, he wrote:

| Some things I have seen that are no good:
| - the editor not telling me about the encoding and line breaks it has

| detected and not letting me choose

Obviously, "detected" would be a non-issue if there were metadata
specifying the encoding.

HTML and XML files contain an inline declaration, and a standard default
encoding, but not all text files are HTML or XML.

Doug Ewell | Thornton, Colorado, USA | @DougEwell ­
Received on Fri Oct 19 2012 - 16:06:02 CDT

This archive was generated by hypermail 2.2.0 : Fri Oct 19 2012 - 16:06:02 CDT