summaryrefslogtreecommitdiff
path: root/scripting/Jar_MemoryUsage.mk
diff options
context:
space:
mode:
authorJustin Luth <justin.luth@collabora.com>2024-02-09 17:26:52 -0500
committerMiklos Vajna <vmiklos@collabora.com>2024-02-21 08:45:08 +0100
commitd7cd7dff0e8f71b3d83b4c91b574f39248a25e2f (patch)
tree2b8c30f33ffdc6e3b42ccda52a1f89cc7b68fcfa /scripting/Jar_MemoryUsage.mk
parented91971c9312e4b8a33c03c28d339bff6c5accc7 (diff)
tdf#126533 docx export: page background vml fill: tiles/patterns
This patch only benefits LO. MSO ignores "frame" and always treats page background as it if were tiled, but that is a trait we do NOT want to mimic. Textures are the primary fill type that needs to be tiled (instead of scaled/stretched). LO export also treats patterns as tiled bitmaps, and the end result of exporting as a tile looks the same as the original pattern. It just loses HOW the page background (i.e. as a pattern) but that is very low value. It is rather difficult to export as a true pattern and just not worth the effort of identifying the correct fore/background colors, converting to b&w image, and inverting the B&W image if the first pixel is white instead of black. [Hatching seems similar to patterns, but rarely (and only coincidentally) would it tile well. I think hatching is a new DML-only thing. Hatching is not in the page background UI of MS Word. LO just exports any hatching as a solid color.] Change-Id: I5cd3f1c6e380edb5e5b21900bad289fa298574e2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/163206 Tested-by: Jenkins Reviewed-by: Justin Luth <jluth@mail.com>
Diffstat (limited to 'scripting/Jar_MemoryUsage.mk')
0 files changed, 0 insertions, 0 deletions