Bug Hunting Session
Bug 65976 - FORMATTING: Character formating/font lost for documents written with pre 4.x
Summary: FORMATTING: Character formating/font lost for documents written with pre 4.x
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.3.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-20 16:14 UTC by aw-libreoffice
Modified: 2014-07-08 17:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example ODTs and PDFs under v3341, v3572, and v4132. (199.20 KB, application/zip)
2013-11-15 14:09 UTC, Owen Genat (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description aw-libreoffice 2013-06-20 16:14:48 UTC
I have documents which use fax, telephone and mail symobols from the OpenSymbol font. This work for me over the last years.
When I open these documents with current release of writer the references to OpenSymbol are lost - I see some rectangles which is what the paragraph font has for the given code.
When I manually change the font for the "rectangles" to OpenSymbol I get what I expect.

Something to mention:
The paragraph references helvetica font - I am not sure if I have this font installed.
Comment 1 Joel Madero 2013-06-21 01:08:20 UTC
We'll need the attachment - marking as NEEDINFO

Once the attachment is provide mark as UNCONFIRMED and we'll take a look.


Thanks!
Comment 2 Owen Genat (retired) 2013-11-15 14:09:24 UTC
Created attachment 89273 [details]
Example ODTs and PDFs under v3341, v3572, and v4132.

I am attaching some example documents showing the likely symbols used from the OpenSymbol font for fax, telephone, and mail (there is no correct fax symbol). All have been generated under Crunchbang 11 x86_64 running these versions of LO:

- v3.3.4.1 OOO330m19 Build:401 (OpenSymbol v2.4.3)
- v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b (OpenSymbol v102.2)
- v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a (OpenSymbol v102.3)

All symbols display as expected, when the two older files are opened under v4.1.3.2. From the description it sounds like the Helvetica font is somehow being substituted for OpenSymbol (perhaps because the OpenSymbol font cannot be found)?
Comment 3 QA Administrators 2014-06-01 21:30:45 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


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


Warm Regards,
QA Team
Comment 4 QA Administrators 2014-07-08 17:18:30 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO