RE: Problem with conditionnal page sequences

2004-02-11 Thread Kielen, Agnes
Hi Simon,
You're confusing several things I think. First you're not only using XSL-FO but 
also XSLT, seen to your xsl:if statements. Furthermore you try to print tags in 
stead of elements. Printing only a start tag or an end tag is not possible in 
XSLT.

When you do something like:
xsl:if test=SOUSTHEME != following-sibling::FICHE[1]/SOUSTHEME 
!-- First I close the current sequence  -- 
/fo:flow  --  
/fo:page-sequence 
  snip/
/xsl:if 
You're XML is not wellformed anymore and no XML-Parser will accept it. It 
doesn't even reach the XSLT-parser or FO-parser. That's why you get the 
following error from the XML-Parser (probably Xerces).
[Fatal Error] XMLToFO_CD.xsl:1295:3: The element type xsl:if must be 
terminated by the matching end-tag /xsl:if. 

XSL-Fo has the concept of conditional page masters 
http://www.dpawson.co.uk/xsl/sect3/pagelayout.html#d10268e184, but I wonder if 
this is what you need. Why do you need a new page master sequence for you're 
SvG. Why can't you include it in the new one. Maybe on a new page or something 
like that.

Cheers,
Agnes





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



Re: Misaligned text columns

2004-02-11 Thread Chris Bowditch
[EMAIL PROTECTED] wrote:
I'm trying to set a document in two columns using fop (0.20.5).
Unfortunately, when the two columns do not have exactly the same amount of
material, the baselines of the first lines of the two columns do not align.
They can be as much as 1.5 lines off.
I cant think of a workaround in the general sense.
You could try placing your content into a table, starting a new row for 
each paragraph and using keep-together=always on the rows. That way 
the top of each column would always start with a new paragraph and the 
baseline alignment may be improved.

Another technique is to try to guess when a column has been filled and 
place break-after=column at appropriate places in the XSL-FO during 
XSLT processing. Very messy I know...

fop does not seem to have implemented .minimum and .maximum (or
.conditionality or .precedence) in space-before and space-after, so the
vertical spaces in the columns are constant rather than mutable. This seems
to be at least part of the problem; leastwise, mucking about with 'stretch'
and 'shrink' values doesn't seem to help..
Neither does giving a value to display-align in the region-body make any
difference.
display-align is only implemented in block-containers and table cells.
I'm rather mystified, since my reading of the XSL spec and Pawson's book
gives me no clue how I could achieve this effect if I wanted to.
They wouldnt give you any pointers to solve this problem, because they 
are written in general XSL-FO terms, with a fully compliant XSL-FO 
formatter in mind. In other words they are not written specifically for 
FOP users.

Chris

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


fo:leader pattern=dots

2004-02-11 Thread Abhijit Junnare
Hello!
I am using fo:leader with pattern=dots the fo code
is like this

fo:leader leader-pattern=dots 
rule-thickness=2pt
leader-length=100%
start-indent=10pt/

When I generate a PDF the rule is shown in PDF with
dotted pattern. However when I print the PDF the rule
is NOT AT ALL printed. This does not happen if I use
leader-pattern=rule. I am using fop version 0.20.5
and I am embedding custom fonts with FOP.

Any clues why this is happening?
Abhi

__
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

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



PCL is ok, PS is wrong orientation

2004-02-11 Thread Nicholson, Robb
Title: PCL is ok, PS is wrong orientation





I have some server side Java code that does some FOP transformations (fop 0.20.5) and prints the resulting output to a printer. 

When I perform the transforation going to a PDF or PCL file, everything comes out fine. (The stylesheets I am using defines the page to be landscape). I get a landscape page with all my data on there. 

I couldn't get the PCL to print from our development Linux machine, however, so I switched from PCL to PostScript rendering. Now it tries to print the page in Portrait, cutting off the right side of the output.

At first I thought it was the Java Print Service API or the print driver, but I downloaded a PostScript viewer to look at the rendered output, and fop is doing this.


Here's a sample of my page definition if that's the culprit:


fo:simple-page-master master-name=A4 page-width=297mm page-height=210mm margin-top=0.5in margin-bottom=0.0in margin-left=0.5in margin-right=0.5in


Thanks for any insight!
Robb





RE: leader pattern=dots

2004-02-11 Thread Andreas L. Delmelle
 -Original Message-
 From: Abhijit Junnare [mailto:[EMAIL PROTECTED]

 Hello!
 I am using fo:leader with pattern=dots the fo code
 is like this

 fo:leader leader-pattern=dots
 rule-thickness=2pt
 leader-length=100%
 start-indent=10pt/

 When I generate a PDF the rule is shown in PDF with
 dotted pattern. However when I print the PDF the rule
 is NOT AT ALL printed.

Strange... so it does show up in Acrobat, but not when you print it from
there?
(seems more like Acrobat-weirdness)

 This does not happen if I use leader-pattern=rule.
snip /
 Any clues why this is happening?

The only thing that comes to mind, is to try and use 'leader-pattern-width'
for dots, instead of 'rule-thickness'... although I'm not at all sure
whether this is the cause of the strange behaviour (you never know --maybe
some tiny difference in PDF code when rendered?)


Cheers,

Andreas


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



RE: leader pattern=dots

2004-02-11 Thread Abhijit Junnare
Tried with 'leader-pattern-width' but still it shows
up in acrobat but will NOT PRINT when printed. seems
very strange to me too. any more things come to
anyones mind? 

  When I generate a PDF the rule is shown in PDF
 with
  dotted pattern. However when I print the PDF the
 rule
  is NOT AT ALL printed.
 
 Strange... so it does show up in Acrobat, but not
 when you print it from
 there?
 (seems more like Acrobat-weirdness)
 
  This does not happen if I use
 leader-pattern=rule.
 snip /
  Any clues why this is happening?
 
 The only thing that comes to mind, is to try and use
 'leader-pattern-width'
 for dots, instead of 'rule-thickness'... although
 I'm not at all sure
 whether this is the cause of the strange behaviour
 (you never know --maybe
 some tiny difference in PDF code when rendered?)
 
 
 Cheers,
 
 Andreas
 
 

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


__
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

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



Re: leader pattern=dots

2004-02-11 Thread Clay Leeds
As I recall, there were problems getting fo:leader output to show 
anything besides rule under -awt  -print. PDF correctly 
outputs/displays 'dots' and other types, but AWT does not. I checked in 
the fop-user archives (this has been discussed before), but I had 
trouble finding the thread, sorry. Perhaps someone else can shed more 
light on this, and provide the thread.

Clay
On Feb 11, 2004, at 11:39 AM, Abhijit Junnare wrote:
Tried with 'leader-pattern-width' but still it shows
up in acrobat but will NOT PRINT when printed. seems
very strange to me too. any more things come to
anyones mind?
When I generate a PDF the rule is shown in PDF
with
dotted pattern. However when I print the PDF the
rule
is NOT AT ALL printed.
Strange... so it does show up in Acrobat, but not
when you print it from
there?
(seems more like Acrobat-weirdness)
This does not happen if I use
leader-pattern=rule.
snip /
Any clues why this is happening?
The only thing that comes to mind, is to try and use
'leader-pattern-width'
for dots, instead of 'rule-thickness'... although
I'm not at all sure
whether this is the cause of the strange behaviour
(you never know --maybe
some tiny difference in PDF code when rendered?)
Cheers,
Andreas

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


RE: PCL is ok, PS is wrong orientation

2004-02-11 Thread Nicholson, Robb
Title: PCL is ok, PS is wrong orientation



By 
changing the definition of the printer in Linux we got PCL to print, so this is 
a moot point. Thanks anyways! 
--Robb


-Original 
Message-From: Nicholson, Robb 
[mailto:[EMAIL PROTECTED]Sent: Wednesday, February 11, 
2004 11:38 AMTo: '[EMAIL PROTECTED]'Subject: PCL is 
ok, PS is wrong orientation

  I have some server side Java code that does some FOP 
  transformations (fop 0.20.5) and prints the resulting output to a printer. 
  
  When I perform the transforation going to a PDF or PCL file, 
  everything comes out fine. (The stylesheets I am using defines the page to be 
  landscape). I get a landscape page with all my data on there. 
  I couldn't get the PCL to print from our development Linux 
  machine, however, so I switched from PCL to PostScript rendering. Now it tries 
  to print the page in Portrait, cutting off the right side of the 
  output.
  At first I thought it was the Java Print Service API or the 
  print driver, but I downloaded a PostScript viewer to look at the rendered 
  output, and fop is doing this.
  Here's a sample of my page definition if that's the 
  culprit: 
  fo:simple-page-master master-name="A4" page-width="297mm" 
  page-height="210mm" margin-top="0.5in" margin-bottom="0.0in" 
  margin-left="0.5in" margin-right="0.5in"
  Thanks for any insight! Robb 
  


Re: PCL is ok, PS is wrong orientation

2004-02-11 Thread Jeremias Maerki
Good to hear. Anyway, if you still want this information, here's a
couple of workarounds:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25882


On 11.02.2004 22:50:20 Nicholson, Robb wrote:
 By changing the definition of the printer in Linux we got PCL to print, so
 this is a moot point. Thanks anyways! 
 
 --Robb
  
  
  -Original Message-
 From: Nicholson, Robb [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, February 11, 2004 11:38 AM
 To: '[EMAIL PROTECTED]'
 Subject: PCL is ok, PS is wrong orientation
 
 
 
 I have some server side Java code that does some FOP transformations (fop
 0.20.5) and prints the resulting output to a printer. 
 
 When I perform the transforation going to a PDF or PCL file, everything
 comes out fine. (The stylesheets I am using defines the page to be
 landscape). I get a landscape page with all my data on there. 
 
 I couldn't get the PCL to print from our development Linux machine, however,
 so I switched from PCL to PostScript rendering. Now it tries to print the
 page in Portrait, cutting off the right side of the output.
 
 At first I thought it was the Java Print Service API or the print driver,
 but I downloaded a PostScript viewer to look at the rendered output, and fop
 is doing this.
 
 
 Here's a sample of my page definition if that's the culprit: 
 
 fo:simple-page-master master-name=A4 page-width=297mm
 page-height=210mm margin-top=0.5in margin-bottom=0.0in
 margin-left=0.5in margin-right=0.5in


Jeremias Maerki


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