Bertrand Delacretaz wrote
The whole point of the StructureHandler interface is to be able to
reuse FOP's frontend for structure-based renderers.
The impact of StructureHandler on the standard FOP output formats
(PDF mostly) is minor, but it allows the FOP pipeline to branch
cleanly, after
jeremias2003/06/23 01:36:13
Modified:src/documentation/content/xdocs pdfencryption.xml
Log:
Added instructions for embedding.
Revision ChangesPath
1.6 +69 -1 xml-fop/src/documentation/content/xdocs/pdfencryption.xml
Index: pdfencryption.xml
Le Lundi, 23 juin 2003, à 10:35 Europe/Zurich, J.U. Anderegg a écrit :
...
How do you plan to handle RTF styles?
In jfor we defined an extension to XSL-FO (the jfor-style attribute)
to control RTF styles.
Another way would be to recognize sets of attribute values in the input
XSL-FO and map
Bertrand Delacretaz wrote:
...
How do you plan to handle RTF styles?
In jfor we defined an extension to XSL-FO (the jfor-style attribute)
to control RTF styles.
I think some form of extension is needed as (AFAIK) the concept of
styles does not exist in XSL-FO, as it is meant for printed
Le Lundi, 23 juin 2003, à 12:08 Europe/Zurich, J.U. Anderegg a écrit :
Bertrand Delacretaz wrote:
...In jfor we defined an extension to XSL-FO (the jfor-style
attribute)
to control RTF styles
(1) This is not a FOP extension, but rather a fundamental change of the
XSL-FO language, which does
On 6/21/2003 9:16 AM, Victor Mote wrote:
OK. The web site repository has now been updated. It should go live
sometime in the next 6 hours.
Yahoo! My name in lights (and my son's too! ;p) We just celebrated his
birthday this weekend. He turned 1 and got to swim with 4 girls in his
new kiddie
Nice idea, but there's a problem. The xsl namespace gets filtered out by
the XSLT engine, or IOW expanded to the FO attributes before they reach
FOP. FOP never sees anything with the xsl: prefix.
On 23.06.2003 18:51:45 Clay Leeds wrote:
Forgive my intrusion, and perhaps this is not related, or
On 6/23/2003 10:19 AM, Jeremias Maerki wrote:
Nice idea, but there's a problem. The xsl namespace gets filtered out by
the XSLT engine, or IOW expanded to the FO attributes before they reach
FOP. FOP never sees anything with the xsl: prefix.
Does this mean that just about every fo:block in the
On 23.06.2003 19:33:23 Clay Leeds wrote:
On 6/23/2003 10:19 AM, Jeremias Maerki wrote:
Nice idea, but there's a problem. The xsl namespace gets filtered out by
the XSLT engine, or IOW expanded to the FO attributes before they reach
FOP. FOP never sees anything with the xsl: prefix.
Does
I have done so now. I've added a new (sub)page to the Wiki to avoid
making the FOPAvalonization page even longer.
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAvalonization/AltAPIProposalJM
While writing down my thought about the API I have come to the
realization that I cannot make up my
Jeremias Maerki wrote:
I have done so now. I've added a new (sub)page to the Wiki to avoid
making the FOPAvalonization page even longer.
Interesting proposal. One thing I'm still missing:
- Renderer: You guys hate me for that, I know, but I still refuse to
give it so much visibility in these
Jeremias Maerki wrote:
Speaking of which, how does the file created by '-at' differ from the
file generated by running xalan.bat?
That's the Area Tree XML: The layouted pages serialized to a proprietary
XML format. It's only interesting for debugging purposes (in layout
engine development).
And
On 23.06.2003 21:28:56 J.Pietschmann wrote:
Jeremias Maerki wrote:
I have done so now. I've added a new (sub)page to the Wiki to avoid
making the FOPAvalonization page even longer.
Interesting proposal. One thing I'm still missing:
- Renderer: You guys hate me for that, I know, but
13 matches
Mail list logo
