https://bugs.documentfoundation.org/show_bug.cgi?id=122823
Justin L changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
Status|NEW
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #12 from Timur ---
Is there a reason to keep this bug open?
(In reply to Mike Kaganski from comment #3)
> I will check if I can hack the hack from tdf#108849 to not break
> applications that generate hacked OOXMLs, but
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
Xisco Faulí changed:
What|Removed |Added
Version|6.1.0.2 rc |6.0.0.0.alpha1+
--
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #11 from M. A. Sridhar ---
Mike, I've changed our code so that it inserts the sectPr as a child of a pPr
element of the paragraph that contains the page break element. That seems to
work fine in our tests so far, both in Word
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #10 from M. A. Sridhar ---
Thank you for all your help, Mike. I will try out the steps you indicated.
By the way, for what it's worth, I have tried saving similar test files in Word
to understand what causes it to fail to
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #9 from Mike Kaganski ---
And please, save your file with Word! You will see the proper structure if you
do. Not only creating something that opens "correctly", but also saving the
result and inspecting the code written by
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #8 from Mike Kaganski ---
(In reply to M. A. Sridhar from comment #7)
Please download the standard, and compare the two subsequent sections:
> 17.6.17 sectPr (Document Final Section Properties)
> 17.6.18 sectPr (Section
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #7 from M. A. Sridhar ---
Sorry for being dense here. I did in fact look at the link you mentioned
(108849) but did not get any sense that it applied to this situation, because I
honestly don't know the innards of these
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #6 from Mike Kaganski ---
(In reply to M. A. Sridhar from comment #5)
> I was the one that reported this bug. I generated this document using some
> code that we use for document generation using template expansion. I am not
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #5 from M. A. Sridhar ---
I was the one that reported this bug. I generated this document using some code
that we use for document generation using template expansion. I am not fully
aware of the rules around correct
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #4 from Mike Kaganski ---
But if it's LibreOffice that generates such files, then it would be another
bug, with much higher priority! Please file the bug if it's so!
--
You are receiving this mail because:
You are the
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
--- Comment #3 from Mike Kaganski ---
Oh. I should have known that fixing one invalid document to be bug-to-bug
compatible with Word, I'll break another invalid document. And this one,
indeed, violates OOXML standard in a similar way as
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
raal changed:
What|Removed |Added
CC||mikekagan...@hotmail.com,
https://bugs.documentfoundation.org/show_bug.cgi?id=122823
Dieter Praas changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
14 matches
Mail list logo
