xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject svn commit: r1416775 [6/6] - in /xmlgraphics/site/trunk/content/fop: ./ 0.95/ 1.0/ 1.1/ dev/ dev/design/ trunk/
Date Tue, 04 Dec 2012 05:01:42 GMT
Modified: xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext Tue Dec  4 05:01:25 2012
@@ -1,6 +1,7 @@
 Title: Apache(tm) FOP Design: Embedding Apache™ FOP in Other Applications
 
 #Apache™ FOP Design: Embedding Apache™ FOP in Other Applications
+
 <authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person></authors>
 
 ## Introduction <a id="intro"></a>

Modified: xmlgraphics/site/trunk/content/fop/dev/design/extending.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/extending.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/extending.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/extending.mdtext Tue Dec  4 05:01:25 2012
@@ -33,14 +33,20 @@ PDF Outline - This is output document ex
 PDF Additions - This can be done with an XML Document extension. A simple xml document is
defined that provides the appropriate information. When the document is rendered a handler
converts the document into PDF markup.
 
 For example:
-<my:script-link script="app.execMenuItem('AcroSrch:Query');">
-Search
-</my:script-link>
+
+    <my:script-link script="app.execMenuItem('AcroSrch:Query');">
+
+    Search
+
+    </my:script-link>
+
 to result in a text box referencing the following PDF action:
-<<
-/S /JavaScript
-/JS (app.execMenuItem("AcroSrch:Query");)
->>
+
+    <<
+    /S /JavaScript
+    /JS (app.execMenuItem("AcroSrch:Query");)
+    >>
+
 # Status <a id="status"></a>
 
 ### To Do <a id="status-todo"></a>

Modified: xmlgraphics/site/trunk/content/fop/dev/design/properties.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/properties.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/properties.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/properties.mdtext Tue Dec  4 05:01:25 2012
@@ -110,12 +110,12 @@ Because the properties defined in the st
 
 In the properties xml files, one can define generic property definitions which can serve
as a basis for individual property definitions. There are currently several generic properties
defined in foproperties.xml. An example is GenericColor, which defines basic properties for
all ColorType properties. Since the generic specification doesn't include the inherited or
default elements, these should be set in each property which is based on GenericColor. Here
is an example:
 
- `<property type='generic'>
-    <name>background-color</name>
-    <use-generic>GenericColor</use-generic>
-    <inherited>false</inherited>
-    <default>transparent</default>
-  </property>` 
+     `<property type='generic'>
+        <name>background-color</name>
+        <use-generic>GenericColor</use-generic>
+        <inherited>false</inherited>
+        <default>transparent</default>
+      </property>` 
 
 A generic property specification can include all of the elements defined for the property
element in the DTD, including the description of components for compound properties, and the
specification of keyword shorthands.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/index.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/index.mdtext Tue Dec  4 05:01:25 2012
@@ -13,13 +13,14 @@ For basic and user information on FOP, p
 
 The main development happens on "FOP Trunk".
 The SVN repository URL for the trunk is:<br></br> `http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/`

+
 # Getting Involved <a id="involved"></a>
 
-### Understand Apache Roles <a id="apache-roles"></a>
+## Understand Apache Roles <a id="apache-roles"></a>
 
 Review the [Apache Project Roles and Responsibilities](http://xml.apache.org/roles.html)
document for an understanding of the various roles of contributors within the community.
 
-### How you can help <a id="fop-tasks"></a>
+## How you can help <a id="fop-tasks"></a>
 
 There are many different ways that you can help with FOP development. The following is a
non-exhaustive list of ways that *non-programmers* can help. Remember that an hour spent on
the tasks below is an hour that a programmer can devote to fixing bugs or adding features
instead:
 
@@ -51,7 +52,7 @@ Of course, we're glad to have programmer
 
 At the moment FOP is mainly a tool to render XSL-FO files to pdf. Therefore if you want to
contribute to FOP you should become familiar with these standards. You can find links at [Specifications](../resources.html#specs)
.
 
-### Review the Developer Documentation <a id="doc"></a>
+## Review the Developer Documentation <a id="doc"></a>
 
 ### Understand FOP's Design <a id="design"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/dev/rtflib.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/rtflib.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/rtflib.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/rtflib.mdtext Tue Dec  4 05:01:25 2012
@@ -60,6 +60,7 @@ The following table summarizes the vario
 | Text | RtfParagraph.newText() | Character Formatting | N/A |
 
 ### Attributes <a id="userdoc-attributes"></a>
+
 <warning>This section is very incomplete.</warning>
 Attributes can be set for each container and piece of content in the document. The general
approach is to build an RtfAttributes object containing the various attributes, then pass
that RtfAttributes object to the method that creates the new container or content. See the
Javadoc API documentation for RtfAttributes for details on the syntax for creating an RtfAttributes
object. The following information lists the various attributes that can be set for each type
of container.
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/events.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/events.mdtext Tue Dec  4 05:01:25 2012
@@ -31,6 +31,7 @@ A full example of what is shown here can
 ### Writing an EventListener <a id="write-listener"></a>
 
 The following code sample shows a very simple EventListener. It basically just sends all
events to System.out (stdout) or System.err (stderr) depending on the event severity.
+
     import org.apache.fop.events.Event;
     import org.apache.fop.events.EventFormatter;
     import org.apache.fop.events.EventListener;
@@ -56,6 +57,7 @@ The following code sample shows a very s
             }
         }
     }
+
 You can see that for every event the method `processEvent` of the `EventListener` will be
called. Inside this method you can do whatever processing you would like including throwing
a `RuntimeException` , if you want to abort the current processing run.
 
 The code above also shows how you can turn an event into a human-readable, localized message
that can be presented to a user. The `EventFormatter` class does this for you. It provides
additional methods if you'd like to explicitly specify the locale.
@@ -68,6 +70,7 @@ To register the event listener with FOP,
 
     FOUserAgent foUserAgent = fopFactory.newFOUserAgent();
     foUserAgent.getEventBroadcaster().addEventListener(new SysOutEventListener());
+
 Please note that this is done separately for each processing run, i.e. for each new user
agent.
 
 ### An additional listener example <a id="listener-example1"></a>
@@ -108,6 +111,7 @@ You can also customize the exception to 
         }
         
     }
+
 This throws a `RuntimeException` with the `FileNotFoundException` as the cause. Further processing
effectively stops in FOP. You can catch the exception in your code and react as you see necessary.
 
 ## The producer side (for FOP developers) <a id="producer"></a>
@@ -157,11 +161,13 @@ Here's an example of such an event produ
         void complain(Object source, String reason, int blah);
         
     }
+
 To produce the same event as in the first example above, you'd use the following code:
 
     EventBroadcaster broadcaster = [get it from somewhere];
     TestEventProducer producer = TestEventProducer.Provider.get(broadcaster);
     producer.complain(this, "I'm tired", 23);
+
 ### The event model <a id="event-model"></a>
 
 Inside an invocation handler for a dynamic proxy, there's no information about the names
of each parameter. The JVM doesn't provide it. The only thing you know is the interface and
method name. In order to properly fill the `Event` 's parameter map we need to know the parameter
names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model`
package. The data for the object model is retrieved from an XML representation of the event
model that is loaded as a resource. The XML representation is generated using an Ant task
at build time ( `ant resourcegen` ). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`
) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/)
to parse these interfaces.

Modified: xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext Tue Dec  4 05:01:25 2012
@@ -19,6 +19,7 @@ By convention, FO extensions in FOP use 
 
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
              xmlns:fox="http://xmlgraphics.apache.org/fop/extensions">
+
 ### PDF Bookmarks <a id="bookmarks"></a>
 
 In old versions of Apache FOP there was a `fox:outline` element which was used to create
outlines in PDF files. The redesigned code makes use of the [bookmark feature defined in the
W3C XSL 1.1 standard](http://www.w3.org/TR/xsl11/#fo_bookmark-tree) .
@@ -30,6 +31,7 @@ Use the fox:destination element to defin
     <fox:destination internal-destination="table-of-contents"/>
     ...
     <fo:block id="table-of-contents">Table of Contents</fo:block>
+
 <warning>It is possible that in some future release of FOP, *all* elements with "id"
attributes will generate named-destinations, which will eliminate the need for fox:destination.</warning>
 ### Table Continuation Label <a id="table-continue-label"></a>
 
@@ -147,6 +149,7 @@ The example fo `examples/fo/advanced/rou
 
 This section defines a number of extensions related to [prepress](http://en.wikipedia.org/wiki/Prepress)
support. `fox:scale` defines a general scale factor for the generated pages. `fox:bleed` defines
the [bleed area](http://en.wikipedia.org/wiki/Bleed_%28printing%29) for a page. `fox:crop-offset`
defines the outer edges of the area in which crop marks, registration marks, color bars and
page information are placed. For details, please read on below.
 Those extensions have been implemented in the PDF and Java2D renderers only.
+
 #### fox:scale<a id="scale"></a>
 
 Value: <number>{1,2}

Modified: xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext Tue Dec  4 05:01:25 2012
@@ -142,9 +142,10 @@ java -cp build\fop.jar;lib\avalon-framew
           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
           msmincho.ttc msminch.xml
 Alternatively, the individual sub-fonts of a TrueType Collections can be selected using the
"sub-font" attribute on the "font" element. That means that generating an XML font metrics
file for TrueType collections is not necessary anymore. Example:
-<font embed-url="gulim.ttc" sub-font="GulimChe">
-  <font-triplet name="GulimChe" style="normal" weight="normal"/>
-</font>
+
+    <font embed-url="gulim.ttc" sub-font="GulimChe">
+      <font-triplet name="GulimChe" style="normal" weight="normal"/>
+    </font>
 
 
 ### Auto-Detect and auto-embed feature <a id="autodetect"></a>
@@ -156,6 +157,7 @@ Manifest-Version: 1.0
           
           Name: font/myfont.ttf
           Content-Type: application/x-font
+
 This feature allows you to create JAR files containing fonts. The JAR files can be added
to fop by providem them in the classpath, e.g. copying them into the lib/ directory.
 
 #### The font cache <a id="font-cache"></a>

Modified: xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext Tue Dec  4 05:01:25 2012
@@ -11,12 +11,14 @@ Apache&trade; FOP uses Liang's hyphenati
 
 Because of [licensing issues](#license-issues) (and for convenience), all hyphenation patterns
for FOP are made available through the [Objects For Formatting Objects](http://offo.sourceforge.net/hyphenation/index.html)
project.
 If you have made improvements to an existing Apache&trade; FOP hyphenation pattern, or
if you have created one from scratch, please consider contributing these to OFFO so that they
can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user)
.
+
 ### License Issues <a id="license-issues"></a>
 
 Many of the hyphenation files distributed with TeX and its offspring are licenced under the
[LaTeX Project Public License (LPPL)](http://www.latex-project.org/lppl.html) , which prevents
them from being distributed with Apache software. The LPPL puts restrictions on file names
in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files
have other or additional restrictions, for example against use for commercial purposes.
 
 Although Apache FOP cannot redistribute hyphenation pattern files that do not conform with
its license scheme, that does not necessarily prevent users from using such hyphenation patterns
with FOP. However, it does place on the user the responsibility for determining whether the
user can rightly use such hyphenation patterns under the hyphenation pattern license.
 <warning>The user is responsible to settle license issues for hyphenation pattern files
that are obtained from non-Apache sources.</warning>
+
 ### Sources of Custom Hyphenation Pattern Files <a id="sources"></a>
 
 The most important source of hyphenation pattern files is the [CTAN TeX Archive](http://www.ctan.org/tex-archive/language/hyphenation/)
.
@@ -49,6 +51,7 @@ and run Ant with build target `jar-hyphe
 - Put the pattern source file(s) into a directory of your choice and configure FOP to look
for custom patterns in this directory, by setting the [<hyphenation-base>](configuration.html)
configuration option.
 
 <warning>Either of these three options will ensure hyphenation is working when using
FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the
hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the [<hyphenation-dir>](configuration.html#hyphenation-dir)
configuration option programmatically (option 3).</warning>
+
 ## Hyphenation Patterns <a id="patterns"></a>
 
 If you would like to build your own hyphenation pattern files, or modify existing ones, this
section will help you understand how to do so. Even when creating a pattern file from scratch,
it may be beneficial to start with an existing file and modify it. See [OFFO's Hyphenation
page](http://offo.sourceforge.net/hyphenation/index.html) for examples. Here is a brief explanation
of the contents of FOP's hyphenation patterns:

Modified: xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext Tue Dec  4 05:01:25 2012
@@ -77,6 +77,7 @@ The basic pattern to parse the area tree
     } finally {
         out.close();
     }
+
 This example simply reads an area tree file and renders it to a PDF file. Please note, that
in normal FOP operation you're shielded from having to instantiate the FontInfo object yourself.
This is normally a task of the AreaTreeHandler which is not present in this scenario. The
same applies to the AreaTreeModel instance, in this case an instance of a subclass called
RenderPagesModel. RenderPagesModel is ideal in this case as it has very little overhead processing
the individual pages. An important line in the example is the call to `endDocument()` on the
AreaTreeModel. This lets the Renderer know that the processing is now finished.
 
 The area tree XML format can also be used from the [command-line](running.html#standalone-start)
by using the "-atin" parameter for specifying the area tree XML as input file. You can also
specify a "mimic renderer" by inserting a MIME type between "-at" and the output file.
@@ -139,6 +140,7 @@ The basic pattern to parse the intermedi
     } finally {
         out.close();
     }
+
 This example simply reads an intermediate file and renders it to a PDF file. Here IFParser.parse()
is used, but you can also just get a SAX ContentHandler by using the IFParser.getContentHandler()
method.
 
 ### Concatenating Documents <a id="concat-if"></a>

Modified: xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext Tue Dec  4 05:01:25 2012
@@ -37,6 +37,7 @@ Document-level metadata can be specified
     </fo:declarations>
     <fo:page-sequence ...
     [..]
+
 `fo:declarations`  **must** be declared after `fo:layout-master-set` and before the first
`page-sequence`.
 
 ## Implementation in Apache FOP <a id="xmp-impl-in-fop"></a>

Modified: xmlgraphics/site/trunk/content/fop/trunk/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/output.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/output.mdtext Tue Dec  4 05:01:25 2012
@@ -99,6 +99,7 @@ Here is some sample code that uses iText
         e.printStackTrace();
       }
     }
+
 Check the iText tutorial and documentation for setting access flags, password, encryption
strength and other parameters.
 
 ### Watermarks <a id="pdf-watermark"></a>
@@ -150,6 +151,7 @@ The PostScript renderer configuration cu
       <dsc-compliant>true</dsc-compliant>
       <rendering>quality</rendering>
     </renderer>
+
 The default value for the "auto-rotate-landscape" setting is "false". Setting it to "true"
will automatically rotate landscape pages and will mark them as landscape.
 
 The default value for the "language-level" setting is "3". This setting specifies the PostScript
language level which should be used by FOP. Set this to "2" only if you don't have a Level
3 capable interpreter.
@@ -214,6 +216,7 @@ The PCL renderer configuration currently
       <text-rendering>bitmap</text-rendering>
       <disable-pjl>false</disable-pjl>
     </renderer>
+
 The default value for the "rendering" setting is "speed" which causes borders to be painted
as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available.
If you want support for all border modes, set the value to "quality" as indicated above. This
will cause the borders to be painted as bitmaps.
 
 The default value for the "text-rendering" setting is "auto" which paints the base fonts
using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting
methods results in unwelcome output, you can set this to "bitmap" which causes all text to
be rendered as bitmaps.
@@ -311,6 +314,7 @@ The AFP Renderer requires special config
       <!-- AFP Renderer -->
       ...
     </renderer>
+
 There are 4 font configuration variants supported:
 
 
@@ -350,6 +354,7 @@ A typical raster font configuration look
       <font-triplet name="Times-Roman" style="normal" weight="normal"/>
       <font-triplet name="TimesNewRoman" style="normal" weight="normal"/>
     </font>
+
 An outline font configuration is simpler as the individual font size entries are not required.
However, the characterset definition is now required within the afp-font element.
 
     <font>
@@ -443,6 +448,7 @@ Experimentation has shown that the font 
       <font-triplet name="monospace" style="normal" weight="bold"/>
       <font-triplet name="Courier" style="normal" weight="bold"/>
     </font>
+
 By default, all manually configured fonts are embedded, unless they are matched in the [section
of the configuration file](fonts.html#embedding) . However, the default fonts shown above
will not be embedded.
 
 For double byte EBCDIC encoded character sets, there is an optional tag that must be set
to prevent characters from being miscoded. This defaults to "false" if not specified.
@@ -454,6 +460,7 @@ For double byte EBCDIC encoded character
 By default the AFP Renderer creates output with a resolution of 240 dpi. This can be overridden
by the <renderer-resolution/> configuration element. Example:
 
     <renderer-resolution>240</renderer-resolution>
+
 #### Images<a id="afp-image-config"></a>
 
 By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden
by the <images/> configuration element. Example:
@@ -478,12 +485,15 @@ Setting `cmyk="true"` on the `images` el
 When the color mode is set to 1 bit (bi-level), the "dithering-quality" attribute can be
used to select the level of quality to use when converting images to bi-level images. Valid
values for this attribute are floating point numbers from 0.0 (fastest) to 1.0 (best), or
special values: "minimum" (=0.0), "maximum" (1.0), "medium" (0.5, the default). For the higher
settings to work as expected, JAI needs to be present in the classpath. If JAI is present,
0.0 results in a minimal darkness-level switching between white and black. 0.5 does bayer-based
dithering and 1.0 will use error-diffusion dithering. The higher the value, the higher the
quality and the slower the processing of the images.
 
     <images mode="b+w" bits-per-pixel="1" dithering-quality="maximum"/>
+
 When the boolean attribute pseg (default false) is set to true, non-inline FS11 and FS45
IOCA images are wrapped in page segment. This option is provided to support printers/print
servers that require this MO:DCA structure.
 
     <images mode="b+w" bits-per-pixel="8" pseg="true"/>
+
 Setting the boolean attribute fs45 to true (default false) will force all images to FS45.
 
     <images mode="b+w" bits-per-pixel="8" fs45="true"/>
+
 By default, JPEG images are rasterized to a bitmap and the bitmap is included in the AFP
doc. However it is possible to encode in a lossless way to maintain maximum quality. But due
to lack of support for compression schemes like LZW (patent concerns), bitmap data is currently
not compressed resulting in large AFP files. Using the "allow-embedding" attribute on jpeg
child element allows the user to pass the JPEG as is in the document. The default is set to
"false" since there are compatibility concerns as some AFP printers don't support JPEG decoding.
Using the "bitmap-encoding-quality" attribute it is possible to enable lossy compression (JPEG
baseline DCT). The default is "1.0" which means lossless encoding. Setting a value lower than
1.0, JPEG compression is enabled and the setting is used as the quality setting when encoding
bitmap data. Note that this setting does not always have an effect. Bi-level (1 bit) bitmaps
are not compressed using JPEG. Example:
 
     <images mode="color" cmyk="true">
@@ -499,9 +509,11 @@ Not all AFP implementations support GOCA
 GOCA is enabled by default. You can disable GOCA entirely in which case the AFP support falls
back to generating bitmaps for vector graphics. Example:
 
     <goca enabled="false"/>
+
 Some AFP implementations have trouble rendering text in GOCA. You can instruct the AFP support
to render text as shapes (i.e. use vector graphics to paint text). Example:
 
     <goca enabled="true" text="shapes"/>
+
 If you disable GOCA or let text render as shapes, the size of the generated AFP usually increases
considerably.
 
 #### Shading<a id="afp-shading-config"></a>
@@ -515,6 +527,7 @@ By default, filled rectangles are painte
 By default the AFP Renderer will place all data resource objects such as images within the
document of the main output datastream. An external resource group file where document resources
may be specified with the <resource-group-file/> configuration element. Example:
 
     <resource-group-file>external_resources.afp</resource-group-file>
+
 Be careful when using this option not to overwrite existing resource files from previous
rendering runs.
 #### Resource Level Defaults<a id="afp-resource-level-defaults"></a>
 
@@ -522,7 +535,8 @@ By default, bitmap image objects (or pag
 
 It is possible to override these defaults, either per image (see the [afp:resource-level](#afp-foreign-attributes-resource)
extension attribute below) or by specifying different defaults in the configuration:
 
-<default-resource-levels goca="print-file" bitmap="inline"/>
+    <default-resource-levels goca="print-file" bitmap="inline"/>
+
 "goca" refers to GOCA graphics and "bitmap" refers to IOCA images. The possible values for
the attributes are "inline" and "print-file". In the future, additional possibilities may
be added.
 
 ### Extensions <a id="afp-extensions"></a>
@@ -724,6 +738,7 @@ The TIFF and PNG renderer configuration 
       <rendering>quality</rendering>
       <fonts><!-- described elsewhere --></fonts>
     </renderer>
+
 The default value for the `"color-mode"` setting is `"rgba"` which is equivalent to a 24bit
RGB image with an 8bit alpha channel for transparency. Valid values are:
 
 
@@ -754,6 +769,7 @@ In addition to the above values the TIFF
       <compression>CCITT T.6</compression>
       <fonts><!-- described elsewhere --></fonts>
     </renderer>
+
 The default value for the "compression" setting is "PackBits" which which is a widely supported
RLE compression scheme for TIFF. The set of compression names to be used here matches the
set that the Image I/O API uses. Note that not all compression schemes may be available during
runtime. This depends on the actual codecs being available. Here is a list of possible values:
 
 
@@ -781,6 +797,7 @@ The IF-based bitmap output implementatio
 
     userAgent.getRenderingOptions().put(
         "target-bitmap-size", new Dimension(320, 200));
+
 ## TXT <a id="txt"></a>
 
 The text renderer produces plain ASCII text output that attempts to match the output of the
PDFRenderer as closely as possible. This was originally developed to accommodate an archive
system that could only accept plain text files, and is primarily useful for getting a quick-and-dirty
view of the document text. The renderer is very limited, so do not be surprised if it gives
unsatisfactory results.

Modified: xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext?rev=1416775&r1=1416774&r2=1416775&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext Tue Dec  4 05:01:25 2012
@@ -44,6 +44,7 @@ Here is a minimal code snippet to demons
             throw new ServletException(ex);
         }
     }
+
 There are numerous problems with the code snippet above. Its purpose is only to demonstrate
the basic concepts. See below for details.
 
 ### Adding XSL tranformation (XSLT) <a id="xslt"></a>
@@ -84,7 +85,9 @@ A common requirement is to transform an 
     
     //Send content to Browser
     response.getOutputStream().write(out.toByteArray());
-    response.getOutputStream().flush();Buffering the generated PDF in a ByteArrayOutputStream
is done to avoid potential problems with the Acrobat Reader Plug-in in Microsoft Internet
Explorer.
+    response.getOutputStream().flush();
+
+Buffering the generated PDF in a ByteArrayOutputStream is done to avoid potential problems
with the Acrobat Reader Plug-in in Microsoft Internet Explorer.
 The `Source` instance used above is simply an example. If you have to read the XML from a
string, supply a `new StreamSource(new
           StringReader(xmlstring))` . Constructing and reparsing an XML string is generally
less desirable than using a SAXSource if you generate your XML. You can alternatively supply
a DOMSource as well. You may also use dynamically generated XSL if you like.
 
@@ -118,6 +121,7 @@ Here's how to set it up in your servlet.
         this.uriResolver = new ServletContextURIResolver(getServletContext());
         [..]
     }
+
 The ServletContextURIResolver reacts on URIs beginning with "servlet-context:". If you want
to access an image in a subdirectory of your web application, you could, for example, use:
"servlet-context:/images/myimage.png". Don't forget the leading slash after the colon!
 
 Further down, you can use the URIResolver for various things:



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


Mime
View raw message