Support for Office Open XML, the office XML-format designed by Microsoft. See also: [http://wiki.openoffice.org/wiki/OOX] The "TODO: OOXML_spec" comments are related to wrong implementation of the spec. The oox code was written against the OOXML dialect produced by MSO 2007, which is not standard compliant. Newer MSO version use the correct default values as desribed in the spec. We need a way to handle both in the future. The first step is to mark these places when you see them. Many of them already have a comment that the implemented default value is not in line with the spec. == DrawingML Custom shapes and presets == custom shapes are part of DrawingML and are different to binary ppt and VML in older formats, so we needed to add new code to work with these. the import happens in oox/source/drawingml, where they are imported as LO's enhanced custom shape's. see offapi/com/sun/star/drawing/CustomShape.idl and offapi/com/sun/star/drawing/EnhancedCustomShape*.idl the export is quite behind now, as it was done before we started work on fully supporting drawingml custom shapes. (see FUTURE WORK below) example of drawingml preset: example of drawingml custom shape (equal to star5 preset): we needed to extend our custom shapes for missing features and so 5 new segment commands were added. G command for arcto drawingml record and H I J K commands for darken, darkenless, lighten, lightenless records. the commands are save into ODF in special namespace drawooo, which is extension not yet in the standard. Thorsten suggested to put it in such a namespace and keep original (incomplete) geometry for backward compatibility, before we can extend the ODF. that's why you will see 2 of them in cases where some of the new commands was needed. Radek backported code for the new commands to 3-6 and 4-0 branches. the drawingml also contains new presets (compared to binary/VML) and so we now have code with these presets - they are basically predefined custom shapes. we generate them using scripts in oox/source/drawingml/customshapes/ and the output are oox/source/drawingml/customshapepresets[123456].cxx source files containing the definition for the preset shapes. this mean that we import presets from OOXML files perfectly. one area to look at might be check how handles on the imported custom shapes (and presets) work. the source code generation happens in these steps: * generate pptx files by running generatePresetsPPTXs.pl. it generates files in pptx/ from cshape.pptx sample - replacing slide1.xml in it and placing it in new file in pptx/ named after the preset plus one cshape-all.pptx file all the presets * build oox module with debug (ie. make -s debug=t dbglevel=2) * import cshape-all.pptx into impress and redirect output to custom-shapes.log * generate oox-drawingml-cs-presets data file by running generatePresetsData.pl - it uses debug output from the custom-shapes.log file * check generated data file oox-drawingml-cs-presets and move them to oox/source/drawingml/ * build oox with new source files and test while importing presets, we also set the name of the custom shape so that we can detect it on export as save it again as preset. the scripts in oox/source/drawingml/customshapes/ also generate pptx files for signle presets and also for all presets cshape-all.pptx. the cshape-all.pptx file is then loaded into impress build with debug enabled in oox and the command line output contains information, which are used by generatePresetsCXX.pl. redirect the output into custom-shapes.log in oox/source/drawingml/customshapes/ and run the script. it creates the customshapepresets[123456].cxx source files with presets definitions. also the generated pptx files can be used when debugging bugs in custom shapes import/export. also the cshape-all.pptx can be used to test the round trips. there's small problem with these pptx as they cannot be imported into powerpoint, but that can be fixed quickly. when fixed, we can use it to test powerpoint odp export and see how complete it is regarding custom shapes. OpenXML SDK tools might help when fixing cshape-all.pptx http://www.microsoft.com/en-us/download/details.aspx?id=30425 FUTURE WORK: because we have to make sure that all the roundtrips like PPTX --> ODP --> PPTX work correctly and doesn't lose data. the only problematic part is probably saving custom shapes (ie. not presets) to PPTX. that part of code predates work on custom shapes and is unable to export general custom shapes yet. it will need a bit of work as LO has more complex equations than DrawingML. other parts should work OK, PPTX --> ODP should work and don't lose any data. presets should already survive PPTX --> ODP --> PPTX roundtrip