How to export 'Octagon Bevel' and 'Diamond Bevel' to OOXML

[Miklos Vajna]

Hi Regina,

On Sun, Apr 10, 2022 at 12:55:42AM +0200, Regina Henschel <rb.henschel at t-online.de> wrote:
> Because there exist no suitable OOXML preset shape, we need to export them
> with <custGeom>. I could make dedicated 'Write_Octagon_Bevel' and
> 'Write_Diamond_Bevel' methods with OOXML handles and guides. Should I do
> that?
> 
> I can at least move them from lcl_IsOnDenylist to lcl_IsOnAllowlist. That
> way the export will generate the outline as octagon or diamond with fixed
> lines from the current handle state of the shape. I think that would be
> better than the 'rect' now.

If we have a preset where there is no OOXML preset, then writing the
full custom geometry sounds good to me.

> The real problem is their shading. It is not contained as command in the
> enhanced geometry. It is encoded into the type identifier, see
> https://bz.apache.org/ooo/show_bug.cgi?id=33139. The current implementation
> of that "feature" has a bug, see
> https://bz.apache.org/ooo/show_bug.cgi?id=80216.
> This "feature" uses more grades of shading than the four available in OOXML.
> So what should I do with the shading of these shapes?

I think if our feature set there is more rich than what OOXML allows,
then either we can just say this is not our problem or if this really
bothers somebody, we can change our preset to use shading which is
simple enough for OOXML to handle.

The trouble in the second case is to make sure we don't break old
documents.

Regards,

Miklos