Sam Fuqua a écrit :
Hi Andreas,
I'm quite sure that it has an embedded resolution of 72dpi. I opened
it in GIMP, and that was the resolution that I was given.
If it does turn out to be different, then I will either resize it or
try to find another way of embedding the image
Thanks
Sam
On
Hi
I did increase my heapspace to a 512mb like so in the fop bash file:
fop_exec_command=exec \$JAVACMD\ -Xmx512m $LOGCHOICE $LOGLEVEL -classpath
\$LOCALCLASSPATH\ $FOP_OPTS org.apache.fop.cli.Main $fop_exec_args
Secondly:
java version 1.6.0_13
Java(TM) SE Runtime Environment (build
Thank you everyone for your help. I was able to increase the resolution
with FopFactory.setSourceResolution() to get it to the proper size.
Sam
On Wed, Jun 24, 2009 at 3:18 AM, Pascal SANCHO pascal.san...@takoma.frwrote:
Sam Fuqua a écrit :
Hi Andreas,
I'm quite sure that it has an
On 24 Jun 2009, at 13:11, Johan Pretorius wrote:
Hi
I did increase my heapspace to a 512mb like so in the fop bash file:
fop_exec_command=exec \$JAVACMD\ -Xmx512m $LOGCHOICE $LOGLEVEL -
classpath
\$LOCALCLASSPATH\ $FOP_OPTS org.apache.fop.cli.Main $fop_exec_args
Secondly:
java version
Hi Andreas,
Still another thing: the same table of contents that showed the earlier
reported errors still showed on error: When running the fo-file from my
application, the fo:page-number-citation element was left aligned, although the
fo (snippet below) clearly said text-align=right. I ran
On 24 Jun 2009, at 15:34, Georg Datterl wrote:
Hi Georg
snip /
Maybe that's helpfull.
Definitely! I just looked at the code for
org.apache.fop.area.inline.UnresolvedPageNumber, and the issue is that
those areas are serializable, but the Font instance member is
explicitly declared as
Hi Andreas,
Thanks for the help. Since I am rebuilding fop.jar anyway, wouldn't it work if
I just declare the font member not-transient?
Regards,
Georg Datterl
-- Kontakt --
Georg Datterl
Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg
HRB Nürnberg: 17193
Hi Andreas,
Pity. But proves again: For every problem there's a simple, obvious and wrong
solution.
Mit freundlichen Grüßen
Georg Datterl
-- Kontakt --
Georg Datterl
Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg
HRB Nürnberg: 17193
Geschäftsführer:
On 24 Jun 2009, at 17:23, Georg Datterl wrote:
Pity. But proves again: For every problem there's a simple, obvious
and wrong solution.
:-)
I think the real solution would be to store the referenced FontTriplet
in the UnresolvedPageNumber, instead of the Font instance.
FontTriplets are
Hi Andreas,
[BTW (slightly off-topic for this particular thread): I'm
wondering whether we do not need /all/ applicable font-
families. After all, page- numbers can be formatted, so
the eventual font would have to have all the necessary
glyphs. Right now, one single Font instance is
Andreas,
I took your advice and have gotten some error output. It doesn't print this
every time, but it has printed for every font I have installed something to
the effect of Failed to load font file ___ . Could not load InputStream.
If it could find the files itself, then I know that it wasn't
On 24 Jun 2009, at 18:15, Georg Datterl wrote:
[Me: ]
[BTW (slightly off-topic for this particular thread): I'm
wondering whether we do not need /all/ applicable font-
families. After all, page- numbers can be formatted, so
the eventual font would have to have all the necessary
glyphs. Right
On 24 Jun 2009, at 19:19, Sam Fuqua wrote:
Hi Sam
I took your advice and have gotten some error output. It doesn't
print this every time, but it has printed for every font I have
installed something to the effect of Failed to load font file
___ . Could not load InputStream. If it
13 matches
Mail list logo
