Re: FO to RTF
On Friday 26 July 2002 20:05, J.U. Anderegg wrote: . . . RTF is the format of yesterday: better generate MicroSoft Office XML or Open Office XML. Depends on what you're aiming for. RTF is a terrible format, yes, but at least it allows documents to be opened by a fair number of wordprocessors. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: FO to RTF
Hi Peter, I tentatively suggested using XSLT to generate RTF a little while ago, but I had no idea whether it was feasible. The main question would seem to be: is RTF a text-only format or a binary format? Can anyone answer that one for us? AFAIK, everything in RTF can be expressed with text-only characters, and it would certainly be possible to convert XSL-FO to RTF using XSLT. Our choice to use java for the jfor converter was based on better availability of programming and debugging tools. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FO to RTF (new jfor license)
Hello, On Friday 26 July 2002 10:20, Mulet, Jordi wrote: . . . We have started to experiment with jfor (FO-RTF) and we don't know the best path to follow and if there are plans to integrate jfor in FOP as a RTF renderer. . . . Note that the jfor license was recently changed to allow it to an ASF-compatible one, see www.jfor.org for more info. This allows jfor to be distributed with ASF projects. This means that the RTF library part of jfor can be used in binary form as a back-end for FOP (StructureHandler) to generate RTF, without having to maintain two RTF libraries (which would be the case if the jfor RTF code was moved to the FOP codebase). I think this will ease the transition from jfor to FOP for RTF generation, until FOP 1.x is released. -- Bertrand Delacrétaz (codeconsult.ch, jfor.org) buzzwords: XML, java, XSLT, cocoon, mentoring/teaching/coding. disclaimer: eternity is very long. mostly towards the end. get ready. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: CTM - e (tx) and f (ty) divided by 1000
On Sat, 2002-07-27 at 01:40, Kevin O'Neill wrote: Ok, so the millipoints conversion is specific to the xsl:fo to pdf conversion, the fo tree being in millipoints (correct me if I'm wrong). All lengths are in millipoints from the properties, fo tree to area tree. The renderers usually work in points (I think all of them that draw to an output do). So they need to divide by 1000. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [PDF Viewer] Utility request
On Mon, 2002-07-29 at 11:40, RamanaJV wrote: Ralph, Your idea of Fixing the awt renderer is the correct one. After a deep thought, I too came to the conclusion that instead of writing a PDF renderer, if we can tune up the AWT renderer, it will be great. The main problem with AWT renderer now is the heavy memory it uses. We need to find the source of memory drain and tune it. Heavy memory use: - holds onto every page in memory - area tree holds onto fo tree - all images are also held in the area tree and image factory - in general far too much memory is used for many structures Solutions: - separate area tree from fo tree - allow pages to be saved to disk to reduce memory - improve image handling The design for this is mostly implemented in HEAD. (One day I will convince someone to help out with HEAD code) We need to come up with the basic plan for this. Also, we have to first look and summarize the current issues with AWT renderer and step accordingly. Ramana. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: FO to RTF
Bertrand, Thanks for clarifying that. The feasibility of an XSLT transform would be greatly influenced by the complexity of the mappings of properties into RTF structures. If the inheritance model of XSLFO had no ready parallel in RTF, that set of transformations would be a nightmare, I imagine. Peter Bertrand Delacretaz wrote: Hi Peter, I tentatively suggested using XSLT to generate RTF a little while ago, but I had no idea whether it was feasible. The main question would seem to be: is RTF a text-only format or a binary format? Can anyone answer that one for us? AFAIK, everything in RTF can be expressed with text-only characters, and it would certainly be possible to convert XSL-FO to RTF using XSLT. Our choice to use java for the jfor converter was based on better availability of programming and debugging tools. -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: any limitation to generate-id()
Kutz Clemens (PEA-FE2/BA-T) wrote: hmmm. I indeed use the span-attribute in my appendix to list all TT-elements (TT=technical term). To test this I removed all span-attributes in my stylesheet, but the error still exist. any other idea? Well, it could be other undiscovered bug, try to simplify your stylesheet in order to locate it. -- Oleg Tkachenko Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
