Created attachment 181336 [details] SmartArt 'Pyramid' plus screenshot Open attached document. It has a SmartArt on the first slide and a screenshot from it on the second slide. The font color is 'black' in PowerPoint but 'white' in Impress.
Created attachment 181343 [details] The first example file in current nightly and PP 2010 Confirming in Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 21a31eefab1401d288dbb8220f3df3365be9efaf CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded Seems like this color is coming from a theme.
*** Bug 150103 has been marked as a duplicate of this bug. ***
After a little investigation, it seems to me that this is more of an MS-Office bug for two Smart-Art types (Basic-Pyramid and Inverted-Pyramid). The problem does not occur with the other two Pyramid Smart-Art types (Pyramid List, Segmented Pyramid). The original error file also appears in white font when opened in OnlyOffice and Google Slides. The reason is that in ppt/diagrams/drawing1.xml, each <dsp:txBody> element has a <dsp:style> <a:fontRef idx="minor"> <a:schemeClr val="lt1"/> </a:fontRef> </dsp:style> <a:lt1> <a:sysClr val="window" lastClr="FFFFFF"/> </a:lt1> style font color set which in ppt/theme/theme1.xml refers to a white font color. I have created other Smart-Art types in MS-Office which default to black font color (Pyramid List --> attached Pyramid list.pptx, Continuous Arrow Process --> attached Continuous Arrow Process.pptx, Circle Process, Basic Venn, etc...) and they are displayed with black font color in LibreOffice, OnlyOffice and Google Slide. In these documents, the character color style for each <dsp:txBody> element in ppt/diagrams/drawing1.xml is either not referenced by any color (<a:fontRef idx="minor" />) or is referenced by black (<a:schemeClr val="tx1"/>). Since the original bugdoc (with Basic-Pyramid and/or Inverted-Pyramid) was created in Microsoft Office with the default black text color, but was saved with white text color style, so according to OOXML Standard it should appear with white text color as it is happening in Google Sheet, OnlyOffice and in LibreOffice as well. See attached file Pyramid_basic-vs-Pyramid_list-after-MSO-export.png
Created attachment 200160 [details] Pyramid_basic-vs-Pyramid_list-after-MSO-export
Created attachment 200161 [details] Pyramid list
Created attachment 200162 [details] Continuous Arrow Process
Created attachment 200163 [details] Pyramid_list_MSO-LO
Created attachment 200164 [details] Compare_bugdoc_in_LO-OF-GS-MSO
(In reply to Balázs Varga (allotropia) from comment #3) > After a little investigation, it seems to me that this is more of an > MS-Office bug for two Smart-Art types (Basic-Pyramid and Inverted-Pyramid). : > Since the original bugdoc (with Basic-Pyramid and/or Inverted-Pyramid) was > created in Microsoft Office with the default black text color, but was saved > with white text color style, so according to OOXML Standard it should appear > with white text color as it is happening in Google Sheet, OnlyOffice and in > LibreOffice as well. So it appears everyone except for Microsoft properly implements the OOXML Standard here? As the originator of this document (and the duplicated bug #150103) let me close this as NOTOURBUG. (Anyone disagreeing, please override me.) Thank you for the excellent diagnosis, Balázs.
(In reply to Gerald Pfeifer from comment #9) > So it appears everyone except for Microsoft properly implements the > OOXML Standard here? Ideally the goal would be for LO to match MSO bug-for-bug in case of OOXML and other Office format, as they are the authoritative implementation of these formats. Regardless, since I can add nothing else here, I'm leaving this bug report as is.