I've encountered a strange problem where arrowheads in my document are replaced by tiny squares after I add tags to the document in Acrobat 9 Pro. Here is my workflow:
1. Print book from Framemaker 7.2 to a PostScript file.
2. Run the PostScript file through Distiller 9.
3. Open the resulting PDF in Acrobat 9 Pro. At this point, all arrowheads appear as expected.
4. Choose Advanced > Accessibility > Add Tags to Document.
5. Save PDF.
6. Close and reopen PDF. Arrowheads have been replaced by tiny squares.
While researching this problem, I have read that adding the tags in FrameMaker might work better, but our screen reader users have told us that files with tags added by Acrobat work better with their screen reader software. Perhaps we were not properly configuring the logical structure levels in FrameMaker? I cannot find good resources for configuring tags in FrameMaker.
Thank you,
Amanda
When you tag an untagged PDF with Acrobat one thing that happens is the mapping of characters to unicode.
The "tiny squares" may be indicative of a character that is not mapping to unicode.
Using Acrobat to tag the PDF relies on the tag element sets provided within Acrobat. No mapping of incoming
FM paragraph tags. As discussed in the PDF References & ISO standard this mapping is "loose" by design.
Makes sense to me that a screen reader application's coding would be easier by just looking at the PDF "defaults" and
not working the mapping information available in the structure tree.
This could explain why screen readers that just rely on the Acrobat tag elements are better/easier from the user perspective.
The user does not have to ask the application to do what it is not coded to do.
Downside is the screen reader application short changes the user to some degree.
As the ISO specification begins to reflect the recommendations of the PDF/UA working group I suspect that there will
be an increased interest in provided the ability to pre-stage more in authoring applications that support tagged
output PDFs (such as FM). All of which provides incentive for noodling out what is already possible with FM.
I agree, not much "how-to" for FM. Actually, authoring for tagged output PDF is somewhat "new" & the development
scene seems to be changing briskly.
So, for now we all have to do "what if" trials as time permits. Take notes & maybe
find time do some kind of smooth write up which, hopefully, is shared.
Eventually, some bright person will put some good stuff in a book & we'll all buy it.Be well...
Be well...