W3C home > Mailing lists > Public > www-international@w3.org > January to March 2007

RE: CSS3 Text - Edit suggestions

From: Paul Nelson (ATC) <paulnel@winse.microsoft.com>
Date: Fri, 23 Feb 2007 02:09:00 -0800
Message-ID: <49C257E2C13F584790B2E302E021B6F91297205F@winse-msg-01.segroup.winse.corp.microsoft.com>
To: "fantasai" <fantasai.lists@inkedblade.net>
CC: "WWW International" <www-international@w3.org>, <www-style@w3.org>

I liked Asmus' suggestion to make the information a UTN.

-----Original Message-----
From: fantasai [mailto:fantasai.lists@inkedblade.net] 
Sent: Friday, February 23, 2007 4:45 PM
To: Paul Nelson (ATC)
Cc: WWW International; www-style@w3.org
Subject: Re: CSS3 Text - Edit suggestions

Paul Nelson (ATC) wrote:
> What I am saying is that an annex/appendix should be created that has
> the information and publish that annex/appendix. This should be doable
> in a short amount of time.

Ok, I think I see what you mean. I can certainly shift the definition
into an appendix in CSS3 Text. I'm not sure how you want it done,
though.
Should I write it to define a 'tibetan' keyword, but define it within
an informative appendix; or should I write only the description of how
the justification system works, and say that CSS3 does not provide a
means of triggering this sytem?

Personally, I feel that putting it in an appendix makes it feel more
important and more permanent than marking it as to-be-deleted.. but
if you prefer putting it in an appendix, I can do that.

~fantasai
Received on Friday, 23 February 2007 10:08:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:09 GMT