Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Accessibility error: Encoding (CMap) specified by a font is corrupt

855 views
Skip to first unread message

Adam L. Ellis

unread,
Jun 5, 2002, 10:34:21 AM6/5/02
to
I'm trying to make all of our PDFs accessible but I keep running into this error. After running the accessibility checker, the error "encoding (CMap) specified by font is corrupt." Does anyone know how to fix this error? Is it possible to fix without going back to the source document?

Aandi Inston

unread,
Jun 5, 2002, 10:51:36 AM6/5/02
to
I've never heard of this particular error before, so it may have a
common cause in how your PDFs are made. What method was used to make
them?

Aandi Inston

Adam L. Ellis

unread,
Jun 5, 2002, 11:58:47 AM6/5/02
to
I converted them to PDFs using the "convert to PDF" option from Word. It's not affecting all of the files either- just a few. I'll greatly appreciate any suggestions.

Aandi Inston

unread,
Jun 5, 2002, 1:37:58 PM6/5/02
to
I was hoping you'd say something unusual. I don't know in that case;
it may be worth recreating the PDF.

Aandi Inston

BrianPKim

unread,
Jun 5, 2002, 9:26:17 PM6/5/02
to
I've seen it also. I see it in the log created when running the MakeAccessiblePlugIn.

YN_abcXaccess.pdf: Page 1: 1 element(s) with no alternate text. No alternate text for element at (72, 72), (162, 162) The encoding (CMap) specified by a font is corrupted.

Don't know what it means. Occurs on FrameMaker 6.0 files Saved As PDF. The plugin does affect the logical tags defined in FrameMaker. I can see changes occur in Acrobat Window > Tags., I don't have any specialized equipment like a screen reader to check what Make Accessible does..

My reason to use the plugin was a desire to try the Save As HTML option of the SaveAsXML (beta 2) plugin. It's not working for me. Since my source document is Framemaker, I get HTML from FrameMaker instead.

Tonight I'l try different routes to PDF and see if the encoding error continues.

0 new messages