- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 24 Nov 2004 10:20:04 -0600
- To: Peter Sorotokin <psorotok@adobe.com>
- CC: www-svg@w3.org
Peter Sorotokin wrote: > Yes: > - text might need to flow from region to region > - exclusion regions > - flowRef element > > For instance, consider a case when there are two rectangles and text is > flown into a top one first and the bottom one second. So the problem is that you need an order on your areas and an SVG shape would not provide that? But surely one can use an ordered list of SVG shapes? I'm not sure why exclusion regions are an issue. flowRef does need something to reference, but it's not clear to me why flowRef is needed... > That is a good point. I think right now it is undefined. But we are > between a rock and a hard place here: if we don't have a start/end > values that work for both text directions I didn't say you need to drop start/end. I just asked that you _not_ drop left/right, while adding start/end. For that matter, there's no reason to drop the <string> value. The CSS3 Text CR states that the <string> value only applies to table cells. Since there are no table cells in sight in SVG proper, it'll simply be treated as 'start' [1]. In other words, I think you can simply reference the CSS3 Text property without placing additional restrictions on it, I believe. > That is a good catch. We probably should define it more specifically. s/probably//, please. ;) >> For "center", I'm really not sure what a reasonable >> implementation would be. This needs to be defined. > > Yes. I assume that means, "Yes, it needs to be defined"? -Boris
Received on Wednesday, 24 November 2004 16:20:30 UTC