Re: Rendering A Four Column Table In Text Format: What's Best For You

 I would like a copy of the html version with the full table.  Thanks.  This 
will be very helpful.  

Don Marang

There is just so much stuff in the world that, to me, is devoid of any real 
substance, value, and content that I just try to make sure that I am working on 
things that matter. 
Dean Kamen 



From: Homme, James 
Sent: Friday, February 11, 2011 2:32 PM
To: programmingblind@xxxxxxxxxxxxx 
Subject: Rendering A Four Column Table In Text Format: What's Best For You


Hi,

I'm preparing the documentation for my JAWS Eclipse scripts. I'm including the 
entire Eclipse 3.6 default keystrokes set that I earlier put into an Excel 
file. The table is in four columns. If I render it in plain text, what would be 
best for you to hear it. The columns are Keys, Command, Category, and Context. 
One thing that occurred to me is that I can sort by either category or context, 
then prepare a text version that repeats key strokes and commands, and also 
gives the category and context columns merged. I'm also going to include an 
HTML version of the documentation, but I was thinking of just keeping that set 
in a table. What is best for your reading pleasure? I'm also thinking of 
including a plain text file of the entire Eclipse Workbench Guide. Would that 
be good for you to have?

 

Thanks.

 

Jim

Jim Homme,

Usability Services,

Phone: 412-544-1810. Skype: jim.homme

Internal recipients,  Read my accessibility blog. Discuss accessibility here. 
Accessibility Wiki: Breaking news and accessibility advice

 



--------------------------------------------------------------------------------
This e-mail and any attachments to it are confidential and are intended solely 
for use of the individual or entity to whom they are addressed. If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it. If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this e-mail without the author's prior permission. 
The views expressed in this e-mail message do not necessarily represent the 
views of Highmark Inc., its subsidiaries, or affiliates.

Other related posts: