which graphic file formats are supported ?

[Nick Winger]

hi !

anybody know where to get a list of which graphic file formats are supported
in fop ( in  tag ) ?

beside, i can't load the xml.apache.org site or www.apache.org at the moment
seems to be the server is down ?


greetings

Nick Winger

(Software-Developer)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Triggering XALAN/XERXES from a start routine

[Matthias Fischer]

Is it possible to program a start routine, let's say: in some programming
language (preferably Visual Basic) to trigger an XSL transformation from the
outside? Have XALAN/XERXES the necessary interface(s)?

I would need to hand over the source and target paths of the XML instances
and the path of the XSLT.

Has anyone done this already?


Matthias Fischer




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Triggering XALAN/XERXES from a start routine

[Stefan Weber]

wrong group???

-Original Message-
From: Matthias Fischer [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 01, 2002 10:41 AM
To: Liste, FOP
Cc: Zelkanovic, Adnan; Thaler, Gregor
Subject: Triggering XALAN/XERXES from a start routine


Is it possible to program a start routine, let's say: in some programming
language (preferably Visual Basic) to trigger an XSL transformation from the
outside? Have XALAN/XERXES the necessary interface(s)?

I would need to hand over the source and target paths of the XML instances
and the path of the XSLT.

Has anyone done this already?


Matthias Fischer




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

<<<
sitewaerts GmbH
Hebelstraße 15
D-76133 Karlsruhe

Tel: +49 (721) 920 918 0
Fax: +49 (721) 920 918 29
http://www.sitewaerts.de
>>>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: white-space

[Joerg Pietschmann]

> I need white space between fields, how do I do that?
...
> , 
>  

Re: transforming fo to pdf

[Joerg Pietschmann]

"Katiyar, Bhawana" <[EMAIL PROTECTED]> wrote:
> I have the following code :
>   Document docFo ;  //contains a valid fo document
...
> java.lang.NullPointerException
>   at 
>org.apache.fop.layoutmgr.PageLayoutManager.makeNewPage(PageLayoutManager.java:141)
>   at 
>org.apache.fop.layoutmgr.PageLayoutManager.getParentArea(PageLayoutManager.java:176)

The most likely reason is that your FO document is *not* valid,
for example missing a fo:table-body around the rows of a table
body. There may be any number of other explanations.

Get a serialized version of your FO stuff and check it with
the FOP command line application. If you seen an [ERROR]:null
message, the problem is in your document, or you have hit a real
FOP bug. In this case narrow down the error location by cutting
as much stuff from the document until the error disappears, if
you still can't spot the reason ask again on this or better the
fop-user list.
If the command line version produces a PDF, the problem is either
in the DOM implementation you use or in the FOP configuration.
You'll have to supply more information about them if you want to
get more help.

HTH
J.Pietschmann

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: transforming fo to pdf

[Jeremias Maerki]

After looking closer at your mail, when Jörg replied, I realized what's
wrong. Bhawana, you're using the CVS version (main branch) of FOP which
is currently in a redesign phase. That version is not intended to be
used, yet. FOP 0.20.x does not have any LayoutManagers. I suggest you
download a release or get FOP using CVS tag "fop-0_20_2-maintain".

> I wish to transform FO document (docFo) into PDF. I am using fop.20
> I have the following code :
> 
>--
> java.lang.NullPointerException
>   at 
>org.apache.fop.layoutmgr.PageLayoutManager.makeNewPage(PageLayoutManager.java:141)
>   at 
>org.apache.fop.layoutmgr.PageLayoutManager.getParentArea(PageLayoutManager.java:176)
>   at 
>org.apache.fop.layoutmgr.FlowLayoutManager.getParentArea(FlowLayoutManager.java:49)
>   at 
>org.apache.fop.layoutmgr.BlockLayoutManager.getParentArea(BlockLayoutManager.java:81)
>   at 
>org.apache.fop.layoutmgr.LineLayoutManager.createLine(LineLayoutManager.java:95)
>   at 
>org.apache.fop.layoutmgr.LineLayoutManager.addChild(LineLayoutManager.java:118)
>   at 
>org.apache.fop.layoutmgr.TextLayoutManager.parseChars(TextLayoutManager.java:164)
>   at 
>org.apache.fop.layoutmgr.TextLayoutManager.generateAreas(TextLayoutManager.java:55)
>   
> 
> Can someone suggest where I am going wrong.

Cheers,
Jeremias Märki

mailto:[EMAIL PROTECTED]

OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029
Internet http://www.outline.ch


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: white-space

[Rabi Shankar]

Title: RE: white-space






u can put   ( & #  1 6 0 ;)

this will work.

rgds,

Rabi.

-Original Message-

From:   Joerg Pietschmann [SMTP:[EMAIL PROTECTED]]

Sent:   Friday, February 01, 2002 5:37 PM

To: FOP Dev

Subject:    Re: white-space

> I need white space between fields, how do I do that?

...

> , 

>  

[GUMP] Build Failure - Fop

[Sam Ruby]

This email is autogenerated from the output from:



Buildfile: build.xml

init-avail:

init-filters-xalan2:
 [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen

init:
 [echo] --- Fop 1.0dev [1999-2001] 

prepare:
 [echo] Preparing the build directories
[mkdir] Created dir: 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties
[mkdir] Created dir: 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph
 [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf

codegen:
 [echo] Resetting codegen directory
 [copy] Copying 31 files to /home/rubys/jakarta/xml-fop/build/src/codegen
 [echo] Generating the java files from xml resources
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl
[style] : Fatal Error! java.lang.NullPointerException Cause: 
java.lang.NullPointerException
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/foenums_ignore_this.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/charlist.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl
[style] Transforming into 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBoldOblique.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierOblique.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Helvetica.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Helvetica.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBold.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java
[style] Processing 
/home/rubys/jakarta/xml-fop/src/codegen/HelveticaBoldOblique.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBoldOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaOblique.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Symbol.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Symbol.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBold.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBold.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBoldItalic.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesItalic.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesItalic.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesRoman.xml to 
/home/rubys/jakarta/xml-fop/build/src/o

Re: making classes off your fonts...

[Jochen . Maes]

thanks...

it worked but not the way i thought (lol)
i think each space is used as a linebreak (nicxe view though :-]) and some
characters aren't correct (like a "°" in stead off an "ë").

do you know where i can find a tutorial for that (making
metrix-files...)... and implementing correctly (must be doing something
wrong ...

thanks guys



Jochen Maes
EDP departement
Programmeur

KBC-Securities
Havenlaan 16
1080 Brussel

Tel : 02/429.96.81
Fax : 02/429.17.48
E-mail : [EMAIL PROTECTED]

**

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. You must not,
directly or indirectly, use, disclose, distribute, print, or copy any part
of this message if you are not the intended recipient. KBC Securities
reserves the right to monitor all e-mail communications through its
networks. Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorised to state them to be the views of any such entity.
**


   
 
Jeremias Maerki
 
cc:  
 
  Subject: Re: making classes off your 
fonts... 
01-02-02 08:42 AM  
 
Please respond to  
 
fop-dev
 
   
 
   
 




> got a question. when i use FOP i use it with different fonts then
allready
> specified... and loading those fonts into the java takes some time
> now i want to make that FOP more performant... Is there a way to make
> classes (like some allready exist) off them fonts so that the rendering
> takes less time
> if there isn't a way supplied, can i adapt them classes (or java's) to
> whatever font i want?

That was actually the way it was done about a year ago. Personally, I
don't think it will help performance a lot. There are more
performance-critical parts in FOP. Or did you do any measurements that
lead you to this conclusion.

Anyway, if you really want to create classes for your fonts, have a look
at build.xml and the codegen folder which contains XSLTs that convert
XML font metric files to Java classes. Then you need to add these
classes in org.apache.fop.render.pdf.FontSetup.java.

Cheers,
Jeremias Märki

mailto:[EMAIL PROTECTED]

OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029
Internet http://www.outline.ch


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: making classes off your fonts...

[Jeremias Maerki]

Everything on fonts is on the following page:
http://xml.apache.org/fop/fonts.html

Sometimes the metric files need some tweaking, especially for Type 1
fonts, but that requires reading into the font specs.

I'm still quite sure you're making yourself a hard time with little
profit. Good luck.

> it worked but not the way i thought (lol)
> i think each space is used as a linebreak (nicxe view though :-]) and some
> characters aren't correct (like a "°" in stead off an "ë").
> 
> do you know where i can find a tutorial for that (making
> metrix-files...)... and implementing correctly (must be doing something
> wrong ...


Cheers,
Jeremias Märki

mailto:[EMAIL PROTECTED]

OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029
Internet http://www.outline.ch


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 6178] New: - Color palette of .bmp files with 1 bit/pixel not used

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6178

Color palette of .bmp files with 1 bit/pixel not used

   Summary: Color palette of .bmp files with 1 bit/pixel not used
   Product: Fop
   Version: all
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: images
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The color palette of .bmp files with 1 bit/pixel is not used when loading image.
Example of a bmp header I've received from Alchemy on Unix:

  424DAE8E0100 3E002800
0010  1603FC03 01000100
0020  708E0100C21E C21E
0030   FF00
0040   

The palette is inverted (why, I don't know). So a 0 bit means a white pixel and 
a 1 bit means a black pixel.
In class org.apache.fop.image.BmpImage, method loadImage ignores the palette in 
that case (it's not even constructed). For FOP, a 0 bit means always black 
pixel and a 1 bit means always white pixel.
So my image appears in Acrobat Reader as inverted video.

I have fixed the bug with the following statements :

if (headermap[28] == 4 || headermap[28] == 8 || headermap[28] == 1) {

to always build the palette and 

for (int countr = 0; countr < 8 && x < this.m_width;
countr++) {
if ((p & 0x80) != 0) {
this.m_bitmaps[3 * (i * this.m_width + x)] =
//  (byte)0xFF;
palette[3];
this.m_bitmaps[3 * (i * this.m_width + x) + 1] =
//  (byte)0xFF;
palette[4];
this.m_bitmaps[3 * (i * this.m_width + x) + 2] =
//  (byte)0xFF;
palette[5];
} else {
this.m_bitmaps[3 * (i * this.m_width + x)] =
//  (byte)0;
palette[0];
this.m_bitmaps[3 * (i * this.m_width + x) + 1] =
//  (byte)0;
palette[1];
this.m_bitmaps[3 * (i * this.m_width + x) + 2] =
//  (byte)0;
palette[2];
}

to use it.
I think it could help.

Frédéric.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Why do you use FOP instead of ...

[Roland]

At 08:58 PM 1/29/02 -0500, you wrote:
>I would like to know why FOP enthousiast (I am one) are using FO rather 
>than products such as Crystal Reports or other such software (anyone 
>Jetfoms ?). Just for the fun of playing with new technology ?

Good question,
here where I work I'm thinking about switching to iText instead 
http://www.lowagie.com/iText/
It's a much simpler way to generate pdf from Java. The truth is that xsl:fo 
is a headache to use, very complicated...

Roland


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[Jim Urban]

Our application is a servlet based web application.  We have adopted the MVC
approach.  We found Cacoon over kill, so we implmented our own frame work.
Our frame work requires all business components produce XML.  We then use
XSL:HTML to format HTML output for the browser.  It was only a natural next
step to use XSL:FO to generate PDF since we already had XML being generated.
One of the real blessings of this approach is our clients can customize the
look and feel of the application by changing the XSL files without our ever
opening a Java source file.

It was a BIG investment and learning curve up front to take this approach,
but now that we are past that phase, the return on the investment has
enabled us to justify the up front expense.  Looking back, I think it was a
vary sound decission.  We are in a position where adding WAP (WML) and a B2b
SOAP interface are a natural extension of our framework, not a rewrite.

Thank yous go to not only FOP, but Xalan and Xerces for all the XML and XSL
support!

Jim Urban
Product Manager
Netsteps Inc.
Suite 505E
1 Pierce Pl.
Itasca, IL  60143
Voice:  (630) 250-3045 x2164
Fax:  (630) 250-3046



>
> At 08:58 PM 1/29/02 -0500, you wrote:
> >I would like to know why FOP enthousiast (I am one) are using FO rather
> >than products such as Crystal Reports or other such software (anyone
> >Jetfoms ?). Just for the fun of playing with new technology ?
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[fred redf]

Hi all,

I'm working on an e-learning at a french university.
We adopted fop the very same reason Jim has stated.
But i also use iText as a hack for some special
purposes (re-ordering/re-sizing/watermarking mostly)
I think we also made this choice "for the future" as:

- first, we have a pure xml/xsl technology system (no
transitiional xml sub-language to drive iText

- second, we can use SVG (we have a nice grpahic
designer and i can import SVG directly in my FO code)

Hope this helps, if you have to choose one of these
technologies for your project.

Dref.





--- Jim Urban <[EMAIL PROTECTED]> a écrit : > Our
application is a servlet based web application. 
> We have adopted the MVC
> approach.  We found Cacoon over kill, so we
> implmented our own frame work.
> Our frame work requires all business components
> produce XML.  We then use
> XSL:HTML to format HTML output for the browser.  It
> was only a natural next
> step to use XSL:FO to generate PDF since we already
> had XML being generated.
> One of the real blessings of this approach is our
> clients can customize the
> look and feel of the application by changing the XSL
> files without our ever
> opening a Java source file.
> 
> It was a BIG investment and learning curve up front
> to take this approach,
> but now that we are past that phase, the return on
> the investment has
> enabled us to justify the up front expense.  Looking
> back, I think it was a
> vary sound decission.  We are in a position where
> adding WAP (WML) and a B2b
> SOAP interface are a natural extension of our
> framework, not a rewrite.
> 
> Thank yous go to not only FOP, but Xalan and Xerces
> for all the XML and XSL
> support!
> 
> Jim Urban
> Product Manager
> Netsteps Inc.
> Suite 505E
> 1 Pierce Pl.
> Itasca, IL  60143
> Voice:  (630) 250-3045 x2164
> Fax:  (630) 250-3046
> 
> 
> 
> >
> > At 08:58 PM 1/29/02 -0500, you wrote:
> > >I would like to know why FOP enthousiast (I am
> one) are using FO rather
> > >than products such as Crystal Reports or other
> such software (anyone
> > >Jetfoms ?). Just for the fun of playing with new
> technology ?
> >
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, email:
> [EMAIL PROTECTED]
>  

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.fr

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: [PATCH] Proper use of font encodings for "native" fonts

[Christian Geisert]

Arved Sandstrom wrote:

> Hell, why not. :-)


Well, I'm a just bit worried that this patch could introduce new bugs...

> I don't know what your schedule is like...me, I really need to do my work on
> Saturday (uploading Peter West's stuff, mostly). Is that too long for you to

> wait? Tonight and tomorrow night, as earlier this week, I am pretty busy. As


I'm quite busy too (as always..) and have also planed to do my stuff on 
the weekend.

> far as I am concerned the release candidate is available and reasonably
> functional so we are not in a great hurry.


Ok. Any news on the licensing issues ?

> Arved


Christian



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[Roland]

At 10:32 AM 2/1/02 -0600, you wrote:
>step to use XSL:FO to generate PDF since we already had XML being generated.
>One of the real blessings of this approach is our clients can customize the
>look and feel of the application by changing the XSL files without our ever
>opening a Java source file.

We also have a web based service here, and currently are using the same 
approach as you are, but the problems we encouter are the following:

If you generate XSL:FO from XML, the XSLT(stylesheet) can become very 
complicated, at least for us because:

We generate a lot of tables, and they are quite different what concerns the 
formatting/color. That means, there has to be a section in the XSLT for 
each type of table and complicated if-then-else decisions to decide which 
formatting to apply and how. Take into account also, that up to now you 
have to manually code in the column width of each column in every table for 
FOP, this is a nightmare! In other words, changing the XSLT is much, much, 
much more painfull than changing a java source file(supposing the use of 
iText).

An alternative for having a simpler XSLT, would be to encode most of the 
formatting in the XML, but then you would have XML with formatting 
information, and if you want to change the look and feel you have to change 
the java source that is generating the XML.

I think the use of XSLT is only usefull if you have a standardized look and 
feel, like every table looks the same way, etc... But even then, if 
you  decide that you need a new table it is very difficult to define a new 
formatting using XSLT to generate XSL:FO. XSL:FO is a complicated language, 
and the complexity transfers to the generating XSLT(which is cumbersome 
enough on its own), which looks like a big messy thing here at the company. 
Our XSLT files are currently VERY long and MESSY. It would be much simpler 
to code the same thing in Java, take a look at the iText page and their 
examples(http://www.lowagie.com/iText/).

And if you still need your XML, you can take this approach:

1. Generate XML from Java for whatever you need.
2. Generate the PDF from Java using iText.

I think this is probably the approach we are gonna take here...
And if you code smartly you can arrange is to also not have to change the 
java source for a change of look and feel. Just store the formatting 
information in a '.properties' file like:

tableBackGroundColor=red
tableFont=Roman8
etc...

Then you can change the look and fell by just editing that properties file...

I will nail down the weaknesses of the XML->PDF approach:

1. XSL:FO is a very complicated and messy language
2. XSLT is also kinda complicated to use, at least if you have to do 
complicated formatting...

Best regards...Roland


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[Roland]

>
>I will nail down the weaknesses of the XML->PDF approach:
>
>1. XSL:FO is a very complicated and messy language
>2. XSLT is also kinda complicated to use, at least if you have to do 
>complicated formatting...

I'm replying to my own email adding that of course I would be glad if 
someone can show me how to make a simpler XSLT. Maybe we just didn't figure 
out how to make the XSLT simple. But please take a look at the iText 
http://www.lowagie.com/iText/ examples first. That is what I call simplicity!!!
Also keep in mind that we generate many different tables, with different 
formatting each on a single pdf document.

Best regards, Roland


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: i18n in TXTRenderer

[Art Welch]

Yes. I looked a bit at the renderers in the main branch and it looks like
they have been gutted. Seeing this I am a bit concerned that it may be
longer than I thought before the redesigned FOP is functional. But I did not
look at very many things, so maybe it is what I happened to look at. I also
do not recall seeing many commit messages for a while, so maybe someone has
all kinds of cool stuff that they are working on locally.

Art

-Original Message-
From: Arved Sandstrom [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 31, 2002 5:48 PM
To: [EMAIL PROTECTED]
Subject: RE: i18n in TXTRenderer


I think everything like this, maintenance branch.

Arved

-Original Message-
From: Art Welch [mailto:[EMAIL PROTECTED]]
Sent: January 31, 2002 1:06 PM
To: '[EMAIL PROTECTED]'
Subject: RE: i18n in TXTRenderer


I will try to commit this sometime in the next few days.

I have not looked at the code yet, should this be the main branch or the
maintenance branch?

Art

-Original Message-
From: Satoshi Ishigami [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 8:36 PM
To: [EMAIL PROTECTED]
Subject: Re: i18n in TXTRenderer



Hi, Art.

I attach the most simplest changes to this mail.

I created a new org.apache.fop.render.txt.TXTStream class and
modified the TXTRenderer class.

A difference of behavior with an existing code is that a
generated text is written by UTF-8 encoding (not ISO-8859-1).

It maybe more better that users can specify a charset encoding
at anywhere. However I also think that most users will not need
a function more than current TXTRenderer. So I think that this
changes are enough to view the text.

By the way, a generated text is very dirty :)

---
Satoshi Ishigami   VIC TOKAI CORPORATION



On Mon, 28 Jan 2002 12:01:54 -0500 , Art Welch wrote:

> You are probably correct. The TXTRenderer probably should not use the same
> add method as the PCL renderer. Since it should just generate plain text,
> there probably is not a reason that it should not be able to support i18n.
> As coded however, it may be more aptly named the "ASCIIRenderer" (or maybe
> that should be "PC-8").
>
> Without looking at the code, I am not sure how the TXTRenderer would
handle
> chars instead of bytes. My guess is that some (simple) code changes would
> need to be made.
>
> Personally I do not know that the TXTRenderer is useful enough to be worth
> spending much effort on. But if the changes are simple and useful to
> someone... Certainly it would be good for FOP (and all of its components)
to
> support i18n.
>
> Art
>
> -Original Message-
> From: Satoshi Ishigami [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 27, 2002 6:35 PM
> To: [EMAIL PROTECTED]
> Subject: i18n in TXTRenderer
>
>
>
> Hi .
>
> I hacked the TXTRenderer for i18n.
>
> Currently the org.apache.fop.render.pcl.PCLStream class is
> used as OutputStream in TXTRenderer. The add method in
> PCLStream calss is as below:
>
> public void add(String str) {
> if (!doOutput)
> return;
>
> byte buff[] = new byte[str.length()];
> int countr;
> int len = str.length();
> for (countr = 0; countr < len; countr++)
> buff[countr] = (byte)str.charAt(countr);
> try {
> out.write(buff);
> } catch (IOException e) {
> // e.printStackTrace();
> // e.printStackTrace(System.out);
> throw new RuntimeException(e.toString());
> }
> }
>
> I think that this algorithm is wrong for the character > 127.
> This reason is that the literal length of char is 2 bytes and
> the literal length of byte is 1 byte. To avoid this problem,
> I think that the following algorithm is better than now.
>
> public void add(String str) {
> if (!doOutput) return;
> try {
> byte buff[] = str.getBytes("UTF-8");
> out.write(buff);
> } catch (IOException e) {
> throw new RuntimeException(e.toString());
> }
> }
>
> This algorithm may be not good for PCLRenderer because
> I don't know whether the PCL printer supports the UTF-8
> encoding or not.
>
> However I think that the TXTRenderer could use the
> multilingualable encoding because it is possible to include
> some languages in a same single fo file.
>
> Therere I consider that the TXTRenderer should not use the
> PCLStream and had better use original OutputStream (such as
> TXTStream).
>
> Will my thought be wrong?
>
> Best Regards.
>
> ---
> Satoshi Ishigami   VIC TOKAI CORPORATION
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>

-
To unsubscribe

RE: Why do you use FOP instead of ...

[Ralph LaChance]

At 04:06 PM 2/1/02 -0200, you wrote:
>I will nail down the weaknesses of the XML->PDF approach:
>
>1. XSL:FO is a very complicated and messy language
>2. XSLT is also kinda complicated to use, at least if you have to do 
>complicated formatting...

Sometimes it seems folks assume that FO is synomous with "pdf",
but for some of us, the point of using FO is not to create pdf output
but to format and send xml data directly to a printer.   ;-)



 ' Best,
 -Ralph LaChance



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[fred redf]

Hi Roland,

We had the very same prob cause the xsl that translate
from our XML content to FO went quite messy as we made
all modifications needed to paper export (we're
usually building 50->200 pages in our pdfs, with many
pictures, tables cause it's made of courses contents).
So we made some kind of pre-formatting in a
xmlsublanguage of our own then we actually turn
everything to fo). That's not a big prob in our
context since pdf building is almost an offline task,
made by teachers.
Cheers,
Fred.

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.fr

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Why do you use FOP instead of ...

[Patrick Andries]

Ralph LaChance wrote:

> At 04:06 PM 2/1/02 -0200, you wrote:
>
>> I will nail down the weaknesses of the XML->PDF approach:
>>
>> 1. XSL:FO is a very complicated and messy language
>> 2. XSLT is also kinda complicated to use, at least if you have to do 
>> complicated formatting...
>
>
> Sometimes it seems folks assume that FO is synomous with "pdf",
> but for some of us, the point of using FO is not to create pdf output
> but to format and send xml data directly to a printer.   ;-)
>
Well, what does it take to develop an XSL-FO interpreter on a printer ? 
No need to transform to PDF or PS then.

I thought of doing it for some time, but got discouraged when an old 
Xerox guy told me that Adobe actually supplies (for free ?) their PS 
interpreter and that developing an interpeter and fine-tuning it takes a 
LOT of time.

Patrick Andries




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[fred redf]

Forgot to say that our fo formatting would be ready in
10 years when we'll have those *good* voice
synthetizer
that are supposed to *print* our fo code according to
the XSL-FO specs. ;)
Fred.

 
 --- Ralph LaChance <[EMAIL PROTECTED]> a
écrit : > At 04:06 PM 2/1/02 -0200, you wrote:
> >I will nail down the weaknesses of the XML->PDF
> approach:
> >
> >1. XSL:FO is a very complicated and messy language
> >2. XSLT is also kinda complicated to use, at least
> if you have to do 
> >complicated formatting...
> 
> Sometimes it seems folks assume that FO is synomous
> with "pdf",
> but for some of us, the point of using FO is not to
> create pdf output
> but to format and send xml data directly to a
> printer.   ;-)
> 
> 
> 
>  ' Best,
>  -Ralph LaChance
> 
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, email:
> [EMAIL PROTECTED]
>  

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.fr

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[Jim Urban]

>
> 1. XSL:FO is a very complicated and messy language
Given the power of the language, of course its complicated.  Just as
Asembler is complicated compared to basic.

> 2. XSLT is also kinda complicated to use, at least if you have to do
> complicated formatting...
So is any other kind of programming language.  The more complex the task,
the more lines of coded need to achieve the desired results.

We have reduced a huge complex XSL files down to a driver file and series of
template files.  The driver file references templates located in other XSL
template files.  These templates are then reused from document to document,
giving the applications a constant look and feel.  Our graphics designer has
taken over our FO work.  We give him the XML and tell him what the PDF
should look like and he builds the XSL file for us.  We only need to help
occasionally when the XSL requires complex programmatic logic.

I will say this. To work effectivly with XML, XST and FO, an application
should be designed around the concept.  Coming along and adding XSL:FO to an
application that does not have a standard XML definition to begin with would
be a messy task.

Jim


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[Ralph LaChance]

It does seem a shame that this entire quo vadis thread
isn't on fop-user

 ' Best,
 -Ralph LaChance



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Why do you use FOP instead of ...

[Patrick Andries]

Well it is also (after being suggested yesterday).

Ralph LaChance wrote:

>
>
> It does seem a shame that this entire quo vadis thread
> isn't on fop-user
>
> ' Best,
> -Ralph LaChance
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Why do you use FOP instead of ...

[Roland]

At 12:59 PM 2/1/02 -0600, you wrote:

> > 2. XSLT is also kinda complicated to use, at least if you have to do
> > complicated formatting...
>So is any other kind of programming language.  The more complex the task,
>the more lines of coded need to achieve the desired results.

Wrong! Look at iText http://www.lowagie.com/iText/ to see how simple their 
examples are. They build a complex table with just a few lines of java 
codes. Try doing the same with the XML/XSLT/XSL:FO approach and I guarantee 
you that the total outcome will be much more both in lines and complexity. 
I think to generate PDF with iText is as easy as generating XML from Java. 
XSLT is just a complicated language.

But I will take a closer look at our xsl files and see how and if things 
could be simplified...

Roland


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Why do you use FOP instead of ...

[Matt Savino]

I've attached an XSLT stylesheet that we use to create a PDF version of
a clinical trial participant's lab report. It uses some fairly
complicated presentation logic that by necessity needs take place in the
last stage of processing. The FO output that it produces is also
somewhat involved, making use of many of the advanced features of
XSL:FO. The stylesheet represents about a man-month of work.

I sleep a lot better at night knowing that if for some reason FOP can't
meet my needs, there's a good chance I can switch over one of the
commercial FO->PDF processors without a major coding initiative. If
XSL:FO were prorietary to FOP, I would be living in fear of (1) having
to learn some new proprietary input format then (2) either weaving it
into this stylesheet or worse yet moving all this logic into some Java
class. 

In my opinion XSLT an extremely elegant presentation language. Java
seems clunky to me now. If you can manage your XML input so that it
represents the underlying structure of the data, you won't need to do
much processing at all in your stylesheet (ie - our levels are report,
study, doctor, patient, visit, test, analyte, etc.). For most of our
management reports the stylesheet is only a few templates and almost no
logic. XSLT/XPATH can be a little frustrating/intimidating when you're
first learning, especially if there's no one with experience nearby. I
have yet to find a good exhaustive XPATH reference. But it becomes more
straightforward once you learn all the shorthand. Like any good
language, after you learn a few pieces you can start guessing on the
syntax. 

We have a mirror of this stylesheet that outputs an HTML version of the
lab report. Yes it's a little bit of work to maintain both in parallel.
But I know if I really needed to (I.E. - we had 50 canned reports
instead of 6) I could come up with a system that factors out most of the
common presentation logic between HTML and FO. As far as I can see, if I
was using some straight XML->Java->PDF system like iText, I'd have to
either have my HTML generation in a JSP and my iText input creation in
some involved Java package, or try to create both outputs from some
really involved Java package. I don't think either system would be much
fun to mantain from a presentation POV. 

-Matt




Roland wrote:
> 
> At 12:59 PM 2/1/02 -0600, you wrote:
> 
> > > 2. XSLT is also kinda complicated to use, at least if you have to do
> > > complicated formatting...
> >So is any other kind of programming language.  The more complex the task,
> >the more lines of coded need to achieve the desired results.
> 
> Wrong! Look at iText http://www.lowagie.com/iText/ to see how simple their
> examples are. They build a complex table with just a few lines of java
> codes. Try doing the same with the XML/XSLT/XSL:FO approach and I guarantee
> you that the total outcome will be much more both in lines and complexity.
> I think to generate PDF with iText is as easy as generating XML from Java.
> XSLT is just a complicated language.
> 
> But I will take a closer look at our xsl files and see how and if things
> could be simplified...
> 
> Roland
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


http://www.w3.org/1999/XSL/Transform"; xmlns:fo="http://www.w3.org/1999/XSL/Format";>

 
 
 
 

 
 
 
 

 
 
 
 

 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

 
  

 
  http://www.w3.org/1999/XSL/Format";>
   
  
 

 

  

 
 
 

   

   


 Page: 



 Laboratory Report
 
  
   
   
   
   
   

 
  


   

 
  
 
   
 
   
   
 
   
   
   
   
   ,   
   
   
 
   
    
  
 

   
   
  
 
 
 
  


   

  
 
 


 
   

   





 
  
   Patient Name
   
  
  
   Patient ID
   
  
  
   Age
   
  
  
Sex
   
  


   
   
  
 

  

 
  

   






 
  
   Page
of 
  
  
   Requisition #
   
  
  
  

fop dtd attached

[Chuck Paussa]

A couple of people have written in recently asking for an FOP dtd. I'm guessing so 
they can use it
with PSGML. So, I made one using the standard document as well as I could read it. I 
tried to
include lists of valid values for things like  so, if you want to use it as a 
real
validating document, those lists are going to invalidate valid integers. (Replace the 
list with
CDATA and you should be fine) Also, the DTD omits the FO: prefix for the elements. 
Feel free to
fix the problems and repost the DTD.

FOP DTD attached

Chuck

__
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com






















































































































































































-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]