- From: Al Gilman <asgilman@access.digex.net>
- Date: Sun, 25 Oct 1998 23:19:20 -0500 (EST)
- To: hakkinen@dev.prodworks.com (Markku T. Hakkinen)
- Cc: coder@acnet.net, w3c-wai-ig@w3.org
Sorry, I was too eliptical. I am not (to first order) knocking ABBR and ACRONYM as a way to associate full-word text with abbreviations. What I was talking about was user-aware selection of which to say, assuming that you know both. Later, assuming that we can get some agreement on internet dictionary interfaces, I would like to plug into that and retire the requirement for ABBR and ACRONYM markup, which is an awkward implementation of information better handled in a dictionary. I just expect better response working on the browsers to use the dictionary interface than working on the authors to use the ABBR markup. So I am not resting on our laurels with the definition of ABBR and ACRONYM. But yes, for now they should certainly be used. Not to let "the better" get in the way of "the good." Al to follow up on what Markku T. Hakkinen said: > This ideal, is indeed ideal. My synthesizers have their rules > for abbreviations and acronyms ("delaware facto standard" and > "world wide web dot c n n dot com" as some of my favorites), > yet I haven't taken the time to edit their dictionaries and I > accept the results. > I would certainly prefer to have the authors (or their tools) > make use of the mark-up we already have defined (ABBR and > ACRONYM), and allow the markup aware browsers/accessibility > aids (as well as synthesizers ... SABLE or whatever) use this > information to provide the user with meaningful information. > > > > In an ideal world, the preferences governing what acronyms and > > abbreviations get pronounced (e.g. WAI) and which get pronounced > > as the full-word expansion associated with them would be part of > > _the user's personal dictionary extensions_ and not a stylesheet > > or HTML structure generated by the source site author. > > > > This would seem to be more a function of the specific > > abbreviation and listener than of the document context in which > > it is used. > > > > FWIW > > > > Al > > > > to follow up on what Markku T. Hakkinen said: > > > From w3c-wai-ig-request@w3.org Sun Oct 25 13:39:58 1998 > > > Resent-Date: Sun, 25 Oct 1998 13:34:49 -0500 (EST) > > > Resent-Message-Id: <199810251834.NAA24457@www19.w3.org> > > > From: "Markku T. Hakkinen" <hakkinen@dev.prodworks.com> > > > To: "Charles F. Munat" <coder@acnet.net>, <w3c-wai-ig@w3.org> > > > Date: Sun, 25 Oct 1998 13:33:24 -0500 > > > Message-ID: <000101be0045$f32b57c0$5b3f2581@nisc.jvnc.net> > > > X-Priority: 3 (Normal) > > > X-MSMail-Priority: Normal > > > X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 > > > In-Reply-To: <012401be0040$ac0a0f80$3c1172a7@acnet.net> > > > Importance: Normal > > > X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 > > > Subject: RE: Two new sites > > > Resent-From: w3c-wai-ig@w3.org > > > X-Mailing-List: <w3c-wai-ig@w3.org> archive/latest/1698 > > > X-Loop: w3c-wai-ig@w3.org > > > Sender: w3c-wai-ig-request@w3.org > > > Resent-Sender: w3c-wai-ig-request@w3.org > > > Precedence: list > > > > [Charset utf-8 unsupported, skipping...] > > > > >
Received on Sunday, 25 October 1998 23:19:24 UTC