Re: PCL is ok, PS is wrong orientation
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: > > 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]
RE: PCL is ok, PS is wrong orientation
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: Thanks for any insight! Robb
Re: leader pattern="dots"
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". 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"
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". > > > 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"
> -Original Message- > From: Abhijit Junnare [mailto:[EMAIL PROTECTED] > > Hello! > I am using fo:leader with pattern="dots" the fo code > is like this > > 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". > 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]
PCL is ok, PS is wrong orientation
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: Thanks for any insight! Robb
fo:leader pattern="dots"
Hello! I am using fo:leader with pattern="dots" the fo code is like this 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]
Re: Misaligned text columns
[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]
Misaligned text columns
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. 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. 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. Is there any help for this? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Problems with Saxon -> FOP?
Hi, it turned out that the encoding had nothing to do with the error. As you stated, something seems to be messed up with the DOM. I debugged into the FOP source, it chokes after processing the attributes of the fo:root element, for any reason the element name and its namespace uri always is null then. Though using SAX would surely be worth the effort, in the current project state the FO tree is needed for post-processing. I'll post any new perceptions i may discover. greets michael -Ursprüngliche Nachricht- Von: J.Pietschmann [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 10. Februar 2004 20:52 An: [EMAIL PROTECTED] Betreff: Re: Problems with Saxon -> FOP? Rauh, Michael wrote: > I'm running XSLT transformations from within Java and put the result DOM into > FOP's AWTRenderer. ... That's all working fine with Xalan (from the JDK) and > jd.xslt. But with Saxon 6.5.3 and Saxon 7.8, FOP throws > NullPointerExceptions. > Here's the ouput when using Saxon-6.5.3: ... > [ERROR] Unsupported element encountered: null (Namespace: null). Source > context: unavailable I use Saxon with FOP all the time. However, I use SAX to pipe the transformation result to the FOP driver (see http://xml.apache.org/fop/embedding.html#ExampleXML2PDF) I guess there is a problem with the DOM or the DOM walker implementation, or perhaps you screwed the DOM while postprocessing. If you dont process the transformation result, I recommend using SAX, it's more ressource friendly anyway (less memory). 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: Problem with conditionnal page sequences
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: > > > <-- > > 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-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: Problem with conditionnal page sequences
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > But now, my favourite graphist gave me beautifull SVG files to > integrate between the differents categories... So I thought i'd be > able to make something like a "conditionnal page sequences" to > insert this SVG between my different categories... I tried this code : > > > > This is the flaw in the approach. XML in general (therefore also XSLT) will never allow you to start an element at some place and put its end-tag in a different element. (like you can do with HTML) You have to to map the structure to page-sequences without use of an xsl:if in this particular way... Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with conditionnal page sequences
Hello, I am using FOP for a while, and that's a pretty good tools to generate PDF files... I usually don't have any problem using XSL:FO, but I can't find a way to integrate conditionnal page sequences. Here is the example file : it might help you to understand my problem better. http://www.tatouage.fr/temp/cata.pdf In this catalog, I detect the categories changements and then insert a break-after attribute to my tag so I can insert a blank page between the different categories. The code for that was pretty simple : odd-page But now, my favourite graphist gave me beautifull SVG files to integrate between the differents categories... So I thought i'd be able to make something like a "conditionnal page sequences" to insert this SVG between my different categories... I tried this code : I thought something like that should work, but it doesn't, here is the FOP output : [Fatal Error] XMLToFO_CD.xsl:1295:3: The element type "xsl:if" must be terminated by the matching end-tag "". I'm sure there is a way to answer my need with FOP, but I can't wonder how to do that... If someone have an idea, it would be really appreciated (I don't have so much time to integrate these graphical stuff). Just a precision : I am obligated to use another page-sequence cause I want a full blank page for my SVG stuff, I don't want to keep the static contents (page number, etc...) on this pages. Thanks forward, please excuse my poor english ! ;o) -- Simon OUALID -- ARTE FRANCE Analyste Programmeur [EMAIL PROTECTED] Tél : 01.55.00.70.70 Fax : 01.55.00.73.89 --
Re: How to capitalize text ???
Of course, if you're only using the string in one place, or if you always want it capitalized, then you should be able to do the conversion in your database SQL to begin with: select upper(column_name) from table_name; Glen - Original Message - From: "Dang Minh Phuong" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 10, 2004 5:08 AM Subject: RE: How to capitalize text ??? > It works. Thank you very much. > > -Original Message- > From: Wouter de Vaal [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 08, 2004 11:16 PM > To: [EMAIL PROTECTED] > Subject: Re: How to capitalize text ??? > > You should use XSLT for this: > > ABCDEFGHIJKLMNOPQRSTUVWXYZ > > abcdefghijklmnopqrstuvwxyz > > > > > > This will translate all lowercase text in XML to uppercase. > > Wouter > > - Original Message - > From: Dang Minh Phuong > To: '[EMAIL PROTECTED]' > Sent: Monday, February 09, 2004 3:50 AM > Subject: How to capitalize text ??? > > > Hi all, > > I have a text received from the DB and put in xml file. Now I want to > capitalize that text when showing it in PDF using FOP. How can I do that ??? > > Thanks for your help. > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
