Hi Regina, [ Sorry for the slow reply, I was not reading mail last week. ] On Wed, Jul 19, 2023 at 06:36:41PM +0200, Regina Henschel <rb.henschel@xxxxxxxxxxx> wrote: > > If you're interested in a setting similar to OOXML's > > allowTextAfterFloatingTableBreak option, that would be rather > > per-document, not per-table. And there is some benefit if ODF's matching > > setting would be also per-document, it simplifies the job of ODF -> > > OOXML filters. If that direction makes sense, then I guess this would be > > rather a second boolean in settings.xml, not a 3rd value for the > > proposed text:may-break-between-pages attribute. > > I dislike to put such information which is essential for the layout of the > document into the settings.xml. The settings.xml contains only > implementation-dependent settings. I don't know whether other application > even read it. I agree it's not ideal that most of settings.xml is not standardized; it would be indeed nice to standardize the "wrap on all pages" option. > Perhaps we can make a compromise? Keep the text:may-break-between-pages as > boolean attribute at the <draw:frame> element and add a second attribute to > the style to describe how the text wraps around a <draw:frame> element, > which spans several pages? > > Thus way the "how-to-wrap" attribute can be stored in the top element of the > styles hierarchy to have a document wide default which can be used for > export to OOXML, but still be overwritten by the style of an individual > frame for ODF. > > I am an advocate of ODF and don't like limiting ODF to the capabilities of > OOXML. Yes, I think that's a good compromise. Do you need anything else from me to file an OASIS proposal for these 2 attributes? Thanks, Miklos