It seems that this is a most clear way for
me. Unfortunately, I’m not so familiar with some concepts that you said. Do
you know any document that a little more explain about this way & SpreadsheetML, transformer.
Thanks
Farid
-Original Message-
From: [EMAIL PROTECTED]
[mail
I think you will find the following
XSL snippet useful (I think it does exactly what you want):
Hi guys,I need to put some content into columns dynamically with XSL-FO. I've a template called AnswerKeySection which can have one or more AnswerKeyQuestions. Now I need them arranged like 3 AnswerKeyQuestions into 1 row. So I want something like Question1 Question2 Question3 Questio
An additional update to my testing:
After reading the spec, I thought of trying to make the image a fixed
width, so I tried
That makes images less than 5.5 inches wide be 5.5 inches wide, but the
PDF file created by FOP still blows up when it encounters images larger
than 5.5 inches wide.
T
Hi, Andreas,
> Try 396 (= 5.5in at 72dpi), unless you're overriding the
> default resolution of course...
Yup. I caught that right after I posted that message. I used to use 96 dpi
screen captures (at a previous job), but I use 72 dpi these days.
> See above: If you're not overriding the defaul
> so I'll let you know more detail soon (later today).
I had to add width="100%" to my fo:table instructions to avoid a warning
message.
I'm more than a bit of a purist (and a perfectionist, too), so I don't
think I'm done coding until I get 0 warnings. So, 0.90alpha1 worked on
most of my file
Charles Murphy wrote:
javax.xml.transform.TransformerException: Had IO Exception with stylesheet
file: .\report_drivers\Includes.xsl
The Java library had problems accessing the file Includes.xsl.
Check whether you can open the file with some other tool (you
seem to run Windows, try Notepad). T
On Dec 9, 2005, at 23:19, [EMAIL PROTECTED] wrote:
Hi Jay,
I wrote an extension function in Java for Saxon that gives me the
width
(and height, but that's less relevant) of an image. Then, if the
width is
greater than 5.5 inches (the space I have available for screen
shots in
this documen
I wrote an extension function in Java for Saxon that gives me the width
(and height, but that's less relevant) of an image. Then, if the width is
greater than 5.5 inches (the space I have available for screen shots in
this document format), the XSLT adds the content-width="scale-to-fit"
attribu
I finally got the danged thing to download from the svn repo. Took me all day
to figure out how to get around our doggone proxy. I'm going to try building
it and see if that will fix my problem. In the interim if somebody could help
me with an algorithm I'd be ever so grateful. I'm an ameture at
On Dec 9, 2005, at 20:28, [EMAIL PROTECTED] wrote:
Are you using some kind of special parser? Or is this maybe a bug
in my fop version?
My configuration:
Errmm, you're right again. Sorry, no that's not it... By testing, I
meant running the XSLT with an XML corresponding to the SAX events
y
Ok, I've been toiling over this for far too long and I'm 'bout to be fired as
a result. I really need some help. My report works as follows. Depending on
what option the report runs with there will be nested elements
representing the layout of the data respective to the UI selection. each
grou
Are you using some kind of special parser? Or is this maybe a bug
in my fop version?
My configuration:
Servlet:
handler.startElement("", "", "root", atts);
handler.startElement("", "", "Hello", atts);
handler.characters("Hello".toCharArray(), 0, "Hello".length());
handler.endElement("", "", "He
Yeah, I tried just running the raw XSL-FO through and still got an out of
memory. I've also had the biggest problem getting the SVN source to build. If
someone could check it out and send it to me in an archive (any archive type,
I run Linux) I'd appreciate it. You see This is my first time usin
On Dec 9, 2005, at 20:04, Andreas L Delmelle wrote:
On Dec 9, 2005, at 19:56, [EMAIL PROTECTED] wrote:
No offense taken ;o) Yes, I did correct the mistake.
Arrgh, *my* mistake...
or
or
instead of match="/"
Phew! Finally :-)
Andreas
-
On Dec 9, 2005, at 19:56, [EMAIL PROTECTED] wrote:
No offense taken ;o) Yes, I did correct the mistake.
Arrgh, *my* mistake...
or
should do the trick.
Tested and confirmed.
Cheers,
Andreas
-
To unsubscribe, e-mail: [E
No offense taken ;o) Yes, I did correct the mistake.
Fo without input looks like this:
http://www.w3.org/1999/XSL/Format";
xmlns:xdt="http://www.w3.org/2004/07/xpath-datatypes";
xmlns:fn="http://www.w3.org/2004/07/xpath-functions";
xmlns:xs="http://www.w3.org/2001/XMLSchema";>
fo with inpu
On Dec 9, 2005, at 19:36, [EMAIL PROTECTED] wrote:
Hi,
for this test I used the stylesheet with the xsl:for-each tag. I
was hoping
the transformation would pick up the xml tag with the input.
BTW: What do you mean by the FO not containing any xml input? Is
there nothing in the FO at all,
Hi,
for this test I used the stylesheet with the xsl:for-each tag. I was hoping
the transformation would pick up the xml tag with the input.
I'm also 100% clueless...
cheers,
Pete
> --- Ursprüngliche Nachricht ---
> Von: Andreas L Delmelle <[EMAIL PROTECTED]>
> An: fop-users@xmlgraphics.apach
On Dec 9, 2005, at 18:41, [EMAIL PROTECTED] wrote:
Pete,
I just added a root node. But it has no effect on the
transformation both
the fo and pdf do not conatain any xml input. It seems the xsl
tranformation just ignores the "hello" tag.
Is that the stylesheet with or without the xsl:for-ea
Hi,
I just added a root node. But it has no effect on the transformation both
the fo and pdf do not conatain any xml input. It seems the xsl
tranformation just ignores the "hello" tag.
cheers,
Pete
> --- Ursprüngliche Nachricht ---
> Von: Andreas L Delmelle <[EMAIL PROTECTED]>
> An: fop-users@x
On Dec 9, 2005, at 18:03, [EMAIL PROTECTED] wrote:
Hi Peter,
It seems that the source of the evil bug is not the typo but the
for-each
tag like Andreas suggested. I removed it and voilá some output on the
screen. I looked at the fo document and it seems ok. So back to the
orginal
question
Well, now I'm investigating how to get the content-width of the image and
see if that exceeds the content-width of the content rectangle that will
hold the image.
Support for the scale-down-to-fit value for the content-width property
would work nicely. If I were to request an enhancement, that
Has anyone seen this error before
[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
[ERROR] javax.xml.transform.TransformerConfigurationException:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException: Had IO Exception with stylesheet
file: .\report_driv
Yeah, that's more or less what the formatter should be doing. The
problem is that i-f-o and e-g both only create a Knuth box which has a
fixed size. No shrink/stretch there, yet.
On 09.12.2005 17:47:13 Andreas L Delmelle wrote:
> On Dec 9, 2005, at 17:33, Jeremias Maerki wrote:
>
> >
> > On 09.12
Hello,
thanks for the many comments. I corrected the typo in the hello tag.
This minimal configuration was my intention in the first place because the
only thing I need, is to establish the pipeline from the creation of xml
document to the pdf output.
It seems that the source of the evil bug is n
On Dec 9, 2005, at 17:33, Jeremias Maerki wrote:
On 09.12.2005 17:06:00 JBryant wrote:
The trouble is that I don't want images that are less than the
width of
the page to be expanded to the width of the page. The old behavior of
scaling images that exceeded the size of the container to fit t
On 09.12.2005 17:06:00 JBryant wrote:
> I did read the upgrading page. It doesn't mention scaling.
Well, it mentions instream-foreign-object and a Buzilla entry that
explains a lot there. But maybe we need to make that a little clearer.
Sounds like that FAQ Roland suggested might yet be necessary
On Dec 9, 2005, at 17:26, Andreas L Delmelle wrote:
On Dec 9, 2005, at 15:33, Clifton Craig wrote:
Why is it that I would get the same OutOfMemoryError on the XEP
personal edition?
That's what has me wondering if it's really something wrong with
my FO syntax or
my stylesheet.
It has me won
On Dec 9, 2005, at 15:33, Clifton Craig wrote:
Why is it that I would get the same OutOfMemoryError on the XEP
personal edition?
That's what has me wondering if it's really something wrong with my
FO syntax or
my stylesheet.
It has me wondering about one section in my stylesheet that matches
I did read the upgrading page. It doesn't mention scaling.
> 1. A content-width="scale-to-fit" will do what you want.
Well, no, it won't, actually. The trouble is that I don't want images that
are less than the width of the page to be expanded to the width of the
page. The old behavior of scali
Hi J
You should really read the "Upgrading" document. It's all there:
http://xmlgraphics.apache.org/fop/0.90/upgrading.html
Both problems are easily solvable:
1. A content-width="scale-to-fit" will do what you want. It was 0.20.5
that was wrong here. BTW, adding the "scale-to-fit" will make the
Paul,
what exactly is the problem? Are you just trying to control the font
name you can using inside XSL-FO? If yes, you can ignore what font name
is written into the font metrics. Only the font name you specify in the
font configuration (userconfig.xml) is relevant.
On 09.12.2005 16:06:43 Paul M
Hi, Jeremias,
I have run 0.90alpha1 on a couple of my larger documents, and I have
bumped into only two issues (one of which causes real trouble for me):
1. Images are not scaling to fit the space in which they are placed. I can
live with that, because I can go scale the images by hand before F
On 09.12.2005 16:00:26 Peter B. West wrote:
> Thanks for that. I have tried OpenOffice Draw, exporting to SVG, but
> Gimp doesn't like the result (it complains that no image size is specified.)
This is the raw SVG I get from Inkscape for a rounded rect. I'd play a
little with the values there,
Hi Andreas,
Sorry, that was a typo in my mail. It was the correct option -fn I
used.
I just double-checked by running the command again to make sure.
... what name you *do* get as a result?
Well, for example, if I try it with Letter Gothic Bold, and use the
option:
-fn "LetterGothicBold"
Thanks for that. I have tried OpenOffice Draw, exporting to SVG, but
Gimp doesn't like the result (it complains that no image size is specified.)
In practiavl terms, do I need a border around the border-line I am
drawing, so that I must make the target are a little larger to
accomodate the bo
Thank you all so much. I have another question though. Why is it that I would
get the same OutOfMemoryError on the XEP personal edition? That's what has me
wondering if it's really something wrong with my FO syntax or my stylesheet.
It has me wondering about one section in my stylesheet that mat
The layout engine of 0.90alpha1 works differently. It's a bit difficult
to compare the two versions. But I'd have to say the same optimization
is currently not possible in 0.90/Trunk unless we extend the breaking
algorithm to support a first/best fit strategy so the objects can be
released early (i
Or you could use GLIPS Graffiti Editor which is a Java SVG editor. Create the
SVG in GLIPS and pull it into your stylesheet.
--
Clifton C. Craig, Software Engineer
[EMAIL PROTECTED]
On Friday 09 December 2005 5:40 am, Jeremias Maerki wrote:
> SVG images work nicely as background images. Just use
You know what? Is the patch already in the new Alpha release? Cause if it is
then it's not worth my time applying it to FOP-0.20.2. I've already tried my
stylesheet with the alpha version and I still have the memory issue.
On Thursday 08 December 2005 10:17 pm, Andreas L Delmelle wrote:
> On Dec
SVG images work nicely as background images. Just use a tool like Adobe
Illustrator, CorelDraw or even Inkscape to create the SVG with a rounded
rectangle. The only problem is that you need to know the exact size of
the rectangle beforehand as you can't scale background images. Some
manual tweaking
I need to draw a rounded rectangle around an area on a document.
Setting the background-image property seems to be the way to go. What
tools are best for generating the image? Background-image limits me
pretty severely in what I can specify.
Peter
---
[This E-mail has been scanned for viruse
I think I need to correct myself. The way the line number information is
implemented it's only available during FO tree building and validation
but not after that. I was just working on reporting overflow conditions
during layout where I wanted to make sure that as much context
information is avail
I've just fixed that. Thanks for spotting it.
http://svn.apache.org/viewcvs?rev=355401&view=rev
As a little "thank you" I've implemented that XSLT parameter you've
suggested last month. See:
http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/200511.mbox/[EMAIL
PROTECTED]
http://svn.ap
Roland,
that's exactly the kind of stuff I wanted to hear. Thank you very much.
Some comments inline...
On 09.12.2005 00:57:47 Roland Neilands wrote:
> Jeremias,
>
> I haven't test it thoroughly yet, but you asked, so but here's what I've
> seen:
>
> 1. Images are not scaled & overrun block-co
46 matches
Mail list logo
