> After my last mail about text, I played around a little more again and > stumbled over a very strange behaviour. > I have to boxes which are combined and text is flowed into them. I > placed them one below the other... I imagined the text would continue in > the second box... but unless its really close, it doesn't. > Open the attached fly, mark the below box with the node-selection tool > by selecting all nodes and move the box down with the arrow keys... the > text will disappear from it. Yes, this is weird and (after a careful reading of the spec) incorrect. It's actually not doing what you think it's doing, as you can determine by moving the second region to alongside the first: the text runs straddle both regions so the entire document is read top-to-bottom (this bit is correct). The layout code is attempting to enforce the rule that anything after the end of a region gets cut off, but it's seeing the gap between the two regions as the end and simply stopping rather than shifting by line-advance and trying again.

If you want the behaviour that you seem to be describing then the flow boxes should be two objects, not one object with two paths. This is demonstrated by examples/flowsample.svg and does work.

> I guess I should file a bug, shouldn't I? But maybe it would be good to > know, what causes the problem... It is a bug, please file it as such.

In order to create one yourself you will need two shapes (separate objects) and some unflowed text. Select all three and do Text->Flow into frame. The order in which the frames are used depends on the order in which you selected them, so if it's wrong hit undo and try again.

The hole in the middle of flowsample.svg is done with a flowRegionExclude tag, but there's no need for that (and, in fact, no UI for it either) - you can just create a compound shape using, for example, Path->Difference.