Created attachment 124404 [details] Sberbank file The standard Sberbank (Russia's largest bank) document incorrect open in LO Write
Created attachment 124405 [details] Correct layout in MS Word 2010
Reproducible on Windows 10 64-bits with: BrOffice 3.3.4 OOO330m19 (Build:401) tag libreoffice-3.3.4.1 Versão: 5.1.2.2 ID de compilação: d3bf12ecb743fc0d20e0be0c58ca359301eb705f Threads da CPU:4; Versão do SO: Windows 6.2; Realizador da interface: padrão; Local: pt-BR (pt_BR) Maybe duplicate of an existing one?
Confirm the issue on LibreOffice 5.1.2.2
Wps Office opens this file a bit incorrectly, but OnlyOffice Desktop Editors seems to open it fully correctly. File also sent to WPS Office developers. Maybe this information will be somehow useful.
(In reply to Mikhail Novosyolov from comment #4) > Wps Office opens this file a bit incorrectly, but OnlyOffice Desktop Editors > seems to open it fully correctly. > File also sent to WPS Office developers. > > Maybe this information will be somehow useful. Not really, sorry. But thanks for reporting of course.
Still remains in Libreoffice 5.4
Hi Justin, Maybe of interest for you. In the first table in attachment 124405 [details] (from comment #1) first row, turn of paragraph setting "Keep with next .." and the row moves to the first page. Same for following rows..
@justin: see comment 7
Created attachment 135552 [details] isk_short.docx: simplified version of the description's test document I was unable to create a cleanroom sample - I could only simplify the provided example. I think this has more to do with section breaks than anything else. It looks like the "paragraph before the table"'s keep with next property isn't connecting to the table because of the section break, and thus the table floats freely. A bRemove in DomainMapper.cxx::lcl_utext seems to be causing the import problem. Don't remove if pContext->isSet(PROP_PARA_KEEP_TOGETHER)? But then you get extra empty paragraphs each round-trip. This simple file also exports poorly - even to .doc and .odt format. I'm not going to look into this further - too ugly.
If Justin, who does a lot of good work on interoperability cases, says it's too ugly and he's not going to look further at it, I think we can best close as WontFix. Of course anyone is free to assign the task to him/herself and reopen.