If we are going to be pedantic, then I would suggest that we remove the
attribute altogether. I would rather have implementations add their
own (incompatible) extensions, and have those extensions implement this
properly, than have the kludge suggested above. I mean, we already have
existing practive to show that the a content-orientation attribute is
very useful as a hint to a number-up algorithm to determine both page
rotation and placement. I would hate to see us ignore that experience.
And Bob, the orientation is useful for *all* number-up > 1. If you
go back and think about number-up 4, one would place the logical
pages on the physical page in a different order based upon the
orientation hint.
think about it...
...walker
-- Jim Walker <walker@dazel.com> System Architect/DAZEL Wizard DAZEL Corporation, Austin, TX