Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: "Alan J. Flavell" <flavell@xxxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 10:43:06 +0000
On Fri, 30 Dec 2005, Eric Bohlman wrote:
> Samwyse <samwyse@xxxxxxxxx> wrote in news:Pa1tf.38841$dO2.20814
> @newssvr29.news.prodigy.net:
>
> > Alan, I am in awe of your skills in pedantry. In the future, I
> > promise that I will *never* use the term "ASCII" to mean anything
> > other than whatever it was you just said.
>
> It's not pedantry. The subject of character encodings is one that
> simply can't be meaningfully discussed without using extremely
> precise language;
[...]
Thanks. It might be worth adding, since the original poster is in
..fr, that their data *might* be using the French MS-DOS code page
(this doesn't seem to be listed amongst the Unicode cross-mapping
tables - I'm sure it's listed in my old DOS manual in the office),
although one of my French colleagues, back in MS-DOS days, told me
that he preferred to use the French-Canadian code page instead - that
would be:
http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/PC/CP863.TXT
I already mentioned the possibility of CP850, the Latin1 Multinational
code page. The original poster used the term "OEM", but a search for
"OEM codepage" will easily reveal that there are *many* different
MS-DOS "OEM" codepages: http://www.google.co.uk/search?q=oem+codepage
See also http://www.unicode.org/Public/MAPPINGS/VENDORS/IBM/readme.txt
for some useful notes.
> "you know what I mean" simply won't cut it here because in fact
> different people will come up with *radically* different ideas of
> what you mean. "High ASCII" or "wide ASCII" mean different things
> to different people, because there is simply no common definition
> for them (which in turn comes from the fact that they're inherently
> contradictory).
Quite.
Things aren't helped by the fact that MS mischievously refer to their
proprietary Windows character encoding(s) as "ANSI". On finding
contradictory assertions about this, I researched further, and am
convinced that the (US-)American National Standards Inst. has never
published such a specification. After they had initially discussed a
US specification for an ASCII-based 8-bit character coding, they
wisely decided not to have one, and adopted the international
iso-8859-1 specification instead.
Not that it's directly relevant to the present question, but I
concluded that a conscientious author would avoid referring to
Windows-1252 (or to the Windows-125x family of codings) as "ANSI"
character coding(s).
best regards
.
- References:
- [FR/EN] how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: Alextophi
- Re: [FR/EN] how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: Paul Lalli
- Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: Alextophi
- Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: Samwyse
- Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: Alan J. Flavell
- Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: Samwyse
- Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- From: Eric Bohlman
- [FR/EN] how to convert the characters ASCII(0-255) to ASCII(0-127)
- Prev by Date: Re: Ordering string of commands in a file
- Next by Date: FAQ 2.14 What mailing lists are there for Perl?
- Previous by thread: Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- Next by thread: Re: how to convert the characters ASCII(0-255) to ASCII(0-127)
- Index(es):
Relevant Pages
|
