RE: [xep-support] ENABLE_ACCESSIBILITY resulting in huge file...

From: Kevin Brown <>
Date: Wed Sep 01 2010 - 11:46:11 PDT



Enabling Tagged PDF through Accessibility has the effect of embedding
essentially the XPATH to every element in the PDF on every object. This is
the "tagged" part.


If you were to examine the XEP Intermediate Format, you can get an idea of


Without ...


<xep:text value="Rewards:" x="108584" y="514977" width="51618"/>


With ...


<xep:text value="Rewards:" x="108584" y="514977" width="51618"

The xpath information must be embedded into the PDF to understand structure
from the source as this is the requirement of 508. Thus, it significantly
increases the size of the PDF as the xpath itself is much larger that the
content (in this case, just the word "Rewards:". This is especially true
when it comes to tabular structures -- you may have
row->table-cell->block->inline ... for each and every cell (and if you nest
tables ..... think of it).


Kevin Brown



From: []
On Behalf Of Harvey, Paul
Sent: Wednesday, September 01, 2010 2:05 PM
Subject: [xep-support] ENABLE_ACCESSIBILITY resulting in huge file...




I am trying to create a "508-compliant" PDF file using RenderX (4.17) by
setting the ENABLE_ACCESSIBILITY option in xep.xml to "true". For the
document in question this increases the file size from 167K to 1009K. If
COMPRESS is set to "false", the file size increases further, to 1563K.


I'd like to know if there's a way to avoid the large file size.





(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
Received on Wed Sep 1 11:54:45 2010

This archive was generated by hypermail 2.1.8 : Wed Sep 01 2010 - 11:54:46 PDT