Bug 98265 - Poor formatting in Table of Contents with Multiple Fonts
Summary: Poor formatting in Table of Contents with Multiple Fonts
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: TableofContents-Indexes
  Show dependency tree / graph
 
Reported: 2016-02-29 02:19 UTC by Tim Chambers
Modified: 2023-02-01 03:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
test case (353.01 KB, application/vnd.oasis.opendocument.text)
2016-02-29 02:21 UTC, Tim Chambers 		Details
This is the formatting I am aiming for (60.64 KB, application/pdf)
2016-03-10 00:35 UTC, Tim Chambers 		Details
This is the odd format with symbol in the table caption (68.31 KB, application/pdf)
2016-03-10 00:36 UTC, Tim Chambers 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Chambers 2016-02-29 02:19:02 UTC 
User-Agent:       Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36
Build Identifier: LibreOffice 5.1.0.3

I have a table of contents field set to give me a list of the tables in my document. I am using the font "Calibri" as the base font, but have some tables where I have used the unit "micrograms per litre), with a mu symbol (font Symbol, character hex U+F06D.
If this character is present, the formatting for the entry in the table is very badly justified (stretched too far to the right). If I remove the character and update the table, the formatting is correct.

Reproducible: Always

Actual Results:  
will submit sample file


[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no


Reset User Profile?No
Comment 1 Tim Chambers 2016-02-29 02:21:11 UTC 
Created attachment 123066 [details]
test case

If you go to the caption for Table 2 and remove the "ug/L" then update the "List of Tables in Text table, the formatting is corrected.
Comment 2 Buovjaga 2016-03-09 08:53:13 UTC 
I see no problem with justification. Yet, in 5.1, the symbol is not shown in the ToC. In 5.2, it is shown as a box.

Win 7 Pro 64-bit, Version: 5.1.0.3 (x64)
Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: fi-FI (fi_FI)

Version: 5.2.0.0.alpha0+
Build ID: b89feb8018bf3610faf01e73995d576f6566e20b
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-03-07_03:36:17
Locale: fi-FI (fi_FI)
Comment 3 Tim Chambers 2016-03-10 00:35:24 UTC 
Created attachment 123454 [details]
This is the formatting I am aiming for
Comment 4 Tim Chambers 2016-03-10 00:36:09 UTC 
Created attachment 123455 [details]
This is the odd format with symbol in the table caption
Comment 5 Tim Chambers 2016-03-10 04:24:59 UTC 
I have tried replacing the Symbol character with the equivalent Opensymbol character (OpenSymbol U+3BC) in the table caption instead of the (proprietary) SYmbol (Symbol U+F06D).  The correct behaviour occurs.  Not sure why there is a difference as the Symbol versions work correctly in WOrd 2013, which I also have (but do not like).
Comment 6 E M Culver 2016-05-11 23:38:10 UTC Comment hidden (off-topic)
Comment 7 E M Culver 2016-05-12 00:06:55 UTC 
I'm getting the same sort of problem with tables of contents -- when I update, one of the 2nd level headings (font:  Liberation Serif) gets converted to OpenSymbol.  This also happens for all the automatically inserted, but not manually inserted, captions:  they get inserted in OpenSymbol font.  

For the OpenSymbol font entries in the ToC, if I select the entry and select "remove direct formatting" (^M), the text returns to the normal font.
Comment 8 Buovjaga 2016-05-12 10:42:45 UTC 
New per comment 7
Comment 9 QA Administrators 2017-05-22 13:39:58 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2021-01-31 04:48:00 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2023-02-01 03:20:42 UTC 
Dear Tim Chambers,

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