Bug 41638 - FILESAVE: Black character shadows will be shown grey by MS PPT Viewer
Summary: FILESAVE: Black character shadows will be shown grey by MS PPT Viewer
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected)
3.4.3 release
Hardware: Other All
: low minor
Assignee: Not Assigned
Whiteboard: BSA
Keywords: filter:ppt
Depends on:
Blocks: PPT
  Show dependency treegraph
Reported: 2011-10-09 22:30 UTC by Rainer Bielefeld Retired
Modified: 2023-08-24 03:14 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

test kit with sample.odp, sample.ppt, screenshot comparision (586.54 KB, application/zip)
2011-10-09 22:30 UTC, Rainer Bielefeld Retired

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2011-10-09 22:30:56 UTC
Created attachment 52162 [details]
test kit with sample.odp, sample.ppt, screenshot comparision

Problem description: 

Steps to reproduce with "LibreOffice 3.4.3  - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:302)]" :
1. Start IMPRESS from LibO start Center, Empty presentation, 
2. Select Presentation Background "Blue and Red Gradient" (what
   in fact is black and blue, see "Myowntest343.odp"
3. Type some own text in text fields (see sample) 
4. Menu 'Format -> Character Font Effects -> Shadow' (check)
5. Save as sample.odp and run slide show: text shadow is black
6. Exit slide show
7. Save as sample.ppt and Exit
8. open sample.ppt with MS PPT Viewer
   Expected: character shadows black
   Actual: character shadows white
Comment 1 Rainer Bielefeld Retired 2011-10-09 22:39:18 UTC
I picked this one form Apache OOo Bugzilla.
Still a problem with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID:  d3d1481-3f8994a-2ba0a9f)]" (110909)

Not a new problem, also visible with "LibreOffice Portable 3.3.3  - WIN7  Home Premium (64bit) German UI [OOO330m19 (Build:301  Tag]" 

NEW due to observation in Apache OOo Bugzilla

Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.

- Reported with Bug Submission Assistant -
Comment 2 A (Andy) 2013-03-03 12:41:49 UTC
reproducible with LO (Win7 Home, 64bit), but when opening the ppt in MSO 2007 the font looks for me a little bit blurred.
Comment 3 QA Administrators 2015-02-19 15:39:29 UTC Comment hidden (obsolete)
Comment 4 Buovjaga 2015-03-07 14:23:00 UTC
Reproduced from the .odp to .ppt and checked with ms ppt viewer.

Win 7 Pro 64-bit, LibO Version:
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Locale: fi_FI
Comment 5 tommy27 2016-04-16 07:22:58 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2017-05-22 13:22:39 UTC Comment hidden (obsolete)
Comment 7 Xisco Faulí 2017-07-13 12:21:22 UTC
Setting Assignee back to default. Please assign it back to yourself if you're
still working on this issue
Comment 8 QA Administrators 2018-07-14 02:47:20 UTC Comment hidden (obsolete)
Comment 9 Buovjaga 2019-08-23 11:29:44 UTC
Still repro from odp -> ppt & MSO 365

Doing some prioritisation to help the new PPT* improvement team.

Version: (x64)
Build ID: 3e64065612acec2eb29aa21e2b515953422256d7
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-08-15_22:57:26
Locale: fi-FI (fi_FI); UI-Language: en-US
Calc: threaded
Comment 10 QA Administrators 2021-08-23 03:51:20 UTC Comment hidden (obsolete)
Comment 11 Rainer Bielefeld Retired 2021-08-23 04:33:20 UTC
Google Sliedes viewer shows .pdp AND .ppt AND .potx (from Version: (x64)  Build: 85f04e9f809797b8199d13c421bd8a2b025d52b5) from kit without shadow. This might indicate that it's a bit more complicated that simply "filesafe LibO-bug".
Comment 12 QA Administrators 2023-08-24 03:14:22 UTC
Dear Rainer Bielefeld Retired,

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