Bug 55459 - [EMF] FILEOPEN Missing hatch pattern and wrong text fonts
Summary: [EMF] FILEOPEN Missing hatch pattern and wrong text fonts
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx, filter:emf
Depends on:
Blocks: emf-testbed EMF-WMF
  Show dependency treegraph
 
Reported: 2012-09-30 06:06 UTC by Nadav
Modified: 2025-08-14 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
example file (983.59 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2012-09-30 06:06 UTC, Nadav
Details
Screenshot of image3.emf from the example file (83.32 KB, image/png)
2019-05-14 08:44 UTC, Gabor Kelemen (allotropia)
Details
Third image from example file (190.44 KB, image/x-emf)
2019-05-14 08:45 UTC, Gabor Kelemen (allotropia)
Details
Fifteenth image from example file (176.83 KB, image/x-emf)
2019-05-14 08:46 UTC, Gabor Kelemen (allotropia)
Details
Screenshot of image15.emf from the example file (43.81 KB, image/png)
2019-05-14 08:47 UTC, Gabor Kelemen (allotropia)
Details
Screenshot of image21.emf from the example file (68.89 KB, image/png)
2019-05-14 08:49 UTC, Gabor Kelemen (allotropia)
Details
Twentyfirst image from example file (184.90 KB, image/x-emf)
2019-05-14 08:50 UTC, Gabor Kelemen (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nadav 2012-09-30 06:06:27 UTC
Created attachment 67866 [details]
example file
Comment 1 bfoman (inactive) 2013-03-22 12:26:54 UTC
Checked with:
LO 4.0.1.2
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit

LibreOffice crashes while loading this file. Word 2010 opens without issues.
Comment 2 Jacques Guilleron 2013-03-24 00:04:30 UTC
Hi Nadav,

No crash for me with LO 4.0.2.1 and LOdev 4.0.3.0+ (Build ID: 2a2ada8fcfeb18b91599a8fb09f3c2081e66abe) on Windows 7 Home Premium.
Arial(body CS) replaced By Arial help. 
If I directly copy one by one graphs from Word to Writer, I get clean copies.
So, for me, perhaps a docx import filter issue.

Regards,

Jacques Guilleron
Comment 3 QA Administrators 2015-02-19 15:46:40 UTC Comment hidden (obsolete)
Comment 4 Nadav 2015-02-19 19:48:12 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2016-02-21 08:37:48 UTC Comment hidden (obsolete)
Comment 6 Armin Le Grand (collabora) 2016-04-26 12:56:11 UTC
Can load without problems using

Version: 5.2.0.0.alpha1+
Build ID: fdc1bd89559ea5efe2b3f6aa45b5158fedaed587
CPU Threads: 8; OS Version: Windows 6.1; UI Render: default; 

The Charts look bad since they are painted using the Canvas MetaFileRenderer (rendering::XMtfRenderer), not the only problem with that part (check bug 90677)
Comment 7 QA Administrators 2017-05-22 13:26:57 UTC Comment hidden (obsolete)
Comment 8 Thomas Lendo 2018-05-24 21:43:23 UTC
Still reproducible with Version: 6.1.0.0.alpha1+
Build ID: 6fecbff9810ae9afc2de8c4d5e9e8a8a511d1f2d
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: de-DE (de_DE.UTF-8); Calc: group
from yesterday.
Comment 9 Gabor Kelemen (allotropia) 2019-05-14 08:39:52 UTC
In current 6.3 master the following problems are still there with these charts:

- They are emf images, adjusting meta bug
- The Hebrew text is garbled, this is the same as bug #102780
- The text and numbers seem to be bold in Paint, but not in Draw
- The columns have a fill pattern that is lost and only the solid color remains, this seems to be bug #101639
- Some data points have no columns only an X axis label in Paint, but in Draw a negative direction column is drawn

I'll upload extracted example files and their renderings for the third and fifth problems.

Version: 6.3.0.0.alpha0+
Build ID: c5c425296debb2fbd67af8ec29f87e285d08575f
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: threaded
Comment 10 Gabor Kelemen (allotropia) 2019-05-14 08:44:06 UTC
Created attachment 151387 [details]
Screenshot of image3.emf from the example file

The text is bold in Paint but now in draw.

Also: missing fill pattern and garbled characters.
Comment 11 Gabor Kelemen (allotropia) 2019-05-14 08:45:01 UTC
Created attachment 151388 [details]
Third image from example file
Comment 12 Gabor Kelemen (allotropia) 2019-05-14 08:46:06 UTC
Created attachment 151389 [details]
Fifteenth image from example file
Comment 13 Gabor Kelemen (allotropia) 2019-05-14 08:47:16 UTC
Created attachment 151390 [details]
Screenshot of image15.emf from the example file

This shows columns under the X axis where there is none in Paint
Comment 14 Gabor Kelemen (allotropia) 2019-05-14 08:49:29 UTC
Created attachment 151391 [details]
Screenshot of image21.emf from the example file

This has a small column under the X axis in Paint, but it becomes much larger in Draw.
Comment 15 Gabor Kelemen (allotropia) 2019-05-14 08:50:16 UTC
Created attachment 151392 [details]
Twentyfirst image from example file
Comment 16 Chris Sherlock 2021-08-14 20:46:03 UTC
This is because we haven’t implemented brush patterns.

See https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-emfplus/ffb875ee-9713-4356-a869-5e4dc4ea4afa

The hatch styles are here: https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-emfplus/ac72d44f-1ec9-401b-82d6-f16c8e84134d

typedef  enum 
 {
   HatchStyleHorizontal = 0x00000000,
   HatchStyleVertical = 0x00000001,
   HatchStyleForwardDiagonal = 0x00000002,
   HatchStyleBackwardDiagonal = 0x00000003,
   HatchStyleLargeGrid = 0x00000004,
   HatchStyleDiagonalCross = 0x00000005,
   HatchStyle05Percent = 0x00000006,
   HatchStyle10Percent = 0x00000007,
   HatchStyle20Percent = 0x00000008,
   HatchStyle25Percent = 0x00000009,
   HatchStyle30Percent = 0x0000000A,
   HatchStyle40Percent = 0x0000000B,
   HatchStyle50Percent = 0x0000000C,
   HatchStyle60Percent = 0x0000000D,
   HatchStyle70Percent = 0x0000000E,
   HatchStyle75Percent = 0x0000000F,
   HatchStyle80Percent = 0x00000010,
   HatchStyle90Percent = 0x00000011,
   HatchStyleLightDownwardDiagonal = 0x00000012,
   HatchStyleLightUpwardDiagonal = 0x00000013,
   HatchStyleDarkDownwardDiagonal = 0x00000014,
   HatchStyleDarkUpwardDiagonal = 0x00000015,
   HatchStyleWideDownwardDiagonal = 0x00000016,
   HatchStyleWideUpwardDiagonal = 0x00000017,
   HatchStyleLightVertical = 0x00000018,
   HatchStyleLightHorizontal = 0x00000019,
   HatchStyleNarrowVertical = 0x0000001A,
   HatchStyleNarrowHorizontal = 0x0000001B,
   HatchStyleDarkVertical = 0x0000001C,
   HatchStyleDarkHorizontal = 0x0000001D,
   HatchStyleDashedDownwardDiagonal = 0x0000001E,
   HatchStyleDashedUpwardDiagonal = 0x0000001F,
   HatchStyleDashedHorizontal = 0x00000020,
   HatchStyleDashedVertical = 0x00000021,
   HatchStyleSmallConfetti = 0x00000022,
   HatchStyleLargeConfetti = 0x00000023,
   HatchStyleZigZag = 0x00000024,
   HatchStyleWave = 0x00000025,
   HatchStyleDiagonalBrick = 0x00000026,
   HatchStyleHorizontalBrick = 0x00000027,
   HatchStyleWeave = 0x00000028,
   HatchStylePlaid = 0x00000029,
   HatchStyleDivot = 0x0000002A,
   HatchStyleDottedGrid = 0x0000002B,
   HatchStyleDottedDiamond = 0x0000002C,
   HatchStyleShingle = 0x0000002D,
   HatchStyleTrellis = 0x0000002E,
   HatchStyleSphere = 0x0000002F,
   HatchStyleSmallGrid = 0x00000030,
   HatchStyleSmallCheckerBoard = 0x00000031,
   HatchStyleLargeCheckerBoard = 0x00000032,
   HatchStyleOutlinedDiamond = 0x00000033,
   HatchStyleSolidDiamond = 0x00000034
 } HatchStyle;
Comment 17 Chris Sherlock 2021-08-14 20:47:58 UTC
Note that the EMF+ reference image shows this more clearly.
Comment 18 Sophie Sipasseuth 2023-08-14 09:24:49 UTC
The bug is still present in LO 24.2.0.

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 2b0b4ddc8bd8fdd4cd689300620fe4621d7533b7
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL threaded
Comment 19 QA Administrators 2025-08-14 03:12:58 UTC
Dear Nadav,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug