Bug 49549 - FILESAVE PPT PPTX Overlining lost after saving & reopening file
Summary: FILESAVE PPT PPTX Overlining lost after saving & reopening file
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA interoperability
Keywords: filter:ppt, filter:pptx
Depends on:
Blocks: PPT PPTX-Characters
  Show dependency treegraph
 
Reported: 2012-05-06 06:02 UTC by Wagner
Modified: 2023-06-09 03:14 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file to demostrate the bug (71.00 KB, application/vnd.ms-powerpoint)
2013-06-03 00:18 UTC, Wagner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wagner 2012-05-06 06:02:09 UTC
Problem description: 
If you format a character to have an 'overline' and you save the presentation as PPT, when you reopen the file, the character will no longer have the overline.

Steps to reproduce:
1. Create a presentation file and save it as PPT.
2. Add a text and format a character to have an overline.
3. Save and close the presentation.
4. Reopen the file.
5. Check that the character have lost the overline.

Current behavior:
Character loses the overline format when presentation is saved with PPT.

Expected behavior:
Character keeps the overline format when presentation is saved with PPT.

Platform (if different from the browser):
Windows 7 - 64bits
              
Browser:
IE 9
Comment 1 Wagner 2012-05-06 06:03:50 UTC Comment hidden (obsolete)
Comment 2 Joel Madero 2012-06-17 18:28:32 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2013-05-26 22:32:20 UTC Comment hidden (obsolete)
Comment 4 Wagner 2013-06-03 00:18:43 UTC
Created attachment 80172 [details]
Example file to demostrate the bug

Open the attached PPT file. Select the "XXXXX" text and right-click on it. Select the "Character..." contextual menu. Select the overline format. The selected text will be formatted with an overline. Save the file and re-open it. Check that the overline format has been lost.
Comment 5 Wagner 2013-06-03 00:20:11 UTC Comment hidden (obsolete)
Comment 6 ign_christian 2013-06-03 02:22:36 UTC
reproducible on LO 4.0.4.1 (Win7 32bit)

Tried several Overlining (single, double, bold, dotted) with automatic/black colored, that format will be lost after saving & reopening.
Comment 7 Joel Madero 2013-06-05 13:48:07 UTC
I know i'm the one who downed the priority but - this is a loss of data one so clearly a Major bug, apologies for the noise
Comment 8 Alexandr 2014-12-14 10:59:57 UTC
I reproduce the problem with LibreOffice 4.3.3 and 4.4.0 beta2 on Debian. Is overlining formatting possible in MS Office file format? I do not see any simple way to make overlinig in MS Office 2010. Googling gives 2 advices: use equations or use [alt] + 773.
Comment 9 Robinson Tryon (qubit) 2015-12-07 16:26:43 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2017-01-03 19:42:42 UTC Comment hidden (obsolete)
Comment 11 Thomas Lendo 2017-06-21 22:51:44 UTC
Reproducible with Version: 6.0.0.0.alpha0+
Build ID: 6ef59d7ace7e4db52caea601a384ed016365bcaf
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-06-20_01:21:33
Locale: de-DE (de_DE.UTF-8); Calc: group
Comment 12 Xisco Faulí 2017-10-19 15:26:41 UTC Comment hidden (obsolete)
Comment 13 Xisco Faulí 2017-10-19 15:27:21 UTC
*** Bug 65278 has been marked as a duplicate of this bug. ***
Comment 14 Xisco Faulí 2018-08-16 21:51:49 UTC
Still reproducible in

Version: 6.2.0.0.alpha0+
Build ID: b264c9276888bb952deeec31abe3a77e05dac164
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: threaded

and in

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 15 QA Administrators 2019-08-19 06:55:17 UTC Comment hidden (obsolete)
Comment 16 Buovjaga 2019-09-25 13:36:35 UTC
The same also happens when saving as PPTX.

Is this a limitation in PPT (or even present-day PPTX)? It is hard to find out this type of historical information. When looking at search results limited to max. 2007, I see people getting advice to use the equation editor in MSO to achieve an overline.

Version: 6.4.0.0.alpha0+ (x64)
Build ID: e1b51d4588b4b39592bb94dd5bb90de5e04d061e
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-23_09:16:11
Locale: fi-FI (fi_FI); UI-Language: en-US
Calc: threaded
Comment 17 NISZ LibreOffice Team 2021-06-02 09:21:14 UTC
(In reply to Buovjaga from comment #16)
> The same also happens when saving as PPTX.
> 
> Is this a limitation in PPT (or even present-day PPTX)? It is hard to find
> out this type of historical information.

Even current MSO 2019 does not support overline character formatting, only underline and strikethrough.
Comment 18 Valek Filippov 2021-06-04 13:35:20 UTC
(In reply to NISZ LibreOffice Team from comment #17)
> (In reply to Buovjaga from comment #16)
> > The same also happens when saving as PPTX.
> > 
> > Is this a limitation in PPT (or even present-day PPTX)? It is hard to find
> > out this type of historical information.
> 
> Even current MSO 2019 does not support overline character formatting, only
> underline and strikethrough.

This looks similar to tdf#56080 -- both are asking to do something which is not natively supported by destination format.

When one saves into non-native format LO shows a message:
"This document may contain formatting or content that cannot be saved in the currently selected file format <...>".
So... if this warning is ignored... then... whose fault is that?

I don't think this is "major, because of the data loss", unless it fails to save overlines in The Good Format.
It looks more like "Enhancement".

Possible implementation could add one line with proper style in the right position per line of text and probably group it.
However, that will not work well on opening the file unless LO is allowed to store some "vendor extension" to read it back.

Let me stop here before it started to sound as "WONTFIX"... ;)
Comment 19 Xisco Faulí 2021-06-08 19:40:19 UTC
it doesn't look like a high/major issue
Comment 20 QA Administrators 2023-06-09 03:14:31 UTC
Dear Wagner,

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