Created attachment 119295 [details]
1) Open attached file
2) Notice that all three rectangles have a hatching fill, though they should have a pattern fill
Build ID: 329496c1f75f97d2e6119ceb214a2ea1fbadb17a
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-10-03_02:47:24
Locale: en-US (en_US.UTF-8)
/word/document.xml has entries similar to this
where "pct5" is the internal pattern name for the 5% pattern, "accent1" is a foreground color of #4F81BD found in /word/theme/theme1.xml (<a:accent1>) and "bg1" is the background color of #FFFFFF found in /word/theme/theme1.xml (<a:lt1>) through <w:clrSchemeMapping w:bg1> in /word/settings.xml. As LO doesnt have any inbuilt patterns to map to, it can utilize the pattern bitmap file with the <mc:Fallback> tag, similar to
<v:fill r:id="rId6" o:title="" color2="white " type="pattern"/>
where "rId6" is referenced in /word/_rels/document.xml.rels to /word/media/image1.gif. The only thing that needs to be done to the black and white pattern bitmap file is swap the colors with the foreground and background colors.
Win 7 Pro 64-bit, Version: 220.127.116.11 (x64)
Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe
Locale: fi-FI (fi_FI)
We now have the MSO patterns (bug 94547), so it is now possible to map the prst attribute value to the presets found in standard.sop file.
As Luke mentioned in bug 94547 comment 16, we correctly utilize the gif file when it is in the old mso format (e.g. attachment 127146 [details]).
Created attachment 146328 [details]
Sample file correctly exported to .odt with Word 2016
LO uses 8x8 pattern, while MSO uses 32x32. The dots patterns do map well, but this is not true for many others. A universal fix would be to import patterns the same way MSO exports them to ODF, by converting the pattern to a tiled bitmap.
Dear Yousuf Philips (jay) (retired),
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!