summaryrefslogtreecommitdiff
path: root/svtools
diff options
context:
space:
mode:
authorRegina Henschel <rb.henschel@t-online.de>2023-01-06 16:02:31 +0100
committerRegina Henschel <rb.henschel@t-online.de>2023-01-06 17:53:01 +0000
commit81e6d47635656297cdddc9030f4422c0bcc203f9 (patch)
treed3a1b04d34ffd259a73f1d789c28cecfdf609e6f /svtools
parent2eefb695c0bfd00abd22e17e64ab2a1692fe2af4 (diff)
tdf#152896 do not apply color shading twice
If a character theme color is shaded, Word writes this as w:themeShade attribute of the w:color element. If the character also has transparency, Word writes an additional w14:textFill element with a w14:lumMod child element. In such cases the w14:textFill element supersedes the w:color element. The initial implementation of Fontwork import in commit cbf30153a5c776e6d1ee26f2f83c8f77503eceb9 does it wrong. It replaces the color itself but not the color transformation, so that the shading was applied twice, once from w:themeShade attribute and the other time from w14:lumMod. The solution here is to reverse the order so that w:color is only evaluated if w14:textFill is not present. Another solution would have been to clear the color transformation vector before adding the values from w14:textFill. I use reverse order here because it more clearly reflects that w14:textFill supersedes w:color. Change-Id: I3e700795167a34238ea619b9c4a691c10da357f4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145150 Tested-by: Jenkins Reviewed-by: Regina Henschel <rb.henschel@t-online.de>
Diffstat (limited to 'svtools')
0 files changed, 0 insertions, 0 deletions