Re: [Understanding] FO Tree [3]

Keiron Liddle wrote: ... By using element mappings it is possible to read other XML and either - set information on the area tree - create pseudo FO Objects that create areas in the area tree - create FO Objects ** Mapping elements to classes? I'm not sure what the question is.

RE: [Understanding] FO Tree [3]

The question is, How are extension element properties mapped? I new element seems to be recognized by FOP just fine, but any properties I include are ignored by FOP, i.e. an exception is raised stating that the property in question is ignored and/or no maker found. matthew l. avizinis

[Understanding] Property Handling [5]

Property Handling - During XML Parsing, the FO tree is constructed. For each FO object (some subclass of FObj), the tree builder then passes the list of all attributes specified on the FO element to the handleAttrs method. This method converts the attribute specifications into a

Re: REDESIGN: where I have been hiding

Peter B. West wrote: I'll try to explain the algorithm a bit for line-building; maybe that will help to clarify what I meant. The TextLayoutManager generates a BreakPosition for each possible line break (not including hyphenation at first). This means breakable spaces or other possible line end

cvs commit: xml-fop/src/codegen foproperties.xml properties.xsl

klease 02/02/23 08:47:02 Modified:src/codegen foproperties.xml properties.xsl Log: Add corresponding properties for space-* Revision ChangesPath 1.30 +9 -0 xml-fop/src/codegen/foproperties.xml Index: foproperties.xml

cvs commit: xml-fop/src/org/apache/fop/area CTM.java RegionReference.java

klease 02/02/23 08:47:37 Modified:src/org/apache/fop/area CTM.java RegionReference.java Log: Support PDF rendering Revision ChangesPath 1.3 +5 -1 xml-fop/src/org/apache/fop/area/CTM.java Index: CTM.java

cvs commit: xml-fop/src/org/apache/fop/render/pdf PDFRenderer.java

klease 02/02/23 08:48:59 Modified:src/org/apache/fop/render AbstractRenderer.java src/org/apache/fop/render/pdf PDFRenderer.java Log: Take CTM into account for PDF rendering (small test) Revision ChangesPath 1.11 +12 -3

Some writing-mode questions

Dear editors, I've got a couple of issues regarding writing-mode where I'd like to make sure I'm interpreting the spec as you intended. --- Issue 1: whose writing-mode determines the value of corresponding absolute properties. Section 4.2.3 states: For

[REDESIGN] TextLayoutManager whitespace handling

Keiron, I see you've actually started to make TextLayoutManager do something. I noticed during my CTM testing with the PDF renderer, that it's eating the first character of my text, ie. Hello world came out as ello world. Since I don't think you're French which could account for not pronouncing

Re: REDESIGN: where I have been hiding

A couple of remarks below: Keiron Liddle wrote: Hi Karen, Welcome back. Yes it would be great if you could write about the property handling stuff if you have the time. Done. As for the CTM stuff. For PDF there is a class PDFState which keeps track of pdf graphic state information.

Margin properties on region-body

Dear editors, I've got some questions about the properties used to specify the position of the region-body. Most of the discussion in 6.4.13, as well as the illustration, uses the absolute property names margin-top, margin-left, etc. to describe the positioning of the region-body viewport