"Steve Welsh" <nobody@linux.bogus> wrote in message
news:j-GdnZOEzqG3qs3enZ2dnUVZ8qSdnZ2d@eclipse.net.uk...
> BillW50 wrote:
> > "Moe Trin" <ibuprofin@painkiller.example.tld> wrote in message
news:slrndktuqt.jcu.ibuprofin@compton.phx.az.us...
> > Hi Moe... It must have been along time since you have either Updated
> > a Windows machine or actually had used one. As this used to be MS'
> > SOP, but now they lock them down tight
>
> yes, they do - they lock them down so tight that seriously experienced
> WinBlows Sysadmins are chasing their tails trying to find out Why TF
> their systems don't work any more!!

Not the competent ones (i.e. the one that either test before deployment or,
in smaller shops, simply read about the tests that other people have
done...)

> > In June 2004, the ISO/IEC working group responsible for
> > maintaining eight-bit coded character sets disbanded and ceased
> > all maintenance of ISO 8859, including ISO 8859-1, in order to
> > concentrate on the Universal Character Set and Unicode. In
> > computing applications, encodings that provide full UCS support
> > (such as UTF-8 and UTF-16) are finding increasing favor over
> > encodings based on ISO 8859-1.
>
> You obviously totally fail to realise that 7-bit ASCII and Extended
> ASCII (aka ISO 8859-1) are, and will continue to be recognised subsets
> of UFT-8 and UTF-16. If you don't realise this, then you obviously have
> no clue as to what Unicode is all about, or how it works.

Hmm. Neither side is distinguishing themselves with this one ;o)

Shame on you! A Brit who doesn't realise the importance of Unicode *clients*
(unless someone's trying to be a little disingenuous..)

A server platform often just transports stuff around that's been encoded by
one client, and will be decoded by another client. Add a DMBS storing text,
and you might be rather tightly-coupled to the client, but that's getting
away from the pure transport side. Which, if we're to make any sense of your
arguments, we seem to be talking about.

The client, OTOH, either requires a different version for each and every
language (the traditional technique, using fast footwork with code pages),
or uses Unicode where required and takes the memory and/or bandwidth hit.

With the argument over the esset now sorted, I certainly haven't seen any
proposals to add new letters to the alphabets of any European languages. So
I can't see any need to maintain the associated ISO standard. Hell, ASCII
hasn't changed for /decades/...

> > I use HTML email when I need to use tables, bullets, newsletters,
> > pictures, etc. It's all part of the MIME standard. Nothing wrong
> > with that. Plain text is about 50 years old now.
>
> But you seriously misunderstand that presentation and content _should_
> and _must_ be separated - that is precisely why we are in the M$ induced
> horror of ActiveX, etc, etc.......

Tut, tut. Quite apart from the fact that, by definition, email content is
100% pure content (lookee, they even use the "c" word), you are either
mixing up basic programming concepts in your head, or have a major problem
is understanding the concepts of data and content.

And, quite possibly, the purpose of SGML.

> > It is time for some to quit hanging on to the old past. It is
> > time some people actually start using all of that computing power
>
> It has fuck all to do with computing power!! My Linux server is a P-II
> 350 - it does its job - it sits there and *serves*

Fine. Dandy. And if you're running a bunch of client software on it, then
you also need to take a good, hard look at Industry Best Practise for the
last couple of decades ;o)

--

Hairy One Kenobi

Disclaimer: the opinions expressed in this opinion do not necessarily
reflect the opinions of the highly-opinionated person expressing the opinion
in the first place. So there!