Bug 140125 - character border implementation issues vs. Word
Summary: character border implementation issues vs. Word
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Character
  Show dependency treegraph
 
Reported: 2021-02-03 14:21 UTC by Michael Stahl (allotropia)
Modified: 2025-05-13 03:11 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Word 2013 DOCX test case (15.83 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2021-08-11 15:41 UTC, Michael Stahl (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stahl (allotropia) 2021-02-03 14:21:40 UTC
character border was added in Writer 4.2

there's a few situations where it looks differently from Word:
* Ruby
* tab-stops
* footnote anchors

these are text formatting bugs.
Comment 1 mulla.tasanim 2021-02-03 20:27:13 UTC
Thank you for reporting the bug. 
Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. 
Please provide a clearer set of step-by-step instructions on how to reproduce the problem.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested information is provided.
Comment 2 Regina Henschel 2021-02-03 22:06:51 UTC
Michael, you have likely a test document. Please can you attach it?
Comment 3 QA Administrators 2021-08-04 03:46:05 UTC Comment hidden (obsolete)
Comment 4 Michael Stahl (allotropia) 2021-08-11 15:41:08 UTC
Created attachment 174211 [details]
Word 2013 DOCX test case

oops i forgot to attach this; small file with some corner cases
Comment 5 BogdanB 2023-05-13 04:41:58 UTC
Michael, could you attach a screenshot from Word?
Comment 6 QA Administrators 2025-05-13 03:11:10 UTC
Dear Michael Stahl (allotropia),

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