W3C home > Mailing lists > Public > www-style@w3.org > June 2006

Re: [css3-gcpm] New WD: Generated Content for Paged Media

From: Håkon Wium Lie <howcome@opera.com>
Date: Fri, 16 Jun 2006 11:08:11 +0200
Message-ID: <17554.29947.924090.941486@localhost.localdomain>
To: Allan Sandfeld Jensen <kde@carewolf.com>
Cc: www-style@w3.org

Also sprach Allan Sandfeld Jensen:

 > It really like the ad hoc counter styles


 > I don't see how they are specially related to paged media 
 > though.

You're right. Possible reuse is mentioned in the introduction:

  Some of the proposed functionality (e.g., hyphenation and ad hoc
  counter styles) may also used with other media types.

The reason for putting this into a paged media draft is that they are
essential for numbering footnotes.

 > For instance they should allow urls beside strings. It is not more than a few 
 > weeks someone asked on the list how to count with "1.gif", "2.gif", etc.
 > This would be simple with  
 > @counter-style graphic url("1.gif") url("2.gif") url("3.gif")

Yes. Hmm. It introduces a new problem, though: How do you set the
size/resolution of the images?

 > Another thing is that we might as well use it to replace the absurd number of 
 > new alphabets and number systems in the CSS3 list module. This only requires 
 > being able to set a type counter. The types could be: enumerate(default), 
 > numeric and alphabetic. 
 > This way I can define a danish alphabetic counter using:
 > @counter-style danish 
 > alphabetic "a" "b" "c" "d" "e" "f" "g" "h" "i" "j" "k" "l" "m" "n" "o" "p" "q" "r" "s" "t" "u" "v" "x" "y" "z" "æ" "ø" "å"

Why do you give it two names ("danish", "alphabetic"), isn't one
enough (e.g., "danish-alphabetic")?

 > And there would be no reason to include it as a standard list-style or trying 
 > to get a political agreement if it's a danish or a norwegian alphabet ;-)

No need for agreement, I'll make sure the next draft declares them to
be Norwegian once and for all :-)

 > One thing though we should consider if there should be some special 
 > requirements to custom names. This counts for both list-styles but also 
 > string sets. This is a avoid clashes with future extensions. One solution 
 > could be to require them to start with '-'.

It looks ugly, though.

              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Friday, 16 June 2006 09:08:22 UTC

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