More coal on the fire
Darrell Shandrow
plug-discuss@lists.plug.phoenix.az.us
Mon, 16 Sep 2002 19:55:29 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0005_01C25DBB.020DEDD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi Fred,
Unfortunately, I am not quite convinced with respect to Open Office. =
Some of my colleagues have sent me Open Office documents which have been =
converted to Microsoft Word format, and they have lacked some structural =
elements which they would have contained if they had been created using =
Microsoft Word. I am a blind person, and document accessibility to =
screen readers is paramount. At this time, when it comes to =
accessibility, MS has it all over Sun. Currently, even the Windows =
version of Open Office isn't accessible to screen readers.
Thanks.
----- Original Message -----=20
From: Fred Wright=20
To: plug-discuss@lists.plug.phoenix.az.us=20
Sent: Monday, September 16, 2002 6:30 PM
Subject: More coal on the fire
The following is From the Lockergnome Tech Specialist Newsletter. =
This is another action on MS's part that might give folks impetus to =
move at least to OpenOffice - -
Word Security Flaw Poses Threat - MS Responds=20
http://www.microsoft.com/technet/security/topics/secword.asp=20
A new Microsoft Word flaw has surfaced that could result in documents =
being exposed to prying eyeballs. I think Microsoft did a good job with =
explaining the basics of how the bug works and how best to protect =
against its effects. It's clear from the text, however, that Office 97 =
users, which comprise a significant 30% of the Office user base, will be =
left out in the cold when it comes to a fix. They note that Office 97 =
was created in another era (as if it's been decades since the release) =
and security architecture has been improved greatly since then. Call me =
silly, but offering up a helpful nudge into Office XP as a "fix" for a =
bug that works the same way in all affected versions seems rather =
patronizing to the 30% of their patronage.=20
Fred Wright
fawright@earthlink.net=20
------=_NextPart_000_0005_01C25DBB.020DEDD0
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.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Fred,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Unfortunately, I am not quite convinced =
with=20
respect to Open Office. Some of my colleagues have sent =
me Open=20
Office documents which have been converted to Microsoft Word format, and =
they=20
have lacked some structural elements which they would have =
contained if=20
they had been created using Microsoft Word. I am a blind person, =
and=20
document accessibility to screen readers is paramount. At this =
time, when=20
it comes to accessibility, MS has it all over Sun. Currently, even =
the=20
Windows version of Open Office isn't accessible to screen =
readers.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Thanks.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dfawright@earthlink.net =
href=3D"mailto:fawright@earthlink.net">Fred=20
Wright</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3Dplug-discuss@lists.plug.phoenix.az.us=20
=
href=3D"mailto:plug-discuss@lists.plug.phoenix.az.us">plug-discuss@lists.=
plug.phoenix.az.us</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, September 16, =
2002 6:30=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> More coal on the =
fire</DIV>
<DIV><BR></DIV><FONT face=3D"Courier New, Courier">The following is =
>From the=20
Lockergnome Tech Specialist Newsletter. This is another action =
on MS's=20
part that might give folks impetus to move at least to OpenOffice -=20
-<BR><BR></FONT><FONT face=3D"Courier New, Courier" size=3D2>Word =
Security Flaw=20
Poses Threat - MS Responds <BR><BR><A=20
=
href=3D"http://www.microsoft.com/technet/security/topics/secword.asp">htt=
p://www.microsoft.com/technet/security/topics/secword.asp</A>=20
<BR><BR>A new Microsoft Word flaw has surfaced that could result in =
documents=20
being exposed to prying eyeballs. I think Microsoft did a good job =
with=20
explaining the basics of how the bug works and how best to protect =
against its=20
effects. It's clear from the text, however, that Office 97 users, =
which=20
comprise a significant 30% of the Office user base, will be left out =
in the=20
cold when it comes to a fix. They note that Office 97 was created in =
another=20
era (as if it's been decades since the release) and security =
architecture has=20
been improved greatly since then. Call me silly, but offering up a =
helpful=20
nudge into Office XP as a "fix" for a bug that works the same way in =
all=20
affected versions seems rather patronizing to the 30% of their =
patronage.=20
<BR><BR><BR></FONT><X-SIGSEP>
<P></X-SIGSEP>Fred Wright<BR>fawright@earthlink.net=20
</P></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0005_01C25DBB.020DEDD0--