Summary: | LO 7.6 Creates Duplicate / Unwanted Paragraph Direct Formatting | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | bugzilla |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | stephane.guillou |
Priority: | medium | ||
Version: | 7.6.4.1 release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
bugzilla
2024-02-29 19:45:00 UTC
Additional observations are: 1) Another adverse consequence of this bug is the potential loss of List levels. For example: 'Find and Replace' (Ctrl+H) > Other options > enable Paragraph Styles, then e.g. Find= 'List 1' Replace= 'List 2' paragraph styles. The result under LO 7.6 (as before) is a change of the underlying style to 'List 2' but the numbering style of 'List 1' being retained. However all List levels are changed to level one. For example: A., A.1, A.1.a. become A., A., A. thus losing important document formatting. LO 7.3 changes Paragraph style correctly and retains the original list Level values. 2) To aid the identification in LO 7.6 of paragraphs containing Paragraph Direct Formatting, enable the Spotlight function: Show Side Menu (F11) > select Styles button (Alt+2) > select Paragraph Styles tab > enable Spotlight. Diagonal background hatching (instead of solid) identifies the paragraphs containing Direct Formatting making them easier to spot. I've tested various LO AppImage versions for this issue and test results as follows: VERSION RESULT DATE RLSE -------- ------ --------- 7.3.7.2 OK 03Nov22 7.4.7.2 OK 11May23 7.5.9.2 OK 07Dec23 7.6.0.3 Bug 21Aug23 7.6.5.2 Bug 22Feb24 (current Stable) 24.2.0.3 Bug 31Jan24 24.2.1.2 Bug 29Feb24 (current Fresh) I've been alerted to Bug 159366 which was raised about 1 month before this one. I believe it describes the same root problem, therefore this report could be considered a Duplicate of it. Thank you for the report. Indeed, let's mark as duplicate. *** This bug has been marked as a duplicate of bug 159366 *** |