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

Re: [css3-page] New WD for CSS paged Media

From: David Latapie <david@empyree.org>
Date: Fri, 13 Oct 2006 16:47:49 +0200
Message-Id: <15B6FF7E-414D-45C1-BC9C-D5DF44D482DB@empyree.org>
Cc: www-style@w3.org
To: Bert Bos <bert@w3.org>

Le 13 oct. 06 à 15:48, Bert Bos a écrit :

> The CSS WG just published a new draft of CSS Paged Media. There is a
> good chance that it is the last draft of this module, so this is a  
> last
> call for comments.
>     http://www.w3.org/TR/2006/WD-css3-page-20061010

== Aliases for boxes ==

* bottom-right-corner
* bottom-left-corner
* top-right-corner
* top-left-corner

have duplicates as

* right-bottom-corner
* left-bottom-corner
* right-top-corner
* right-bottom-corner

These two areas overlaps, because they are a matter of point of view.  
I really have no idea whether we should enforce concision (by  
imposing a point of view, although it comes as natural, at least for  
Westerners) or generalisation (by using two keywords for one property)

== Center and middle ==

Also, I personally consider middle as a one-dimension value while  
center is a two-dimension value

  |                 |
  |                 |
  M                 M
  I                 I
  D     CENTER      D
  D                 D
  L                 L
  E                 E
  |                 |
  |                 |

That may just be me... or not. I think this is important to clarify  
this (I stop counting how many time I mispelled vertical-align:center  
instead of vertical-align:middle). It is also possible that I just  
*reversed* the meanings.

  |                 |
  |                 |
  C                 C
  E                 E
  N     MIDDLE      N
  T                 T
  E                 E
  R                 R
  |                 |
  |                 |

== headers/footers and CSS/UA ==

> The module defines the basic features of paged media: page breaks,  
> page
> numbers, running headers and footers. (More advanced features that are
> typically found on printed pages, such as columns, footnotes, leaders
> and cross-references, are in modules that we'll work on later.)

> Compared to the previous draft, "string sets" (for copying text to
> running headers and footers) has been moved out of this module.

Is it in the scope of this recommendation to state how UA and CSS  
should work when it comes to headers and footers? For instance, more  
often than not, I (and I presume most people) do not want  
administrative informations to be written on a page (like the address  
of the printed document: C://bla/ble/bli.html).

- Providing a way to prevent such administrative information to be  
displayed at all would often be useful: I don't want my resumé to  
have this address on it!

- How would headers and footers work with the UA headers and footers?  
Like I want page numberings at the right-bottom-corner, but the UA  
already put its own kind of page numbering.

Shall I understand this issue is moved to another draft? Which one?  
Not set up yet?

== Orientation ==

Orienting an Image on the Page <http://www.w3.org/TR/2006/WD-css3- 
page-20061010/#orienting> doesn't appear to me as Paged Media  
specific. Could you explain why it is here?

Have a nice day,
http://blog.empyree.org/   U+0F00
Received on Friday, 13 October 2006 14:48:06 UTC

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