Bug 68159 - FORMATTING: Formatting issue with word art
Summary: FORMATTING: Formatting issue with word art
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.1.1.1 rc
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-15 18:04 UTC by phly95
Modified: 2015-02-11 20:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
How it should look (864.25 KB, video/mp4)
2013-09-25 16:47 UTC, phly95
Details
How it should look HD (2.88 MB, video/mp4)
2013-09-25 18:59 UTC, phly95
Details

Note You need to log in before you can comment on or make changes to this bug.
Description phly95 2013-08-15 18:04:22 UTC
Problem description: 

Steps to reproduce:
1. use word art in Powerpoint 2007+
2. Save it as pptx
3. Open the same presentation in OpenOffice

Current behavior:
No Word Art, sometimes making text unreadable under black backgrounds and 3D text effects are destroyed

Expected behavior:
Word Art functions properly with smooth letters
              
Operating System: Windows 8
Version: 4.1.1.1 rc
Comment 1 tommy27 2013-09-04 20:58:37 UTC
please provide a test file which shows the bug.

are LibO 4.0.x versions affected by this bug too or is just a 4.1.x bug?
Comment 2 phly95 2013-09-19 17:25:32 UTC
It applies to all Libreoffice versions. I'm attaching a test file right now.
Comment 3 tommy27 2013-09-19 17:59:47 UTC
I see no attachment.
Comment 4 phly95 2013-09-19 18:18:00 UTC
This file is a presentation I used for class. It uses lots of Word art and angle changes, and some other formatting. Lots of formatting is lost in Libreoffice unfortunately. Some animations that start automatically require click in libreoffice sometimes and sometimes the text color is not correct in the case where it becomes unreadable such as this presentation. Sorry for the russian page, I couldn't upload the file directly to the bug report (too large). Just click the download button and it'll work. http://download.files.namba.kg/files/82433272
Comment 5 phly95 2013-09-19 18:18:28 UTC
sorry for the confusion
Comment 6 tommy27 2013-09-21 18:17:26 UTC
please tell me the number of the most problematic slides so I can exactly see where the bug should appear.
Comment 7 phly95 2013-09-25 16:47:30 UTC
Created attachment 86577 [details]
How it should look

This is a video showing how it should look. Sorry for low quality, I got less than 1 MB so that it wouldn't get rejected from the upload here.
Comment 8 phly95 2013-09-25 17:07:14 UTC
actually, I was aiming for 5 MB, but on the bitrate calculator, I looked at megabits instead of megabytes.
Comment 9 phly95 2013-09-25 17:11:56 UTC
I'll upload HD if 5 MB is acceptable.
Comment 10 phly95 2013-09-25 18:59:17 UTC
Created attachment 86586 [details]
How it should look HD

Full HD with just slightly worse as what ppt spit out (they spit out a 55 MB file and it had some compression artifacts, can you believe that?) The magic of Handbrake. I was going to upload 5 MB HD, but this site can handle only 3 MB but here it is in 3 MB HD.
Comment 11 Joel Madero 2014-06-25 16:06:33 UTC
Complex files are pretty useless for us, also please upload to an English site so that QA knows what buttons to click to download the file.

Marking as NEEDINFO. Please do the following:

Create simple test cases
Attach the simple test case along with a pdf created from Microsoft Office and another created with LibreOffice.

It would be great to have a collection so if you could take the time to make these simple test cases I'll try to push them forward a bit.

Once at least 1 (simple) test case is added that demonstrates a single problem along with the pdf's, please set back to UNCONFIRMED.

Again - this would be really really useful for us so I hope you have some time to add these test cases. One problem per test case is best.
Comment 12 QA Administrators 2015-01-10 18:06:52 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

Message generated on: 10/01/2015
Comment 13 QA Administrators 2015-02-11 19:55:25 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

Message generated on: 2015-02-11
Comment 14 QA Administrators 2015-02-11 20:01:57 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
Message generated on: 2015-02-11