cvs commit: xml-fop/docs/xml-docs/fop gethelp.xml
keiron 02/03/19 01:08:56 Modified:docs/xml-docs/fop gethelp.xml Log: fixed a few minor errors, added link to How to Ask Questions the Smart Way Submitted by: Peter S. Housel [EMAIL PROTECTED] Revision ChangesPath 1.2 +6 -2 xml-fop/docs/xml-docs/fop/gethelp.xml Index: gethelp.xml === RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/gethelp.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- gethelp.xml 17 Mar 2002 17:46:15 - 1.1 +++ gethelp.xml 19 Mar 2002 09:08:56 - 1.2 @@ -4,7 +4,7 @@ !-- How to get Help -- document header -titleHow to get Help/title +titleHow to Get Help/title subtitleSolving problems/subtitle authors /authors @@ -15,7 +15,7 @@ ol li pHave a look at the documentation pages on this site. You can find information on how to run FOP, - how to embedd it, how to add custom fonts etc./p + how to embed it, how to add custom fonts etc./p /li li pConsult the jump href=faq.htmlFAQ/jump to see if your question has already been answered before./p @@ -34,6 +34,10 @@ don't forget to supply the version you're using, detailed error messages etc. This makes it easier to help you. The instructions on how to subscribe can be found in the jump href=resources.htmlResources/jump/p /li +li +pYou should probably read ESR's +jump href=http://www.tuxedo.org/~esr/faqs/smart-questions.html;How to Ask Questions the Smart Way/jump/p +/li note pPlease don't use Bugzilla to post questions and please ask on the user mailing list first, if you think you've found a bug./p - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Suggestions for the How to get Help page
Thanks, its fixed (in CVS). On 2002.03.19 00:05 Peter S. Housel wrote: 1. In item 1, the word embed is spelled incorrectly. 2. The word get in the title should probably be capitalized. 3. A link to ESR's How to Ask Questions the Smart Way (http://www.tuxedo.org/~esr/faqs/smart-questions.html) might be helpful. Cheers, -Peter S. Housel- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FO to PDF XSL tranformation
Xalan is implementation of XSLT. Output format is XML, HTML or TEXT. If PDF is TEXT file, I can imagine XSLT script which can transform FO to PDF. Am I right? Therefore I am looking for such fo2pdf.xslt script. What do you think? Is it reasonable? Then I can imagine DocBook to PDF transformation as sequence of two transformations: xxx.dbx docbook2fo.xsl = xxx.fo fo2pdf.xsl = xxx.pdf. Is not it nice? Thanks for your comments. Libor alex wrote: At 17:16 18/03/02, Libor Kramolis wrote: Does anybody know about some XSL tranformation from Formatting Objects to PDF or other formats? FOP is an implementation of part of the XSL spec - so is Xalan, but different parts of the spec. Xalan converts XML to XML, and FOP converts XSL:FO (which is XML) to other formats which usually are not XML. They are both written in Java because the authors like Java :-) Does that help explain things? Alex -- Libor Kramolis, Software Engineer | [EMAIL PROTECTED] NetBeans/Sun Microsystems, XML Project | http://xml.netbeans.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Colon character problematic in xsl:template match=StringContainingColon ??
Joe Sytniak [EMAIL PROTECTED] wrote: I am able to create XSL for normal transformations to HTML just fine. But in order to get XSLFO to work, I must change the names of the 'rs:data' and 'z:row' nodes to something that does not contain a colon charater (ie. rs-data z-row). Such changes should not be necessary. In what sense does XSLFO not work? What are the exact symptoms? Do you get an error message or unexpected results? Is the problem caused by the transformation or during formatting? Did you inspect the intermediate FO? Can you show the relevant parts of your XSLT and source XML (please trim the files down to the problematic parts)? XSLT questions are better asked on the XSL list [EMAIL PROTECTED] J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Colon character problematic in xsl:template match=StringContainingColon ??
Marylynne Henry [EMAIL PROTECTED] wrote: Similarly, I am having problems with the '' character. Is there a way to escape this character when it appears in the text? Yes, there is a way, read the spec at http://www.w3.org/TR/REC-xml, one of the countless XML FAQs or get some XML for Dummies books. BTW the problem you seem to describe is quite unsimilar to that of the original poster. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FO to PDF XSL tranformation
This is not possible. PDF can be a text format but is generally in binary. It would be impossible to process most of the required things using xslt eg. images, markers, links, pagenumbers, layout, property resolving, footnotes, floats. Whats left would be extremely complex. On 2002.03.19 10:20 Libor Kramolis wrote: Xalan is implementation of XSLT. Output format is XML, HTML or TEXT. If PDF is TEXT file, I can imagine XSLT script which can transform FO to PDF. Am I right? Therefore I am looking for such fo2pdf.xslt script. What do you think? Is it reasonable? Then I can imagine DocBook to PDF transformation as sequence of two transformations: xxx.dbx docbook2fo.xsl = xxx.fo fo2pdf.xsl = xxx.pdf. Is not it nice? Thanks for your comments. Libor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Triggering WH2FO from inside Word(R)
Hello Matthias, I think it is a good idea to extend word with macros like this. The macro should be developed at least with word 97 for compatiblity and should be configureable that an other version or an other converter like html2fo runs to do the job. There should be an option for use htmltidy for preformating / correcting word 97 output. Regards Enrico Am Montag, 18. März 2002 17:06 schrieben Sie: Would you think it a good idea to write a VB for Word(R) which: 1) Finds out the path/name of the active file 2) Automatically triggers WH2FO to transform the Word file As an extension of this idea, would you consider it useful to insert into the Word(R) menu a series of commands such as: - Generate XHTML file - Generate XML file - Extract XSL file - Generate XML and XSL files Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Triggering WH2FO from inside Word(R)
Hi Enrico, the problem with Word 97 is related to the fact that the produced HTML doesn't contain all the extra information needed for the pagination and flow control. So WH2FO will not be able to extract those information to generate the correct page-masters and page-sequences. I don't know anything about html2fo converter, but if someone is interested to create a macro it will be usefull to have support for multiple tools. Unfortunately I'm not a VBA expert :-)) so I must rely on someone Fabio -Original Message- From: Enrico Schnepel [mailto:[EMAIL PROTECTED]] Sent: 18 March 2002 20:58 To: [EMAIL PROTECTED] Subject: Re: Triggering WH2FO from inside Word(R) Hello Matthias, I think it is a good idea to extend word with macros like this. The macro should be developed at least with word 97 for compatiblity and should be configureable that an other version or an other converter like html2fo runs to do the job. There should be an option for use htmltidy for preformating / correcting word 97 output. Regards Enrico Am Montag, 18. März 2002 17:06 schrieben Sie: Would you think it a good idea to write a VB for Word(R) which: 1) Finds out the path/name of the active file 2) Automatically triggers WH2FO to transform the Word file As an extension of this idea, would you consider it useful to insert into the Word(R) menu a series of commands such as: - Generate XHTML file - Generate XML file - Extract XSL file - Generate XML and XSL files Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Going in the _Forrest_
On 2002.03.18 15:18 Nicola Ken Barozzi wrote: BTW, if you want, in the meantime I can make a patch to your build to use Cocoon and the new slim xml.apache.org style that is in current Cocoon cvs. It has the same LF of the current one but doesn't make use of batik, and site is much slimmer. The libs would be an additional 1.4 Mb, comprising the Avalon framework and Excalibur jars that you will need anyways. The Cocoon jar itself is less than 1Mb. If this would help you and get us closer to an automated website, then I would like to give the patch a go. I am interested in the forrest project as an observer. Thanks, Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FO to PDF XSL tranformation
Hello, I am ajay, and I am new to xml development group. I've tried to create pdf document using xsl, and fo, but couldnot succeed. Please help me out, with sample code in xsl,fo files. Thankyou with regards, K. AjayKumar Software Developer Pass IT Consulting Pvt Ltd Hyderabad, India [EMAIL PROTECTED] -Original Message- From: Keiron Liddle [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 19, 2002 3:03 PM To: [EMAIL PROTECTED] Subject: Re: FO to PDF XSL tranformation This is not possible. PDF can be a text format but is generally in binary. It would be impossible to process most of the required things using xslt eg. images, markers, links, pagenumbers, layout, property resolving, footnotes, floats. Whats left would be extremely complex. On 2002.03.19 10:20 Libor Kramolis wrote: Xalan is implementation of XSLT. Output format is XML, HTML or TEXT. If PDF is TEXT file, I can imagine XSLT script which can transform FO to PDF. Am I right? Therefore I am looking for such fo2pdf.xslt script. What do you think? Is it reasonable? Then I can imagine DocBook to PDF transformation as sequence of two transformations: xxx.dbx docbook2fo.xsl = xxx.fo fo2pdf.xsl = xxx.pdf. Is not it nice? Thanks for your comments. Libor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FO to PDF XSL tranformation
OK. Keiron, thanks for your explanation. Libor Keiron Liddle wrote: This is not possible. PDF can be a text format but is generally in binary. It would be impossible to process most of the required things using xslt eg. images, markers, links, pagenumbers, layout, property resolving, footnotes, floats. Whats left would be extremely complex. On 2002.03.19 10:20 Libor Kramolis wrote: Xalan is implementation of XSLT. Output format is XML, HTML or TEXT. If PDF is TEXT file, I can imagine XSLT script which can transform FO to PDF. Am I right? Therefore I am looking for such fo2pdf.xslt script. What do you think? Is it reasonable? Then I can imagine DocBook to PDF transformation as sequence of two transformations: xxx.dbx docbook2fo.xsl = xxx.fo fo2pdf.xsl = xxx.pdf. Is not it nice? Thanks for your comments. Libor -- Libor Kramolis, Software Engineer | [EMAIL PROTECTED] NetBeans/Sun Microsystems, XML Project | http://xml.netbeans.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: development status
I agree with the configuration in general but not with the cocoon concept. The parts like configuration, logging, etc. could help us with the functionality and the architecture. To serialize between the Area Tree and the Renderers there are some serious problems that would get in the way: - in many cases the area tree will need to be complete before sending anything across, this defeats the whole purpose and will use a lot of memory - embedded xml will need to be parsed twice and saxified - how do we handle area tree extensions - forward references for some renderers will mean that the renderer may also need to store the whole area tree (or part thereof) on the other side of the sax events - the layout depends on the output target, for font information On 2002.03.15 16:32 Nicola Ken Barozzi wrote: What bugs me in FOP currently (the famous itch to scratch ;-) , is what drives the whole process itself. Configuration, URI resolving, logging, and so on. The infrastructure. snip When this is in place, all the infrastructure is there, and we can concentrate on the real FOP code. The problem is that the *real* FOP code significantly effects the way that the processing and caching works. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FW: Triggering WH2FO from inside Word(R)
Sorry, this one should have gone to the WH2FO Dev List... Matthias -Original Message- From: Matthias Fischer [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 5:06 PM To: [LIST] FOP Developers Cc: [EMAIL PROTECTED] Subject: Triggering WH2FO from inside Word(R) Would you think it a good idea to write a VB for Word(R) which: 1) Finds out the path/name of the active file 2) Automatically triggers WH2FO to transform the Word file As an extension of this idea, would you consider it useful to insert into the Word(R) menu a series of commands such as: - Generate XHTML file - Generate XML file - Extract XSL file - Generate XML and XSL files Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: development status
Keiron Liddle wrote: ... To serialize between the Area Tree and the Renderers there are some serious problems that would get in the way: - in many cases the area tree will need to be complete before sending anything across, this defeats the whole purpose and will use a lot of memory - embedded xml will need to be parsed twice and saxified - how do we handle area tree extensions - forward references for some renderers will mean that the renderer may also need to store the whole area tree (or part thereof) on the other side of the sax events - the layout depends on the output target, for font information Keiron, Could you sketch out the way font information is communicated to layout? I had the vague notion that the renderers were obliged to provide font information at the configuration stage. I hoped this would obviate any further communication between the layout process and the renderer. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[GUMP] Build Failure - Fop
This email is autogenerated from the output from: http://jakarta.apache.org/builds/gump/2002-03-19/xml-fop.html Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init: [echo] --- Fop 1.0dev [1999-2002] prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf codegen: [echo] Resetting codegen directory [copy] Copying 30 files to /home/rubys/jakarta/xml-fop/build/src/codegen [echo] Generating the java files from xml resources [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/foenums_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/charlist.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl [style] Transforming into /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Helvetica.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Helvetica.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Symbol.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Symbol.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBoldItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesRoman.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesRoman.java [style] Processing
DO NOT REPLY [Bug 7241] New: - keep-with-previous, keep-with-next only working on the first page break
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241 keep-with-previous, keep-with-next only working on the first page break Summary: keep-with-previous, keep-with-next only working on the first page break Product: Fop Version: 0.20.3 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a large table, using about 8 pages. Some rows (about every 4th) has the keep-with-previous=always. On the first page-break this works fine. The following page breaks ignore the keep-with-previous. The same is for the keep-with-next. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Colon character problematic in xsl:template match=StringContainingColon ??
The only time I have this problem is
when trying to use FO.
- Original Message -
From:
Adrian
Edwards
To: [EMAIL PROTECTED]
Sent: Tuesday, March 19, 2002 12:00
AM
Subject: RE: Colon character problematic
in xsl:template match="StringContainingColon" ??
Dear
Joe,
You
have opened a can of worms. See the last QA at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/htm/xslt_starter_8f3o.asp
which shows you how to make the transformation work with MSXML, but I'm
not sure the fragment identifier as namespace identifier ('#RowsetSchema')
will work with Xalan. The namespace issues that Microsoft have built
into their ADO persisted XML have sparked long and controversial discussions
among greater minds than ours. Perhaps it's time to move to
ADO.NET?
You
say that you are "able to create XSL for normal transformations to HTML just
fine", but I assume that you are using MSXML as your XSLT engine (probably
through IE?). Try using any other XSLT engine and I'll wager your
"normal" transformation to HTML won't work.
BTW,
is this really a question for fop-dev? Perhaps you aren't aware of the
[EMAIL PROTECTED]mailing
list... Even then, the issue really has little to do with fop,
being largely a general XSLT issue. That is, you would have the same
problem transforming ADO persisted XML to any schema, not just
XSL-FO.
Still, happy to help initially.
Adrian Edwards
Netimpact Online Publishing
http://www.netimpact.com.au
-Original Message-From: Joe Sytniak
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, 19 March 2002 10:22
AMTo: [EMAIL PROTECTED]Subject: Colon character
problematic in xsl:template match="StringContainingColon"
??
All -I am using ADO to produce XML. This tends to get created
as such: ?xml-stylesheet
type="text/xsl"? xml
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:rs="urn:schemas-microsoft-com:rowset"
xmlns:z="#RowsetSchema" s:Schema
id="RowsetSchema" .
clipped schema elements
/s:Schema
rs:data z:row
atributes go here/z:row
/rs:dataI am able to create XSL for normal transformations
to HTML just fine. But inorder to get XSLFO to work, I must change the
names of the 'rs:data' and'z:row' nodes to something that does not
contain a colon charater (ie.rs-data z-row). This seems to
indicate that it is the colon character thatis causing the problem. Not
sure if it could be anything else. I suppose Icould copy nodes to
another more friendly node, but it seems that thisshould not be
necessary.Anyone have a better way of dealing with
this?TIAJoe SytniakPhase Forward,
Inc.
Re: development status
On 2002.03.19 14:45 Nicola Ken Barozzi wrote: I would consider the possibility (configurable) of having FOP make just sensible assumptions to continue processing and sacrifice some things it should do later. That sounds very vague. So what will you do if someone has a table of contents as the second page. Will you pass across a whole lot of to be resolved things for the page numbers to the renderer, so the renderer needs to do the resolving from some further information. Will the renderer go until it reaches a to be resolved thing then need to do some awkward processing of all the following pages. It all sounds like an extra level of complexity that we really don't need. Rather than helping us it will simply make things more difficult. - embedded xml will need to be parsed twice and saxified Why twice? May need to read it to get the width and height and do some pre-processing with a DOM. ATM, I don't have a clear list of all the things that need to be held back before resolution. Is there a list somewhere? It would be of great help for me. Page references. Internal links. Retrieve Markers? Extensions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: development status
Hi Peter, The font information is obtained from the renderer at the start before building any of the area tree. There should be no further need for communication except of course in the case when handling dynamic effects (but lets not get into that right now). On 2002.03.19 13:37 Peter B. West wrote: Keiron Liddle wrote: ... To serialize between the Area Tree and the Renderers there are some serious problems that would get in the way: - in many cases the area tree will need to be complete before sending anything across, this defeats the whole purpose and will use a lot of memory - embedded xml will need to be parsed twice and saxified - how do we handle area tree extensions - forward references for some renderers will mean that the renderer may also need to store the whole area tree (or part thereof) on the other side of the sax events - the layout depends on the output target, for font information Keiron, Could you sketch out the way font information is communicated to layout? I had the vague notion that the renderers were obliged to provide font information at the configuration stage. I hoped this would obviate any further communication between the layout process and the renderer. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Colon character problematic in xsl:template match=StringContainingColon ??
You are correct - I am using the
MSXML parser. I only use the apache code for FO - PDF.By the way - it
works really great - as long as I use this workaround.
I will follow your suggestion and use
another engine to test the XSLT to html. If the problem is the same,then I
agree that this is a problem topic that has no relevance on this list and I
apologize.
Still - it seems to me that the
problem I am seeing (and working around) should not be happening.
- Original Message -
From:
Joe Sytniak
To: [EMAIL PROTECTED]
Sent: Tuesday, March 19, 2002 9:26
AM
Subject: Re: Colon character problematic
in xsl:template match="StringContainingColon" ??
The only time I have this problem
is when trying to use FO.
- Original Message -
From:
Adrian Edwards
To: [EMAIL PROTECTED]
Sent: Tuesday, March 19, 2002 12:00
AM
Subject: RE: Colon character
problematic in xsl:template match="StringContainingColon" ??
Dear Joe,
You have opened a can of worms. See the last QA
at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/htm/xslt_starter_8f3o.asp
which shows you how to make the transformation work with MSXML, but
I'm not sure the fragment identifier as namespace identifier
('#RowsetSchema') will work with Xalan. The namespace issues that
Microsoft have built into their ADO persisted XML have sparked long and
controversial discussions among greater minds than ours. Perhaps it's
time to move to ADO.NET?
You say that you are "able to create XSL for normal transformations
to HTML just fine", but I assume that you are using MSXML as your XSLT
engine (probably through IE?). Try using any other XSLT engine and
I'll wager your "normal" transformation to HTML won't
work.
BTW, is this really a question for fop-dev? Perhaps you aren't
aware of the [EMAIL PROTECTED]mailing
list... Even then, the issue really has little to do with fop,
being largely a general XSLT issue. That is, you would have the same
problem transforming ADO persisted XML to any schema, not just
XSL-FO.
Still, happy to help initially.
Adrian Edwards
Netimpact Online Publishing
http://www.netimpact.com.au
-Original Message-From: Joe Sytniak
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, 19 March 2002 10:22
AMTo: [EMAIL PROTECTED]Subject: Colon character
problematic in xsl:template match="StringContainingColon"
??
All -I am using ADO to produce XML. This tends to get created
as such: ?xml-stylesheet
type="text/xsl"? xml
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:rs="urn:schemas-microsoft-com:rowset"
xmlns:z="#RowsetSchema" s:Schema
id="RowsetSchema" .
clipped schema elements
/s:Schema
rs:data z:row
atributes go here/z:row
/rs:dataI am able to create XSL for normal transformations
to HTML just fine. But inorder to get XSLFO to work, I must change the
names of the 'rs:data' and'z:row' nodes to something that does not
contain a colon charater (ie.rs-data z-row). This seems to
indicate that it is the colon character thatis causing the problem.
Not sure if it could be anything else. I suppose Icould copy nodes to
another more friendly node, but it seems that thisshould not be
necessary.Anyone have a better way of dealing with
this?TIAJoe SytniakPhase Forward,
Inc.
subscript, superscript
hi, can someone help me where to find the settings for subscript and superscript in the fop-0.20.3 sourcecode? I have especially trouble using subscript as it places text too low for my application requirements. regards Henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: subscript, superscript
That's what I've been using so far, and it also works great forme too. (I'm using FOP 20.3) baseline-shift doesnt seem to work Guillaume - Original Message - From: Etwin van Krimpen To: [EMAIL PROTECTED] Sent: Tuesday, March 19, 2002 4:44 PM Subject: Re: subscript, superscript Hi,Try this with fop, in a previous version it worked:fo:inline vertical-align="super"Regards, Etwin- Original Message -From: "Klosa Uwe" [EMAIL PROTECTED]To: [EMAIL PROTECTED]Sent: Tuesday, March 19, 2002 4:36 PMSubject: SV: subscript, superscript Hi Henrik, I've got the same problem and I asked for this several times here. But I didn't get an answer. The recommendation says, that you have to use baseline-shift="super" or baseline-shift="sub". But this isn't implemented yet and I find now no time to do it. Perhaps is there someone else who needs this parameter, too. If you want to implemented baseline-shift, might it be an good idea. Best regards Uwe -Ursprungligt meddelande- Fran: Henrik Holle [mailto:[EMAIL PROTECTED]] Skickat: den 19 mars 2002 14:14 Till: [EMAIL PROTECTED] Amne: subscript, superscript hi, can someone help me where to find the settings for subscript andsuperscript in the fop-0.20.3 sourcecode? I have especially trouble using subscript as it places text too low for my application requirements. regards Henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, email: [EMAIL PROTECTED]
Re: development status
From: Keiron Liddle [EMAIL PROTECTED] On 2002.03.19 14:45 Nicola Ken Barozzi wrote: I would consider the possibility (configurable) of having FOP make just sensible assumptions to continue processing and sacrifice some things it should do later. That sounds very vague. So what will you do if someone has a table of contents as the second page. Will you pass across a whole lot of to be resolved things for the page numbers to the renderer, so the renderer needs to do the resolving from some further information. Will the renderer go until it reaches a to be resolved thing then need to do some awkward processing of all the following pages. I would output a ? instead of the real pages. While this is not generally acceptable, in reports, for example, these references are usually not needed. High memory consumption is *the*killer*, and it's a burden that is not needed in these cases. It all sounds like an extra level of complexity that we really don't need. Rather than helping us it will simply make things more difficult. Good point. I will keep this in mind. - embedded xml will need to be parsed twice and saxified Why twice? May need to read it to get the width and height and do some pre-processing with a DOM. It can be equally done by a sub-pipeline with SAX. But I understand that Batik is still DOM based :-( ATM, I don't have a clear list of all the things that need to be held back before resolution. Is there a list somewhere? It would be of great help for me. Since propertiy resolution is basically inherited AFAIK, it seems that what you specify is in fact what really breaks the nice SAX stuff. Page references. Yes. Internal links. May be. In HTML it's not needed since I can write an internal link (#myref) before specifying it. Retrieve Markers? IMHO yes, since you can make a forward reference with it. Extensions. Let's bypass extensions for now. So we absolutely need to stop output and cache events if there is a forward reference. If we find it at the end, all the pages must remain in memory, and now I see that this can make FOP behave no better than it does now. There are three possibilities I see: 1. Start storing the SAX events as soon as a forward reference is caught, and flush them after the resolved reference. 2. Ignore the forward references (speed property); if someone doesn't use any of the above features, there is no difference in output anyway. 3. Do the FOP processing in 2 steps. 1- Process all the stuff without the references writing to disk 2- resolve them by rereading the file This resolves memory issues but not speed. I would go for 1 and 2. If we store the SAX events before firing them, they are smaller than DOM and can be saved to a Store that can also be a disk in case of low memory. This is how Cocoon caches pages, and this is how we could cache SAX fragments that are there just to wait for a forward reference. We can also give a clear indication to users to how to optimize pages: no forward references = much less memory = higher speed. Anyway, these forward references are a pain in the ass :-/ -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: development status
On 2002.03.19 16:47 Nicola Ken Barozzi wrote: So we absolutely need to stop output and cache events if there is a forward reference. If we find it at the end, all the pages must remain in memory, and now I see that this can make FOP behave no better than it does now. Thats not true. We can do better and the current development is developing towards a way that will do better. The key is that there is a definite API between the Area Tree and the Renderers. This means that we can prepare a page and later render its contents. All following pages can be rendered if they are finished. The forward reference resolution can be done in the area tree with the help of the layout managers and then the completed page can be rendered (depends if the renderer supports out of order which pdf does). If the memory gets low then a page can be stored to disk and retrieved when forward references are resolved. Without needing to handle this on two sides of the fence it is more straight forward and flexible. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: SV: subscript, superscript
I need to do subscript/superscript as well. when you find an answer, pls let me know Thanks Mathy Klosa Uwe wrote: Hi Henrik, I've got the same problem and I asked for this several times here. But I didn't get an answer. The recommendation says, that you have to use baseline-shift=super or baseline-shift=sub. But this isn't implemented yet and I find now no time to do it. Perhaps is there someone else who needs this parameter, too. If you want to implemented baseline-shift, might it be an good idea. Best regards Uwe -Ursprungligt meddelande- Fran: Henrik Holle [mailto:[EMAIL PROTECTED]] Skickat: den 19 mars 2002 14:14 Till: [EMAIL PROTECTED] Amne: subscript, superscript hi, can someone help me where to find the settings for subscript and superscript in the fop-0.20.3 sourcecode? I have especially trouble using subscript as it places text too low for my application requirements. regards Henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: development status
From: Keiron Liddle [EMAIL PROTECTED] On 2002.03.19 16:47 Nicola Ken Barozzi wrote: So we absolutely need to stop output and cache events if there is a forward reference. If we find it at the end, all the pages must remain in memory, and now I see that this can make FOP behave no better than it does now. Thats not true. We can do better and the current development is developing towards a way that will do better. The key is that there is a definite API between the Area Tree and the Renderers. This means that we can prepare a page and later render its contents. All following pages can be rendered if they are finished. The forward reference resolution can be done in the area tree with the help of the layout managers and then the completed page can be rendered (depends if the renderer supports out of order which pdf does). If the memory gets low then a page can be stored to disk and retrieved when forward references are resolved. Ah, so it's done with pages. But with some renderers pages could not be defined (as the spec allows), like in HTML rendering. Anyway, I didn't come up with this possibility, since I don't usually deal with them, but it's a really neat solution to the problem, but still useless if every page has forward references. Without needing to handle this on two sides of the fence it is more straight forward and flexible. Two sides of the fence? Never thought so. Ok, so I see that there is agreement on the fact that using SAX events as intermediate steps of the FOP processing pipeline is not the best solution ATM. I will focus now on implementing Avalon stuff in FOP, starting from Configuration (non static) and URI resolving (for images). Thank you all for the wonderful feedback on my Random Thoughts :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
NPE from Driver.render(Document)
I noticed some unanswered questions in the archives in regards to driver.render(Document) throwing a NullPointerException. Why is this? I read a workaround, but I like to know if the straight forward method work. Thanks. :) -- David B. Bitton [EMAIL PROTECTED] Diversa ab illis virtute valemus. msg06018/pgp0.pgp Description: PGP signature
NPE on Driver.render(Document)
--WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I noticed some unanswered questions in the archives in regards to driver.re= nder(Document) throwing a NullPointerException. Why is this? I read a workaround, but I like to know if the straight forwa= rd method works. Thanks. :) --=20 David B. Bitton [EMAIL PROTECTED] Diversa ab illis virtute valemus. --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8l7lmMNOMzNRRk50RAiOJAJ4jClevJtMFIt++LE095gQy5v9jJgCgjn62 oO4zXGHTKIs82ss87yaPYbE= =cXoq -END PGP SIGNATURE- --WIyZ46R2i8wDzkSu--
Re: Colon character problematic in xsl:template match=StringContainingColon ??
In what sense does XSLFO not work? What are the exact symptoms? Do you get an error message or unexpected results? Is the problem caused by the transformation or during formatting? Did you inspect the intermediate FO? Can you show the relevant parts of your XSLT and source XML (please trim the files down to the problematic parts)? Perhaps an XSLT list would be the best place to look for answers on this one. Except I only seem to be having problems when using my XSL templates with FO templates. I suppose this could just be coincidental. Others have suggested that it is likely that I would have this problem with XSLT using the same parser. I will check this once I get a hold of another XSL engine. I am interpreting the errors as parsing errors. Error message follows: [INFO]: FOP 0.20.3rc file:///previewfo.xsl; Line 34; Column 42; [ERROR]: null Relevant XML follows ?xml-stylesheet type=text/xsl? xml xmlns:s=uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882 xmlns:dt=uuid:C2F41010-65B3-11d1-A29F-00AA00C14882 xmlns:rs=urn:schemas-microsoft-com:rowset xmlns:z=#RowsetSchema s:Schema id=RowsetSchema . clipped schema elements /s:Schema rs:data z:row atributes go here...elements clipped /z:row /rs:data Relevant XSL-FO follows: xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; version=1.0 xsl:template match=/ fo:root fo:layout-master-set fo:simple-page-master master-name=simple page-height=16.4cm page-width=24.2cm margin-top=0.5cm margin-bottom=0.5cm margin-left=2cm margin-right=2cm fo:region-body margin-top=0.5cm margin-bottom=0.75cm/ fo:region-after precedence=true extent=0.5cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=simple fo:static-content flow-name=xsl-region-after fo:block text-align=end font-size=8pt font-family=serif line-height=14pt vertical-align=bottom p. fo:page-number/ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body xsl:apply-templates select=xml/ /fo:flow /fo:page-sequence /fo:root /xsl:template xsl:template match=xml xsl:apply-templates select=rs:data/!-- error message above refers to end of this line - change to rs-data and FO works fine -- /xsl:template xsl:template match=rs-data xsl:apply-templates select=z-row/ !-- select was on row-- /xsl:template xsl:template match=z-row ... clipped detailed processing from here /xsl:template - Original Message - From: Joerg Pietschmann [EMAIL PROTECTED] To: FOP Dev [EMAIL PROTECTED] Sent: Tuesday, March 19, 2002 4:20 AM Subject: Re: Colon character problematic in xsl:template match=StringContainingColon ?? Joe Sytniak [EMAIL PROTECTED] wrote: I am able to create XSL for normal transformations to HTML just fine. But in order to get XSLFO to work, I must change the names of the 'rs:data' and 'z:row' nodes to something that does not contain a colon charater (ie. rs-data z-row). Such changes should not be necessary. In what sense does XSLFO not work? What are the exact symptoms? Do you get an error message or unexpected results? Is the problem caused by the transformation or during formatting? Did you inspect the intermediate FO? Can you show the relevant parts of your XSLT and source XML (please trim the files down to the problematic parts)? XSLT questions are better asked on the XSL list [EMAIL PROTECTED] J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: development status
-Original Message- From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] Sent: March 19, 2002 11:48 AM To: [EMAIL PROTECTED] Subject: Re: development status From: Keiron Liddle [EMAIL PROTECTED] Retrieve Markers? IMHO yes, since you can make a forward reference with it. -Original Message- The section on retrieve-marker is not well written, but I would assert with a high degree of confidence that for any retrieve-marker, the only qualifying markers have already been seen. Supporting analysis: Spec Statement 1 - The term 'containing page' is used here to mean the page that contains the first area generated or returned by the children of the retrieved fo:marker. Spec Statement 2 - [ qualifying ] areas do not have a position in the hierarchy if they are within pages that follow the containing page. Statement 1 tells me that the page containing the fo:retrieve-marker is the containing page. Statement 2 tells me that markers, which otherwise qualify on the basis of class-name and retrieve-boundary, are ruled out. This is pretty unambiguous, although other parts of the relevant discussion are not. I am open to counter-arguments. The reason I am open to counter-arguments is I read stuff like this, for example: A) If the value of the retrieve-position property is last-starting-within-page, then the last qualifying area in the containing page whose is-first trait has a value of true is better than any other area. If there is no such area, then the last qualifying area in the containing page is better than any other area. AND B1) Every area in the hierarchy is considered preferential to, or better than, any area below it in the hierarchy. When comparing two areas to determine which one is better, the terms first and last refer to the preorder traversal order of the area tree. COUPLED WITH B2) A qualifying area within a page is better than any qualifying area within a preceding page. and my brain starts to implode. What does this mean? That _if_ there are NO areas on the containing page that have is-first = true, and in fact, there are no qualifying areas on the containing page at all, then Rule A kicks in and a qualifying area on page 11 is better than a qualifying area on page 18? In fact the entire question of what qualifying areas should be selected of nothing is found on the containing page is up in the air - apparently one always selects the first qualifying area (pre-order traversal of the area tree) subject to class-name and retrieve-boundary. Better to select nothing at all. Anyway, that's my little rant on markers. I raised the issue last year but never got an answer. But in terms of forward references fortunately the spec is very clear. Regards, AHS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Colon character problematic in xsl:template match=StringContainingColon ??
Whether the problem that you are seeing (and working
around) should be happening is the subject of the controversy that I
mentioned. If you are interested in the discussion of why relative URIs
(including fragment identifiers such as '#RowsetSchema') are often discouraged
as namespace identifiers, follow the thread beginning with Michael Champion's
reply to:
http://lists.w3.org/Archives/Public/xml-uri/2000May/.html
PS: No
apologies necessary either way Joe. I can see what led you to suspect that
thismight bea problem with fop.
-Original Message-From: Joe Sytniak
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, 20 March 2002 2:05
AMTo: [EMAIL PROTECTED]Subject: Re: Colon character
problematic in xsl:template match="StringContainingColon"
??
You are correct - I am using the
MSXML parser. I only use the apache code for FO - PDF.By the way -
it works really great - as long as I use this workaround.
I will follow your suggestion and
use another engine to test the XSLT to html. If the problem is the
same,then I agree that this is a problem topic that has no relevance on
this list and I apologize.
Still - it seems to me that the
problem I am seeing (and working around) should not be happening.
- Original Message -
From:
Adrian Edwards
To: [EMAIL PROTECTED]
Sent: Tuesday, March 19, 2002 12:00
AM
Subject: RE: Colon character
problematic in xsl:template match="StringContainingColon" ??
Dear Joe,
You have opened a can of worms. See the last QA
at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/htm/xslt_starter_8f3o.asp
which shows you how to make the transformation work with MSXML, but
I'm not sure the fragment identifier as namespace identifier
('#RowsetSchema') will work with Xalan. The namespace issues that
Microsoft have built into their ADO persisted XML have sparked long and
controversial discussions among greater minds than ours. Perhaps
it's time to move to ADO.NET?
[Fwd: ScanMail Message: To Sender, sensitive content found and actiont aken.]
Fops, Re my prior message, I received this response. Nice to know someone's mail is carefully monitored. Peter Trend SMEX Content Filter has detected sensitive content. Place = fop-dev; ; ; [EMAIL PROTECTED] Sender = Peter B. West Subject = [Fwd: Re: development status] Delivery Time = March 20, 2002 (Wednesday) 06:22:57 Policy = Sexual Discrimination Action on this mail = Archive message Warning message from administrator: Sender, Content filter has detected a sensitive e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Using FOP with xmlspy -- THANKS FOR HELP, QUESTIONANSWERED
Thanks Malcolm Sinclair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7259] New: - Additional space generated after inline on PDF Renderer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7259. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7259 Additional space generated after inline on PDF Renderer Summary: Additional space generated after inline on PDF Renderer Product: Fop Version: 0.20.3 Platform: PC OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The following extract of code generates additional space after the 'red text' when generating PDF but not in the AWT version. I can see no obvious reason for this, there is no addition whitespace in the source (regardless of what yahoo mail does to it). Development Platform : Solaris 8 Intel (JDK Solaris_JDK_1.2.1_04c) FOP Version : 0.20.3 Acrobat Version : acroread-4.05 (solaris Intel) and Acroread-5.0 (Win32) Regards, Peter Bray Sydney, Australia ?xml version=1.0 standalone=no? !DOCTYPE fo:root SYSTEM fo.dtd fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=BodyPage page-width=210mm page-height=297mm margin-top=0.5in margin-bottom=0.5in margin-left=1in margin-right=1in fo:region-body margin-top=0.5in margin-bottom=0.5in/ fo:region-before extent=0in/ fo:region-after extent=0.25in/ /fo:simple-page-master fo:page-sequence-master master-name=BodySequence fo:repeatable-page-master-reference master-reference=BodyPage/ /fo:page-sequence-master /fo:layout-master-set fo:page-sequence master-reference=BodySequence fo:flow flow-name=xsl-region-body fo:block fo:inline font-family=monospace font-size=9.5ptsoftware# fo:inline font-style=italic font-weight=bolddiff Makefile.unix Makefile/fo:inline/fo:inline /fo:block fo:block font-family=serif font-style=italic font-size=9ptModify line 28/fo:block fo:block font-family=monospace font-size=8.5ptfo:inline font-style=italicold: /fo:inlineBINDIR = fo:inline font-style=italic color=red/usr/local/fo:inline/bin/fo:block fo:block font-family=monospace font-size=8.5ptfo:inline font-style=italicnew: /fo:inlineBINDIR = fo:inline font-style=italic color=red/pkgs/psutils-1.17/fo:inline/bin/fo:block /fo:flow /fo:page-sequence /fo:root - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
SV: subscript, superscript
Etwin, I'm using fo:inline vertical-align=super and fo:inline vertical-align=sub, but the results aren't good. Subscript places the text too low och superscript too high. Uwe -Ursprungligt meddelande- Från: Etwin van Krimpen [mailto:[EMAIL PROTECTED]] Skickat: den 19 mars 2002 16:45 Till: [EMAIL PROTECTED] Ämne: Re: subscript, superscript Hi, Try this with fop, in a previous version it worked: fo:inline vertical-align=super Regards, Etwin - Original Message - From: Klosa Uwe [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 19, 2002 4:36 PM Subject: SV: subscript, superscript Hi Henrik, I've got the same problem and I asked for this several times here. But I didn't get an answer. The recommendation says, that you have to use baseline-shift=super or baseline-shift=sub. But this isn't implemented yet and I find now no time to do it. Perhaps is there someone else who needs this parameter, too. If you want to implemented baseline-shift, might it be an good idea. Best regards Uwe -Ursprungligt meddelande- Fran: Henrik Holle [mailto:[EMAIL PROTECTED]] Skickat: den 19 mars 2002 14:14 Till: [EMAIL PROTECTED] Amne: subscript, superscript hi, can someone help me where to find the settings for subscript and superscript in the fop-0.20.3 sourcecode? I have especially trouble using subscript as it places text too low for my application requirements. regards Henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
