Hi Sarah,
Sorry to be so long in replying. The system is far from ideal, so here's
what I would do.
Put the tip in the version of the program that can do what you are
describing. For example Rank Spelling I believe was introduced in v8 of K1k,
so put it under Kurzweil 8.0. Something like Ignore Suspicious regions
didn't get introduced until 10.0, so put that in the 10.0 category.
Feel free to elaborate freely about what versions do what in the actual tip.
When a user filters the list its by product anyways, its not by version
number.
I think BookShare would like to someday have a system like mine developed,
so I'm not going to throw a bunch of hours behind this one *grin*. Ideally
of course the versions would be checkboxes, but to do that verses the combo
box...well I'd rather work on getting another book into the collection.
Best,
Jake
----- Original Message -----
From: "Sarah Van Oosterwijck" <curiousentity@xxxxxxxxxxxxx>
To: <bksvol-discuss@xxxxxxxxxxxxx>
Sent: Sunday, December 04, 2005 3:59 PM
Subject: [bksvol-discuss] Re: Tips page update
Thank you for the changes, and more importantly the information on what you did, so when submitting tips we can get them to look as intended. :-)
I think I caused some of the mess when I submitted my scanning with Kurzweil tip. The title clearly says what the tip is for, but I didn't know what to do about the tip actually being relevant to all versions of Kurzweil. Sorry about that. How should I deal with that in the future if I have a tip that fits in more than one category, but not in all?
Sarah Van Oosterwijck
Assistive Technology Trainer
http://home.earthlink.net/~netentity
----- Original Message ----- From: "Jake Brownell" <jabrown@xxxxxxxxx>
To: <bksvol-discuss@xxxxxxxxxxxxx>
Sent: Saturday, December 03, 2005 5:49 PM
Subject: [bksvol-discuss] Tips page update
Hi all,
I had a little free time today and so I made a minor upgrade to the tips area.
A. I was using pre tags and displaying the submitted tip just as the submitter entered it. Therefore a paragraph was considered a single line visually, not to a screen reader. So sighted users would have to scroll horizontally, something that is very unappealing. I now interpret single line breaks as br tags and two line breaks as p tags. So double line breaks makes a new "paragraph" whereas a single line break just forces the text to the next line.
B. The application/version was being run together. I had a space separating the two variables that hold that data in the code and it should have been displayed correctly, but for some reason it wasn't. So I added a dash in between the two to force a separation. Screen reader users should no longer hear Kurzweil100010 *grin*
There are a couple of tips that are in the wrong application category on the website. I'll fix that sometime. It will require me to manually edit the database as I didn't code a web based way to do it.
Cheers! Jake
--------------------------------------------------------------------------------
No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.11/191 - Release Date: 12/2/2005
To unsubscribe from this list send a blank Email to
bksvol-discuss-request@xxxxxxxxxxxxx
put the word 'unsubscribe' by itself in the subject line. To get a list of available commands, put the word 'help' by itself in the subject line.
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.11/191 - Release Date: 12/2/2005
To unsubscribe from this list send a blank Email to bksvol-discuss-request@xxxxxxxxxxxxx put the word 'unsubscribe' by itself in the subject line. To get a list of available commands, put the word 'help' by itself in the subject line.
