[xep-support] Re: Problem creating a tagged PDF

[Daniel Boughton]

That was helpful.  My problem was that I was running the FO->XEP with
ENABLE_ACCESSIBILITY set to "false" and then running XEP->PDF with
ENABLE_ACCESSIBILITY set to "true".  When I have ENABLE_ACCESSIBILITY set
to "true" for both steps, the document renders correctly.

Thanks for your help.

On Mon, Jul 23, 2012 at 1:43 PM, Kevin Brown <kevin at renderx.com> wrote:

> Daniel:****
>
> ** **
>
> If you run without your custom post process are things OK? Meaning if you
> go from FO->XEP and then XEP->PDF **without modification**. If so,
> describe what you are doing in the custom process, perhaps that is breaking
> things. I just ran a document to XEPOUT with ENABLE_ACCESSIBILITY set to
> “true” and ran that to PDF and it worked fine. I suspect it is something in
> the modification script that is breaking things.****
>
> ** **
>
> In the XEPOUT of the document, you should see things like this:****
>
> ** **
>
> <xep:text value="Custom Dashes" x="23177" y="566090" width="78243" xpath=
> "/*[1][name()=&apos;root&apos;]/*[2][name()=&apos;page-sequence&apos;]/*[1][name()=&apos;flow&apos;]/*[1][name()=&apos;block-container&apos;]/*[1][name()=&apos;table&apos;]/*[2][name()=&apos;table-body&apos;]/*[1][name()=&apos;table-row&apos;]/*[1][name()=&apos;table-cell&apos;]/*[1][name()=&apos;block&apos;]"
> />
>
> ****
>
> The “xpath” element is what is driving the tagged PDF. If your code is
> modifying (perhaps stripping this or double escaping it) it would break
> everything.****
>
> ** **
>
> Kevin Brown****
>
> RenderX****
>
> ** **
>
> *From:* xep-support-bounces at renderx.com [mailto:
> xep-support-bounces at renderx.com] *On Behalf Of *Daniel Boughton
> *Sent:* Monday, July 23, 2012 6:56 AM
> *To:* xep-support at renderx.com
> *Subject:* [xep-support] Problem creating a tagged PDF****
>
> ** **
>
> I am having trouble creating a tagged PDF from the XEP proprietary file
> format.  If I render a tagged PDF directly from FO it works just fine, but
> if I go from FO to XEP to PDF, the reader tell me that every page is blank.
>  The Adobe accessibility report states that "None of the contents of this
> page are contained in the structure tree" for all pages.  I need to run a
> post process on the XEP file, but I also need a tagged PDF as the result.
>  Is there something I need to do differently when rendering a tagged PDF
> from the XEP file format?
> ****
>
> ** **
>
> Thanks.****
>
> -- ****
>
>
> __________________________________________________________________________________
> *Daniel Boughton | Technical Analyst IV | RR Donnelley*
> W6545 Quality Dr | Greenville, WI 54942
> Office: 920.997.3635 | Mobile: 920.450.3581 | Fax: 920.997.3754
> daniel.r.boughton at rrd.com<http://inside.rrd.net/insiderrd/pages/google/rrd_google_signature.aspx>
> http://www.rrdonnelley.com****
>
>
>  ****
>
> _______________________________________________
> (*) To unsubscribe, please visit
> http://lists.renderx.com/mailman/options/xep-support
> (*) By using the Service, you expressly agree to these Terms of Service
> http://w
> ww.renderx.com/terms-of-service.html
>



-- 

__________________________________________________________________________________
*Daniel Boughton | Technical Analyst IV | RR Donnelley*
W6545 Quality Dr | Greenville, WI 54942
Office: 920.997.3635 | Mobile: 920.450.3581 | Fax: 920.997.3754
daniel.r.boughton at rrd.com<http://inside.rrd.net/insiderrd/pages/google/rrd_google_signature.aspx>
http://www.rrdonnelley.com


!DSPAM:87,500da0ac63731976247327!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20120723/c31e5d47/attachment.html>