<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user">
    <title>gmane.text.xml.fop.user</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34209"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34208"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34207"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34206"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34205"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34204"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34203"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34202"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34201"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34200"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34199"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34198"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34197"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34196"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34195"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34194"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34193"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34192"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34191"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/34190"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34209">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34209</link>
    <description>&lt;pre&gt;Thanks, this is a useful comparison. I can clearly see a number of
differences, such as kerning and word spacing, which I need to investigate
further. So stay tuned.

On Wed, May 23, 2012 at 4:20 PM, Warren Young &amp;lt;warren&amp;lt; at &amp;gt;etr-usa.com&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Glenn Adams</dc:creator>
    <dc:date>2012-05-23T23:39:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34208">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34208</link>
    <description>&lt;pre&gt;
Here's a pretty good example of what I mean:

     http://etr-usa.com/fop/titles-admin-20120523-1511.fo
     http://etr-usa.com/fop/titles-admin-20120523-1511-fop.pdf
     http://etr-usa.com/fop/titles-admin-20120523-1511-xep.pdf

The .fo file comes from a very simple .dbx file, basically just an 
&amp;lt;informaltable&amp;gt; inside an &amp;lt;article&amp;gt;.  The .xsl customization layer I use 
is also very basic, doing only things like defining margins.

The biggest problem in the FOP PDF output is that the headers and 
footers are smashed to the left instead of taking the full page width. 
I suppose it's possible XEP is the one doing something wrong, but given 
how much better it looks when they do that, I have to believe it's FOP 
at fault here instead.

You can also see differences in kerning.  The "Animal holiday" row on 
the first page shows how a bit of loose kerning can turn into a blight. 
  There are several more examples of this on the second page.
&lt;/pre&gt;</description>
    <dc:creator>Warren Young</dc:creator>
    <dc:date>2012-05-23T22:20:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34207">
    <title>Re: table of contents page number not showing in RTF output</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34207</link>
    <description>&lt;pre&gt;what do you mean by "Word will display the numbers"?

On Wed, May 23, 2012 at 2:21 PM, Chen Yang &amp;lt;cyang&amp;lt; at &amp;gt;hrsg.ca&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Glenn Adams</dc:creator>
    <dc:date>2012-05-23T20:26:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34206">
    <title>table of contents page number not showing in RTF output</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34206</link>
    <description>&lt;pre&gt;Hey guys,

I am converting xml to rtf using fop trunk ver. page numbers (table of
content to be exact) showing up as # symbol but field codes are correct,
if I print the document, Word will display the numbers, what is it that
I need to do to display the numbers immediately? 

 

example:

CONFLICT
MANAGEMENT..............................................................
........................................................................
........................................................................
.............................................................. # 

DEVELOPING
OTHERS..................................................................
........................................................................
........................................................................
.................................................................. # 

FOSTERING
LEARNING................................................................
.....................................................&lt;/pre&gt;</description>
    <dc:creator>Chen Yang</dc:creator>
    <dc:date>2012-05-23T20:21:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34205">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34205</link>
    <description>&lt;pre&gt;I presume you are referring to the features defined at [1].

[1] http://www.w3.org/TR/xsl/#d0e13293

The answer to question is NO, there is no activity (of which I'm aware) to
implement the features defined in XSL-FO 1.1 Section 6.10. It would be
useful for you to file a bug [2], with severity 'enhancement', that
requests the specific features from 6.10 that you need.

[2] https://issues.apache.org/bugzilla/enter_bug.cgi

It would also be useful for Siemens to identify or provide resources to
perform this implementation activity. Most work on FOP these days is
(informally) sponsored by a variety of commercial activities that make use
of FOP.

Regards,
Glenn

On Wed, May 23, 2012 at 11:45 AM, Hintz, David &amp;lt;david.hintz&amp;lt; at &amp;gt;siemens.com&amp;gt;wrote:

&lt;/pre&gt;</description>
    <dc:creator>Glenn Adams</dc:creator>
    <dc:date>2012-05-23T17:58:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34204">
    <title>RE: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34204</link>
    <description>&lt;pre&gt;We use Apache FOP 1.0 for writer drafts only.  The main (possibly only) feature preventing us from using it for production (customer deliverables) is the lack of indexing support.  Consequently, we use an expensive PDF generation tool for customer deliverables.  Any chance that indexing will be supported in FOP 1.1?

Dave Hintz
Siemens

From: Glenn Adams [mailto:glenn&amp;lt; at &amp;gt;skynav.com]
Sent: Monday, May 21, 2012 7:49 PM
To: fop-users&amp;lt; at &amp;gt;xmlgraphics.apache.org
Subject: Re: Information about Apache FOP


On Mon, May 21, 2012 at 3:05 PM, Warren Young &amp;lt;warren&amp;lt; at &amp;gt;etr-usa.com&amp;lt;mailto:warren&amp;lt; at &amp;gt;etr-usa.com&amp;gt;&amp;gt; wrote:
On 5/21/2012 8:04 AM, Glenn Adams wrote:

(1) a new revision, FOP 1.1, is being prepared for release,

Yay!

which will contain, in addition to bug fixes:

Do "bug fixes" include improvements to XSL-FO compliance?  I don't see any change between the 1.0 and development columns in this table:

       https://xmlgraphics.apache.org/fop/compliance.html

there have been a few additions for XSL-FO com&lt;/pre&gt;</description>
    <dc:creator>Hintz, David</dc:creator>
    <dc:date>2012-05-23T17:45:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34203">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34203</link>
    <description>&lt;pre&gt;


perhaps you can look more closely at the differences that lead you to this
impression, and give us some concrete input on what you find
&lt;/pre&gt;</description>
    <dc:creator>Glenn Adams</dc:creator>
    <dc:date>2012-05-23T15:26:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34202">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34202</link>
    <description>&lt;pre&gt;
I only use XSL-FO via DocBook and the standard stylesheets, so I'm at 
two removes from XSL-FO itself.  I've noticed that RenderX XEP output 
usually looks nicer than FOP output.  One would have to chase the 
reasons for that through two layers of indirection to get to the level 
of actionable suggestion you're asking for.
&lt;/pre&gt;</description>
    <dc:creator>Warren Young</dc:creator>
    <dc:date>2012-05-23T10:42:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34201">
    <title>Re: Is it possible to load &amp; use a font at runtime?</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34201</link>
    <description>&lt;pre&gt;
The is an api call for setting the location of fonts etc.

FopFactory.setFontBaseURL(Sting urlAsString);

You may need a new factory per invocation.

But I can't help wondering why you're not simply putting them all in the 
same place as you get them? Unless all fonts in fontBaseURL are cached?
However, there's a fair amount of convention in the naming etc. which 
you will want to load with setUserConfig( File fontNames.xml).  This 
puts the onus on the user to craft the appropriate font defn. file as 
well as specify the fonts and my be a bigger issue than simply finding 
the fonts (dynamically or not).

rjs


On 05/22/2012 02:26 PM, Phillip B Oldham wrote:
&lt;/pre&gt;</description>
    <dc:creator>Rob Sargent</dc:creator>
    <dc:date>2012-05-22T21:09:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34200">
    <title>Re: Is it possible to load &amp; use a font at runtime?</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34200</link>
    <description>&lt;pre&gt;Thanks Pascal. I need to keep the system running (FOP will be
embedded), and the font will be chosen/added by the user, so it looks
like I'll have to create a new config in memory and load it for each
request. Would it be worth forking a thread for each "run" of FOP and
loading the config/fonts locally to that thread? The docs say that FOP
may not be completely thread safe... are there any techniques I can
follow to reduce issues?

&lt;/pre&gt;</description>
    <dc:creator>Phillip B Oldham</dc:creator>
    <dc:date>2012-05-22T20:26:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34199">
    <title>Re: writing-mode="rl" and start sidebar = "left" and end sidebar = "right"</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34199</link>
    <description>&lt;pre&gt;First, the specification of writing-mode on fo:region-* elements has no
affect, unless use is made of the from-page-master-region() property value
function [1]. However, this property value function is not yet supported in
FOP. Work is underway to support it, but has not been committed yet. See
[2] for tracking.

Second, there is a bug in that writing-mode on fo:simple-page-master is not
being used to determine the layout of region viewport/reference pairs
within the page. See [3] for tracking.

[1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#d0e5961
[2] https://issues.apache.org/bugzilla/show_bug.cgi?id=53128
[3] https://issues.apache.org/bugzilla/show_bug.cgi?id=53276

You may wish to add yourself to the Cc list on these bugs to receive
notifications of fixes.

On Tue, May 22, 2012 at 10:54 AM, Jonathan Levinson &amp;lt;
Jonathan.Levinson&amp;lt; at &amp;gt;intersystems.com&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Glenn Adams</dc:creator>
    <dc:date>2012-05-22T17:37:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34198">
    <title>writing-mode="rl" and start sidebar = "left" and end sidebar = "right"</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34198</link>
    <description>&lt;pre&gt;Hi,

A colleague of mine claims that the start region should be "right" in the attached PDF file generated from the attached fo.

Is she correct (and there is a bug in FOP) or is there a misunderstanding?

Thanks,
Jonathan


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe&amp;lt; at &amp;gt;xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help&amp;lt; at &amp;gt;xmlgraphics.apache.org&lt;/pre&gt;</description>
    <dc:creator>Jonathan Levinson</dc:creator>
    <dc:date>2012-05-22T16:54:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34197">
    <title>Re: Is it possible to load &amp; use a font at runtime?</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34197</link>
    <description>&lt;pre&gt;Hi,

FOP Fonts do not need to be installed on your system.
You just need to pass fonts location to FOP.

1/ register all used font files in configuration file (see [1], more 
precisely "register a particular font")

2/ depending on how you use fop (either command line or embedded in your 
app), provide your config file to FOP (see [2] or [3])

note that the &amp;lt;font-base&amp;gt; configuration option can be very usefull here, 
either directly set in config file, or using the 
fopFactory.setFontBaseURL() method (see [4]).


[1] http://xmlgraphics.apache.org/fop/1.0/fonts.html#register
[2] 
http://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available
[3] http://xmlgraphics.apache.org/fop/1.0/embedding.html#config-external
[4] http://xmlgraphics.apache.org/fop/1.0/embedding.html#fop-factory

Le 22/05/2012 13:28, Phillip B Oldham a écrit :

&lt;/pre&gt;</description>
    <dc:creator>Pascal Sancho</dc:creator>
    <dc:date>2012-05-22T15:16:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34196">
    <title>Is it possible to load &amp; use a font at runtime?</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34196</link>
    <description>&lt;pre&gt;Is it possible to start an app which uses the FOP jar and, at runtime,
load and use a font rather than "installing" it before running the
app? I'm developing an library for our team to use which will load an
FO file, any image assets and (hopefully) any fonts needed to render a
PDF. I've got everything working except the fonts, where I've hit a
bit of a wall. Is it possible?

&lt;/pre&gt;</description>
    <dc:creator>Phillip B Oldham</dc:creator>
    <dc:date>2012-05-22T11:28:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34195">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34195</link>
    <description>&lt;pre&gt;


there have been a few additions for XSL-FO compliance; the table will be
fully updated before a release;



do you have any specific features you're interested in?
&lt;/pre&gt;</description>
    <dc:creator>Glenn Adams</dc:creator>
    <dc:date>2012-05-22T00:49:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34194">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34194</link>
    <description>&lt;pre&gt;
Yay!


Do "bug fixes" include improvements to XSL-FO compliance?  I don't see 
any change between the 1.0 and development columns in this table:

https://xmlgraphics.apache.org/fop/compliance.html

Is that table out of date, or is 1.1 going to implement no more of the 
spec than 1.0 does?
&lt;/pre&gt;</description>
    <dc:creator>Warren Young</dc:creator>
    <dc:date>2012-05-21T21:05:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34193">
    <title>Re: Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34193</link>
    <description>&lt;pre&gt;I'm sure others will like to respond as well, but I can provide some
information based on my observations as a contributor and committer on the
FOP project:

(1) a new revision, FOP 1.1, is being prepared for release, which will
contain, in addition to bug fixes:

   - support for complex scripts, including bidirectional scripts (arabic,
   hebrew), indic scripts (devanagari, tamil, etc.), and southeast asian
   scripts (thai, etc)
   - support for font specific advanced typographic features with
   non-complex scripts, specifically, those enabled by opentype advanced
   typographic tables
   - improved support for PDF rendering, including
      - CMYK color encoding
      - spot color
      - bitmap conversion mode
      - 128-bit encryption
      - object streams
      - improved accessibility support

(2) Following a FOP 1.1 release, I anticipate other improvements as we move
forward, including:

   - support for vertical writing modes
   - improved support for CJK language handling
   - support for CFF e&lt;/pre&gt;</description>
    <dc:creator>Glenn Adams</dc:creator>
    <dc:date>2012-05-21T14:04:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34192">
    <title>Information about Apache FOP</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34192</link>
    <description>&lt;pre&gt;Hi!

My name is Markus Eriksson and I am working on a Swedish company called Zert
AB.

Im contacting you on behalf of Zert ABs customers who are using your
product, Apache FOP

We are about to have a gathering for all our customers to talk about the
future, so Im wondering if you have something to say about your products
future.

Some new updates, features or what is happening with this product?

 

Best Regards
Markus Eriksson 


  _____  


Zert - logo


markus.eriksson&amp;lt; at &amp;gt;zert.se

Direkt:    +46 (0)950 346 60      


Zert AB

Växel:     +46 (0)950 132 30      



 

 

&lt;/pre&gt;</description>
    <dc:creator>Markus Eriksson</dc:creator>
    <dc:date>2012-05-21T06:25:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34191">
    <title>Re: external-graphic image path with antislash</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34191</link>
    <description>&lt;pre&gt;Thank Glenn.

 

Christian Pestel

christian.pestel&amp;lt; at &amp;gt;orange.fr


From: Glenn Adams 
Sent: Thursday, May 17, 2012 1:19 AM
To: fop-users&amp;lt; at &amp;gt;xmlgraphics.apache.org 
Subject: Re: external-graphic image path with antislash

since use of backslash is invalid in a URL as a path separator, it would be an improvement (in validation) rather than a regression


On Wed, May 16, 2012 at 4:07 PM, Christian Pestel &amp;lt;christian.pestel&amp;lt; at &amp;gt;orange.fr&amp;gt; wrote:

  Hello developpers,

  We use hugely Fop 1.0 in our software.
  We have noticed that the image URI path &amp;lt;fo:external-graphic src=”file:///C:\Temp\ImageGIF.gif” /&amp;gt; don’t generate an error with fop 1.0, but with Fop 1.1dev, this URI generate this error : : org.apache.fop.fo.expr.PropertyException: Invalid URI specified

  &amp;lt;fo:external-graphic src=”file:///C:/Temp/ImageGIF.gif” /&amp;gt; work fine with Fop 1.1

  Is URI validation has become more strict or is it a regression ?
  Thanks.
  Christian Pestel



  ---------------------------------------------------------------------
&lt;/pre&gt;</description>
    <dc:creator>Christian Pestel</dc:creator>
    <dc:date>2012-05-19T08:52:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34190">
    <title>Re: getting error when use -print</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34190</link>
    <description>&lt;pre&gt;
actually i installed bullzip free pdf printer as default printer.
when i give the command
fop xslfo.fo -print 1 
it will send to bullzip pdf printer it gives the output in pdf format,but
when i change my default 
printer to epson fx-2175 it prints an empty page but in bullzip pdf printer
it shows the matter..
any reply


lmpmbernardo wrote:

&lt;/pre&gt;</description>
    <dc:creator>pr4321</dc:creator>
    <dc:date>2012-05-18T05:18:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/34189">
    <title>Re: getting error when use -print</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/34189</link>
    <description>&lt;pre&gt;
thanks you its working

lmpmbernardo wrote:

&lt;/pre&gt;</description>
    <dc:creator>pr4321</dc:creator>
    <dc:date>2012-05-17T16:27:29</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.xml.fop.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.xml.fop.user</link>
  </textinput>
</rdf:RDF>

