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

[Kirch Fritz]

Dear XEP-support,

 

Instead of setting the ENABLE_ACCESSIBILITY option in xep.xml to "true",

I want to set  ENABLE_ACCESSIBILITY at runtime with my XSLT-Stylesheet.

 

How can I do this?

Do you have an example?

 

Friedrich Kirch 
Softwareentwicklung Media Business Suite

 

 

Tel.:

 +49 911 30 730-0

FAX:

 +49 911 30 730-111

Mail:

 Friedrich.Kirch at it2media.de <mailto:Friedrich.Kirch at it2media.de> 

Homepage:

 www.it2media.de <http://www.it2media.de/> 

________________________________

IT2media GmbH & Co. KG, Pretzfelder Str. 15, 90425 Nürnberg; Kommanditgesellschaft, Sitz Nürnberg, HRA Nürnberg 12784, Persönlich haftende Gesellschafterin: IT2media Beteiligungsgesellschaft mbH, Sitz Nürnberg, HRB Nürnberg 19511; Geschäftsführer: Dr. Gerhard Baier, Claudia Dietrich

 

 

________________________________

Von: owner-xep-support at renderx.com [mailto:owner-xep-support at renderx.com] Im Auftrag von Kevin Brown
Gesendet: Donnerstag, 2. September 2010 20:30
An: xep-support at renderx.com
Betreff: RE: [xep-support] ENABLE_ACCESSIBILITY resulting in huge file...

 

Paul:

 

Many of our Us Gov customers actually generate both. That way, they can still meet requirement of 508 but not overly burden users that don't need the enhancements that 508 documents deliver.

 

Kevin

 

From: owner-xep-support at renderx.com [mailto:owner-xep-support at renderx.com] On Behalf Of Harvey, Paul (Contractor)
Sent: Thursday, September 02, 2010 2:10 PM
To: 'xep-support at renderx.com'
Subject: RE: [xep-support] ENABLE_ACCESSIBILITY resulting in huge file...

 

Makes good sense Kevin, thanks.

 

________________________________

From: owner-xep-support at renderx.com [mailto:owner-xep-support at renderx.com] On Behalf Of Kevin Brown
Sent: Wednesday, September 01, 2010 2:46 PM
To: xep-support at renderx.com
Subject: RE: [xep-support] ENABLE_ACCESSIBILITY resulting in huge file...

 

Paul:

 

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 this:

 

Without ...

 

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

 

With ...

 

<xep:text value="Rewards:" x="108584" y="514977" width="51618" xpath="/*[1][name()=&apos;root&apos;]/*[3][name()=&apos;page-sequence&apos;]/*[2][name()=&apos;flow&apos;]/*[2][name()=&apos;block-container&apos;]/*[1][name()=&apos;block&apos;]/*[1][name()=&apos;inline&apos;]"/>

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 root->page-sequence->flow->block-container->block->table->table-body->table-row->table-cell->block->inline ... for each and every cell (and if you nest tables ..... think of it).

 

Kevin Brown

RenderX

 

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

 

Hi,

 

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.

 

Thanks,

 

Paul

**********************************************************************
Diese E-Mail wurde auf Viren ueberprueft.
mailsweeper at it2media.de <mailto:mailsweeper at it2media.de> 
**********************************************************************


**********************************************************************
Diese E-Mail wurde auf Viren ueberprueft.
mailsweeper at it2media.de
**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20100915/918982c7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 3146 bytes
Desc: image002.jpg
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20100915/918982c7/attachment.jpg>