[Bug 13804] New: Is normative rgb-icc() prototype wrong?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Bug 13804] New: Is normative rgb-icc() prototype wrong?

Bugzilla from bugzilla@jessica.w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13804

           Summary: Is normative rgb-icc() prototype wrong?
           Product: XSLFO
           Version: 1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]
         QAContact: [hidden email]


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                                   [hidden email]
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

--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.