https://bugs.documentfoundation.org/show_bug.cgi?id=148834
Justin L <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Summary|Line numbering for specific |Line numbering for specific |paragraphs gets lost after |paragraphs gets lost after |saving to .docx file format |saving to ODT->.docx file | |format Priority|medium |low Version|3.3.0 release |Inherited From OOo Severity|normal |minor --- Comment #2 from Justin L <[email protected]> --- Low priority: Things designed in Word seem to round-trip well. Things designed in LO using simple styles seem to work well also. MS Word has line numbering tied to a section. All paragraphs in a section participate, and require an explicit "suppress line numbers" paragraph property to avoid being numbered. LO does not tie numbering to page styles or sections AFAICS. It is just on or off for the whole document. But that sounds like it all should work. What is the problem then? I assume that the property <w:suppressLineNumbers/> is not written when it is false. Yup - here it is: if ( !rNumbering.IsCount( ) ) m_pSerializer->singleElementNS(XML_w, XML_suppressLineNumbers); Generally, that is a good thing, but not when it needs to override an inherited value (like in this case where the style says suppress, but the direct formatting says don't suppress). See ExportPoolItemsToCHP for some ideas on how to check that. -- You are receiving this mail because: You are the assignee for the bug.
