Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: [News] [Rival] Microsoft's Internet Crimes Remain Unresolved

  • Subject: Re: [News] [Rival] Microsoft's Internet Crimes Remain Unresolved
  • From: Homer <usenet@xxxxxxxxxx>
  • Date: Fri, 10 Apr 2009 12:21:37 +0100
  • Bytes: 3649
  • Cancel-lock: sha1:A12RG4dFLMc+1H2PYgm94iwU8Os=
  • In-reply-to: <36456447.cf7GyZ856L@xxxxxxxxxxxxxxx>
  • Newsgroups: comp.os.linux.advocacy
  • Openpgp: id=BF436EC9; url=http://slated.org/files/GPG-KEY-SLATED.asc
  • Organization: Slated.org
  • References: <36456447.cf7GyZ856L@xxxxxxxxxxxxxxx>
  • User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv: Gecko/20090105 Fedora/ Thunderbird/ Mnenhy/
  • Xref: ellandroad.demon.co.uk comp.os.linux.advocacy:756233
Verily I say unto thee, that Roy Schestowitz spake thusly:

> Microsoft hijacks now web standards and the W3C: -m$ fonts?
> http://www.noooxml.org/forum/t-89497/microsoft-hijacks-now-web-standards-and-the-w3c:m-fonts

I took the time to research this issue completely, and it seems this is
not uniquely a Microsoft problem.

The fact that Microsoft have so many non-standard methods for HTML (and
everything else) is undoubtedly a problem (for anyone not using their
software), but in this specific case they seem to be doing nothing more
than attempting compliance with one particular W3C standard [*], albeit
in a manner which might cause even more problems. Generally speaking,
there's no easy way for Microsoft to implement standards compliance
without completely breaking backwards compatibility, unless they further
add to the mess by retaining multiple standards support. It's this
complexity that the commentators seem to be complaining about.

However, as I suggested, it seems this is not uniquely a Microsoft
issue. The /real/ problem is the existence of /any/ vendor specific
extensions at /all/, since both Mozilla and Opera are guilty of exactly
the same thing.

The solution should be for /all/ browser vendors to stop using
proprietary standard extensions, and come to some consensus about which
methods need to be implemented - and exactly how to implement them, in a
manner that does not tie those standards to any specific browser, so the
W3C can once and for all remove all vendor-specific extensions from
their standards.

Of course, /getting/ that cooperation from Microsoft is another thing,
since as far as they're concerned this disparity works in their favour.

[*] http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords


| "The shepherd drives the wolf from the sheep's throat, for which
| the sheep thanks the shepherd as his liberator, while the wolf
| denounces him for the same act, as the destroyer of liberty.
| Plainly the sheep and the wolf are not agreed upon a definition of
| the word liberty; and precisely the same difference prevails today
| among human creatures." ~ Abraham Lincoln

Fedora release 8 (Werewolf) on sky, running kernel
 12:21:38 up 155 days, 19:04,  4 users,  load average: 0.36, 0.14, 0.09

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index