W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 1998

RE: mdash

From: David Poehlman <poehlman@clark.net>
Date: Fri, 30 Jan 1998 10:58:54 -0500 (EST)
To: "Pawson, David" <DPawson@rnib.org.uk>
cc: w3c-wai-ig@w3.org
Message-ID: <Pine.GSO.3.96.980130105747.8878A-100000@shell.clark.net>

so, That's what &#151; is.  my screenreader with lynx just pronounces the
code.  I haven't been able to find them in netscape yet, but am looking
for them.
 On Fri, 30 Jan 1998, Pawson, David wrote:

> 
> 	Chris wrote:
> > On another subject has anyone had any bright ideas about
> > what to do with mdashes -- one site I've been helping with
> > has been using two regular dashes, like this: -- and I've
> > been using &#151; on another site. However I've now realized
> > that while &#151; works OK it's not in the ISO character
> > set. And what is concerning me more is how speech
> > synthesizers would deal with this, anyone got any ideas?
> > 
> 	In-house experience seems to respond.
> 
> 	1. User preferences 
> 			Punctuation can be turned on or off
> 			(Assumes you are using  --)
> 	2.	Screen reader capability.
> 		Can the punctuation be 'turned off' may not be on some
> 		lower end products.
> 	3.	Likewise if 'm-dash'  (#151) or any other 'graphical'
> character
> 		is used, with high end products they can be 'trained' to
> 		pronounce them as 'm dash' or ignored.
> 
> 		Perhaps the cleaner solution is to use the proper entity
> set
> 		then permit those who can and want to, to train the
> system
> 		to 'pronounce' entities as intended.
> 
> 	The quick and dirty is to avoid using them - there are
> alternatives.
> 
> 	regards, DaveP
> 

Hands-On-Technolog(eye)s
touching the internet
voice: 1-(301) 949-7599
poehlman@clark.net
ftp://ftp.clark.net/pub/poehlman
http://www.clark.net/pub/poehlman
Received on Friday, 30 January 1998 10:59:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:38 GMT