Some comments on the build system

Fops, I would like to see the build system overhauled. The overall objectives of the overhaul would be to simplify the build process and decrease barriers to entry for would-be developers. The tactical objectives would be to eliminate XSL from the build, and to generate the classes directly

Re: font-family and font names list

Joerg, I share your opinion about the detrimental effects of CSS on the spec, or rather, as Chris points out, of the manner in which CSS compatibility was introduced "font-family" is especially nasty, not only because it can have a comma-separated list of (family-name|generic-family) items,

Recent additions to ALT DESIGN documentation

Keiron has committed for me some additions to the ALT DESIGN documentation, which resides under the NEW DESIGN item in the FOP web pages. These should be available shortly. The new items include discussion on co-routines (some changes still pending) galleys footnotes Some of this discussion

[DOCUMENTATION] design/alt.design new files [2 of 2]

Arved or Keiron, Attached are new files for the xml-fop/docs/design/alt.design directory. They are in 2 of 2 .tgz files. This one contains line-area-5.png line-area-6.png traits.xml Some diffs for other files have also been sent. Peter alt.design.2.tgz Description: GNU Zip compressed data

[DOCUMENTATION] design/alt.design new files [1 of 2]

Arved or Keiron, Attached are new files for the xml-fop/docs/design/alt.design directory. They are in 1 of 2 .tgz files. This one contains compound-properties.xml coroutines.png coroutines.xml footnotes.xml galley-preprocessing.png galleys.xml initial-column-values.png Some diffs for other fi

[DOCUMENTATION] diffs for files in design/alt.design

Arved or Keiron, Attached are diffs for xml-fop/docs/design/alt.design/alt.properties.xml and xml-fop/docs/design/alt.design/book.xml. A previous email included new files for the design/alt.design directory. Peter Index: alt.properties.xml

Re: development status

Joerg, You have highlighted one of the nastinesses of page formatting. A Q&D solution often suggested is to allow a fixed width for the page numbers, but I don't see how this can stand as a final solution. The gaps are going to be obvious in something purporting to be a high-quality rende

Netiquette

When someone offends against netiquette, I should think that garden-variety etiquette would decree that you post your complaints to that individual. If he (resp. she) continues to offend, then try the public humiliation of which netizens seem so fond. That public rebuke could legitimately in

[Fwd: Re: development status]

f difficulty. More core! Muzzle the Bitch! Peter Nicola Ken Barozzi wrote: >From: "Peter B. West" > >>Nicola Ken Barozzi wrote: >> >>>Don't get me wrong, maybe I don't understand something, but still I'm >>> >very > >>

[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

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

Re: Area tree -> renderer ("pr.fo" for structure renderers)

Bertrand, There's another gotcha - markers. The properties in markers are resolved relative to the retrieve-marker invocation point. Peter Bertrand Delacretaz wrote: >On Monday 18 March 2002 13:37, Peter B. West wrote: > >>The big problem is in defining the p.res step. Ho

Re: Area tree -> renderer ("pr.fo" for structure renderers)

Bertrand, See below... Bertrand Delacretaz wrote: >On Saturday 16 March 2002 14:52, Peter B. West wrote: > >>. . . >>The last stage of the FOP process translates one page >>description (the area tree) into another (the input to the target >>renderer.) >> &

Updates to xml docs

Arved, After Karen's post on her updates I checked the repository, and I note that you have installed the alt.design and understanding directories. Many thanks to you and to Cyril. Attached are "cvs diff -u" output files for xml-fop/build.xml and xml-fop/docs/design/book.xml whcih will bring

Area tree -> renderer

My comments earlier about the area tree and page description languages have started me thinking about the topic. The way I see it, there's no daylight between the area tree and the renderer(s). I was talking about the output from the area tree being a PDL, but Postscript and PDF are page desc

Re: development status

Nicola Ken Barozzi wrote: >From: "Arved Sandstrom" <[EMAIL PROTECTED]> > ... > I read the FO spec fully at >least 3 times ;-) > Impossible! Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [E

Re: development status

Nicola Ken Barozzi wrote: >From: "Peter B. West" <[EMAIL PROTECTED]> > >>There is very active development on FO Tree building, property >>resolution and layout models. A lot of that development is desisn >>speculation, such as the design notes I have been

Re: development status

Keiron, You have pre-empted my last post on this topic. Keiron Liddle wrote: > On 2002.03.14 10:55 Nicola Ken Barozzi wrote: > >> Ok, nice. This seems more like evolution than revolution, am I right? > > > You could say that. > The code is forming a revolution, not the people. We needed to go b

Re: [PROPOSAL] FOP+iText = FOP-NG -next generation-

Bertrand, Aside from my low opinion of SAX for process coupling, there should be no need for communication back from the renderer. The Area Tree should just give orders to the renderer. All of the layout decisions have been made by the time the Area Tree is constructed. The feedback is with

Re: [PROPOSAL] FOP+iText = FOP-NG -next generation-

Keiron Liddle wrote: > On 2002.03.14 09:00 Nicola Ken Barozzi wrote: > >> What I would like to see, is that FOP stops discussing about the >> logging, >> resolving, pipelineing and stuff and starts to focus on the core >> functionality. >> IMHO, the best way to get this thing going *quick* is to

Re: development status

Nicola, Comments interspersed. Nicola Ken Barozzi wrote: >From: "Keiron Liddle" <[EMAIL PROTECTED]> > >>There was a notice of this a number of months ago. Admittedly we have it >>the other way around. Maintenance releases are made from a branch. So the >>main branch is where the active develop

Re: [PROPOSAL] FOP+iText = FOP-NG -next generation- (was: mergingtwo libraries)

Nicola, I think there are a few issues to be considered here. Essentially, what is FOP? There may be a number of requirements of an XSL-FO processor. The basic one is, "Show me this on a page or screen." Any kind of renderer, using any approach whatsoever, will achieve this, more or less.

from-nearest-specified-value on compounds

Fops and others, What's the opinion on whether an assignment to a compound qualifies for from-nearest-specified-value() on one of the components? My attitude would be that it does qualify because of the implicit assignment to the component. Peter ---

Re: Serialization

Keiron, Thanks. I thought that would be the case. I'm looking at serializing a subtree and replacing it with a node that says where it can be found again. At the moment my Tree class has Node as an inner class. I'll have to pull them apart again. Peter Keiron Liddle wrote: > Hi Peter, >

Serialization

Dear Fops, I'm naïve about serialization (among other things.) Can anyone tell me whether it is possible to serialize an instance of an inner class without implicitly serializing the containing class instance? Peter - To un

Re: userconfig.xml

Polly, You are not the first, nor will you be the last, to be thrown by this. All of the work of the Options object is done in the constructor. You don't have to do anything more with it. It sets up a lot of static data, accessible by static methods, in a Configuration class. Have a look

[Fwd: text-shadow and text-decoration]

The editors, 7.16.5 "text-shadow" has offsets defined in terms of "horizontal distance to the right" and "vertical distance below" the text. The section also specifies: Inherited: no, see prose There is no mention of inheritance in the prose of section 7.16.5. 7.16.4 "text-decoration", lik

Re: Understanding FOP documentation

ll we send addtions to, and edits of, his stuff and my notes directly to you? Peter Arved Sandstrom wrote: >I can do this. Just let me know what branch it's for and any extra >processing involved. > >AHS > >-Original Message- >From: Peter B. West [mailto:[EMAIL P

Understanding FOP documentation

Cyril Rognon has been tracking Keiron's notes on Understanding FOP, and keeping me up to date with them. I am about to send him some minor corrections. However, neither Cyril nor I have access to the CVS for update. Keiron is busy with other things, so I would to be able to direct Cyril's w

Re: [Xslfo-proc-devel] Core function questions

Arved, As I read the spec, the diference is that "[i]t is an error if this property is not an inherited property," for inherited-property-value(). For from-parent(), it is the value of that property on the parent, regardless of inheritance. This is consistent with the handling of shorthands

Re: Options

Jeremias The files are *rather*, but not *entirely* static, especially scripts at the moment. It seems to me that in principle such file should be able to be changed completely independently of the code base. Peter Jeremias Maerki wrote: > >I see. Are those three not rather static so it wou

Re: Options

Jeremias, Jeremias Maerki wrote: >Hi Peter > ... >You'll have to create a GUI or use OS X. :-) Well, that leads me to the >question: What are you actually trying to do? We're talking about >solutions here, but not what you need them for (I think). > There's a very useful discussion going on abo

Re: [Understanding] Property Handling [5]

Karen, Thanks for this detailed info. What do you do about "ems" lengths in a marker? Peter [EMAIL PROTECTED] wrote: > Expressions involving "em" units which are relative to >font-size _are_ resolved during the FO tree building however. > -

Re: Options

Jeremias, Jeremias Maerki wrote: >Peter > >(comments inline) > >>In config.xml: >> >> >>userConfigFileName >>userconfig.xml >> >> > >Ok, that means FOP looks in the current directory for userconfig.xml. >I can agree with that. I guess there are pros and cons: This mechanism >can redu

Re: XMLSpy - FOP

Arved et al, To clarify further: there are three re-design efforts going on. Keiron & Karen in Java, building on the existing code base. Arved doing a ground-up redesign in Perl (protptyping) and C or C++, as he has discussed. Me, in Java, doing a ground-up. Do not despair. If Flannery O'

Re: Options

Jeremias Maerki wrote: > Hmm, why not? What would your default entry in the system config be (or > better: where does it look for the userconfig by default)? Jeremias, In config.xml: userConfigFileName userconfig.xml languageConfigFileName xml-lang.xml (More on la

Re: Options

Jeremias, Jeremias Maerki wrote: >I hope you forgive me my switching over to fop-dev which is the right >place for this discussion. > Of course. > >First, I'd like to start asking if you intend to work on this in the >maintenance or the main branch. If you're working on the main branch, I >woul

[Fwd: Re: Options]

As Cyril pointed out, this went to the wrong list. Peter Jeremias, Pardon my ignorance, but could you sketch out the nature of the problem for me? I ask in particular because the current situation is dirty. There is a lot of talk going on about the plumbing, which is generally over my h

Notes on multiple columns

I have added some notes on multiple columns to my discussion of footnotes. The excerpt is attached. Peter A possible method for multi-column layout and balancing with footnotes, using a galley-based approach. This note assumes a galley, as discussed above, flowing

Some notes on footnotes

Please find attached some preliminary notes on the implementation of footnotes. Peter Implementing footnotes Footnotes present difficulties for page layout primarily because their point of invocation in the flow is different from their

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

Re: REDESIGN: where I have been hiding

[EMAIL PROTECTED] wrote: >The other thing I've worked on is in the actual LayoutManager logic. >I've got this concept of a "BreakPosition" and have some code written at >the inline level (text, inline, line). The idea is that instead of an LM >calling generateAreas on its child LM, it repeatedly

Design issues: co-routines

FOPs, I am putting some xml notes together on design aspects of area tree construction. Attached is some xml with the notes so far. Comments solicted. Peter Implementing co-routines All general page layout systems have to solve the same

Re: FOP AWT Window Shuts Down Application

Christian Geisert wrote: > > Ok, I'll do it .. but it's to late for 0.20.3rc2 (which is already > on icarus, waiting for Arved to move it to daedalus) > Oops! I hope icarus is not on Solaris. It will go down any time now. Peter

[Fwd: Re: Integrating Tree into FO tree handling]

Bertrand Delacretaz wrote: >On Sunday 17 February 2002 06:07, Peter B. West wrote: > >>. . . >>FOTree maintains the property stacks with the initial value, current >>value and history of the properties being defined on elements of the >>FO Tree. It also implements

Re: REDESIGN: where I have been hiding

Karen, It's good to hear from you. In answer to your question, "Yes please," personally speaking. I would like to hear, inter alia, about the timing of property resolution. Peter [EMAIL PROTECTED] wrote: >I'm happy to see that we seem to be getting some new blood in the group >and I applau

Integrating Tree into FO tree handling

For those of you who were here when my Tree class was discussed, here is the latest on the integration of that datastructure into the expression of the FO Tree. The initial structure is a Tree class with a member class Node. (Node itself has a number of Iterator member classes.) Class FOTree

Re: [Understanding] FO Tree [3]

Keiron, Some questions below. Keiron Liddle wrote: > > > FO Tree > --- > > The FO Tree is a representation of the XSL:FO document. This represents > the steps Objectify from the spec. The Refinement step is part of reading > and using the properties which may happen immediately or during t

[Fwd: Inheritance from the layout-master-set]

Original Message Subject: Inheritance from the layout-master-set Date: Wed, 13 Feb 2002 16:10:52 +1000 From: "Peter B. West" <[EMAIL PROTECTED]> To: xsl-editors <[EMAIL PROTECTED]> The editors, Could you please clarify for me the role of properties d

Re: Multiple fonts

This was in the final PR, at least, and it is a piece of syntactical nastiness which comes to us from CSS. Not only is the font-family value a comma-separated list of indeterminate length, but individual names may include spaces, and such names need not be quoted. Syntax like this makes prop

Re: StructureEvents concept

Bernard, What sort of structure does rtf exhibit? Is it a page-based structure, or is it divided, like xslfo, into page definitions and flows? This is a critical difference as far as the design goes. From what you say below, it seems to rely on a flow-based model. Peter Keiron Liddle wrot

Re: Seeking Comments on Status of Project

Matthew L. Avizinis wrote: > >Well, now that I consider it more, I have to say that I guess I am just used >to a "corporate" way of developing software that has a definite >administrative structure and plan of action with people assigned specific >tasks. Since I've never worked on an Open Source

Documentation volunteer?

Do we have a volunteer to track Keiron's tutorials and turn them into web page documentation? Keiron has recently extended the documentation generation on the CVS trunk to make this process a bit easier. Keiron tells me that Apache is readying a major overhaul of its web site and xml->html ge

Re: Seeking Comments on Status of Project

Matthew, Yes, we're all entitled to a little ranting now and then. So I'll rant a little, and end with a few practical suggestions. As to who's in charge: Arved is the man, but Arved has recently started a new job, so you can imagine what his current situation is. Nonetheless, he is prepar

Web site maintenance

Keiron, Was it you who reorganised the xml-docs/html-docs framework on the development branch? If so, do you see any problems in retro-fittting that structure to the maintenance branch? Peter - To unsubscribe, e-mail: [EMAI

Re: Seeking Comments on Status of Project

Keiron, Welcome back. Been on holidays? Looking at the number of people who have expressed an interest in being of some help, I thought it might be of some use for you or Karen, or both, to run a "school". I appreciate that many of the thorny problems with fop require the redesign, but if t

Re: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available

Arved Sandstrom wrote: >Hi, Peter > >I've included an attachment which is a tree listing of what I obtained with >wget. > >Please review and let me know what I missed. Thanks. > Arved, All of the html-docs stuff is redundant as far as the docs build is concerned - it will all be generated.

Re: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available

t; >I can do the getting...I have cable. > >Arved > >-Original Message- >From: Peter B. West [mailto:[EMAIL PROTECTED]] >Sent: January 24, 2002 12:25 AM >To: [EMAIL PROTECTED] >Subject: Re: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available > > >Arved,

Re: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available

ay to specify the dtd in the production files? Peter Peter B. West wrote: > Arved, > > Ok. I'll just have to find out how to integrate my docs, which are at > the top level, into the existing top-level elements. Keiron said > soemthing about creating a book. If anyone

Changes to XML parsing methods

Dear readers, I have added some methods to XMLEvent.java to make usage a bit easier, mainly: getStartElement(SyncedCircularBuffer events, LinkedList list) expectStartElement(events, list) The objects in list essentially contain a URI and local name, and the methods return the first start elem

Re: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available

Arved, Ok. I'll just have to find out how to integrate my docs, which are at the top level, into the existing top-level elements. Keiron said soemthing about creating a book. If anyone has done this, and has a short recipe, I would be grateful. Otherwise I'll sort it oout and get back to

Re: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available

Arved, Keiron mentioned the possibility of including my recent html design notes in the distribution. Is that feasible for this release? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAI

Re: Documentation on SAX parsing and modularisation

Listners, I have added some details of the XMLEvent buffer access methods to the above documentation. Peter - To unsubscribe, e-mail

Documentation on SAX parsing and modularisation

Dear list, I have added some documentation on the approach I have taken to the related topics of SAX parsing of the input source and modularisation of the FOP processing. I also generated javadocs for the experimental

Re: xml-docs

Keiron, Without having resoved the generation of books, I have converted my html to xml, and run it against a cut-down fop.xml in one of the earlier builds. The results are at . The xml files are in the parallel x

xml-docs

Keiron, I went to cvs looking for examples of how to write the xml for multi-level menus like the "new design" menus, but could not see where it was happening. I found this - - in fop.xml, but not the source. Where is it? Peter -

Re: Properties documentation

Keiron, Thanks for clueing me up on the documentation. I strongly accept you recommendation, and I will gladly use it in future. Btw, the heading graphics from the the design documents seem to have been screwed up. Have you noticed this? Peter Keiron Liddle wrote: > Hi Peter, > > Thanks

Re: Properties documentation

on a particular browser are still unpredictable. Peter Bertrand Delacretaz wrote: >On Saturday 29 December 2001 02:57, Peter B. West wrote: > >>. . .let me know if there is some easy way to get full >>conformance with the Apache XML norm, or if there are severe problems >>vi

Properties documentation

Dear list, After sepnding some days wrestling with various graphics tools in linux in an attempt to make html that looked like the standard apache documentation, I finally surrendered and made do with CSS to create a facsimile that should be sufficient for this list. It works with a recent M

compound property inheritance

Karen, What do you make of the following direction in 5.11? "Compound values of properties are inherited as a unit and not as individual components. After inheritance any complete form specification for a component is used to set its value." I take this to mean that individual compund compone

Re: Numeric properties

Joerg, I must remember to trim. I must remember to trim. I must... Peter Peter B. West wrote: > Christopher, > > Many thanks. It's glaringly obvious, isn't it? Oh well. - To unsubscribe, e-mail: [E

Re: Numeric properties

Christopher, Many thanks. It's glaringly obvious, isn't it? Oh well. Peter Christopher R. Maden wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >At 06:25 6-12-2001, Peter B. West wrote: > >>I don't know how kosher this is, and would appreciate

Numeric properties

I found it very difficult to develop a coherent way of representing numeric property values when I was looking at the property values expression evaluator. My initial approach had a structure that looked something like: PropertyValue |

Optional + on integer and number

of an optional '+' or '-' character followed by a sequence of digits followed by an optional '.' character and sequence of digits. A property may define additional constraints on the value. Endquote Peter -- Peter B. W

Evaluating and

FOPs, I have sent the follwing enquiry to the editors. The editors, I cannot see any provision for , or in Section 5.9. How is it intended that such properties be evaluated? Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall

[Fwd: ]

tent-type:xml/svg". 'A namespace specification has the form "namespace-prefix:" followed by a declared namespace prefix, e.g., content-type="namespace-prefix:svg". If the namespace prefix is null, the content-type refers to the default namespace.' The

Re: Merging jfor into FOP - what's the plan?

> -> StructureRenderer > > StructureRenderer is > EITHER Layout + PrintRenderer > OR StructureProcessor (RTF, MIF, etc.) > > What we need to find out is how much the existing FOP and these "structure > renderers" have in common. > > - Bertrand &g

... and scripts

I have added a script list from the first draft of the standard. Peter Peter B. West wrote: > I have created a class LanguageFileReader and a config file xml-lang.xml > to adrees the (slightly)dynamic nature of the 639/3166 codes. A > modified Options class checks for languageConfi

Coountries and languages

HashMaps in Configuration. The codes can then be adjusted independently of builds. All in my experimental files, of course. Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall

Re: 5.11 and

subsequent discussions of the topic on fop-dev into the xsl-editors list. I see that this has happened. Sorry Max. Peter Christopher R. Maden wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > At 05:37 23-11-2001, Peter B. West wrote: > >>In 5.11 the spec. has: &g

Re: uri parser?

Keiron, Thanks. I was looking at the handling of 'url(...)' in the property expression parser, and I thought that the general solution would be a uri parser. Peter Keiron Liddle wrote: > On 2001.11.20 16:23 Peter B. West wrote: > >> Does anyone know of a general URI

5.11 and

- and 3-letter country codes. Is the spec correct here? Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go?" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additiona

Re: convert line height value from pixel to pt

) , >> >> When I run FOP 0.20.0, I found the line height is wrong. >> >> So, I not sure how to convert the value from pixel to pt, anyone know how >> to calculate? >> >> >> Thank you. >> >> lpkhoo. > > > --------

Re: uri parser?

oken for a URI-SPECIFICATION in PropertyParser, and wondered whether it was easy to find a parser. Peter Ulrich Mayring wrote: > "Peter B. West" wrote: > >>Does anyone know of a general URI parser tucked away in the code >>somewhere, or failing that, available els

uri parser?

Does anyone know of a general URI parser tucked away in the code somewhere, or failing that, available elsewhere? Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go?" --

Question about colour

byte array? What is the relationship between the the linear RGB space and sRGB, which, from my glance at the document, seems to involve a color profile, and between the sRGB and the ICC color profiles? All information will be gratefully received. Peter -- Peter B. West [EMAIL PROTECTED]

Re: [REDESIGN] Initial cut at Layout Manager

ing useful whatsoever yet. >>> >>>Regards, >>>Karen >>> >>- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, email: [EMAIL PROTECTED] >> > > -

layout-master-set and the FO tree

ent and fo:flow. Peter -- 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: User-config (RE: Question on XSLTInputHandler)

;>thanks in advance for any pointers, >> >>Ulrich >> >>-- >>Ulrich Mayring >>DENIC eG, Systementwicklung >> >>--------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >

Re: Crossposts

lfo-proc list, explain what > you were about and are about, and indicate that you intend to assist with > high-level design, if that strikes your fancy. > > Regards, > Arved > -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go

Changes to FOPropertyConsts and FObjects

carry this information, but the problem of deriving the set of applicable properties for a given FO persuaded me to the HashSets. These are, as before, available at http://home.iprimus.com.au/pbwest Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall

Re: embedded configuration file

-- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go?" -

Serializing subtrees

-- 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]

Code home, integerization, configuration

output modes and files. Naturally, these can be overridden in the command line. Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go?" - To unsubscribe, e-mail: [EMAIL PROT

Stash

Listners, If there is any interest in the work I am doing, would it be possible to set up a stash somewhere for my files? At the moment I am saving things on my ISP's web server. Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom s

[Fwd: Re: Compound datatypes]

Dear List, I have some responses from Paul Grosso to questions about compound properties. Peter Original Message Subject: Re: Compound datatypes Date: Wed, 03 Oct 2001 09:02:38 -0400 From: Paul Grosso <[EMAIL PROTECTED]> To: "Peter B. West" <[EMAIL PROTE

[Fwd: Re: Questions about compound type]

Original Message Subject: Re: Questions about compound type Date: Thu, 04 Oct 2001 09:16:43 -0500 From: Paul Grosso <[EMAIL PROTECTED]> To: "Peter B. West" <[EMAIL PROTECTED]>, xsl-editors <[EMAIL PROTECTED]> Peter, Again, thanks for your input.

[Fwd: Re: Compound datatypes: ]

Original Message Subject: Re: Compound datatypes: Date: Thu, 04 Oct 2001 09:17:54 -0500 From: Paul Grosso <[EMAIL PROTECTED]> To: "Peter B. West" <[EMAIL PROTECTED]>, xsl-editors <[EMAIL PROTECTED]> At 12:21 2001 09 28 -0400, Peter B. West wrote:

Re: Compound datatypes

of refinement. And > property correspondence maps individual properties into traits. Doesn't the above imply that the components of a compound are assigned to before refinement? > The intent in the case of compound datatypes is that each > individual component is mapped into a trait during the > refinement process. > > We will try make this more explicit somewhere (either in 5.3 > or 5.11, I would think, but the editors will decide). > > Explicit assignment to a relative property isn't overridden > by the mapping of absolute to relative and components are > handled individually. Therefore, for example: > >border-top-width="10pt" > border-top-width.minimum="5pt" > border-before-width.optimum="20pt"> > > (assuming lr-tb) ends up setting traits in a fashion equivalent to: > > border-before-width.minimum="5pt" > border-before-width.optimum="10pt" > border-before-width.maximum="20pt" > border-before-width.conditionality="discard" > > paul I'm sorry if this is repetetive, but I still see a problem here. Peter -- 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: Questions about compound type

Paul Grosso wrote: > Peter, > > Again, thanks for your input. Comments embedded. > > At 00:53 2001 09 27 -0400, Peter B. West wrote: > >>The following sections contain references to start-space and end-space. >>I assume that these references should b

<    3   4   5   6   7   8   9   >