xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r913004 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/trunk/output.html
Date Thu, 19 Jun 2014 10:32:53 GMT
Author: buildbot
Date: Thu Jun 19 10:32:53 2014
New Revision: 913004

Staging update by buildbot for xmlgraphics

    websites/staging/xmlgraphics/trunk/content/   (props changed)

Propchange: websites/staging/xmlgraphics/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 19 10:32:53 2014
@@ -1 +1 @@

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html Thu Jun 19 10:32:53 2014
@@ -351,7 +351,7 @@ $(document).ready(function () {
         <div id="items">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div>
-      	<div class="section-content"><h1 id="apachewzxhzdk42-fop-output-formats">Apache&trade;
FOP Output Formats</h1>
+      	<div class="section-content"><h1 id="apachewzxhzdk43-fop-output-formats">Apache&trade;
FOP Output Formats</h1>
 <p>Apache&trade; FOP supports multiple output formats by using a different renderer
for each format. The renderers do not all have the same set of capabilities, sometimes because
of the output format itself, sometimes because some renderers get more development attention
than others.</p>
 <h2 id="general">General Information</h2>
 <h3 id="general-fonts">Fonts</h3>
@@ -488,6 +488,19 @@ Here is some sample code that uses iText
 <p>Note: Not all PDF Viewers (including some Acrobat Versions) will open the embedded
file when clicking on the link. In that case, the user will have to open he attachment via
the separate list of file attachments.</p>
+<h4 id="custom-document-properties">Custom Document Properties</h4>
+<p>In Adobe Reader (and possibly other PDF viewers), in the Document Properties window,
there is a tab that shows custom properties that have been set on the document:
+<img alt="PDF Custom Document Properties" src="images/pdf-custom-document-properties.png"
+<p>Such properties can be set in the FO document using the <code>pdf:info</code>
extension element as a child of <code>fo:declarations</code>:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:declarations&gt;</span>
+  <span class="nt">&lt;pdf:info</span> <span class="na">xmlns:pdf=</span><span
+    <span class="nt">&lt;pdf:name</span> <span class="na">key=</span><span
class="s">&quot;MyCustomProperty&quot;</span><span class="nt">&gt;</span>MyPropertyValue<span
+  <span class="nt">&lt;/pdf:info&gt;</span>
+<span class="nt">&lt;/fo:declarations&gt;</span>
+<p>Each custom property must be specified using the <code>pdf:name</code>
element. Remember that the property name must be different to the reserved keywords, which
are Title, Author, Subject, Keywords, Creator, Producer, CreationDate, ModDate and Trapped.</p>
 <h2 id="ps">PostScript</h2>
 <p>The PostScript renderer has been brought up to a similar quality as the PDF renderer,
but may still be missing certain features. Currently, the PostScript renderer generates PostScript
Level 3 with most DSC comments. Actually, the only Level 3 features used are the FlateDecode
and DCTDecode filter (the latter is used for 1:1 embedding of JPEG images), everything else
is Level 2.</p>
 <h3 id="ps-configuration">Configuration</h3>

To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org

View raw message