From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.redhat.com (mail.redhat.com [199.183.24.239]) by listman.redhat.com (Postfix) with ESMTP id F0ABD2F0AE for ; Sat, 28 Apr 2001 18:28:22 -0400 (EDT) Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id f3SMPIN07879 for blinux-list@listman.redhat.com; Sat, 28 Apr 2001 18:25:18 -0400 Received: from linux.local ([24.67.241.29]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id f3SMPGb07872 for ; Sat, 28 Apr 2001 18:25:17 -0400 Received: (from kajarii@localhost) by linux.local (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id f3SMRbo00948 for blinux-list@redhat.com; Sat, 28 Apr 2001 15:27:37 -0700 Date: Sat, 28 Apr 2001 15:27:37 -0700 From: Dave Csercsics To: blinux-list@redhat.com Subject: Re: writing screenreader friendly software Message-ID: <20010428152737.A944@linux.ok.shawcable.net> References: <20010428192311.A29351@khan.acc.umu.se> <000701c0d01a$23a4bda0$e08caad8@tds.net> <20010429000434.B9458@khan.acc.umu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <20010429000434.B9458@khan.acc.umu.se>; from woormie@acc.umu.se on Sun, Apr 29, 2001 at 12:04:34AM +0200 X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: Yes it should be quite easy to do that. And the characters you mentioned in your first message are quite different from each other in braille so that there should not be a problem at all. And the lynx interface should work quite well as that program works great with a braille display and speech as well so it should be good. On Sun, Apr 29, 2001 at 12:04:34AM +0200, Peter Toneby wrote: > John, > Actually this is not the problem since everything in the table of > contents will be links (otherwise is the book not standards compliant), > so just pointing out headline/pages should be enough (even if it mostly > is quite obvious which is which). > > /Peter > > On Sat, Apr 28, 2001 at 03:33:44PM -0400, John J. Boyer wrote: > > Peter, > > Jaws has ways of showing various types of highlighting, including bold and > > underline, by using dots 7 and 8 in various combinations on an 8-dot Braille > > display. Usually, highlighted text is indicated by turning on both dats 7 > > and 8. I have not tried other options, since this has been sufficient. So if > > I am reading a Web page and come on words that have dots 7 and 8 raised, I > > know this is probably a link. Jawws also puts the word "link" or "graphic" > > on the display. > > John > > > > Computers to Help People, Inc. > > http://www.chpi.org > > 825 East Johnson; Madison, WI 53703 > > > > > > ----- Original Message ----- > > From: "Peter Toneby" > > To: > > Sent: Saturday, April 28, 2001 13:23 > > Subject: writing screenreader friendly software > > > > > > > Hello > > > > > > I'm currently working on a (to be free) player for Daisy-books, now > > > I've got some of the basic dataparsing working and want to move onto > > > the UI but I'm not sure how to make it so it fits screenreaders. > > > > > > My primary concern are braille displays, because according to a friend > > > of mine they can't show bold, underline or any other kind of > > > charactermodifications. > > > > > > My questions about this are: > > > 1. How should I design the UI? (see below for my thoughts) > > > 2. What library should I use to write it? are some better than others? > > > 3. Are there any special considerations I should take to make things > > > work with both braille displays and speech synthesizers? > > > > > > Daisy is an open standard based on standard fileformats such as xhtml > > > (http://www.w3.org/TR/xhtml1/), smil (http://www.w3.org/TR/REC-smil) > > > and mp3. > > > > > > The layout of the book is pretty much like a normal printed book, there > > > is a table of contents (ToC), from this ToC links lead to .smil-files > > > which in turn points to the exect (1/100th of s exact) point in the > > > audiostream to play, these .smil-files also points where in the text of > > > the book the narrator reads. > > > > > > And now my thoughts on the UI-issue (only for the ToC). > > > I think that a lynx-like UI is the best to use for the ToC, but because > > > braille displays can not show bold text I need to show on which line > > > there are 1 link and where there are >1 links. The ToC is built from > > > -tags and -tags (containing links). The header-tags are > > > required to be sections (they should follow the printed book as closley > > > as possible) and the span-tags contains links to pages. > > > > > > So to diffrentiate between these I'm thinking about reserving the 2 > > > leftmost columns to show if the line is a heading or contains pages. > > > I was thinking about using '*' for headings and '>' for pages, but I > > > don't know how much these differs on different displays (I'm sighted and > > > do not have easy access to any braille-displays). So it would look > > > something like this: > > > * 15. Treatment of Early Trauma and Insight > > > > 217 218 219 220 > > > > > > So now, flame on and give me some nice input on this and you might have > > > a free, open source Daisy-player "soon" (this is a for fun, sparetime > > > project, so sometimes it goes unattended for a few weeks). > > > > > > /Peter Toneby > > > -- > > > Alpha Test Version: Too buggy to be released to the paying public. > > > Beta Test Version: Still too buggy to be released. > > > Release Version: Alternate pronunciation of "Beta Test Version". > > > > > > > > > > > > _______________________________________________ > > > Blinux-list mailing list > > > Blinux-list@redhat.com > > > https://listman.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > _______________________________________________ > > Blinux-list mailing list > > Blinux-list@redhat.com > > https://listman.redhat.com/mailman/listinfo/blinux-list > > -- > Alpha Test Version: Too buggy to be released to the paying public. > Beta Test Version: Still too buggy to be released. > Release Version: Alternate pronunciation of "Beta Test Version". > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list