RE: [REDESIGN] Line layout manager discussion
Comments inline. -Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED]] Sent: May 1, 2002 2:19 AM To: [EMAIL PROTECTED] Subject: Re: [REDESIGN] Line layout manager discussion [ SNIP ] Look at basic-linka paragraph of text blockwith a block/block and more text/basic-link What about the restriction that a given area's children must all be of the one type (4.2.1 Area Types)? Doesn't that oblige us to wrap the block within an inline? Then that inline wrapper can sit in sequence with the inline-areas 't', 'e', 'x', 't', ' ', as indeed the basic-link inline-area already sits in sequence with 'S','o','m','e',' ','t','e','x','t',' '? What's your take on this? There were many discussions last year, as I recall, that espoused this viewpoint, that the area rules precluded a number of FO-level combinations and juxtapositions. This school of thought, and I belong(ed) to it, held that a block or inline contains either block FO children _or_ inline FO children, but not both. I am no longer convinced that this needs to be the case. It is certainly safe to ensure that all the children of a given FO are either block-level FOs _or_ inline-level FOs. In these cases we have area generation and layout which is (I think) well understood. But this treatment shows, I think, that the area rules can be satisfied without having to homogenize the type of FO children. 4.2.1 is a restriction on areas, as you know. Certainly the areas that I have diagrammed do not violate this constraint. N.B. I have attached the SVG generated by Dia. I don't know what the quality is like, but if the quality of the generated PNG is anything to go by, probably not too good. If we can all get access to a reasonable SVG vector editor that will write PNGs, we will be able to pass the editable file around as well, which will greatly facilitate this sort of discussion. Any candidates for a linux-enabled SVG editor? I'll have to take a look around. I happened to use Visio because it's on the machine and I'm familiar with it, plus it's a nice piece of gear. The most recent Visios do SVG, I believe, but I don't have a copy at home. We could use Postscript as well. Arved - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Anything for a non-programmer to do?
Matthew, I've moved this to fop-dev. Look over the documentation that we have (basically, the web site html) and see what you think. As a non-programmer, you will be mainly interested in the user perspective. How much of a non-programmer are you? If you can grok the code at all, your input on the Understanding section, which Cyril Rognon is currently collecting and html-ifying, might be appreciated. Have you read the spec? This is a tall order, but I think it would be useful if a writer with some understanding of the spec could monitor the design discussions and, referring them back to the spec, develop a series of notes - like annotations on the spec - which unified the often scattered references in the text on certain difficult issues. If you are subscribed to fop-dev, you will have seen the recent discussions on layout and line-area handling. Related to that is the gradual building-up of a form of concept index into the specification, perhaps in the form of a FADesignQ. More simply, a series of precis on the design discussions about controversial, or just plain difficult, areas, summing up the points of view and the eventual, one hopes, resolution. Does any of this appeal to you? Peter Matthew Huggett wrote: Hi: Is there anything that a non-programmer can do to help the FOP project? I'm a technical writer. Is there anything involving documentation that needs to be done? Matthew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8698] New: - NullPointerException when trying to render FO file
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=8698. 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=8698 NullPointerException when trying to render FO file Summary: NullPointerException when trying to render FO file Product: Fop Version: 0.20.3 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I try to render the attached FO file, I get this exception [INFO]: FOP 0.20.3 [DEBUG]: using SAX parser org.apache.xerces.parsers.SAXParser [INFO]: building formatting object tree [DEBUG]: setting up fonts [ERROR]: null org.apache.fop.apps.FOPException at org.apache.fop.apps.Driver.render(Driver.java:486) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:72 ) at org.apache.fop.apps.Fop.main(Fop.java:19) - java.lang.NullPointerException at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:965) at org.apache.fop.apps.Driver.render(Driver.java:481) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:72 ) at org.apache.fop.apps.Fop.main(Fop.java:19) - java.lang.NullPointerException at org.apache.fop.fo.flow.Flow.setFlowName(Flow.java:98) at org.apache.fop.fo.flow.Flow.init(Flow.java:77) at org.apache.fop.fo.flow.Flow$Maker.make(Flow.java:28) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:261) at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1371) at org.apache.xerces.validators.common.XMLValidator.callStartElement(XML Validator.java:840) at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.disp atch(XMLDocumentScanner.java:1223) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentS canner.java:381) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:948) at org.apache.fop.apps.Driver.render(Driver.java:481) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:72 ) at org.apache.fop.apps.Fop.main(Fop.java:19) - java.lang.NullPointerException at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:965) at org.apache.fop.apps.Driver.render(Driver.java:481) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:72 ) at org.apache.fop.apps.Fop.main(Fop.java:19) - java.lang.NullPointerException at org.apache.fop.fo.flow.Flow.setFlowName(Flow.java:98) at org.apache.fop.fo.flow.Flow.init(Flow.java:77) at org.apache.fop.fo.flow.Flow$Maker.make(Flow.java:28) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:261) at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1371) at org.apache.xerces.validators.common.XMLValidator.callStartElement(XML Validator.java:840) at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.disp atch(XMLDocumentScanner.java:1223) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentS canner.java:381) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:948) at org.apache.fop.apps.Driver.render(Driver.java:481) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:72 ) at org.apache.fop.apps.Fop.main(Fop.java:19) ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;fo:layout-master- setfo:simple-page-master margin-bottom=2cm margin-top=2cm margin- right=3cm margin-left=3cmfo:region-before extent=12pt/fo:region-body margin-bottom=20pt margin-top=20pt/fo:region-after extent=12pt//fo:simple-page-master/fo:layout-master-setfo:page- sequencefo:flowfo:block space-after=6pt text-align=centered font- size=24ptMaster's thesis/fo:blockfo:block text-align=centered by Mikael St#9500;Ñldal/fo:block/fo:flow/fo:page-sequencefo:page- sequencefo:sequence-specificationfo:sequence-specifier-repeating page- master-repeating=one page-master-first=one//fo:sequence- specificationfo:static-content flow-name=xsl-beforefo:block font- size=10ptMaster's thesis/fo:block/fo:static-contentfo:static-content flow-name=xsl-afterfo:block text-align=centered font-size=10ptfo:page- number//fo:block/fo:static-contentfo:flow font-family=serif font- size=12ptfo:block space-after=24pt font-size=20ptTable of Contents /fo:blockfo:block Chapter 1 - XML and related standards... fo:page-number-citation ref-id=chap1//fo:blockfo:list-
Re: properties
Hello devs. Does the near-silence on this one signify consent? Peter Keiron Liddle wrote: Hi Peter and others, What is the status of property handling? Are we going to go with Peter's suggestion and commit the java source to cvs and work on handling properties fully from there? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: properties
On Wednesday 01 May 2002 18:19, Peter B. West wrote: Does the near-silence on this one signify consent? I don't know enough about this to give meaningful advice, so in my case yes, silence means consent. - Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: properties
Bertrand Delacretaz wrote: On Wednesday 01 May 2002 18:19, Peter B. West wrote: Does the near-silence on this one signify consent? I don't know enough about this to give meaningful advice, so in my case yes, silence means consent. Yes, it ought to be a reasonable idea. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: [REDESIGN] Line layout manager discussion
Questions: o A basic-link in PDF means an annotation - an annotation defines a rectangle. What's the effect, if the annotation text breaks to a new line? If the basic-link contains more blocks and children? o Middle Easterner write left-to-right, top-to-bottom. Far Easterners write from top-to-bottom, right-to-left. They have their own font metrics. Is the FOP pagination able to handle this? How does it affect the area tree and the document presentation? o fo:external-graphic: can text be flowed around an image? That means, does it make sense for a user to mix text and images within the same block - unless a table is used, but this is a different setup. Hansuli Anderegg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [REDESIGN] Line layout manager discussion
Comments inline. -Original Message- From: J.U. Anderegg [mailto:[EMAIL PROTECTED]] Sent: May 1, 2002 5:19 PM To: [EMAIL PROTECTED] Subject: AW: [REDESIGN] Line layout manager discussion Questions: o A basic-link in PDF means an annotation - an annotation defines a rectangle. What's the effect, if the annotation text breaks to a new line? If the basic-link contains more blocks and children? From the XSL standpoint it's merely a question of the basic-link generating one or more normal inline areas. These map to annotation rectangles in PDF. When the inline areas in question are presented to the renderer they have behaviour traits corresponding to the internal-destination or external-destination. o Middle Easterner write left-to-right, top-to-bottom. Far Easterners write from top-to-bottom, right-to-left. They have their own font metrics. Is the FOP pagination able to handle this? How does it affect the area tree and the document presentation? Can it handle this right now? No. Apart from things like mixing text with different writing-modes, supporting different writing-modes and reference-orientations is actually not much more complicated than the specific Western case, at everything except the immediate glyph-area level. o fo:external-graphic: can text be flowed around an image? That means, does it make sense for a user to mix text and images within the same block - unless a table is used, but this is a different setup. Using a side-float is the best you can do with XSL 1.0. If you are looking to do something like TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT -- TEXT TEXT TEXT TEXT || TEXT TEXT TEXT TEXT | Image| TEXT TEXT TEXT TEXT || TEXT TEXT TEXT TEXT || TEXT TEXT TEXT TEXT -- TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT then, no, without tables and a fair bit of tweaking I don't think so. An external-graphic intermingled with PCDATA is going to normally cause the line it is in to expand to its own size (using line-height or max-height for the line-stacking-strategy), so things will look like TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT -- || | Image| || || TEXT TEXT || TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT assuming that the baseline of the external-graphic is determined by an auto value on alignment-adjust. Hope this helps. Regards, AHS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
