RE: Footer placement...

2004-11-09 Thread Anil R. Pinto
Thanks Chris. Will try out your suggestion and get back to the list of the
outcome.

Anil.

-Original Message-
From: Chris Bowditch [mailto:[EMAIL PROTECTED]
Sent: Monday, November 08, 2004 8:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Footer placement...


Anil R. Pinto wrote:

snip/

 But with the marker approach I noticed that the footer area has to be
 allocated to the other pages (using the layout and region-after values
 applicable to the pages) irrespective. So, untimately although no footer
is
 printed on the middle pages, the area is consumed by a blank portion and
so
 paper will not really be saved (the main intention of this exercise :-) )

Sounds to me like you can fulfill your requirement using a footnote. A
footnote only takes up space if present. So just put a footnote in your last
paragraph and it should appear at the bottom of the last page. No need to
define a region-after.

The only problem with footnotes is that they are a bit buggy in current
version of FOP. Certain scenarios may produce strange effects, e.g. if last
paragraph in document happens to be at bottom of page, then there will be
room
for footnote. What should happen is FOP should move last paragraph to next
page along with footnote, but I dont think this works.

Chris


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





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



AW: AW: chinese characters just working when defined in xsl-fo-page directly

2004-11-09 Thread Christoph Klocker
I found out now, that the problem lies in the esql query,
I generate an XML through xsp/esql with cocoon,
if I have a look on the generated xml, I can see that the chinese glyphs are
not shown as
such ones, just the ones I define in the xsp page.
So there must be something wrong with the querying.

I use the jdbc driver from MS, and my database is MSSQL,

Anyone an Idea how to get Unicode data out of the database??

christoph

-Ursprüngliche Nachricht-
Von: J.Pietschmann [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 06. November 2004 12:21
An: [EMAIL PROTECTED]
Betreff: Re: AW: chinese characters just working when defined in
xsl-fo-page directly


Christoph Klocker wrote:
 Thats what I did, when I Serialize it to XML its as it is stated here, so
I
 got no Idea, why this doesn't work
 FaaLocTextCH#32173;#20063;#32013;/FaaLocTextCH

 I am happy for any suggestion how to solve this problem.

I meant: serialize the input to the PDF serializer to XML, after
the transformation. You should not get a FaaLocTextCH element in
a FO document.
Be sure you aren't using disable-output-escaping either.

J.Pietschmann

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



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



XSL-FO Specification

2004-11-09 Thread Balamuraly




Hello All,

We are very interested in XSL-FO 
concepts.

Can you please clarify the Specification version 
of XSL-FO as per W3C.

What are the limitations in this 
version?

When is the next version is going to be 
released?

What are the points that will be addressed in the 
next version in the current limitations?

It will be really helpful if you give this 
details.

thanks and regards,bala


Re: XSL-FO Specification

2004-11-09 Thread Chris Bowditch
Balamuraly wrote:
Hello All,
 
We are very interested in XSL-FO concepts.
 
Can you please clarify the Specification version of XSL-FO as per W3C.
 
What are the limitations in this version?
See the compliance page for details:
http://xml.apache.org/fop/compliance.html
 
When is the next version is going to be released?
Open Source Development is very different to commercial development. There are 
no project plans. It is likely to be a long time before the redesigned code is 
ready for release.

 
What are the points that will be addressed in the next version in the 
current limitations?
The main purpose of the redesigned code is to facilitate the implementation of 
keep-* properties.

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


Re: XSL-FO Specification

2004-11-09 Thread Clay Leeds
On Nov 9, 2004, at 7:30 AM, Balamuraly wrote:
Hello All,
We are very interested in XSL-FO concepts.
Can you please clarify the Specification version of XSL-FO as per W3C.
What are the limitations in this version?
These questions are answered in detail here[1].
When is the next version is going to be released?
That has not yet been clearly defined, although a search of the fop-dev 
archives (see the FOP Mailing List page[2]) will provide more insight.

What are the points that will be addressed in the next version in the 
current limitations?
You may find information on this topic by reading the FOP Status 
page[3]. Also, the fop-dev archives may provide more insight here, as 
well. Finally the FOP Development: General Information page[4] has even 
more information.

It will be really helpful if you give this details.
thanks and regards,
bala
I hope this helps you find what you are looking for. We welcome 
contributors, so if you are interested in contributing, please let us 
know.

On a side note, I'll probably be adding a link to the 
[EMAIL PROTECTED] mailing list to our FOP Resources page. I see 
you already have posts from some of our committers there.

[1]
http://xml.apache.org/fop/compliance.html
[2]
http://xml.apache.org/fop/maillist.html
[3]
http://xml.apache.org/fop/status.html
[4]
http://xml.apache.org/fop/dev/
Web Maestro Clay
--
Clay Leeds - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: fo failed to process Unicode CJK in servlet

2004-11-09 Thread Ma, Liang
But I checked the jar file against class loader order, couldn't find any
clues yet.

Thank you Pietschmann for your help. 


Liang MA
Software Analyst
--
RADARSAT Mission Control Centre
6767, route de l'Aeroport
Saint-Hubert, Quebec
J3Y 8Y9 Canada
Tel: (450) 926-5099
Fax: (450) 926-5127
---




-Original Message-
From: J.Pietschmann [mailto:[EMAIL PROTECTED]
Sent: November 6, 2004 6:27 AM
To: [EMAIL PROTECTED]
Subject: Re: fo failed to process Unicode CJK in servlet


Ma, Liang wrote:
 Now here is another minor problem. Every time when I first run the servlet
 to generate a pdf file after rebooting tomcat or leaving it for a couple
of
 days, it gives me the following exception. Then I run it again, it works
 fine. Looks like there is something missing to initialize fop in my
servlet.
 root cause 
 
 java.lang.NullPointerException
   at org.apache.fop.apps.Service.providers(Driver.java:597)

Ah, the dreaded class loader problem.
Actually, I don't understand class loading in web apps well enough
to point you to a solution. You might ask this on an appropriate
Tomcat list (be prepared for getting flamed for using code which
is not web app ready)

J.Pietschmann

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

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



Re: XSL-FO Specification

2004-11-09 Thread Clay Leeds
On Nov 9, 2004, at 8:24 AM, Clay Leeds wrote:
snip
On a side note, I'll probably be adding a link to the 
[EMAIL PROTECTED] mailing list to our FOP Resources page. I see 
you already have posts from some of our committers there.

[1]
http://xml.apache.org/fop/compliance.html
[2]
http://xml.apache.org/fop/maillist.html
I see you're already on this page! :-) I'll be adding you (and the 
other Mailing Lists to the FOP Resources page.

[3]
http://xml.apache.org/fop/status.html
[4]
http://xml.apache.org/fop/dev/
Web Maestro Clay
--
Clay Leeds - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]