Peter B. West | 6 Feb 17:11 2003
Picon
Picon

Questions about markers


Background:

Processing of large FO documents is both cpu and memory intensive.
The volume of property information is partly responsible for the
memory requirement.  In order to minimise this demand, I want to
be able to divide the property construction into two phases with
different requirements.

1. The construction of individual branches of the FO tree.  During
this phase, as tree building proceeds down a particular branch
towards a leaf node, the ancestor nodes of that leaf are constructed
without knowledge of the requirements of descendants.  Therefore,
no optimisaton is possible of the set of properties which must be
maintained at each ancestor node.  Whether a particular specified
or inherited property is required by an individual ancestor node,
a full set of properties must be developed and maintained (at
least conceptually) until the inheritance and functional reference
requirements of the last descendant have been determined.  These sets
are constructed as control descends down the tree, making the set
available to each child and its descendants.

2. As control retreats back up the tree, having constructed the
property sets of each of its descendants, there is no further need
for any but the actual properties pertaining to each individual node.
This allows for considerable space (and subsequent performance)
optimisations, by, e.g., reducing the applicable property set to
the minimum required by the FO, and maintaining that set in an
array of predetermined length, whose elements can be accessed by
a mapping array, whose length and contents are predetermined.
(Continue reading)

Peter B. West | 6 Feb 17:21 2003
Picon
Picon

Percentages + absolute lengths


Please clarify the editors' expectation for the resolution of
an expression like "25% + 3pt" an FO where the relative value
is resolved in terms of an enclosing reference area.

The difficulty with respect to such expressions that I have
experienced in implementing FO tree building is that they force
property resolution into dependency on Area tree construction.
Even in the simplest cases, the evaluation of such expressions
assumes the availability of page-based information, as opposed to
the FO tree's flow and static-content view.  I those cases where
the dimensions of areas may be dependent on look-ahead layout
and retries, e.g. during attempts to resolve column widths for
"auto" column layout, the dependency becomes even more tortuous.

The end result is that such expressions must be carried around in
the constructed FO tree, and only resolved as the applicable FO's
areas are generated and returned, or re-generated and returned.
This greatly complicates the expression parsing which must be
done early for the FO tree building to be able to proceed.

While a simple percentage, e.g., "25%", suffers from the same
uncertainties, it can at least be reduced to a single datum,
whose resolution makes no further demands of the expression
parser, which in turn simplifies the parser.

My current implementation of FO tree building rejects
expressions such as "25% + 3pt" on the basis that (part of)
"...the expression value cannot be converted to the necessary
type for the property value," (5.9.12) within the context of
(Continue reading)

Fitzgerald Keith | 6 Feb 20:02 2003

XSL DTD/Schema

Hello,

I am looking for a DTD or schema that outlines all the tags in the XSL namespace. Where can I find this??? Please help! Email me at fitzgerald_keith <at> prc.com

Thanks
Keith

Les Perley | 6 Feb 16:29 2003

Errata - XSL Spec, Version 1.0

While reviewing the XSL specification, I've come across the following error that does not appear in the current "list of known errors" at http://www.w3.org/2001/10/REC-XSL-20011015-errata.

The error is in Section 7.25.10. "maximum-repeats", where it states:
 

7.25.10 "maximum-repeats"

XSL Definition:

Value: <number> | no-limit | inherit
Initial: no-limit
Applies to: fo:repeatable-page-master-reference, fo:repeatable-page-master-alternatives
Inherited: no
Percentages: N/A
Media: visual

Specifies the constraint on the maximum number of pages in the sub-sequence of pages that may be generated by an fo:page-sequence that uses the fo:repeatable-page-master-reference or fo:repeatable-page-master-alternatives on which this property is specified.

The values have the following meanings:

no-limit

No constraint is specified.

<integer>

...

"Value:" lists "<number>" but under "The values have the following meanings:" the reference is to "<integer>" and not "<number>".

Les Perley

XIA Systems Corporation

 

Kay, Michael | 6 Feb 23:43 2003

RE: XSL DTD/Schema

There is a schema for XSLT 2.0 published as part of the XSLT 2.0 working draft, and a DTD for XSLT 1.0 published as part of the XSLT 1.0 Recommendation.
 
Michael Kay
-----Original Message-----
From: Fitzgerald Keith [mailto:Keith.Fitzgerald <at> northropgrumman.com]
Sent: 06 February 2003 19:02
To: 'xsl-editors <at> w3.org'
Subject: XSL DTD/Schema

Hello,

I am looking for a DTD or schema that outlines all the tags in the XSL namespace. Where can I find this??? Please help! Email me at fitzgerald_keith <at> prc.com

Thanks
Keith

Oleg Tkachenko | 7 Feb 14:26 2003

Re: XSL DTD/Schema


Fitzgerald Keith wrote:

> I am looking for a DTD or schema that outlines all the tags in the XSL 
> namespace. Where can I find this??? Please help! Email me at 
> fitzgerald_keith <at> prc.com

And if you are looking for XSL-FO dtd/schema, take a look at
1. "An unofficial DTD for XSL Formatting Objects"
http://www.renderx.com/Tests/validator/fo.dtd.html
2. http://cvs.apache.org/viewcvs.cgi/xml-fop/src/foschema/

--

-- 
Oleg Tkachenko
Multiconn Technologies, Israel

Werner Donné | 8 Feb 16:43 2003
Picon

Deviation margin-left and margin-right from CSS


Hi,

The margin-left and margin-right properties are taken over from CSS. However, they
don't completely behave as in CSS. More specifically the value "auto" is treated
differently. Section 5.1.2 states that for auto values the formulas must be applied.
In this case it would be the last two formulas of section 5.3.2. As a consequence,
it is the same as if margin-left or margin-right were absent. The auto value is not
treated as an explicit value. In my opinion it should be and it should be computed
according to the CSS rules, from which the properties are taken over, even if that
implies an exception to the indentation rules. I see no point in being only partially
compatible with CSS properties.

A practical consequence, for example, is that a fixed-width block which is stacked
in another block can't be centered through setting the margin-left and margin-right
properties to "auto", such as it is the case in CSS. The same goes for aligning the
stacked block to the left or right.

Regards,

Werner.
--

-- 
Werner Donné  --  Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803	e-mail: werner.donne <at> re.be

Paul Grosso | 15 Feb 22:39 2003

Re: Errata - XSL Spec, Version 1.0


Thanks, you are correct.

We already have this on our internal errata list which should
get updated shortly.

paul

At 09:29 2003 02 06 -0500, Les Perley wrote:

>While reviewing the XSL specification, I've come across the following error that does not appear in the
current "list of known errors" at <http://www.w3.org/2001/10/REC-XSL-20011015-errata>http://www.w3.org/2001/10/REC-XSL-20011015-errata.
>The error is in Section 7.25.10. "maximum-repeats", where it states:
> 
>
>
>7.25.10 "maximum-repeats"
>
>
>
>XSL Definition:
>Value: <number> | no-limit | inherit
>Initial: no-limit
>Applies to: fo:repeatable-page-master-reference, fo:repeatable-page-master-alternatives
>Inherited: no
>Percentages: N/A
>Media: visual
>
>Specifies the constraint on the maximum number of pages in the sub-sequence of pages that may be generated
by an fo:page-sequence that uses the fo:repeatable-page-master-reference or
fo:repeatable-page-master-alternatives on which this property is specified.
>
>The values have the following meanings:no-limit  
>No constraint is specified. 
><integer>  
>... 
>
>"Value:" lists "<number>" but under "The values have the following meanings:" the reference is to
"<integer>" and not "<number>".
>
>Les Perley
>
>XIA Systems Corporation
>
> 

Paul Grosso | 22 Feb 00:01 2003

Updated public XSL (FO) Disposition of Comments document


The public XSL (FO) Disposition of Comments document at
http://www.w3.org/Style/XSL/2003/01/FO-DoC
has just been updated with responses to your comments.
If you are unsatisfied with the response, please feel
free to post another comment to xsl-editors <at> w3.org.

Thank you for your interest in XSL FO and for your
patience as we work our way through the comments.

Paul Grosso
for XSL FO Subgroup

Éric Bischoff | 22 Feb 09:20 2003
Picon

Re: Updated public XSL (FO) Disposition of Comments document


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Saturday 22 February 2003 00:01, Paul Grosso a écrit:
> The public XSL (FO) Disposition of Comments document at
> http://www.w3.org/Style/XSL/2003/01/FO-DoC
> has just been updated with responses to your comments.
> If you are unsatisfied with the response, please feel
> free to post another comment to xsl-editors <at> w3.org.
>
> Thank you for your interest in XSL FO and for your
> patience as we work our way through the comments.
>
> Paul Grosso
> for XSL FO Subgroup

Hi Paul,

Nice compilation Work.

However I'm still unhappy with the comments of one of my contribs :

==================================================
No the erratum is correct. The quotes around the "string" are optional and 
have been left out in the example. The enclosing single quotes ensure that 
the value is interpreted as a string literal by the expression language. Note 
that "url" is not a function, but a piece of syntax borrowed from CSS2.
==================================================

Okay with that, but it contradicts the spec then (perharps it's just a bug in 
the spec) :

At
	http://www.w3.org/TR/xsl/slice7.html#src
one can read :
==================================================
	7.28.7 "src"

	XSL Definition:

	Value: 
		<uri-specification> | inherit
==================================================

Please note that it does not accept a <string>, but an <uri-specification>

It's been a long time I wanted to tell you that, but I lacked time to do it. 
Sorry about that.

So I think that that issue is still unclosed.

I hope it helps.

PS Most people know the stylesheets standard as "XSL-FO". I advise that it 
gets reflected in the standard's title as well (currently it's "XSL").

PPS The current standard is uselessly complicated : too much exceptions, too 
much special cases, not enough uniformity. I would say that it would be great 
if it could evolve to become much more orthogonal in the next versions. For 
example, url() and rect() should become functions like any other in next 
versions. All units should be processed in an uniform way. Etc.

- -- 
According to a recent survey, 82% of the citizens of the
European Union are against American planned invasion of Irak.
(EOS Gallup Europe, 15,080 people aged 15+, 21st to 27th January 2003)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+VzLefYJTRPWp6rkRAtbqAJ9y9ho+ZmuVycUK4+vs26CW2dI5PgCeI6pd
JI38VPTIjrilFOolLZ6Ockg=
=ifL4
-----END PGP SIGNATURE-----


Gmane