Text 11696, 209 rader
Skriven 2006-06-19 15:09:26 av Rich (1:379/45)
Kommentar till text 11671 av Geo (1:379/45)
Ärende: Re: PCI hardware ID
===========================
From: "Rich" <@>
This is a multi-part message in MIME format.
------=_NextPart_000_0104_01C693B2.5AACE5A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Two different issues. IE has to apply heuristics to file types =
because the servers that return this content often return bogus, both =
incorrect or invalid, types. It's not easy to fix. IE had to do this =
because netscape didn't enforce types and to be compatible IE couldn't =
either. Because the types aren't enforced lots of servers still do this =
wrong. Because they do types can't be enforced.
Text and Unicode is first a false distinction. It's all text. In =
the case of Notepad, you mean UTF-16 text vs. UTF-8 text vs. ANSI text = as
this is the distinction that Notepad makes on load. Even that misses = the
complexity as what people call ANSI is actually any of 14 distinct = and
incompatible ANSI encodings and is often one of many OEM encodings = which may
be distinct from any of the ANSI ones. It is complicated = because for many of
the ANSI encodings including the one used in the = U.S. and Western Europe,
anything could be valid. Because of this it is = not always possible to make a
distinction between UTF-16 and ANSI as a = file could validly be either. UTF-8
is restrictive so it is easy to = tell if something is valid UTF-8. That could
still be a problem as = valid UTF-8 could be valid ANSI too. Instead some
heuristics are = applied. For example if you see 0D 00 0A 00 then the file is
probably = UTF-16 while if you see 0D 0A it may be ANSI though U+0A0D might be
a = valid Unicode character. I didn't look.
Rich
"Geo" <georger@nls.net> wrote in message news:449444fd$2@w3.nls.net...
That's not what I meant when I said computers today guess. I meant how
computers today guess at the answer when the problem doesn't have a =
unique
solution. Example would be how IE guesses file types or how notepad =
guesses
between text and unicode.
Geo.
"Antti Kurenniemi" <NOantti@SPAManttikPLEASE.com> wrote in message
news:449392b8$1@w3.nls.net...
> It was equally bad having people guess things. "I'll switch this dip =
here
> and that there, and then those jumpers that I just dropped and have =
no
clue
> about where they should go... I'll just make a neat row of them =
here,
> that'll do it". I remember a lot of hardware having huge manuals for =
just
> configuring the stupid dip switches and whatnots, and that it was =
possible
> to fry things by misconfiguring them. No thanks to that - nowadays, =
at
least
> you don't have to get your hands dirty to break your computer <g>
>
>
> Antti Kurenniemi
>
> "Geo" <georger@nls.net> wrote in message =
news:44938e6a$2@w3.nls.net...
> I kind of prefer the days when computers didn't "guess" at things. =
We used
> to have a saying "computers don't make mistakes" but all that =
changed
now..
>
> Geo.
> "Rich" <@> wrote in message news:4493558b$1@w3.nls.net...
> You don't expect a mainframe to automatically detect any off =
the
shelf
> adapter that is plugged in. The PC could go back to the dark ages =
too as
> this is how things used to be when the PC first came to be.
>
> Rich
>
>
>
------=_NextPart_000_0104_01C693B2.5AACE5A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2> Two different =
issues. IE has to=20
apply heuristics to file types because the servers that return this =
content=20
often return bogus, both incorrect or invalid, types. It's not = easy
to=20
fix. IE had to do this because netscape didn't enforce types and = to
be=20
compatible IE couldn't either. Because the types aren't enforced = lots
of=20
servers still do this wrong. Because they do types can't be=20
enforced.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Text and Unicode is first =
a false=20
distinction. It's all text. In the case of Notepad, you mean =
UTF-16=20
text vs. UTF-8 text vs. ANSI text as this is the distinction that =
Notepad=20
makes on load. Even that misses the complexity as what people call = ANSI
is=20
actually any of 14 distinct and incompatible ANSI encodings and is often = one
of=20
many OEM encodings which may be distinct from any of the ANSI = ones. It
is=20
complicated because for many of the ANSI encodings including the one = used in
the=20
U.S. and Western Europe, anything could be valid. Because of this = it
is=20
not always possible to make a distinction between UTF-16 and ANSI as a =
file=20
could validly be either. UTF-8 is restrictive so it is easy to = tell
if=20
something is valid UTF-8. That could still be a problem as valid =
UTF-8=20
could be valid ANSI too. Instead some heuristics are = applied.
For=20
example if you see 0D 00 0A 00 then the file is probably UTF-16 while if = you
see=20
0D 0A it may be ANSI though U+0A0D might be a valid Unicode = character.
I=20
didn't look.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Geo" <<A =
href=3D"mailto:georger@nls.net">georger@nls.net</A>> wrote=20
in message <A=20
=
href=3D"news:449444fd$2@w3.nls.net">news:449444fd$2@w3.nls.net</A>...</DI=
V>That's=20
not what I meant when I said computers today guess. I meant =
how<BR>computers=20
today guess at the answer when the problem doesn't have a =
unique<BR>solution.=20
Example would be how IE guesses file types or how notepad =
guesses<BR>between=20
text and unicode.<BR><BR>Geo.<BR><BR>"Antti Kurenniemi" <<A=20
=
href=3D"mailto:NOantti@SPAManttikPLEASE.com">NOantti@SPAManttikPLEASE.com=
</A>>=20
wrote in message<BR><A=20
=
href=3D"news:449392b8$1@w3.nls.net">news:449392b8$1@w3.nls.net</A>...<BR>=
> It=20
was equally bad having people guess things. "I'll switch this dip =
here<BR>>=20
and that there, and then those jumpers that I just dropped and have=20
no<BR>clue<BR>> about where they should go... I'll just make a neat =
row of=20
them here,<BR>> that'll do it". I remember a lot of hardware having =
huge=20
manuals for just<BR>> configuring the stupid dip switches and =
whatnots, and=20
that it was possible<BR>> to fry things by misconfiguring them. No =
thanks=20
to that - nowadays, at<BR>least<BR>> you don't have to get your =
hands dirty=20
to break your computer <g><BR>><BR>><BR>> Antti=20
Kurenniemi<BR>><BR>> "Geo" <<A=20
href=3D"mailto:georger@nls.net">georger@nls.net</A>> wrote in =
message <A=20
=
href=3D"news:44938e6a$2@w3.nls.net">news:44938e6a$2@w3.nls.net</A>...<BR>=
> I=20
kind of prefer the days when computers didn't "guess" at things. We=20
used<BR>> to have a saying "computers don't make mistakes" but all =
that=20
changed<BR>now..<BR>><BR>> Geo.<BR>> "Rich" =
<@>=20
wrote in message <A=20
=
href=3D"news:4493558b$1@w3.nls.net">news:4493558b$1@w3.nls.net</A>...<BR>=
> =20
You don't expect a mainframe to automatically detect any off=20
the<BR>shelf<BR>> adapter that is plugged in. The PC could go =
back to=20
the dark ages too as<BR>> this is how things used to be when the PC =
first=20
came to be.<BR>><BR>> =20
Rich<BR>><BR>><BR>><BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0104_01C693B2.5AACE5A0--
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
|