Bug 123454 - Decimal tabs are rendered as right tabs in imported RTF (and other) documents
Summary: Decimal tabs are rendered as right tabs in imported RTF (and other) documents
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: RTF
  Show dependency treegraph
 
Reported: 2019-02-13 22:17 UTC by lbr
Modified: 2023-05-24 15:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Decimal tabs in example files (2.66 KB, application/zip)
2019-02-13 22:17 UTC, lbr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lbr 2019-02-13 22:17:59 UTC
Created attachment 149287 [details]
Decimal tabs in example files

This happens with all my .rtf, .doc, and .docx documents (the .doc and .docx files resulted from imported .rtf). LibreOffice once treated this correctly, but I have replaced my previous version with 6.2.0 and can't conveniently check 6.1.0. Version 5.4.7.2 exhibits the same problem.

Attached are two files, one \rtf\mac and the other \rtf\ansi, which display the problem in LibreOffice 6.2.0 but not in Word, Nisus Writer, or TextEdit. Note that the \rtf\ansi file also renders the uppercase sigma glyph from the Symbol font as "D".
Comment 1 raal 2019-02-14 18:56:49 UTC
Confirm with Version: 4.1.0.0.alpha1+
Build ID: 863d38fbfa4fb4861e476828c46410602100919 and Version: 6.3.0.0.alpha0+
Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Comment 2 QA Administrators 2021-02-14 04:04:22 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2023-02-15 03:21:00 UTC
Dear lbr,

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