Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" 
for change notification.

The following page has been changed by JeremiasMaerki:
http://wiki.apache.org/xmlgraphics-fop/PDF_Accessibility

The comment on the change is:
Some additional notes

------------------------------------------------------------------------------
  The section [#head-1aae9f58ba7b221421d56567b1b6a50d9a75792c Changes to your 
XSL-FO input files] will illustrate where you provide this information in the 
input XSL-FO file.
  
  == Implementation ==
+ 
+ The initial implementation is for PDF output only (as this is the only 
currently implemented format that supports accessibility) and is based on the 
code for the new intermediate format.
  
  The challenge is to find the corresponding FO of a text element or image that 
is sent to the PDFPainter.drawText respectively PDFPainter.drawImage from the 
LM's. This is required to build the structure tree.
  
@@ -105, +107 @@

  
  '''(R3)''' Decide how the language should be defined. Other implementations 
specify the @xml:lang on fo:root level. The same attribute is set for 
descendant's to override the default language. There is also the common FO 
property {{{country}}} and {{{language}}} to consider.
  
+    * [JM] XSL defines {{{xml:lang}}} as a shorthand for 
{{{country}}}/{{{language}}}/{{{script}}}. So both are equivalent from a user's 
perspective. It should be verified that {{{xml:lang}}} is properly mapped to 
the other three properties. Internally, the code should work off the basic XSL 
properties, not the shorthand.
+ 
+ '''(R3)''' Implement PDF/A-1a support when PDF Accessibility is available 
(JM).
+ 
+ '''(R3)''' Implement support for the "role" property which would allow to 
keep fo:blocks containing titles apart from fo:blocks containing normal text. 
May involve adding support for the "!RoleMap" dictionary entry of PDF's 
"!StructTreeRoot".
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to