https://bugs.documentfoundation.org/show_bug.cgi?id=147100
raal <r...@post.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caol...@redhat.com
Keywords|bibisectRequest |bibisected, bisected
--- Comment #4 from raal <r...@post.cz> ---
This seems to have begun at the below commit.
Adding Cc: to Caolán McNamara; Could you possibly take a look at this one?
Thanks
bdd0a608f23b1c4e54e3ec396e888cd40e2afa6f is the first bad commit
commit bdd0a608f23b1c4e54e3ec396e888cd40e2afa6f
Author: Matthew Francis <mjay.fran...@gmail.com>
Date: Sun Mar 15 03:02:50 2015 +0800
source-hash-705a8c226aee3e68db492083b7cf8b704335328b
commit 705a8c226aee3e68db492083b7cf8b704335328b
Author: Caolán McNamara <caol...@redhat.com>
AuthorDate: Tue Sep 23 20:35:50 2014 +0100
Commit: Caolán McNamara <caol...@redhat.com>
CommitDate: Wed Sep 24 10:04:48 2014 +0100
WW8PLCFMan::AdjustEnds deeply flawed concept wrt change tracking
The whole idea of clipping the char attributes to before the cr that
word uses
as the end of para marker is flawed from especially the perspective of
redlining which is a char property in word.
If the redline encompasses the newline in order to state that it is
deleted,
then if the prop is clipped to before that newline then the end-of-para
doesn't
get marked as deleted
For now just remove the character attributes clipping from here to be
as
conservative as possible.
Hopefully the ordering of processing start pap before start chp and end
chp
before end pap and the other million improvements in the parser that
came about
after AdjustEnds was created avoids whatever problems were trying to be
worked
around here.
Change-Id: I5a72e462db2fff60f52b12c2125ea6ac363de695
--
You are receiving this mail because:
You are the assignee for the bug.
