Bug 48648 - Formatting issues with special characters
Summary: Formatting issues with special characters
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.5.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-04-13 06:57 UTC by Jonathan
Modified: 2015-06-08 14:26 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Image of the incorrectly parsed font (917 bytes, image/png)
2012-04-13 06:57 UTC, Jonathan

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan 2012-04-13 06:57:14 UTC
Created attachment 59909 [details]
Image of the incorrectly parsed font

There exists an issue that cropped up in one of the later versions of OpenOffice (approx v3.2) that has carried into the LibreOffice suite, where certain characters do not format correctly in .doc formatted writer documents. Certain characters from the Wingdings font (and other special character fonts) tend to display as the wrong character. 

For example, a checkbox actually displays as the wrong character. For example, in some instances it appears as a small equation (1/(2x)). There are several characters from this set that do not display correctly, the attachment has an example. It should be as below, but looks like the image in the attachment in LibreOffice Writer 3.5.2
  Friend				
  Relative
Comment 1 Buovjaga 2014-10-31 09:29:53 UTC
I tried inserting all kinds of characters that look like checkboxes in Wingdings, but they all render fine. The Unicode character you gave as an example, F07F, looks like an elongated box in Wingdings and renders ok. Please provide a sample document where the problem occurs.

Tested on Win 7 64-bit Version:
Build ID: 56019dcb79475606952a954fe732a3109441ffec
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-30_07:27:11
Comment 2 QA Administrators 2015-05-06 14:14:31 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:

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 3 QA Administrators 2015-06-08 14:26:29 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 our bug tracker

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team