This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13804 - Is normative rgb-icc() prototype wrong?
Summary: Is normative rgb-icc() prototype wrong?
Status: NEW
Alias: None
Product: XSLFO
Classification: Unclassified
Component: XSL-FO (show other bugs)
Version: 1.1
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Tony Graham
QA Contact: Mailing list for comments on XSL (XSl-FO)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-17 11:05 UTC by Tony Graham
Modified: 2011-08-17 11:05 UTC (History)
0 users

See Also:


Attachments

Description Tony Graham 2011-08-17 11:05:11 UTC
The rgb-icc() prototype [1] in the normative HTML for XSL 1.1 is:

color rgb-icc(numeric, numeric, numeric, NCName, numeric, numeric)

However, the non-normative XML source [2] for XSL 1.1 contains:

<proto name="rgb-icc" return-type="color"><arg type="numeric"/><arg type="numeric"/>
<arg type="numeric"/><arg type="NCName"/><arg type="numeric"/><arg type="numeric" occur="rep"/></proto>

I.e., the 'occur="rep"' on the last <arg> does not make it any different from an <arg> without it.

In contrast 'occur="opt"' adds a "?" after the argument in the rendered prototype.  E.g., in 'system-font()'.

Was 'occur="rep"' supposed to add a "+" after the argument name in the rendered prototype?

Regards,


Tony Graham                                   tgraham@mentea.net
Consultant                                 http://www.mentea.net
Mentea       13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
 --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
    XML, XSL FO and XSLT consulting, training and programming

[1] http://www.w3.org/TR/xsl11/#expr-color-functions
[2] http://www.w3.org/TR/2006/REC-xsl11-20061205/xslspec.xml