Re: Review of css-shapes-1

One vaguely interesting top-level comment that ties in with digipub is the
difficulty in applying reasonable line break algorithms (eg something
better than first-fit or best-fit) to text whose line length (physical
width of the line) can change based on line height. So, cases where a span
that makes the line taller could cause the line to become narrower based on
a complex floated shape from a previous line. I am not sure what there is
to do about this, and may just become a footnote (assuming we decide there
is a place for such things in digital publishing!) of any spec that
addresses line breaking/justification/hyphenation.


On Mon, Jan 6, 2014 at 12:59 PM, Cramer, Dave <Dave.Cramer@hbgusa.com>wrote:

>   I haven't found much to say about CSS Shapes Level 1 [1]. The concepts
> are useful, and the examples are clear.
>
>  As always, I looked through my book collection to find examples of text
> wrapping around images. There were very few--even some highly designed
> books were either not wrapping text around objects at all, or they were
> simple rectangles that would work with float as specified today. The
> examples I did find were more complicated, where images were wrapping
> around each other. Since shapes don't affect float, that's not something
> under consideration here.
>
>  I know the case of text wrapping around text (as with drop caps) was
> raised on www-style. I see that as an important use case, but I think the
> full solution to that problem might belong to a formal drop cap proposal. I
> don't really want to draw polygons around letter outlines every time I use
> a new drop cap!
>
>  Dave
>
>  [1] http://dev.w3.org/csswg/css-shapes/
>
>  *:: :: ::*
>
>  *Dave Cramer | Content Workflow Specialist | Hachette Book Group | 237
> Park Avenue NY | NY 10017 | 917 207 7927 <917%20207%207927> |
> dave.cramer@hbgusa.com <dave.cramer@hbgusa.com>*
>
>
> ------------------------------
> This may contain confidential material. If you are not an intended
> recipient, please notify the sender, delete immediately, and understand
> that no disclosure or reliance on the information herein is permitted.
> Hachette Book Group may monitor email to and from our network.
>

Received on Monday, 6 January 2014 21:16:35 UTC