https://bugs.documentfoundation.org/show_bug.cgi?id=169298
--- Comment #6 from Mike Kaganski <[email protected]> --- OK, so this is titled: "Document variable with line break imported without line break". The bugdoc RTF has a document variable with a value with \'0d\'0a control characters. It *also* has a field showing that variable, with a cached field expansion value having a newline. Now for problems. I have confirmed, that MS Word 2016 does export such RTF from the provided DOCM. But at the same time, this DOES NOT mean that MS Word supports \'0d\'0a in the variable's value. Just open the RTF in Word, and inspect the variable - e.g., using the macro like in the DOCM; or update the field. Word replaces these control characters in the variable, and so - NO, we should NOT import "line breaks" in such RTFs, just as Word does. We just need to make sure to strip them *correctly*, not let them spill into the document. On the other hand, Word shows the document - at least initially - with the newline *in the field*. This is not because Word imports newlines in variables; it's because it uses cached values. We update the field immediately. So this bug should be clarified, which specific result is sought. For now, I'm preparing a patch, that would address the newlines spilling from variable values into document body. -- You are receiving this mail because: You are the assignee for the bug.
