https://bugs.documentfoundation.org/show_bug.cgi?id=118927

Terrence Enger <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #5 from Terrence Enger <[email protected]> ---
Created attachment 144214
  --> https://bugs.documentfoundation.org/attachment.cgi?id=144214&action=edit
bibisect in 44max repo, tail of terminal output

Working on debian-buster in 44max bibisect repository, I see that the
bug entered LibreOffice in

    source-hash-c5ed52b1cd6f22787c94bec035ceecf9e1da3271

    commit c5ed52b1cd6f22787c94bec035ceecf9e1da3271
    Author:     Luboš Luňák <[email protected]>
    AuthorDate: Mon Jul 21 10:56:52 2014 +0200
    Commit:     Luboš Luňák <[email protected]>
    CommitDate: Mon Jul 21 11:02:04 2014 +0200

        ww8import create a pagedesc if continuous section changes margins
(bnc#875383)

        This is similar to what writerfilter does. MSWord can have one page
with several
        different margins, which are saved using continuous sections, which
causes all
        kinds of trouble, because either we treat them as Writer sections,
which means
        we lose some of the data, or we treat them as Writer page styles, which
causes
        spurious page breaks if in the wrong place. Either option has its
problems, but
        here it seems slightly better to go for keeping the data and hoping the
page
        break will be in a place where a break will be anyway.

        Change-Id: I8f52aa820750da6788ea04180a15ac334f6bf87b

I was able to get a stable result from bibisect only by creating a new
user profile at each step.  I would welcome thoughts about why this
might be necessary.


Seeing "either option has its problems" in the log message, I wonder
if this bug is one we can fix.

I am setting keywords bibisected, bisected.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to