On 02/23/02 19:44, David Wood [EMAIL PROTECTED] wrote:
On Sat, 23 Feb 2002, Carlos wrote:
While it is cumbersome and I would prefer not to, I can make an extra step
and unescape the the tags before FOP sees the XML; then I can use the
template to convert them into blocks and recover my paragraph breaks.
One solution would be to use another XSLT stylesheet to do this: Have an
XSLT stlyle sheet that detects paragraphs and copies everything else to the
target document.
Hmm... Do you mean do two separate processing steps - i.e. one with a
secondary XSLT processor, and then the next with FOP? Not such a bad
thought. :)
As a matter of fact, you can incorporate both XSLT and FO on the same
stylesheet. A good example of how that is done is Norman Walsh's Docbook XSL
and XSL:FO stylesheets. If Interested you can download them from
http://sourceforge.net/projects/docbook
You can do it with one or two steps, depending on maintenance needs and how
have you structured your documents and stylesheets
Obviously it would be nice if the linefeed-treatment attribute worked and
I could skip this altogether, but c'est la vie...
It's part of the standard so it'll be supported before 1.0 is released. Any
help is welcome
I would be eager to contribute to this (excellent) project - but I
understand that the team is engaged in a rewrite, so any work on the
current Java code would be lost. Meanwhile, I have the vague impression
the rewrite is not far along enough yet for a stranger like me to jump in
and do more good than harm.
Perhaps I am mistaken?
I'll defer to others for the answer to that, but my thought is that it's
always better to have something to modify rather than starting from scratch.
My other issue right at the moment has to do with recreating
baseline-to-basline spacing, which I'm starting to think _might_ be
possible in FO, but can't be done in FOP (because line-height and/or
text-altitude don't seem work on inline or character elements).
If you can dedicate budget to it, look at RenderX, they are pricey but
support more of the XSL standard than FOP does at this time
Thank you very much for this advice. I have looked at RenderX/XEP; they do
have a very impressive degree of completeness, and you are right, they are
extremely expensive. As I am targeting a dual-CPU Wintel server, a XEP
licence would run me 10 large, well beyond what I can afford. :(
It's OK. Both of these (no newlines and no baseline-to-baseline) are an
inconvenience, but they are problems I can work around.
-David
--
Carlos E. Araya
---+ WebCT Administrator/Trainer
P | California Virtual Campus
- | C/O De Anza College
G | 21250 Stevens Creek Blvd
---+ Cupertino, CA 95014
email [EMAIL PROTECTED]
web http://www.cvc1.org/ (work)
http://www.silverwolf-net.net (personal)
phone 408 257 0420 (work)
PGP Fingerprint:E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
We cannot put off living until we are ready. The most salient
characteristic of life is its coerciveness: it is always urgent, 'here and
now' without any possible postponement. Life is fired at us point blank.
Jose Ortega Y Gasset
