> Using the 'latin-1' to mean unknown encoding can easily result
> in Mojibake (unreadable text) entering your application with
> dangerous effects on your other text data.

Agreed. The latin-1 suggestion is purely for people who object to
learning how to handle the encodings in their data more accurately.

I'm not so sure -- it could be used (abused?) for that, but I'm suggesting it be used for mixed ascii-binary data. I don't know that there IS a "right" way to do that -- at least not an efficient or easy to read and write one.">

(original) (raw)

On Fri, Jan 10, 2014 at 6:05 AM, Paul Moore <p.f.moore@gmail.com> wrote:
> Using the 'latin-1' to mean unknown encoding can easily result
\> in Mojibake (unreadable text) entering your application with
\> dangerous effects on your other text data.

Agreed. The latin-1 suggestion is purely for people who object to
learning how to handle the encodings in their data more accurately.

I'm not so sure -- it could be used (abused?) for that, but I'm suggesting it be used for mixed ascii-binary data. I don't know that there IS a "right" way to do that -- at least not an efficient or easy to read and write one.

-Chris


--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice

7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@noaa.gov