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

Aron Budea <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|bibisectRequest             |bibisected, bisected
      Regression By|                            |Pierre-Eric Pelloux-Prayer

--- Comment #3 from Aron Budea <[email protected]> ---
(In reply to Aron Budea from comment #0)
> In 4.1.0.4 and 4.3.0.4, when pressing enter after clearing formatting, the
> Next style setting isn't honored, and Heading 2 style is kept, including the
> direct formatting.
> In 4.0.0.3, when pressing enter after clearing formatting, the Next style
> setting isn't honored, and Heading 2 style is kept, but direct formatting is
> gone.
Bibisected the second change between 4.0 and 4.1 to the following two
consecutive commits (the earlier failed to build) using repo bibisect-41max.

> Let's say you want to get rid of the direct formatting in the heading:
> select the first line, and press Ctrl + M, then unselect, press Enter at the
> end of the line, and type a few characters.
A significant change with these commits is that when performing the steps
listed above (note: start with saving ODT as DOCX and reloading), when you've
moved to the end of line after clearing direct formatting, at that position the
direct formatting is still there.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=8c178a50334109b34ef456ca6aa51cd3d98699ae
author          Pierre-Eric Pelloux-Prayer <[email protected]>    
2013-01-11 14:38:12 +0100
committer       Noel Power <[email protected]>        2013-01-14 15:50:07
+0000

"docx export: also export rPr in <pPr> (paragraph mark styling)"

https://cgit.freedesktop.org/libreoffice/core/commit/?id=1f2c079dd2bc9a2f5aa3597a8222bde3073a04da
author          Pierre-Eric Pelloux-Prayer <[email protected]>    
2013-01-11 14:34:04 +0100
committer       Noel Power <[email protected]>        2013-01-14 15:51:14
+0000

"sax: add methods to duplicate current top marker and reapply it later"

I'd assume this bug mainly has to do with the way these paragraph mark stylings
are handled.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to