W3C home > Mailing lists > Public > www-style@w3.org > May 2004

Re: [CSS3 UI] Last Call comments

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Tue, 04 May 2004 22:00:36 -0700
To: Susan Lesch <lesch@w3.org>, <www-style@w3.org>
Message-ID: <BCBDC2D2.3D0E1%tantek@cs.stanford.edu>

Hello Susan,

Upon double-checking the archives I was unable to find my response to your
email.  Thus apologies for the belated reply.

In short, all your comments were accepted and the changes you suggest have
been made for the CSS3-UI CR draft.

Thank you very much for your feedback and suggested corrections.  Your input
has certainly improved the quality of the CR draft.


Tantek Çelik
editor, CSS3 Basic UI module

On 7/31/03 8:45 PM, "Susan Lesch" <lesch@w3.org> wrote:

> Hello,
> These are very minor Last Call comments for your "CSS3 Basic User
> Interface Module" Working Draft [1]. I think it looks nice.
> In the Status section, please match caps to the W3C Process Document [2]
> (e.g., s/working group/Working Group/, s/working draft/Working Draft/,
> s/style activity/Style Activity/). Also the CSS21 link would be
> http://www.w3.org/TR/CSS21/
> When HTML 4 comes up, you might add XHTML 1.0.
> s/This spec does not defined/This spec does not define/
> s/which portion of a the contents/which portion of the contents/
> s/all the elements contents/all the element's contents/
> s/it and the platform is capable/it and the platform are capable/
> s/recommendation/Recommendation/
> External links need a reference like this for people who print:
>   HTML4 attribute TABINDEX
> becomes:
>   HTML4 attribute 'tabindex' ([HTML4], section 17.11.1)
> (see http://www.w3.org/2001/06/manual/#linking-within)
> In citations, the title of the work would be the link. There's an
> example here: http://www.w3.org/2001/06/manual/#ref-section
> This sentence:
>   The <uri> should indicate (through the use of a fragment
>   identifier) the element to which the focus is to be navigated to in
>   response to directional navigation input respective to the specific
>   property.
> could read (I think. You can probably do better.):
>   In response to directional navigation input, the <uri> should
>   indicate the element to navigate to through the use of a fragment
>   identifier.
> Please spell out first occurrence: user agent (UA). Then you can use
> UA. Or else use user agent throughout.
> It would take some work to do but it might help if each occurrence of a
> property, element and attribute was marked up in lowercase 'code'. (I
> think this will help translators decide when to translate for example
> 'icon', and it might make the spec easier to read in English.) Some
> specs also differentiate properties from elements from attributes with
> color.
> [1] http://www.w3.org/TR/2003/WD-css3-ui-20030703/
> [2] http://www.w3.org/2003/06/Process-20030618/
> Best wishes for your project,
Received on Wednesday, 5 May 2004 01:08:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:13 UTC