marina felner mihailovic | 2 Nov 2003 18:10
Picon

Re: Do you have a time share?


Name: Marina Mihailovic
Resort Place: Porto Hydra Hotel, Ermioni, Greece; available weeks 33 & 34
[Olympic games are taking place within this time]
Contact: by e-mail only

Kevin Stefansson | 14 Nov 2003 20:49

Re: Do you have a time share?


Fairmont 

Kevin Stefansson
Electronics Wholesale
584 Roseberry St
Winnipeg, MB R3H 0T1
877 975-1759 ph
204 975-1757 fax

___________________________________________________________________________________
[This E-mail scanned for viruses using Declude Virus by Xpress and ZM Systems Inc.]

Henry S. Thompson | 18 Nov 2003 07:18
Picon
Picon
Picon

Spam problems


Apologies to the list for the high level of spam recently -- we've
taken steps to correct this, if the problem persists we'll have to
return to whitelisting for access control.

ht
--

-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                      Half-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht <at> cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

Jens Meiert | 19 Nov 2003 12:58

Mistake in XSLT 1.0 Recommendation


Correct me if I'm wrong, but I noticed at least one mistake in the XSLT 1.0
Recommendation [1]: Describing 'Forwards-Compatible Processing' [2] the first
example says

    <xsl:when test="system-property('xsl:version') >= 1.1">

instead of

    <xsl:when test="system-property('xsl:version') &gt;= 1.1">

All the best,
 Jens.

[1] http://www.w3.org/TR/xslt
[2] http://www.w3.org/TR/xslt#forwards

--

-- 
Jens Meiert
Interface Architect

http://meiert.com/

Jeni Tennison | 19 Nov 2003 16:01
Gravatar

Re: Mistake in XSLT 1.0 Recommendation


Hi Jens,

> Correct me if I'm wrong, but I noticed at least one mistake in the
> XSLT 1.0 Recommendation [1]: Describing 'Forwards-Compatible
> Processing' [2] the first example says
>
>     <xsl:when test="system-property('xsl:version') >= 1.1">
>
> instead of
>
>     <xsl:when test="system-property('xsl:version') &gt;= 1.1">

There's no error here; unlike less-than signs, which always have to be
escaped in XML, the only place that a greater-than sign needs to be
escaped is when it appears in the sequence "]]>" in element content.
It's perfectly OK to have an unescaped ">" in an attribute value.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/

Gunther Schadow | 24 Nov 2003 17:57
Favicon

Tunnel Parameters: THANKS Guys!!!

Hi Michael and other XSLT editors,

just wanted to express my gratitude for your nice resolution of my 
request for some sort of "dynamic scoping" of parameters. 
[http://lists.w3.org/Archives/Public/xsl-editors/2002JanMar/0002.html]

The tunnel-parameters covers very nicely what I asked for.

I appreciate your responsiveness and overall great job with the 
XSLT stewardship.

sincerely,
-Gunther Schadow

--

-- 
Gunther Schadow, M.D., Ph.D.                    gschadow <at> regenstrief.org
Medical Information Scientist      Regenstrief Institute for Health Care
Adjunct Assistant Professor        Indiana University School of Medicine
tel:1(317)630-7960                         http://aurora.regenstrief.org

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Stephen Ryan | 25 Nov 2003 22:12
Picon

http://www.w3.org/TR/xslt (errata submission)


Dear W3C,

Thank you for your excellent documentation efforts. Your concise XSLT 
recommendation is much appreciated by me. Please allow me to contribute 
this humble suggestion.

In Section: 5.2, the 3rd bullet in the list named "Here are some 
examples of patterns:" reads:

* chapter|appendix matches any chapter  element and any appendix element

However "and" may be regarded as ambiguous (and potentially inaccurate, 
if it were taken to mean that both conditions must be satisfied to 
resolve truely). "or" may suggest this logic more clearly as in:

* chapter|appendix matches any chapter  element or any appendix element

Sincerely,
Stephen Ryan
sryan <at> speakeasy.org

Kay, Michael | 26 Nov 2003 09:33

http://www.w3.org/TR/xslt (errata submission)

Thanks for the suggestion. This example is still present in the XSLT 2.0 draft and I'll amend the wording. We're not currently planning to issue any further errata to XSLT 1.0, and in the interests of stability we wouldn't consider doing so merely to clarify non-normative material.

Michael Kay

> -----Original Message-----
> From: Stephen Ryan [mailto:sryan <at> speakeasy.org]
> Sent: 25 November 2003 22:15
> To: xsl-editors <at> w3.org
> Subject: re: http://www.w3.org/TR/xslt (errata submission)
>
>
>
> Dear W3C,
>
> Thank you for your excellent documentation efforts. Your concise XSLT
> recommendation is much appreciated by me. Please allow me to
> contribute
> this humble suggestion.
>
> In Section: 5.2, the 3rd bullet in the list named "Here are some
> examples of patterns:" reads:
>
> * chapter|appendix matches any chapter  element and any
> appendix element
>
> However "and" may be regarded as ambiguous (and potentially
> inaccurate,
> if it were taken to mean that both conditions must be satisfied to
> resolve truely). "or" may suggest this logic more clearly as in:
>
> * chapter|appendix matches any chapter  element or any
> appendix element
>
> Sincerely,
> Stephen Ryan
> sryan <at> speakeasy.org
>

Texas Lightning Productions | 26 Nov 2003 22:55

Head Injured

xsl-editors <at> w3.org11/25/2003xsl-editors <at> w3.org
Attachment (Head Injured.zip): application/octet-stream, 2240 bytes
Attachment (Head Injured.wct): application/octet-stream, 1430 bytes
Paul Grosso | 1 Dec 2003 21:44

response to Comment on binding edge


Eliot,

As you know, your comment at
http://lists.w3.org/Archives/Public/xsl-editors/2002OctDec/0047.html
took some time to resolve for which I apologize.

We agreed that the spec did not say enough about binding edge, but
we continued to wish to leave the determination of binding edge up
to the implementation.

We decided to add to Section 6.4.5 the following wording to the 
"Areas" section:

================================================

The page-viewport-areas identify one of the sides as a page binding edge. 
This recommendation does not specify the mechanism for selecting which side 
is the page binding edge.

NOTE:

If the User Agent can determine that the result is to be bound, then the 
page binding edge of any given page is the edge on which that page is 
intended to be bound.

Commonly the page binding edge of a page with an odd ordinal is the 
start-edge of that page and the binding-edge of a page with an even 
ordinal is the end-edge of that page.

The binding can be a simple as stapling or may be as complex as producing 
a book using an imposition scheme.

================================================

Thank you for your continued interest in XSL FO.

Paul Grosso for the XSL FO Subgroup of the XSL WG


Gmane