Clay Leeds wrote:
While we're on the subject of books and resources for FOP Resources,
here's a couple things to add. One of my previous posts included a list
of good books on XSL-FO (some of which you've listed). Here's a link to
my post.
Victor,
While we're on the subject of books and resources for FOP Resources,
here's a couple things to add. One of my previous posts included a list
of good books on XSL-FO (some of which you've listed). Here's a link to
my post.
http://marc.theaimsgroup.com/?l=fop-userm=104463666315238w=2
Victor Mote wrote:
BTW, I think it is good to learn new technology on the job. In fact, having
a real-world problem is about the only way I can learn anything. However,
you do want to have your books at hand as you do it, which is probably what
you meant anyway.
I meant: It is bad to be thrown at
J.Pietschmann wrote:
Buy Mike Kay's book on XSLT (ISBN 1861005067) and perhaps
D.Pawsons book about XSLFO (ISBN 0596003552) and work through
the examples. It is usually unwise to learn a new technology on
the job.
Victor: as usual, something for the ressources page?
Good idea -- I just
Victor Mote wrote:
Good idea -- I just committed a change that has both of these. I
also added
the O'Reilly book XSLT Cookbook, for which I have seen some
good reviews.
I hadn't heard about that one until this week. I hope to publish the web
site this weekend.
Sorry. I meant to throw the
Eric Pement wrote:
So I no longer get the error message. However, the content
of the fo:blocks is now empty, and whatever is in the Title
tags is being ignored and not printed in the output document.
All Xalan did was to confirm that nothing is printed in the
output. Problem is, it didn't
Eric Pement wrote:
file and I'm at a novice level in all of this. So I'd like to build the
.XSL file incrementally, seeing if I can print single tags from the .XML
file, and then successively adding tags until I have a generalized
solution that will work on whatever .XML file we feed it which
Eric Pement wrote:
Right now, I'm getting an error message, fo:flow must contain block-level
children, which I don't know what to do with.
It means exactly what it says.
fo:flow flow-name=xsl-region-body
xsl:apply-templates select=Title /
/fo:flow
. . .
xsl:template match=[EMAIL
At 12:25 PM 4/25/2003 -0600, Victor Mote wrote:
Eric Pement wrote:
Right now, I'm getting an error message, fo:flow must contain block-level
children, which
I've fixed the error message, by changing
fo:flow flow-name=xsl-region-body
xsl:apply-templates select=Title /
/fo:flow
Eric Pement wrote:
So I no longer get the error message. However, the content
of the fo:blocks is now empty, and whatever is in the Title
tags is being ignored and not printed in the output document.
All Xalan did was to confirm that nothing is printed in the
output. Problem is, it didn't tell me
10 matches
Mail list logo
