headers
Andrew Fedoniouk | 1 May 2011 08:02

Re: box-align

Just to ensure that we are speaking about same things.

Illustrations of vertical/horizontal-align in different flows:

Alignments in flow:vertical a.k.a. <vbox> (attachment "alignment.htm"):
http://www.terrainformatica.com/w3/alignments/flow-v-alignment.png
same document but when div overflow:
http://www.terrainformatica.com/w3/alignments/flow-v-alignment-overflow.png

Alignments in flow:horizontal a.k.a. <hbox> (attachment "h-alignment.htm"):
http://www.terrainformatica.com/w3/alignments/flow-h-alignment.png
http://www.terrainformatica.com/w3/alignments/flow-h-alignment-overflow.png

Note: children of divs are not using any flex dimensions.

--

-- 
Andrew Fedoniouk

http://terrainformatica.com

top/left

first element

second element

third element

top/center

first element

second element

third element

top/right (Continue reading)

Permalink | Reply | 0 comments |
headers
Koji Ishii | 1 May 2011 13:34
Picon
Favicon

RE: [css3-fonts] humane 'unicode-range'

This is in reply to a little old thread as this was marked as an issue in the spec[1].

One use case that came up in my mind is to switch fonts for UAX #11 [2] EAW=A code points.

EAW=A contains mostly punctuation and symbols that were unified. I think there are cases where authors want:
* CJK fonts for EAW=A|F|H|W
* Latin fonts for EAW=N|Na

One famous example for EAW=A is U+2026 HORIZONTAL ELLIPSIS; ellipsis are at baseline in Latin fonts while
ellipsis at the vertical center in CJK fonts. If I were writing Japanese documents, I expect it be drawn at
the vertical center.

It would be great if I can use a font like this:

 <at> font-resource {
  font-family: myfont;
  src: local(CJK-font-name);
}

 <at> font-resource {
  font-family: myfont;
  src: local(Latin-font-name);
  unicode-range: EAW=N|Na;
}

Or to do this in opposite way:

 <at> font-resource {
  font-family: myfont;
  src: local(Latin-font-name);
(Continue reading)

Permalink | Reply | 6 comments |
headers
Tab Atkins Jr. | 1 May 2011 17:39
Picon
Gravatar

[css3-animations] Times are listed as unitless

The initial value of the animation-delay and animation-duration are
both listed as '0'.  As only lengths are allowed to be unitless, this
is an error.  They should each be either 0s or 0ms.

~TJ
Permalink | Reply | 19 comments |
headers
Eric A. Meyer | 1 May 2011 18:25
Favicon

Re: [css3-animations] Times are listed as unitless

At 08:39 -0700 5/1/11, Tab Atkins Jr. wrote:

>The initial value of the animation-delay and animation-duration are
>both listed as '0'.  As only lengths are allowed to be unitless, this
>is an error.  They should each be either 0s or 0ms.

    Which raises the more interesting question: why are only lengths 
allowed to be unitless?  Shouldn't any value type that accepts 
numbers permit a '0' (or decimal equivalent like '0.000') with no 
unit identifier?

--

-- 
Eric A. Meyer (eric <at> meyerweb.com)     http://meyerweb.com/
Permalink | Reply | 18 comments |
headers
Boris Zbarsky | 1 May 2011 18:46
Picon
Favicon

Re: [css3-animations] Times are listed as unitless

On 5/1/11 12:25 PM, Eric A. Meyer wrote:
> Which raises the more interesting question: why are only lengths allowed
> to be unitless? Shouldn't any value type that accepts numbers permit a
> '0' (or decimal equivalent like '0.000') with no unit identifier?

That's a question that's been answered on this list at least twice in 
the last 6 months....

-Boris
Permalink | Reply | 17 comments |
headers
Phillips, Addison | 1 May 2011 20:15
Favicon

RE: [css3-fonts] humane 'unicode-range'

Hi Koji,

I don't think adding this to "unicode-range" makes sense. The 'unicode-range' selector is one specific,
effective mechanism for one specific use--selecting font based on a range of Unicode code points.

If we want to provide for selection according various Unicode properties, we should provide a property selector.

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: public-i18n-cjk-request <at> w3.org [mailto:public-i18n-cjk-request <at> w3.org]
> On Behalf Of Koji Ishii
> Sent: Sunday, May 01, 2011 4:35 AM
> To: John Daggett; Christoph Päper
> Cc: CSS WWW Style; CJK discussion (public-i18n-cjk <at> w3.org)
> Subject: RE: [css3-fonts] humane 'unicode-range'
> 
> This is in reply to a little old thread as this was marked as an issue in the
> spec[1].
> 
> One use case that came up in my mind is to switch fonts for UAX #11 [2]
> EAW=A code points.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jonathan Kew | 1 May 2011 21:02

Re: [css3-fonts] humane 'unicode-range'

On 1 May 2011, at 19:15, Phillips, Addison wrote:

> Hi Koji,
> 
> I don't think adding this to "unicode-range" makes sense. The 'unicode-range' selector is one specific,
effective mechanism for one specific use--selecting font based on a range of Unicode code points.

I don't think I agree with you on this. The point of the unicode-range descriptor in  <at> font-face is to control
which characters a particular font is used to render; but selecting on the basis of the actual numeric
values of Unicode codepoints is not necessarily the most useful way to express this.

ISTM that Koji is in effect asking for alternative ways to express "a range of Unicode code points", so as to
avoid the necessity to look up the precise Unicode values of interest - which in many cases will not be a
single contiguous range, but rather several ranges.

Personally, I'd like to see ways to express the "ranges" of interest for unicode-range in terms of various
properties defined in the Unicode character database, in a similar way to the use of properties to express
character classes in Unicode regexps, as an alternative to cumbersome [....] expressions.

JK

> 
> If we want to provide for selection according various Unicode properties, we should provide a property selector.
> 
> Addison
> 
> Addison Phillips
> Globalization Architect (Lab126)
> Chair (W3C I18N WG)
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eric A. Meyer | 1 May 2011 23:04
Favicon

Re: [css3-animations] Times are listed as unitless

At 12:46 -0400 5/1/11, Boris Zbarsky wrote:
>On 5/1/11 12:25 PM, Eric A. Meyer wrote:
>>  Which raises the more interesting question: why are only lengths allowed
>>  to be unitless? Shouldn't any value type that accepts numbers permit a
>>  '0' (or decimal equivalent like '0.000') with no unit identifier?
>
>That's a question that's been answered on this list at least twice 
>in the last 6 months....

    Well, don't leave us hanging-- where, exactly?  I searched my mail 
archives but only came up with mentions of a resolution but no 
explanation of the reasoning behind the resolution.  Which I'd really 
like to see, because if we're going to violate long-standing author 
expectations around '0' it would be nice to have some reason for it 
besides "the WG said so".

--

-- 
Eric A. Meyer (eric <at> meyerweb.com)     http://meyerweb.com/
Permalink | Reply | 16 comments |
headers
Boris Zbarsky | 1 May 2011 23:21
Picon
Favicon

Re: [css3-animations] Times are listed as unitless

On 5/1/11 5:04 PM, Eric A. Meyer wrote:
> Well, don't leave us hanging-- where, exactly? I searched my mail
> archives but only came up with mentions of a resolution but no
> explanation of the reasoning behind the resolution.

See thread starting 
http://lists.w3.org/Archives/Public/www-style/2009Nov/0043.html for 
example (referenced pretty recently too) has reasoning.

> Which I'd really like to see, because if we're going to violate long-standing author
> expectations around '0'

Where are these expectations coming from? 
http://www.w3.org/TR/1998/REC-CSS2-19980512/syndata.html#q20 (CSS 2.0, 
back in 1998) says that times can't be unitless.  Compare it to 
http://www.w3.org/TR/1998/REC-CSS2-19980512/syndata.html#length-units 
which says that 0 lengths can be unitless.

Or is the expectation coming from the fact that most web authors never 
used any times, only lengths, which don't have the same syntax, and now 
they're starting to use times and being confused?

-Boris
Permalink | Reply | 15 comments |
headers
Christoph Päper | 2 May 2011 00:53
Picon
Gravatar

Re: [css3-lists] [css3-speech] Interaction between list-style-type and speak properties

Tab Atkins Jr.:
> <ol>
>   <li><span class=marker>A.</span> foo
>   <li><span class=marker>B.</span> bar
> </ol>
> 
> .marker { display: marker; }
> ol { list-style-type: inline; }

Should this or something like it work, too?

  <ol>
    <li value="A."> foo
    <li value="B."> bar
  </ol>

  li[value]::before {content: attr(value); display: marker; }
  ol { list-style-type: inline; }
Permalink | Reply | 6 comments |

Gmane