W3C home > Mailing lists > Public > www-style@w3.org > February 2011

Re: [css3-text] New WD of CSS Text Level 3

From: Xaxio Brandish <xaxiobrandish@gmail.com>
Date: Fri, 25 Feb 2011 21:58:53 -0500
Message-ID: <AANLkTi=DOJonwiEMCXCLL2ES7_0YMYgxdH-ABXaADSGG@mail.gmail.com>
To: Bert Bos <bert@w3.org>
Cc: W3C style mailing list <www-style@w3.org>
Good evening,

I was reading the editor's draft and had a few thoughts:

Section 5.2 (word-break):
Under value "break-all":

Might this want to reference UAX#29 or link to it from the term "grapheme
clusters" since it is not defined this early in the draft?

The text

Hyphenation is not applied.
>

is used here.  It is not used for the other values.  Before the list of
value definitions, would it make sense to say "Hyphenation is applied unless
otherwise specified." ?

********************************************

Section 6 (hyphenation):

Because of the section subject, replacing occurrences of the word "broken"
with "hyphenated" may be more clear.

********************************************

Section 6.1 (hyphenation control):
Under value "none":

The text says

Words are not broken at line breaks, even if characters inside the word
> suggest line break points.
>

Would it be more usable if this section mentions that section 5.2
(word-break) takes precedence, in case somebody jumps here directly from the
navigation for quick-reference?

Regarding value "all", this could be useful for speech hints, especially for
common words used as proper names with abnormal pronunciation.  I understand
that it is a minor use-case and that this value is intended for debugging,
but I thought I'd throw that out there.

********************************************

Section 6.2 (hyphenate-character):

This section contains a question:

Is the use of hyphenate characters at the beginning of lines common enough
> for this to be part of the specification?
>

The only use-case I can think of for this is a term that contains a hyphen
which can have several words as the secondary portion of the term, whereupon
the secondary portions modify the overall definition of the term and are
then defined in a list format with a preceding hyphen for compound
clarification.  However, all other cases and even this one could/should use
list items instead, right?  What was the original intent of adding the
second parameter to this value?  More specifically, in other languages, is
the hyphenation continuation character different than the hyphenation break
character?

********************************************

Section 6.3 (hyphenate-limit-zone):

This implies to me an area with a limited amount of hyphenation.  What about
"hyphenate-break-zone", "hyphenate-break-area", "hyphenate-break-margin" or
"hyphenate-margin" (or padding...)?

A question is asked:

Should percentages be relative to the line box or the block?
>

One idea is that positive values can be relative to the line box and
negative values to the block.  Otherwise, if one must be chosen, the block
seems like an easier calculation?

********************************************

Section 8.1 (text alignment):

How should section 6.3 calculate in relation to text-align: justify?  If
'justify' can change line boxes, it seems that no-hyphenation zones should
be calculated afterward if applied to lines instead of blocks.

********************************************

Section 8.1.1 (Details on Character-based Alignment in a Table Column):

Should this section specify whether alignment characters generated as the
result of list item prefixes are included in alignment calculations?

********************************************

Section 10.1 (first line indentation):

This section contains a sentence fragment:

Unless otherwise specified via the ‘each-line’ and/or ‘hanging’ keywords,
> only lines that are the first formatted line of an element.
>

Is this fragment intended as an "applies to" description, or is it supposed
to be "...of the line box, unless otherwise..."?

--Xaxio


On Thu, Feb 17, 2011 at 9:40 AM, Bert Bos <bert@w3.org> wrote:

> The CSS WG published an update of the CSS Text module:
>
>    http://www.w3.org/TR/2011/WD-css3-text-20110215/
>
> This module covers line breaking, justification and alignment, white
> space handling, text decoration and text transformation.
>
> The section "Changes" briefly lists the features that have changed since
> the draft of last October:
>
>    http://www.w3.org/TR/2011/WD-css3-text-20110215/#recent-changes
>
> As usual, we ask that all comments on the draft be sent to this mailing
> list, <www-style@w3.org>, with a subject line that starts with
>
>    [css3-text]
>
>
>
> Bert
> --
>  Bert Bos                                ( W 3 C ) http://www.w3.org/
>  http://www.w3.org/people/bos                               W3C/ERCIM
>  bert@w3.org                             2004 Rt des Lucioles / BP 93
>  +33 (0)4 92 38 76 92            06902 Sophia Antipolis Cedex, France
>
>
Received on Saturday, 26 February 2011 03:16:28 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:37 GMT