AXSLIB-L Archives

Liberation Throough IT Accessibility (an EASI member list)

AXSLIB-L@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Audrey Gorman <[log in to unmask]>
Reply To:
Library Access -- http://www.rit.edu/~easi
Date:
Fri, 7 Sep 2001 07:55:35 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Anna,

Thanks, that was very helpful indeed.

I'm going away for two weeks and won't do much email (just checks for urgent items).  When I return, I plan to summarize this exchange on PDF, post the summary back to the group for comment, then send it along to my correspondent to try to help her understand.

Audrey

>>> [log in to unmask] 09/06/01 10:36 AM >>>
Hi Audrey,

I think what the person at Adobe was trying to say was that some documents,
though they look like they are organized as tables and such, don't have
coding that tells Acrobat Reader about this structure.  All Acrobat Reader
sees is text, spaces and returns; there are no codes identifying the text
as being in a table.  This is unstructured text.

In such a case, Acrobat Reader has to guess what the structure of the
document should be.  Apparently the access plug-in designed for Acrobat
Reader 4 was better at guessing how to organize unstructured text than the
new version is.  The person at Adobe was saying that in a later release,
they should consider using this older method to guess about unstructured
text, rather than the newer, less effective one.

I hope this makes sense.

Regards,
Anna

ATOM RSS1 RSS2