Bug 73974 - FILEOPEN: Formulae broken after import of .doc file: hat and bar not recognized
Summary: FILEOPEN: Formulae broken after import of .doc file: hat and bar not recognized
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: filter:doc
Depends on:
Blocks: DOC-Formula
  Show dependency treegraph
 
Reported: 2014-01-23 12:40 UTC by Alexander Wilms
Modified: 2023-09-28 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example document (292.50 KB, application/msword)
2014-01-23 12:40 UTC, Alexander Wilms
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Wilms 2014-01-23 12:40:55 UTC
Created attachment 92659 [details]
Example document

Problem description: 
Most formulae look fine when opening the file, but when double-clicking on one to edit it

Steps to reproduce:
1. Open attached file
2. Edit any formula that contains a hat or a bar
3. See the attribute being replaced by a question mark

Current behavior:
It should show the correct attribute

Expected behavior:
It shows a question mark
              
Operating System: Windows 7
Version: 4.1.4.2 release
Comment 1 Alexander Wilms 2014-01-23 12:41:58 UTC
It is broken in the current 4.3 daily build, too.
Comment 2 Alexander Wilms 2014-01-23 12:49:42 UTC
The markup of the imported formula:
Bar:
 size 12{ {u}  cSup { size 8{_} }}
 
How it should be: size 12 {bar u}

Bar:
Hat:



 size 12{  {i}  cSup { size 8{ and } } }
 
 size 12 {hat i}
Comment 3 Alexander Wilms 2014-01-23 12:52:55 UTC
Sorry, accidentally I saved the last comment while trying to format it with tabs

The markup of the imported formula:

Bar: size 12{ {u}  cSup { size 8{_} }}
Hat: size 12{  {i}  cSup { size 8{ and } } }

How it should be: size 12 {bar u}

Bar: size 12 {bar u}
Hat: size 12 {hat i}
Comment 4 Jacques Guilleron 2014-06-19 09:29:10 UTC
Hi Fabian Alexander Wilms,

Reproduced with LO 4.2.4.2 and LO 4.4.0.0.alpha0+
Build ID: 3e82897353e576dc6e3fbf55371fda5a0c3415df
TinderBox: Win-x86@39, Branch:master, Time: 2014-06-17_08:55:34
& Windows 7 Home Premium.

Set Status to NEW.

regards,

Jacques
Comment 5 Alexander Wilms 2014-07-30 11:04:18 UTC
Reproducible with Version: 4.3.0.4
Build-ID: 62ad5818884a2fc2e5780dd45466868d41009ec0
Comment 6 QA Administrators 2015-09-04 02:48:32 UTC Comment hidden (obsolete)
Comment 7 Buovjaga 2015-11-19 12:01:58 UTC
Yep, still question marks.

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: 66d2b72667792cb18b25805387824d636e2a455c
TinderBox: Win-x86@39, Branch:master, Time: 2015-11-18_02:35:53
Locale: fi-FI (fi_FI)
Comment 8 QA Administrators 2017-12-22 03:35:54 UTC Comment hidden (obsolete)
Comment 9 Jacques Guilleron 2018-09-26 14:28:56 UTC
Hi,

Problem is still present in
LO  6.2.0.0.alpha0+ Build ID: 1aa37aa6bee19099b57555a6d839992b054aa405
CPU threads: 2; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-09-23_10:17:54
Locale: fr-FR (fr_FR); Calc: CL
Comment 10 QA Administrators 2019-09-27 03:04:52 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2021-09-27 03:24:20 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2023-09-28 03:17:50 UTC
Dear Alexander Wilms,

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