Bug 156366 - Writer: Double-line characters do not wrap lines correctly
Summary: Writer: Double-line characters do not wrap lines correctly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Anchor-and-Text-Wrap
  Show dependency treegraph
 
Reported: 2023-07-19 02:44 UTC by vicxp0518
Modified: 2025-07-20 03:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vicxp0518 2023-07-19 02:44:37 UTC
Description:
When editing the characters where have the "Double-Lined" style enabled, the line wrapping inside the doubled lined region goes stubborn and odd. Nearly-always-reproducible with CJK letters.

Steps to Reproduce:
1. Define a Double-Lined character style.
2. Apply it to some characters, the long the better.
3. Let it cross the end of the line (ie. let the double-lined text wrap into two major lines).
4. Save the file.
5. Try to insert more chars into the double-lined text at its first major line, and see how the later characters wrap into the second major line.

Actual Results:
It seems that there is "stubborn" invisible line wrapping control marks refuse to change its position automatically.

Expected Results:
Should auto wrap as natually.


Reproducible: Always


User Profile Reset: No

Additional Info:
Current walkaround (but annoying):
1. Select the entire double-lined text;
2. Cut;
3. At position, paste as plain text.
Comment 1 ysui2022 2023-07-20 04:27:20 UTC
I reproduced this bug successfully.

Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 2 QA Administrators 2025-07-20 03:11:18 UTC
Dear vicxp0518,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug