The image (hazard sign) should be rendered with a bold border. (I have comparitive images in the attached PDF.)
Steps to Reproduce:
1. Open File
The image has not a bold border
The image (hazard sign) should be rendered with a bold border.
User Profile Reset: No
Version: 188.8.131.52 (x64)
CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard;
Gebietsschema: de-DE (de_DE); Calc: group
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Created attachment 136501 [details]
Created attachment 136502 [details]
It's not a border, it's just an object boundary. Check this page: https://ask.libreoffice.org/en/question/71487/unwanted-gray-border-showing-up-around-images/
Closing as RESOLVED NOTABUG
Created attachment 136888 [details]
The EMF with the round corners and bold borders.
Created attachment 136889 [details]
Images of the EMF opened
I’m unsure to change the bug status from “RESOLVED NOTABUG“, but please have a second to read this post:
I read the thread you recommended in your answer. The suggestion there was to uncheck boundaries
Tools --> Options --> Application Colours --> Object boundaries --> [uncheck]
Another user in the tread suggested
Tools --> Options --> Application Colours --> Text boundaries --> [uncheck]
But that did not help.
If you open the problematic EMF image as a vector image with another program the border is not only bold, but also round at the corners of the triangle [like a real street sign]
I opened the file with OpenSeeIt (openseeit.sourceforge.com), [GIMP does not support EMF, only WMF] and made a screenshot.
I read in the change log that you massively improved EMF support in the 5.4 release, but I tested it with 184.108.40.206 and the latest 6.0 alpha, but the issue stays.
I also did reset the user profile.
I attached the EMF and a PDF with screenshots.
Thanks you for looking into it! I really appreachate you work!
Version: 220.127.116.11 (x64)
CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: GL;
Gebietsschema: de-DE (de_DE); Calc: group
Version: 18.104.22.168.alpha0+ (x64)
Build ID: 91d5cebbde2e854a73a9a7633725350df1418387
CPU threads: 4; OS: Windows 10.0; UI render: GL;
TinderBox: Win-x86_64@42, Branch:master, Time: 2017-10-09_01:26:55
Locale: de-DE (de_DE); Calc: CL
Yep, you're right. I misunderstood your description.
Build ID: 5273c680d17fa386a844d3bbffd20b6a8bd354a1
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Version 22.214.171.124.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
** Please read this message in its entirety before responding **
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!
still repro in
Version: 126.96.36.199.beta1 (x64)
Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win;
Locale: ru-RU (ru_RU); UI-Language: en-US