You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2015/03/12 11:52:13 UTC
svn commit: r943488 - in /websites/staging/xmlgraphics/trunk/content: ./
fop/trunk/metadata.html
Author: buildbot
Date: Thu Mar 12 10:52:13 2015
New Revision: 943488
Log:
Staging update by buildbot for xmlgraphics
Modified:
websites/staging/xmlgraphics/trunk/content/ (props changed)
websites/staging/xmlgraphics/trunk/content/fop/trunk/metadata.html
Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 12 10:52:13 2015
@@ -1 +1 @@
-1666125
+1666127
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/metadata.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/metadata.html Thu Mar 12 10:52:13 2015
@@ -354,7 +354,7 @@ $(document).ready(function () {
<div id="items">
</div>
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
- <div class="section-content"><h1 id="apachewzxhzdk1-fop-metadata">Apache™ FOP: Metadata</h1>
+ <div class="section-content"><h1 id="apachewzxhzdk2-fop-metadata">Apache™ FOP: Metadata</h1>
<h2 id="overview">Overview</h2>
<p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a>. PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred way of specifying document and object metadata. Therefore, there's no portable way to represent metadata in XSL-FO documents. Each implementation does it differently.</p>
<h2 id="xmp-in-fo">Embedding XMP in an XSL-FO document</h2>
@@ -508,7 +508,20 @@ $(document).ready(function () {
<li>
<p><a href="http://dublincore.org/">http://dublincore.org/</a></p>
</li>
-</ul></div>
+</ul>
+<h1 id="pdf-page-piece">PDF Page Piece</h1>
+<p>Allows indexing of PDF files for tools such as IBM Content Manager OnDemand</p>
+<h2 id="fo">Usage (fo)</h2>
+<p>Add metadata for each page master based on how the software has been configured.</p>
+<div class="codehilite"><pre><span class="nt"><fo:simple-page-master</span> <span class="na">master-name=</span><span class="s">"simple"</span> <span class="na">page-height=</span><span class="s">"27.9cm"</span> <span class="na">page-width=</span><span class="s">"21.6cm"</span><span class="nt">></span>
+ <span class="nt"><fo:region-body</span> <span class="nt">/></span>
+ <span class="nt"><pdf:pagepiece></span>
+ <span class="nt"><pdf:dictionary</span> <span class="na">key=</span><span class="s">"IBM-ODIndexes/Private"</span><span class="nt">></span>
+ <span class="nt"><pdf:string</span> <span class="na">key=</span><span class="s">"Cname"</span><span class="nt">></span>BUD<span class="nt"></pdf:string></span>
+ <span class="nt"></pdf:dictionary></span>
+ <span class="nt"></pdf:pagepiece></span>
+<span class="nt"></fo:simple-page-master></span>
+</pre></div></div>
</div>
<div class="clear"></div>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org