On Wed, 2012-03-21 at 17:37 +0100, Michael Stahl wrote: > but then it was discovered that there was a specific way of splitting up > a table that was impossible to represent in this table model, but was > somehow important (perhaps because MSO can do it?)
yeah, it used to be fairly trivial to achieve un-representable layouts, even from the UI which used to give an awesome dialog about it, and it meant there was plenty of .doc table layouts which were achievable on import. > > That gets us past the first crash, but then the rtf exporter breaks and > > falls over later on, possibly because its hard to get the table > > structure right without the layout information. > > that would need some investigation for sure... > > > I don't think we can call MakeFrms on a table to generate layout > > information in isolation without the full document being laid out (or > > can we?) so I guess we have to suck it down and fix the second layer of > > crashes in the .rtf exporter with the alternative table export branch. > > i don't think MakeFrms will do anything at all but even if it doesn't > crash immediately the layout of just a table won't be correct. Yeah, doesn't do anything. I guess the sensible thing is to try and fix the export code for the non-layout-available branch, though I itch to burn time to see what of the layout info do we use and if it then makes sense, to reactor the table layout stuff to be able to generate the information we need even in the absence of full layout. And there's a bunch of stuff in the html exporter for tables as well. Tables are ugly. C. _______________________________________________ LibreOffice mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice
