summaryrefslogtreecommitdiff
path: root/i18npool/Executable_saxparser.mk
diff options
context:
space:
mode:
authorRegina Henschel <rb.henschel@t-online.de>2020-06-10 20:58:54 +0200
committerRegina Henschel <rb.henschel@t-online.de>2020-06-14 16:06:54 +0200
commit6de8d3109dffa7d4d0cc06f319cca70134f0a8f3 (patch)
treeeb171e57dcc1895e20ce716768a9b85787242778 /i18npool/Executable_saxparser.mk
parent41f9fe6ba53580a67e18cd43222806af438457a2 (diff)
tdf#103474 handle edge cases in ARCANGLETO
The arc-polygon generation in tools does not consider edge cases with zero height or width. That leads to wrong rendering in some ooxml shapes, when the handle is dragged to its extrem position, e.g. in left/right braces/bracket and can. I have switched from tools to basegfx in case ARCANGLETO and added handling for edge cases. Switching to basegfx has the additional advantage, that Bezier curves are used and not polylines. You see the difference, if you convert the shape to curve. ARCANGLETO is not used from our shapes or from import from binary MS Office, but only from OOXML or user-defined custom shapes. tdf#122323 MS Office restricts the swing angle to [-360°,360] in rendering. Such restriction is not in OOXML and not in ODF. Nevertheless, I have added a clamp for ooxml-foo shapes for better interoperability. Change-Id: Ib3233ce14dab950cc521cb8cbac6809a1d3e34a7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/96068 Tested-by: Jenkins Reviewed-by: Regina Henschel <rb.henschel@t-online.de>
Diffstat (limited to 'i18npool/Executable_saxparser.mk')
0 files changed, 0 insertions, 0 deletions