Hello Martin,
as I have heard you are now responsible for the Word import & export filter.

Depending to the Issues 20484 (AutoShapes), 20486 (3D Objects), 20485 (WordArt),
I20490 (grouping problem)  I have a short request. Up from src680m34 a new Shape
is available that is more compatible to the AutoShapes from Microsoft than
everything else we had before. The new shape is called SdrObjCustomShape. It is
now required that the Cumshape Object is activated also for the Word Import.

It's implementation can be found in :
svx/source/svdraw/svdoashp.cxx
svx/source/customshapes/*

At current only the PowerPoint import/export filter is using the new
CustomShapes and for compatibility reasons it is required that the Word & Excel
filter is doing also. I didn't activate CustomShapes for the Word&Excel filter,
because it was easier to integrate the feature for one application only, and of
course I didn't need to take care to the special treatment each application is
having (e.g. objects that are converted into fly frames or similar... ).

The export filter should automatically handle CustomShapes correctly, so only
the import filter needs to be adjusted by setting the
SVXMSDFF_SETTINGS_IMPORT_IAS flag at the SvxMSDffManager with something like that: 
   aSvxMSDffManager.SetSvxMSDffSettings(
       aSvxMSDffManager.GetSvxMSDffSettings()
          | SVXMSDFF_SETTINGS_IMPORT_IAS );

If the import of AutoShapes is activated, nearly each object will be imported as
SdrObjCustomShape, a exception of this rule is the SdrObjGraf and SdrOle2Obj,
thus also means that simple SdrRectObjs or SdrTextObjs won't occur any longer.

Internally each SdrObjCustomShape is derived from the SdrTextObj and adds
following features:
- text frame and shape frame is now strictly separated
- support of "wordwrap text in autoform"
- support of "resize autoform to fit text"
- no support of  "autogrow width" and "autogrow height"

If CustomShapes are loaded, the most important text attributes are already set
in the method:
DffPropertyReader::ApplyCustomShapeTextAttributes,
so it might be possible that some code of the virtual method ProcessObj can be
removed.

If you have any questions, wishes or enhancements than please contact me,
thanks,
Sven