https://issues.apache.org/ooo/show_bug.cgi?id=125045
--- Comment #7 from Armin Le Grand <armin.le.gr...@me.com> --- Reason found; the xml im/export does chain SvXMLExportPropertyMapper to combine properties; this has some caveats (double entries as here, already avoided partly by indexing the static tables with e.g. [1] or [13] in stead of [0] at construction time, also double XMLPropertyHandlerFactory entries). In this case a XMLShapeExportPropertyMapper gets added/chained a CreateParaExtPropMapper(...) which is a XMLTextPropertySetMapper(TEXT_PROP_MAP_SHAPE_PARA). Used PropMaps are aXMLSDProperties[0] and aXMLParaPropMap[1] (the one comes from already avoiding to have the 1st entry double which is a "ParaUserDefinedAttributes" / "UserDefinedAttributes" entry). Unfortunately both contain the fill attribute set now due to writer changes, thus these are exported double. ChainExportMapper is not very convenient but currently used ten times in xmloff, reportdesign, dbaccess and sc, so not simple to replace/correct. Thinking about a good solution... -- You are receiving this mail because: You are watching all issue changes.
