Nabble - FOP - Users

Re: Trying to programmatically add fonts

2008-09-05T19:13:05Z

Alias John Brown wrote:

According to the documentation at
http://xmlgraphics.apache.org/fop/0.95/fonts.html#basics

"It is currently not possible to easily configure fonts from Java code."

I assume that this means that it is not impossible, but I have no idea
how. Hopefully an expert will turn up soon.

John,

Thanks for the reply. I have also tried specifying the config file using the method in the docs. Here is what I tried:

DefaultConfigurationBuilder cfgBuilder = new DefaultConfigurationBuilder();
Configuration cfg = cfgBuilder.buildFromFile(new File(baseDir, "Local\\personal\\durkan\\projects\\fop\\new-font.conf.xml"));
fopFactory.setUserConfig(cfg);

This gives me the same result. The fonts are not available. So, I am probably doing something wrong.

Thanks,
Eric

Re: Trying to programmatically add fonts

2008-09-05T14:42:35Z

eborisow <eborisow <at> yahoo.com> writes:

>
>
> Hi,
>
> I am trying to embed fonts in a program. I was able to get my fonts to work
> when I run fop.bat standalone. Here were the relevant lines from the config
> xml.
>

<snip>
Contents of config file
</snip>

> Like I said, this one works. Now, in an application, I am trying to do the
> same using the API.
>
<snip>
Code to do above programatically
</snip>

<snip>
Contents of log
</snip>

> So, I am obviously doing something wrong. Can someone see what the problem
> is?

According to the documentation at
http://xmlgraphics.apache.org/fop/0.95/fonts.html#basics

"It is currently not possible to easily configure fonts from Java code."

I assume that this means that it is not impossible, but I have no idea
how. Hopefully an expert will turn up soon.

>
> Thanks,
> Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

NPE when rendering fo:block-container inside fo:inline

2008-09-05T10:09:48Z

Hello,

I am using the Antenna House XSL stylesheets to convert XHTML to
XML-FO. This works very well in most cases. However, I have come
across a problem where a fo:block-container inside a fo:inline will
cause an NPE.

An example FO file that exhibits this problem is attached. The stack
trace is also attached. If you remove the fo:inline that encloses the
fo:block-container, then everything works fine.

I'm wondering, is it even legal to have fo:block-container inside a
fo:inline? If it is legal, any chance that this problem has been fixed
in 0.95?

Thank you for any insights.

- Frank

[test-minimal.fo]

<?xml version="1.0" encoding="UTF-8"?> <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:html="http://www.w3.org/1999/xhtml" writing-mode="lr-tb" hyphenate="false" text-align="start" role="html:html"> <fo:layout-master-set> <fo:simple-page-master page-width="auto" page-height="auto" master-name="all-pages"> <fo:region-body column-gap="12pt" column-count="1" margin-left="0.5in" margin-bottom="0.75in" margin-right="0.5in" margin-top="0.75in"/> </fo:simple-page-master> </fo:layout-master-set> <fo:page-sequence master-reference="all-pages"> <fo:flow flow-name="xsl-region-body"> <fo:block> <fo:inline> <fo:block-container width="550px" border="1px solid gray" color="#FF2525" padding="10px" text-align="left" vertical-align="top"> <fo:block end-indent="0pt" start-indent="0pt">Test</fo:block> </fo:block-container> </fo:inline> </fo:block> </fo:flow> </fo:page-sequence> </fo:root>

5-Sep-2008 10:07:34 AM org.apache.fop.cli.Main startFOP
SEVERE: Exception
java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:166)
at org.apache.fop.cli.Main.main(Main.java:197)

---------

java.lang.NullPointerException
at org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(BlockContainerLayoutManager.java:200)
at org.apache.fop.layoutmgr.inline.InlineLayoutManager.getNextKnuthElements(InlineLayoutManager.java:303)
at org.apache.fop.layoutmgr.inline.LineLayoutManager.collectInlineKnuthElements(LineLayoutManager.java:654)
at org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:590)
at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:284)
at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:106)
at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:145)
at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:551)
at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:137)
at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:301)
at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:263)
at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:144)
at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:233)
at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:145)
at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:378)
at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:194)
at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484)
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:165)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:166)
at org.apache.fop.cli.Main.main(Main.java:197)

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

RE: FOP 0.94 : How to increase heap size

2008-09-05T09:51:41Z

There's a line in fop.bat that sets the variable JAVAOPTS; if you modify
that line and put quotes around references to that variable in the rest
of the file, it should work.

Eric Amick
Legislative Computer Systems
Office of the Clerk

-----Original Message-----
From: Newkid [mailto:shyamfrnd@...]
Sent: Friday, September 5, 2008 6:15
To: fop-users@...
Subject: RE: FOP 0.94 : How to increase heap size

Hello Eric,

Thanks for URL.

I need to know how one can modify the FOP.BAT file. Is there any options
thru which I can reset the heap size in FOP.BAT file.

With Thanks!
Newkid

Amick, Eric wrote:

>
> http://xmlgraphics.apache.org/fop/0.94/running.html#memory
>
>
> Eric Amick
> Legislative Computer Systems
> Office of the Clerk
>
> -----Original Message-----
> From: Newkid [mailto:shyamfrnd@...]
> Sent: Thursday, September 4, 2008 10:25
> To: fop-users@...
> Subject: FOP 0.94 : How to increase heap size
>
>
> Hi there!
>
> Could you please assist me how can I increase JVM heap size?
>
> Please let me know what I have to modify in FOP.BAT file so that it
> can take automatically whenever I run FOP from command prompt.
>
> When I am trying to convert XML to PDF using FOP, it's showing
> java.lang:OutofMemory Java heap space error.
>
> Would appreciate your prompt response!
>
> With Thanks!
> Newkid
> --
> View this message in context:
> http://www.nabble.com/FOP-0.94-%3A-How-to-increase-heap-size-tp1930929
> 0p
> 19309290.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@...
> For additional commands, e-mail: fop-users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@...
> For additional commands, e-mail: fop-users-help@...
>
>
>

--
View this message in context:
http://www.nabble.com/FOP-0.94-%3A-How-to-increase-heap-size-tp19309290p
19328398.html
Sent from the FOP - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Trying to programmatically add fonts

2008-09-05T09:19:23Z

Hi,

I am trying to embed fonts in a program. I was able to get my fonts to work when I run fop.bat standalone. Here were the relevant lines from the config xml.

<font-base>file:///C:/programs/apache/fop-0.94-bin-jdk1.3/fonts/</font-base>


<fonts>

<font-triplet name="Verdana" style="normal" weight="normal"/>

<font-triplet name="Verdana" style="normal" weight="bold"/>

<font-triplet name="Verdana" style="italic" weight="bold"/>

</fonts>

Like I said, this one works. Now, in an application, I am trying to do the same using the API.

// Set the Font Base URL
fopFactory.setFontBaseURL("file:///C:/programs/apache/fop-0.94-bin-jdk1.3/fonts/");

String font1 = "verdana.xml";
String font1Url = "verdana.ttf";

String font2 = "verdanab.xml";
String font2Url = "verdanab.ttf";

String font3 = "verdanaz.xml";
String font3Url = "verdanaz.ttf";

FontTriplet fontTriplet1 = new FontTriplet("Verdana", Font.STYLE_NORMAL, Font.WEIGHT_NORMAL);
FontTriplet fontTriplet2 = new FontTriplet("Verdana", Font.STYLE_NORMAL, Font.WEIGHT_BOLD);
FontTriplet fontTriplet3 = new FontTriplet("Verdana", Font.STYLE_ITALIC, Font.WEIGHT_BOLD);

List fontTriplets1 = new ArrayList();
fontTriplets1.add(fontTriplet1);

List fontTriplets2 = new ArrayList();
fontTriplets2.add(fontTriplet2);

List fontTriplets3 = new ArrayList();
fontTriplets3.add(fontTriplet3);

EmbedFontInfo verdanaFontInfo = new EmbedFontInfo(font1, true, fontTriplets1, font1Url);
EmbedFontInfo verdanaBoldFontInfo = new EmbedFontInfo(font2, true, fontTriplets2, font2Url);
EmbedFontInfo verdanaBoldItalicFontInfo = new EmbedFontInfo(font3, true, fontTriplets3, font3Url);
FontCache fontCache = fopFactory.getFontCache();
fontCache.addFont(verdanaFontInfo);
fontCache.addFont(verdanaBoldFontInfo);
fontCache.addFont(verdanaBoldItalicFontInfo);
fontCache.save();

I test the cache using the following:

log.debug("Contains verdana font: " + fontCache.containsFont(verdanaFontInfo));
log.debug("Verdana font info is: " + fontCache.getFont("verdana.ttf").toString());

log.debug("Contains verdana-bold font: " + fontCache.containsFont(verdanaBoldFontInfo));
log.debug("Verdana-bold font info is: " + fontCache.getFont("verdanab.ttf").toString());

log.debug("Contains verdana-bold-italic font: " + fontCache.containsFont(verdanaBoldItalicFontInfo));
log.debug("Verdana-bold-italic font info is: " + fontCache.getFont("verdanaz.ttf").toString());

In the log, I get the following:

2008-09-05 12:05:12,014 [main] DEBUG embedding.ExampleXML2PDF(ExampleXML2PDF.java:153) - Contains verdana font: true
2008-09-05 12:05:12,014 [main] DEBUG embedding.ExampleXML2PDF(ExampleXML2PDF.java:154) - Verdana font info is: metrics-url=verdana.xml,embed-url=verdana.ttf, kerning=true, font-triplet=[Verdana,normal,400], lastModified=-1
2008-09-05 12:05:12,014 [main] DEBUG embedding.ExampleXML2PDF(ExampleXML2PDF.java:156) - Contains verdana-bold font: true
2008-09-05 12:05:12,014 [main] DEBUG embedding.ExampleXML2PDF(ExampleXML2PDF.java:157) - Verdana-bold font info is: metrics-url=verdanab.xml,embed-url=verdanab.ttf, kerning=true, font-triplet=[Verdana,normal,700], lastModified=-1
2008-09-05 12:05:12,014 [main] DEBUG embedding.ExampleXML2PDF(ExampleXML2PDF.java:159) - Contains verdana-bold-italic font: true
2008-09-05 12:05:12,014 [main] DEBUG embedding.ExampleXML2PDF(ExampleXML2PDF.java:160) - Verdana-bold-italic font info is: metrics-url=verdanaz.xml,embed-url=verdanaz.ttf, kerning=true, font-triplet=[Verdana,italic,700], lastModified=-1

However, when it actually tries to convert the XML to PDF, I see the following message in the log:

2008-09-05 12:05:26,905 [main] DEBUG org.apache.fop.fonts.FontInfo(FontInfo.java:134) - Font lookup: Verdana normal 400
2008-09-05 12:05:26,905 [main] WARN org.apache.fop.fonts.FontInfo(FontInfo.java:263) - Font 'Verdana,normal,400' not found. Substituting with 'any,normal,400'.

So, I am obviously doing something wrong. Can someone see what the problem is?

Thanks,
Eric

RE: FOP 0.94 : How to increase heap size

2008-09-05T03:15:01Z

Hello Eric,

Thanks for URL.

I need to know how one can modify the FOP.BAT file. Is there any options thru which I can reset the heap size in FOP.BAT file.

With Thanks!
Newkid

Amick, Eric wrote:

http://xmlgraphics.apache.org/fop/0.94/running.html#memory

Eric Amick
Legislative Computer Systems
Office of the Clerk

-----Original Message-----
From: Newkid [mailto:shyamfrnd@yahoo.com]
Sent: Thursday, September 4, 2008 10:25
To: fop-users@xmlgraphics.apache.org
Subject: FOP 0.94 : How to increase heap size

Hi there!

Could you please assist me how can I increase JVM heap size?

Please let me know what I have to modify in FOP.BAT file so that it can
take automatically whenever I run FOP from command prompt.

When I am trying to convert XML to PDF using FOP, it's showing
java.lang:OutofMemory Java heap space error.

Would appreciate your prompt response!

With Thanks!
Newkid
--
View this message in context:
http://www.nabble.com/FOP-0.94-%3A-How-to-increase-heap-size-tp19309290p
19309290.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

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

Re: Error when using XSL with French Characters

2008-09-04T10:14:42Z

On Sep 4, 2008, at 12:06, Vincent Hennebert wrote:

> <snip />
> No, US-ASCII is a 7-bit character set, which means it can contain only
> 128 characters, none of them being an accented letter [1].

Ouch! Indeed. I'm so used to the basic 7-bit set being extended...
To think that I even tried it over here in an editor. If I had only
also tried to actually save the file, I would have noticed...

Sorry for the confusion, Jeff.

The conclusion is definitely the right one: if you can somehow manage
to have the BASIC code write the file as UTF-8, all the encoding
hassles disappear.

Cheers

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

error creating ttf metrics

2008-09-04T09:13:59Z

ciao,

ttf reader give an error with a barmeno font...
with all other fonts it works fine...
the same ttf file works with TTFReader for fop 0.20.5
any idea? here the debug info...

TTF Reader for Apache FOP 0.95

Parsing font...
Reading Barmeno-Bold.ttf...
sfnt version: OpenType 1.0
Reading 14 dir tables
dir tables: [loca, post, glyf, fpgm, kern, hmtx, hhea, prep, cvt , OS/2,
cmap, name, head, maxp]
unit per em: 1000
Number of glyphs in font: 399
hhea.Ascender: 865 865
hhea.Descender: -250 -250
Number of horizontal metrics: 399
PostScript format: 0x20000
PostScript format 2
Reading 396 glyphnames, that are not in the standard Macintosh set.
Total number of glyphs=399
sTypoAscender: 776 776
sTypoDescender: -243 -243
sTypoLineGap: 150
usWinAscent: 953 953
usWinDescent: 250 250
Error while building XML font metrics file.
java.io.EOFException: Reached EOF, file size=88952 offset=88958
at
org.apache.fop.fonts.truetype.FontFileReader.seekSet(FontFileReader.java:86)
at
org.apache.fop.fonts.truetype.FontFileReader.seekAdd(FontFileReader.java:99)
at
org.apache.fop.fonts.truetype.FontFileReader.skip(FontFileReader.java:109)
at org.apache.fop.fonts.truetype.TTFFile.readOS2(TTFFile.java:1016)
at org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:495)
at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209)
at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164)

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

RE: FOP 0.94 : How to increase heap size

2008-09-04T07:30:20Z

http://xmlgraphics.apache.org/fop/0.94/running.html#memory

Eric Amick
Legislative Computer Systems
Office of the Clerk

-----Original Message-----
From: Newkid [mailto:shyamfrnd@...]
Sent: Thursday, September 4, 2008 10:25
To: fop-users@...
Subject: FOP 0.94 : How to increase heap size

Hi there!

Could you please assist me how can I increase JVM heap size?

Please let me know what I have to modify in FOP.BAT file so that it can
take automatically whenever I run FOP from command prompt.

When I am trying to convert XML to PDF using FOP, it's showing
java.lang:OutofMemory Java heap space error.

Would appreciate your prompt response!

With Thanks!
Newkid
--
View this message in context:
http://www.nabble.com/FOP-0.94-%3A-How-to-increase-heap-size-tp19309290p
19309290.html
Sent from the FOP - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

FOP 0.94 : How to increase heap size

2008-09-04T07:24:36Z

Hi there!

Could you please assist me how can I increase JVM heap size?

Please let me know what I have to modify in FOP.BAT file so that it can take automatically whenever I run FOP from command prompt.

When I am trying to convert XML to PDF using FOP, it's showing java.lang:OutofMemory Java heap space error.

Would appreciate your prompt response!

With Thanks!
Newkid

Re: Error when using XSL with French Characters

2008-09-04T03:06:04Z

Hi,

Andreas Delmelle wrote:

> On Sep 3, 2008, at 18:35, Steffanina, Jeff wrote:
>
> Hi Jeff
>
>> There is always one MORE option to consider!!
>>
>> What would you suggest as the best way to handle this?
>
> I think I'd opt for using (N)umeric (C)haracter (R)eferences. Reasoning
> would be that if one changes the BASIC code to emit the sequence
> 'è', this will never, ever have to be changed (unless Unicode would
> somehow decide on altering the codepoints). You can change the encoding
> in the XML header all you want, NCRs will always work.
>
> On the other hand, if you have a LOT of those characters, using NCRs
> could make your XML a bit bulky (instead of 1 byte/character, you

Not mentioning the fact that this would make the document really tedious
to type, and not very readable...

> actually generate 6-8 bytes to represent one character in the final
> result; the XML parser, instead of needing only one byte, has to parse
> all bytes from '&' up to and including ';').
> The character code you mentioned earlier (130) is the decimal value for
> 'é' in ASCII, so if you're concerned with the size of the XML and do not
> want to generate 6 bytes for one character, try specifying "US-ASCII" as
> encoding for the source XML.

No, US-ASCII is a 7-bit character set, which means it can contain only
128 characters, none of them being an accented letter [1].

From your other message it looks like the default character set on your
system is ISO-8859-15, which is ok for all of the western languages plus
a few more [2]. Your BASIC program probably uses that character set, in
which case you just have to change the header of your xml file:
<?xml version="1.0" encoding="ISO-8859-15"?>

As long as you put the right header in the XML file you can live with
that setup. However, it is safer to switch to UTF-8 now, in order to
avoid troubles in the future. Indeed, it’s probable that when you change
your computer or upgrade your system the default character set will
become UTF-8. Then if you re-edit that file on the new system, accented
letters will be entered as UTF-8 sequences that are incompatible with
ISO-8859-15, and you’ll basically see garbage in the result. Unless your
editor is elaborate enough to recognize that the file is xml, and parses
the header to get its encoding. But I doubt many editors do that...

You can choose to convert your files to UTF-8 later on, but that might
represent a lot of work, plus you will have to edit every file to change
the xml header to UTF-8. Since the use of UTF-8 as the default charset
will happen sooner or later, you better do that now, when you don’t have
too many files.

Changing the default character set is very system-dependent. Basically
you have to play with the LOCALE variable. You can (may) get a list of
available locales by typing the following command in a terminal:
$ locale -a
C
en_US.iso885915
en_US.utf8
...

If no UTF-8 locale is available it must be generated. Try to find
documentation for your system or ask the system administrator if
applicable...

You find that complicated? It is, it has always been, and I’m afraid it
may forever be. This is historical...

[1] http://en.wikipedia.org/wiki/Ascii
[2] http://en.wikipedia.org/wiki/ISO/IEC_8859-15

HTH,
Vincent

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

File size when including SVGs

2008-09-03T12:00:10Z

Hi all,

I'm currently using FOP 0.93, and I've just started looking at
using SVG images in the rendered PDFs. One thing that I have
noticed is that the image size of the resulting PDF grows
considerably.

It would appear that if I import an SVG multiple times, the
resulting PDF includes a new instance of the image. If I have
a 20k SVG displayed in the header of a 20 page document, then
it adds 400k to the PDF (before compression). Is this correct?

If so, is there a way around it? My plan is to use a small
number of SVGs a large number of times, so being able to embed
an image once, and simply reference it each time it is used in
the PDF would greatly reduce space.

If this isn't the case, then I obviously need to try and
figure out why my PDFs seem to grow considerably if I
repeat the same image.

I'm mostly importing SVGs as background images, but some are
inserted with <fop:external-graphic>

Thanks.

--
Be seeing you, http://www.glendale.org.uk
Sam. Mail/IM (Jabber): sam@...

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Re: Referenced pattern not applied when PDF is encrypted

2008-09-03T10:17:04Z

On Sep 3, 2008, at 14:02, Lea Thurman wrote:

Hi

> We am more than happy to spend time on this and hopefully fix and
> submit it
> back. However having never filed a defect or committed to FOP
> before is
> there are starter for 10 that tells me about servers/repositories/
> locations
> etc and the general process to be followed.

If you mean you potentially will do some development on the FOP
codebase, and want to donate it back, then the main 'Development'
page would be a good place to start:
http://xmlgraphics.apache.org/fop/dev/index.html

If OTOH, you simply want to log the issue, supply more info (and
preferably some FO/SVG samples as well), then this is where you need
to be:
http://xmlgraphics.apache.org/fop/bugs.html

Cheers

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Re: Error when using XSL with French Characters

2008-09-03T10:04:40Z

On Sep 3, 2008, at 18:35, Steffanina, Jeff wrote:

Hi Jeff

> There is always one MORE option to consider!!
>
> What would you suggest as the best way to handle this?

I think I'd opt for using (N)umeric (C)haracter (R)eferences.
Reasoning would be that if one changes the BASIC code to emit the
sequence 'è', this will never, ever have to be changed (unless
Unicode would somehow decide on altering the codepoints). You can
change the encoding in the XML header all you want, NCRs will always
work.

On the other hand, if you have a LOT of those characters, using NCRs
could make your XML a bit bulky (instead of 1 byte/character, you
actually generate 6-8 bytes to represent one character in the final
result; the XML parser, instead of needing only one byte, has to
parse all bytes from '&' up to and including ';').
The character code you mentioned earlier (130) is the decimal value
for 'é' in ASCII, so if you're concerned with the size of the XML and
do not want to generate 6 bytes for one character, try specifying "US-
ASCII" as encoding for the source XML.

HTH!

Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Re: Problem with inserting a PNG file

2008-09-03T09:38:02Z

On 8/28/2008 9:34 AM, Jubal Kessler wrote:

> Aug 28, 2008 6:20:05 AM org.apache.fop.fo.flow.ExternalGraphic bind
> SEVERE: Image not available: No ImagePreloader found for

As closure, it turns out I had been staring too long at the same XSL-FO
template, and the problem was a simple error in external-graphics usage.

My apologies to all, and thanks for the replies.

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

RE: Error when using XSL with French Characters

2008-09-03T09:35:56Z

There is always one MORE option to consider!!

What would you suggest as the best way to handle this?

Jeff

-----Original Message-----
From: Andreas Delmelle [mailto:andreas.delmelle@...]
Sent: Wednesday, September 03, 2008 12:32 PM
To: fop-users@...
Subject: Re: Error when using XSL with French Characters

On Sep 3, 2008, at 15:05, Steffanina, Jeff wrote:

Hi Jeff

> fop-0.95
> I am running Redhat Linux 2.4.21-47.0.1.
>
> The letter I am referring to is: é è
> I assume I am having problems with any French character that
> includes a glyph.
>
> What are you using for <?xml version="1.0" encoding="XXXXXXXX"?>
>
> I appreciate any suggestions. I have not had to deal with
> international characters sets before.

If all else fails, remember that XML *always* allows Numeric
Character References, like or for a linefeed (values are
always UTF-8 codepoints).

In UTF-8, the respective character codes are:

è -> è
é -> é

If you output those sequences in the BASIC module, then it should
work, regardless of which encoding is specified in the XML header.

HTH!

Cheers

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Re: Error when using XSL with French Characters

2008-09-03T09:32:01Z

On Sep 3, 2008, at 15:05, Steffanina, Jeff wrote:

Hi Jeff

RE: Error when using XSL with French Characters

2008-09-03T06:08:41Z

Jean-Francois,
On my Linux box I have this entry in: /etc/sysconfig/i18n

LANG="en_US.iso885915"

Jeff Steffanina
FOSSE Development, Bethesda, MD
(301)380-2047
jeff.steffanina@...

This communication contains information from Marriott International, Inc. that may be confidential. Except for personal use by the intended recipient, or as expressly authorized by the sender, any person who receives this information is prohibited from disclosing, copying, distributing, and/or using it. If you have received this communication in error, please immediately delete it and all copies, and promptly notify the sender. Nothing in this communication is intended as an electronic signature under applicable law.

-----Original Message-----
From: Jean-François El Fouly [mailto:jean-francois@...]
Sent: Wednesday, September 03, 2008 8:58 AM
To: fop-users@...
Subject: Re: Error when using XSL with French Characters

There are four kinds of accent current in French (é è ê ë) so you should
be more precise.
None of them can possibly correspond to CHR(130) neither in UTF-8 nor in
ISO-8859-1
On what kind of system/platform/OS are you working ?
Mentioning vi makes me guess it should be some kind of Unix but at the
same time the encoding used makes this improbable...
I guess more information is needed here.

Steffanina, Jeff a écrit :

> Manuel,
>
> We create the XML using a version of BASIC. To create this particular
> character, we send CHR(130) to the XML. When I open the XML in "vi",
> I see the proper FRENCH symbol.
>
>
>
> */Jeff /*
>
> ------------------------------------------------------------------------
> *From:* Manuel Mall [mailto:mm@...]
> *Sent:* Tuesday, September 02, 2008 10:51 PM
> *To:* 'fop-users@...'
> *Subject:* RE: Error when using XSL with French Characters
>
> I am suspicious that although you declare the XML file as being in
> UTF-8 it actually isn't. How do you produce the XML file?
>
>
>
> Manuel
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Steffanina, Jeff [mailto:Jeff.Steffanina@...]
> *Sent:* Wednesday, 3 September 2008 10:23 AM
> *To:* fop-users@...
> *Subject:* Error when using XSL with French Characters
>
>
>
>
>
> My Friends,
> Fop-0.95 My style sheet has been working perfectly. However,
> the user submitted some text in French. In the text was a letter
> "e" with an accent above it.
>
> That character caused the following error:
> Invalid byte 1 of 1-byte UTF-8 sequence.
>
> My .xml looks fine. The "e" with the accent above it is perfect.
> First line in my XML:
> <?xml version="1.0" encoding="UTF-8"?>
>
> Here is the first line of my XSL:
> <?xml version="1.0" encoding="UTF-8"?>
>
> I am confused over why the UTF-8 for the XML understands the
> character but the UTF-8 in the XSL does not?
>
> I found an article that suggests that the problem would be solved
> with:
> <?xml version="1.0" encoding="8859-1"?>
>
> Would this be a viable/recommended solution? Do you have a
> better idea?
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

RE: Error when using XSL with French Characters

2008-09-03T06:05:35Z

Jean-Francois,

fop-0.95
I am running Redhat Linux 2.4.21-47.0.1.

The letter I am referring to is: é è
I assume I am having problems with any French character that includes a glyph.

What are you using for <?xml version="1.0" encoding="XXXXXXXX"?>

I appreciate any suggestions. I have not had to deal with international characters sets before.

Thanks.

Jeff

-----Original Message-----
From: Jean-François El Fouly [mailto:jean-francois@...]
Sent: Wednesday, September 03, 2008 8:58 AM
To: fop-users@...
Subject: Re: Error when using XSL with French Characters

There are four kinds of accent current in French (é è ê ë) so you should
be more precise.
None of them can possibly correspond to CHR(130) neither in UTF-8 nor in
ISO-8859-1
On what kind of system/platform/OS are you working ?
Mentioning vi makes me guess it should be some kind of Unix but at the
same time the encoding used makes this improbable...
I guess more information is needed here.

Steffanina, Jeff a écrit :

Re: Error when using XSL with French Characters

2008-09-03T05:57:37Z

There are four kinds of accent current in French (é è ê ë) so you should
be more precise.
None of them can possibly correspond to CHR(130) neither in UTF-8 nor in
ISO-8859-1
On what kind of system/platform/OS are you working ?
Mentioning vi makes me guess it should be some kind of Unix but at the
same time the encoding used makes this improbable...
I guess more information is needed here.

Steffanina, Jeff a écrit :

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

RE: Error when using XSL with French Characters

2008-09-03T05:16:39Z

Error when using XSL with French Characters

Manuel,

We create the XML using a version of BASIC. To create this particular character, we send CHR(130) to the XML. When I open the XML in "vi", I see the proper FRENCH symbol.

Jeff

From: Manuel Mall [mailto:mm@...]
Sent: Tuesday, September 02, 2008 10:51 PM
To: 'fop-users@...'
Subject: RE: Error when using XSL with French Characters

I am suspicious that although you declare the XML file as being in UTF-8 it actually isn't. How do you produce the XML file?

Manuel

From: Steffanina, Jeff [mailto:Jeff.Steffanina@...]
Sent: Wednesday, 3 September 2008 10:23 AM
To: fop-users@...
Subject: Error when using XSL with French Characters

My Friends,
Fop-0.95   My style sheet has been working perfectly. However, the user submitted some text in French. In the text was a letter "e" with an accent above it.

That character caused the following error:
        Invalid byte 1 of 1-byte UTF-8 sequence.

My .xml looks fine.   The "e" with the accent above it is perfect.
First line in my XML:
        <?xml version="1.0" encoding="UTF-8"?>

Here is the first line of my XSL:
        <?xml version="1.0" encoding="UTF-8"?>

I am confused over why the UTF-8 for the XML understands the character but the UTF-8 in the XSL does not?

I found an article that suggests that the problem would be solved with:
        <?xml version="1.0" encoding="8859-1"?>

Would this be a viable/recommended solution?   Do you have a better idea?

Re: Referenced pattern not applied when PDF is encrypted

2008-09-03T05:02:15Z

Hi,

We am more than happy to spend time on this and hopefully fix and submit it back. However having never filed a defect or committed to FOP before is there are starter for 10 that tells me about servers/repositories/locations etc and the general process to be followed.

Many Thanks
Lea.

Jeremias Maerki-2 wrote:

Please file a bug in Bugzilla for this and add all the information here
to the issue. Thanks.

Encryption is always a bit tricky and our PDF library has still a few
messy parts which can lead to certain corner cases not to be handled
correctly when encryption is present. Someone will have to fix it. Not
sure if I'll have time and energy very soon. At least, with the Bugzilla
entry it won't get forgotten.

On 28.08.2008 11:59:23 Lea Thurman wrote:
>
> Hi,
>
> We are using FOP.0.95Beta on XP Pro and Mac OS X 10.5 and have encountered
> the following problem when we encrypt our PDF's on both OS's.
>
> We are generating the following SVG and then using FOP to convert this into
> a PDF. The PDF is rendered correctly and the referenced pattern applied if
> we do not encrypt the PDF. As soon as we encrypt the PDF the pattern is not
> applied. In both cases the SVG is identical.
>
> <?xml version="1.0" encoding="utf-8"?>
> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
> "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
> <svg xml:space="preserve" height="297mm" width="210mm">
> <defs>
> <pattern width="1" x="0" height="1" y="0" id="1219915834789"
> patternUnits="userSpaceOnUse">
> <image width="1" x="0" height="1" id="img1" y="0"
> xlink:href="file:/tmp/A12/89.png"/>
> </pattern>
> </defs>
> <rect fill="url(#1219915834789)" x="1.0in" width="1.0in" height="1.0in"
> y="1.0in" stroke="none"/>
> </svg>
>
> The code being used to encrypt the pdf is as follows:
>
> userAgent.getRendererOptions().put(
> "encryption-params",
> new PDFEncryptionParams(null, null, false, true, true, true)
> );
>
> Apologies if this is overly wordy. I have tried to simplify the scenario as
> much as possible.
>
> Any help would be much appreciated.
>
> Regards
> Lea.
>
> --
> View this message in context: http://www.nabble.com/Referenced-pattern-not-applied-when-PDF-is-encrypted-tp19197539p19197539.html
> Sent from the FOP - Users mailing list archive at Nabble.com.

Jeremias Maerki

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

Re: Links in SVGs included into PDFs

2008-09-03T01:26:38Z

I have to call in sick today so this is my last message for now. Just to
give you some feedback. BTW, I noticed this should move to fop-dev since
we're discussion development. Please drop the fop-users CC in any
follow-ups.

On 03.09.2008 10:00:59 Stefan Bund wrote:

> Jeremias Maerki <dev@...> writes:
> > It just occurred to me that as an alternative we could simply track all
> > XSL-FO IDs unconditionally.
>
> That was, what I was thinking about. As a very first step, I want to
> implement just the Renderer part: Resolve the internal id references
> if and only if they have been registered with the IdTracker already.
>
> If I have that, the next step is to get the target id's into the
> IdTracker and it has already occured to me, why not just add all
> id's, if that is not, what is already done (from your comments, it's
> not).
>
> > That would make scanning the SVG (or HTML or MathML) for links
> > unnecessary.
>
> Exactly. That would need an extension of Image and so on. I had
> thought of giving Image (or a baseclass) a list of resolvables and
> subclassing Image with a special SVGImage which would then do the
> parsing and store the created SVG DOM Tree to be reused at render
> time.
>
> However, this seems to be FAR more complicated then just registering
> all id's ...

Yes, and I wouldn't have like a SVG-specific solution.

> > The overhead is probably even smaller and could actually have
> > additional side-benefits for certain special use cases. For example,
> > we could have an event that notifies the FOP-User which ID has its
> > first (and last) area on which page. The area tree (and AT XML) size
> > would increase a bit but I don't think by much (String plus
> > PageViewport reference per destination).
>
> Sounds reasonable :-)
>
> > On 03.09.2008 09:35:52 Jeremias Maerki wrote:
> >> Hmm, you're right. This is more complicated that I thought. Getting the
> >> actual position of a link destination on a page is easily done with
> >> information from PDFRenderer.
>
> This is, where I am standing currently. My problem is getting exactly
> that information.
>
> I can use PDFRenderer.getPDFGoToForID(targetID, pvKey), however, for
> that I need to already know the pvKey. As far as I understand, I could
> get that information form the IdTracker but after lot's of grepping
> and reading through the source code I could not find a way to access
> the AreaTreeManager from the PDFRenderer.
>
> So my question at the moment is: a) How do I get at the page viewport
> key given an id or more specifically b) How do I access the
> AreaTreeManager from PDFRenderer.

I don't think you should access the AreaTreeManager. The renderers are
designed to be passive. I believe the Renderer should be informed by the
AreaTreeHandler about any IDs it's managing. Not the other way around.

> >> Maybe that helps. I hope I didn't scare you too much.
>
> No, you have cleared up lots of points which I guessed but was way from
> sure about.

Cool.

> I'd try to continue along the way assuming the register-all-id's stuff
> could work. And even if that would NOT work (register-all-id's), I
> think i would be MUCH farther ... as a last resort I can always hack
> references into the surrounding code, if needed even using some xslt
> to preprocess the fo+svg stuff (which is already generated from
> docbook in my case so adding some more xslt is realtively straight
> forward). Quite a hack and not a general solution but it could at
> least work for the moment :-) and I'm at the point where I'd be
> grateful for ANY working solution (I have not found ANY way to produce
> a PDF file with embeded images containing links into the PDF ... that
> is, using open source technology).
>
> Many thanks for all your insight. I feel, this could even lead
> somewhere :-)

Good luck!

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Re: Links in SVGs included into PDFs

2008-09-03T01:00:59Z

Jeremias Maerki <dev@...> writes:
> It just occurred to me that as an alternative we could simply track all
> XSL-FO IDs unconditionally.

That was, what I was thinking about. As a very first step, I want to
implement just the Renderer part: Resolve the internal id references
if and only if they have been registered with the IdTracker already.

If I have that, the next step is to get the target id's into the
IdTracker and it has already occured to me, why not just add all
id's, if that is not, what is already done (from your comments, it's
not).

> That would make scanning the SVG (or HTML or MathML) for links
> unnecessary.

Exactly. That would need an extension of Image and so on. I had
thought of giving Image (or a baseclass) a list of resolvables and
subclassing Image with a special SVGImage which would then do the
parsing and store the created SVG DOM Tree to be reused at render
time.

However, this seems to be FAR more complicated then just registering
all id's ...

> The overhead is probably even smaller and could actually have
> additional side-benefits for certain special use cases. For example,
> we could have an event that notifies the FOP-User which ID has its
> first (and last) area on which page. The area tree (and AT XML) size
> would increase a bit but I don't think by much (String plus
> PageViewport reference per destination).

Sounds reasonable :-)

> On 03.09.2008 09:35:52 Jeremias Maerki wrote:
>> Hmm, you're right. This is more complicated that I thought. Getting the
>> actual position of a link destination on a page is easily done with
>> information from PDFRenderer.

This is, where I am standing currently. My problem is getting exactly
that information.

I can use PDFRenderer.getPDFGoToForID(targetID, pvKey), however, for
that I need to already know the pvKey. As far as I understand, I could
get that information form the IdTracker but after lot's of grepping
and reading through the source code I could not find a way to access
the AreaTreeManager from the PDFRenderer.

So my question at the moment is: a) How do I get at the page viewport
key given an id or more specifically b) How do I access the
AreaTreeManager from PDFRenderer.

>> Maybe that helps. I hope I didn't scare you too much.

No, you have cleared up lots of points which I guessed but was way from
sure about.

I'd try to continue along the way assuming the register-all-id's stuff
could work. And even if that would NOT work (register-all-id's), I
think i would be MUCH farther ... as a last resort I can always hack
references into the surrounding code, if needed even using some xslt
to preprocess the fo+svg stuff (which is already generated from
docbook in my case so adding some more xslt is realtively straight
forward). Quite a hack and not a general solution but it could at
least work for the moment :-) and I'm at the point where I'd be
grateful for ANY working solution (I have not found ANY way to produce
a PDF file with embeded images containing links into the PDF ... that
is, using open source technology).

Many thanks for all your insight. I feel, this could even lead
somewhere :-)

stefan.

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Re: Links in SVGs included into PDFs

2008-09-03T00:40:37Z

It just occurred to me that as an alternative we could simply track all
XSL-FO IDs unconditionally. That would make scanning the SVG (or HTML or
MathML) for links unnecessary. The overhead is probably even smaller and
could actually have additional side-benefits for certain special use
cases. For example, we could have an event that notifies the FOP-User
which ID has its first (and last) area on which page. The area tree (and
AT XML) size would increase a bit but I don't think by much (String plus
PageViewport reference per destination).

On 03.09.2008 09:35:52 Jeremias Maerki wrote:

> Hmm, you're right. This is more complicated that I thought. Getting the
> actual position of a link destination on a page is easily done with
> information from PDFRenderer. But to know the actual page of the link
> destionation requires the registration of the ID as an item of interest
> at layout time. For basic-link this is a single INTERNAL_DESTINATION
> trait that is set on the area tree object, resolved by a LinkResolver.
> For an SVG, however, only a single area is created and you might have
> multiple links from the SVG into areas created from XSL-FO. This would
> require something slightly different from a LinkResolver, plus you'd
> need to scan the SVG at layout time for any links into XSL-FO so their
> page number is resolved during layout. That needs some additional
> infrastructure (both Java classes and area tree XML). This should
> probably be done by extending Image and ForeignObject (in the area
> package) from a common superclass which can take a list of link
> destinations. The LinkResolver probably can't be used for this, but
> fortunately, it's just a matter of creating another Resolvable and
> making sure it is used.
>
> So in all, not trivial at all, but this could actually be used later
> should anyone ever plug in (X)HTML support into FOP, too. Or JEuclid
> could use something like that for XLinks in MathML back into XSL-FO.
>
> Maybe that helps. I hope I didn't scare you too much.
>
> On 02.09.2008 23:31:57 Stefan Bund wrote:
> > Replying to my own post since I have gotten a little bit further.
> >
> > Implementing internal links seems to be more complicated than I had
> > expected. As far as I understand, internal links are resolved within
> > the area tree before the tree is rendered. An (external) SVG image
> > resource howvever is only parsed at the render stage.
> >
> > However, I could get further if I could access the AreaTreeManager
> > (and thereby its IdTracker) from the PDFANode. However, I could not
> > find any way to get there (I have the PDFGraphics2D object and I can
> > get the PDFDocument or RendererContext but I could not find a
> > reference to the AreaTreeManager anywhere).
> >
> > I know, this is probably not the correct way to do this (I would need
> > to somehow create a LinkResolver for every link in the SVG file while
> > creating the area tree but at the moment that is way over my head). I
> > hope, I can resolve the id's by just querying the IdTracker. This will
> > possibly only work when the id is referenced from some other place,
> > but it would be a start.
> >
> > Any pointer how to proceed?
> >
> > And maybe I got everything completely wrong. If so, could someone
> > please set me right?
> >
> > stefan.
> >

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...

Re: Links in SVGs included into PDFs

2008-09-03T00:35:52Z

Hmm, you're right. This is more complicated that I thought. Getting the
actual position of a link destination on a page is easily done with
information from PDFRenderer. But to know the actual page of the link
destionation requires the registration of the ID as an item of interest
at layout time. For basic-link this is a single INTERNAL_DESTINATION
trait that is set on the area tree object, resolved by a LinkResolver.
For an SVG, however, only a single area is created and you might have
multiple links from the SVG into areas created from XSL-FO. This would
require something slightly different from a LinkResolver, plus you'd
need to scan the SVG at layout time for any links into XSL-FO so their
page number is resolved during layout. That needs some additional
infrastructure (both Java classes and area tree XML). This should
probably be done by extending Image and ForeignObject (in the area
package) from a common superclass which can take a list of link
destinations. The LinkResolver probably can't be used for this, but
fortunately, it's just a matter of creating another Resolvable and
making sure it is used.

So in all, not trivial at all, but this could actually be used later
should anyone ever plug in (X)HTML support into FOP, too. Or JEuclid
could use something like that for XLinks in MathML back into XSL-FO.

Maybe that helps. I hope I didn't scare you too much.

On 02.09.2008 23:31:57 Stefan Bund wrote:

> Replying to my own post since I have gotten a little bit further.
>
> Implementing internal links seems to be more complicated than I had
> expected. As far as I understand, internal links are resolved within
> the area tree before the tree is rendered. An (external) SVG image
> resource howvever is only parsed at the render stage.
>
> However, I could get further if I could access the AreaTreeManager
> (and thereby its IdTracker) from the PDFANode. However, I could not
> find any way to get there (I have the PDFGraphics2D object and I can
> get the PDFDocument or RendererContext but I could not find a
> reference to the AreaTreeManager anywhere).
>
> I know, this is probably not the correct way to do this (I would need
> to somehow create a LinkResolver for every link in the SVG file while
> creating the area tree but at the moment that is way over my head). I
> hope, I can resolve the id's by just querying the IdTracker. This will
> possibly only work when the id is referenced from some other place,
> but it would be a start.
>
> Any pointer how to proceed?
>
> And maybe I got everything completely wrong. If so, could someone
> please set me right?
>
> stefan.
>

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@...
For additional commands, e-mail: fop-users-help@...