https://bugs.documentfoundation.org/show_bug.cgi?id=68117
--- Comment #20 from Markus Mohrhard <[email protected]> --- (In reply to Michael Meeks from comment #19) > Interesting, if we can't reproduce this in master; is that really the case ? > > Also - it's not entirely un-expected I guess to have trouble here; Excel has > a built-in 'boolean' type - but LibreOffice does not - we use a boolean > format on top of a double to simulate that. I guess that (in case this ever > worked properly) something has gone wrong with the boolean format detection > in the XLSX export logic. I wonder what the performance impact of that > format lookup on each double export is however. > > I guess for now we should prolly just export a custom / boolean format for > those cells to Excel to avoid XLSX export perf. regressions. Does that make > sense Markus ? Just to leave some comments here. We are only talking about the boolean format export for now. We export a custom number format for that of the form TRUE;TRUE;FALSE which has the same effect. The issue that has been reported here is not an export issue. If you inspect the exported files you can find the correct content so it is purely an import issue which is consistent with the patch that seems to have introduced this issue. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
