Subject: Re: page-n-columns in RTF From: Matthias Clasen <clasen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> Date: Mon, 21 Jun 1999 23:35:31 +0200 |
> > Actually, I think that even with full page-sequence and column-set-sequenc > > support, you can't use different column-set-models on the same page. Or > > have I misread the spec ? > > > But you can span several columns. So couldn't some stuff be "one column" > by spanning it? Perhaps, but 1) it would be a hack, and 2) it wouldn't allow you to do something like "one-column in the upper half, two-column in the lower half", only "first paragraph one-column, second paragraph two-column". My concern is with the column-set-model-map characteristic. it is explained as "whenever an area from this column-set-sequence is placed in an area whose nearest ancestor of type page-region uses the specified page-model, then the specified column-set-model shall be used." Since all page-regions of a page "use" the same page-model (I'd rather say they are specified in the same page-model), you only get one column-set-model per page. I don't think this is the intended meaning. -- Matthias Clasen, Tel. 0761/203-5606 Email: clasen@xxxxxxxxxxxxxxxxxxxxxxxxxx Mathematisches Institut, Albert-Ludwigs-Universitaet Freiburg DSSSList info and archive: http://www.mulberrytech.com/dsssl/dssslist
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: page-n-columns in RTF, Peter Nilsson | Thread | Re: page-n-columns in RTF, Allan Bowhill |
Re: Convert node to String?, David Keegan | Date | Scheme Programming Reference, Ralph Ferris |
Month |