mumbojumbo
-
Posts
18 -
Joined
-
Last visited
Posts posted by mumbojumbo
-
-
On 12/9/2020 at 9:50 PM, Joachim_L said:
Thanks for your explanation. But why using it, when SVG is better? 🤔
According to support article, Office 2016 SVG only works with paid Office 365 subscription - https://support.microsoft.com/en-us/office/edit-svg-images-in-microsoft-office-365-69f29d39-194a-4072-8c35-dbe5e7ea528c?ui=en-us&rs=en-us&ad=us&fromar=1
On 12/9/2020 at 7:26 PM, Patrick Connor said:We are having trouble replicating your exact problem, so I would ask you to try something. Please create a document with a transparent background (on the colour tab) and see if the exported EMF does not have the white box that gets misinterpreted in Word, it may be the background.
I will double-test Office 2019 compatibility and report later today.
On 12/9/2020 at 10:37 PM, Jowday said:Far, far from all programs support SVG. Especially software purchased years ago with a perpetual license licence you guys love so much. 😄
Back in the day that was the to go format in many workflows including software that pretty much used wmf/emf as the only vector or one of very few formats.
Also huge libraries of such files from the era exist in companies. Supporting them is key.
Correct! We also use EMF & WMF format for legacy engineering programs. Such programs are not going to be updated ever again to support SVG because developers are mostly in graves. The best thing about Windows computers is legacy support. This is very important to do business!
Black lives matter,
mumbojumbo
-
EMF/WMF is broken at least with Office 2016 for me. You are welcome to contribute your bug report to this thread as well.
Black live matter,
mumbojumbo
-
EMF is the only way to insert scalable vector object in Microsoft Office applications, especially (in my case) to Word and Excel. We heavily use this to provide company style templates for Word/Excel that would print flawlessly. Nobody can argue you should respect market share of Microsoft Office products and provide a proper compatibility with them. EMF is a really powerful file format for scalable images which is often overlooked by users. Only SVG is better.
Black lives matter,
mumbojumbo
-
13 minutes ago, Patrick Connor said:
Please calm down using bad language will not change the software any faster. If you read my reply again you would see this is not true, and the post is hidden not deleted. It is still visible to us and contains no more useful information than the first time your reported this. It was hidden because there is no point re-reporting in a beta forum anything that affects the release version as well. The same few people read all the posts and it simply wastes everyone's time to read the same thing a number of times. Very few posts are hidden as most people here follow the guidelines (including those on bad language)
Importantly only issues that are specific to the beta version need to be reported in the beta forums. That is how we organise things round here, so normally your beta forum report would have been moved to the bugs forum. However in this case you already had one in the bugs forum covering the same thing, so the duplicate was hidden. If everyone who has reported a problem posted in every beta thread "you still have not fixed my report" then the threads would be impossible to find any new information, so please do not do that
That's not me who hid valuable bug report without proper notification via PM. There is a reason for me to ask questions and use bad language. And your chronology of my posts is wrong. And you post off-topic here. Warning! Please stick to discussion topic which is "Why EMF export is not working correctly in Affinity Designer since day 1 and nobody fixes it?"
Black lives matter,
mumbojumbo
-
The EMF and WMF export feature is broken in Affinity Designer Customer Beta 1.9.0.864. Have a look at my report with examples.
Black lives matter,
mumbojumbo
-
3 hours ago, Jowday said:
As I wrote before the EMF files your product delivers is not really imported by anything else than Xara. The root cause and real issue is the file from Serif software. I am not really sure the EMF export should be available in its current form. I could not get anything out of it that was imported in any program. Except Xara. And one of your developers once work for Xara... interesting.
I double down on this. I have exported AD drawing to EMF and opened the exported file in Inkscape 1.0. All I see is white space. AD EMF export is broken.
-
I can see you're using current version of Word 2019, I'll double-check EMF claim regarding 2019. My file was created using Word 2016 and there is EMF bug in this case. However I can assure you everything works correctly when using EMF generated using Inkscape and Word 2016. I also have tried opening Circle.EMF generated by AD in Inkscape and the file is just white space. So it's still better to look into EMF export, it's broken!
You are also completely wrong regarding WMF issue. I saved my circle from Circle.AFDESIGN to Circle.SVG using Addinity Designer 1.8.5 & 1.9.0, opened it in Inkscape 1.0 and saved to Circle-Inkscape.WMF. Circle-Inkscape.WMF works absolutely correctly when inserted in Word 2016, no extra white space. So WMF export is broken 100%!!!
I've added 3 files mentioned above [Circle-Inkscape.WMF; Document (Word 2016 with Circle-Inkscape.WMF).DOCX; Document (Word 2016 with Circle-Inkscape.WMF).PDF] to 7Z archive and re-upload it here as Broken EMF-WMF Export Bug Report Source Files (Updated).7z
Black lives matter,
mumbojumbo
-
No it's not. The important files are gone. The 1.8.5 thread was posted by me not moderator. Without a proper 1.9.0 beta thread no developer will fix this before release and I will have to wait another year for a fix. I have reported this bug 2+ years ago in release thread and noone ever did anything about it. FFS is it like not enough disk space on a server to save a topic in beta forum? Like what possible reason can it be to remove a proper bug report on upcoming release??
Black lives matter,
mumjumbo
-
You're welcome. Unfortunately it seems they are not willing to be helpful at all. Someone has even deleted my bug report in 1.9.0 beta forum this morning. And also has deleted my bug report files. If you ask me, this is some s***y attitude to a customer. Only Allah knows how many bug report has been deleted before.
-
1 topic with important example files attached. Now everything is gone!!! Who is responsible for this **** attitude to paying customer?
-
Are you nuts? Is this how you treat your consumers??? Restore my report now: the bug has been reported by me 2 years ago and still has NOT been fixed!!!
Black lives matter!!!
-
I suggest you try saving file to SVG and opening in Inkscape 1.0, then saving to EMF and opening in PowerPoint. It should ungroup. The EMF and WMF export is totally broken in Affinity Designer since 1.6. Please have a look into my bug report featuring similar problem in Microsoft Word 2016+.
-
Hello developers,
Please fix broken EMF and WMF export in Affinity Designer 1.8.5.703 in Windows 10. The bug is there at least since 1.6 (that's when I started using AD). Bug is also present in Affinity Designer Customer Beta 1.9.0.864.
Steps to represent bug in EMF export:
- Start Affinity Designer 1.8.5.703
- Create New Document > Web > SVGA 800x600
- Create grey circle 600x600 in the middle
- Export file to Circle.EMF
- Create new document in Word 2016 or 2019 (I cannot test in earlier versions)
-
Drag and drop Circle.EMF into Word document
- Save Word docment as PDF using File > Save As > PDF
-
Resulting PDF should display grey circle, however there's nothing displayed in PDF (white space)!
Steps to represent bug in WMF export:
- Start Affinity Designer 1.8.5.703
- Create New Document > Web > SVGA 800x600
- Create grey circle 600x600 in the middle
- Export file to Circle.WMF
- Create new document in Word 2016 or 2019 (I cannot test in earlier versions)
- Drag and drop Circle.WMF into Word document
-
Expected Word should display grey circle. The circle is displayed but it is 1/2 smaller and has a lot of extra white space around it.
- Save Word docment as PDF using File > Save As > PDF
-
Resulting PDF has grey circle but it is still small
Steps to represent correct behavior when exporting to EMF/WMF using Inkscape 1.0:
- Start Affinity Designer 1.8.5.703
- Create New Document > Web > SVGA 800x600
- Create grey circle 600x600 in the middle
- Export file to Circle.SVG
- Open Circle.SVG in Inkscape 1.0
- Save Circle.SVG to Circle.EMF using Inkscape > File > Save As > Circle-Inkscape.EMF
- Create new document in Word 2016 or 2019 (I cannot test in earlier versions)
- Drag and drop Circle-Inkscape.EMF into Word document
- Save Word docment as PDF using File > Save As > PDF
-
Resulting PDF shows grey circle correctly
- Same accepts (works correctly) to WMF export using Inkscape 1.0
I'm attaching source files (.AFDESIGN, SVG, EMF, WMF) mentioned in steps to this post in 7z archive — Broken EMF-WMF Export Bug Report Source Files.7z
Black lives matter,
mumbojumbo
-
Snapping not working in following scenarios: a) if I rotate object and then try to snap it's bounding box (or bounding box midpoints) to bounding box or nodes of another object; b) if both objects is rotated; c) if only destination snapping object is rotated. Basically you cannot snap to 90% of objects correctly using bounding box!
Is that another "feature" of Affinity Designer or something's broken?
-
Patrick Connor, again WMF/EMF export is still broken after all those years.
- To reproduce EMF issue in Windows 10: make shape with any properties in Affinity Designer (document size 800x400 px, sRGB, 96 DPI), export as EMF, insert into Word 2016, save as PDF (from Word 2016). Shape is invisible.
- To reproduce WMF issue in Windows 10: make shape with outline stroke 3 px in Affinity Designer (document size 800x400 px, sRGB, 96 DPI), export as WMF, insert into Word 2016, shape outline barely visible, save as PDF, shape outline almost invisible.
WMF/EMF is the only way to insert vector images into Microsoft Office products. Please fix this. Inkscape can save to EMF/WMF perfectly fine.
Two feature requests:
- Please add bitmap tracing via same open-source algorithm that is used in Inkscape. It works great. Affinity Designer has no such feature at all.
- Please add repeat object around shape/path. The workaround using text tool is very messy and provides unsuspected results.
-
i'm using paint.net to edit scans and photos of printed documents on a daily basis. i also do photo editing in photos app for macos. i'm willing to switch to affinity photo because it seems to be modern and well-maintained app. while testing app in windows 10 ltsb n anniversary update i came across some issues. please have a look and tell me what you think:
-
20–75% larger jpeg file size vs paint.net with similar quality when saving with the same quality and resampling settings (95% quality - +35% size, 99% quality - +75% size)
i attach bilinear- and fant-downsized (fant is for supersampling) images so you could zoom in 600% and see paint.net provides same quality or better and a considerably smaller file size - no auto-suggest to use bilinear resampling for downscaling and bicubic for upscaling (explained), annoying to double-check every time, should be able just set it to 'best quality' like paint.net so affinity photo chooses algorithm depending on task (upsize - bilinear, downsize - bicubic)
-
abnormal ram usage like it never goes back to 120 mb after editing multiple images and closing them, please take a look on the screenshot -
affinity photo uses 840 mb of ram with no images open after editing a couple earlier; while google chrome 69 uses 130 mb with 22 heavy tabs; paint.net was editing same images as affinity photo and after closing edits ram usage went back to normal 133 mb - image zoom ratio would drop to 100% after a while for images that are on background tabs, very annoying
-
blurry 200% zoom -
300% zoom is ok -
- no image size under viewport or anywhere on screen, have to use resize dialog to check size
- aspect ratio locked or unlocked when resizing is not being remembered and resets to locked every time, annoying when dealing with a lot of images, refer to paint.net as example how it should be done
- aspect ratio anchor setting when resizing is resets to top left every time, annoying when dealing with a lot of images, refer to paint.net as example how it should be done
- no option to save 16-bit png (65536 colors), this option is included in paint.net low color filetype plugin from 2009 (https://forums.getpaint.net/topic/15317-low-color-filetype-bmp-gif-png-tiff-20091204/)
- navigator viewport selection better be able to snap to image borders (separate setting required)
- quick zoom in and zoom out on the down right would be handy (similar to paint.net)
-
windows 10 dark theme has inverted tabs colors (inactive tab color should ba same as other ui background and active tab color should be a bit lighter, refer to google chrome incognito mode for example on how to do it better)
- flood select tool rmb click to add not working
- when drag n dropping several images their alphabetical order is not being respected for tabs (while list >> order is ok)
thanks for your time. i'm quite happy with the product overall and will report more bugs/suggestions later on. hope you'll fix small shit i'm talking about. it would make life so much easier.
— MUMBOJUMBO
-
20–75% larger jpeg file size vs paint.net with similar quality when saving with the same quality and resampling settings (95% quality - +35% size, 99% quality - +75% size)
.PNG.8bda6e8b54a7e68f456349a6c123e504.PNG)
_PDF.PNG.f5e65026ba40c9f63f22b5a726aac5c1.PNG)
.PNG.59d2c1af546409f0929dcc144c662b84.PNG)
_PDF.PNG.1fcf98d21546d0af1d7be8a1a96e8c5a.PNG)
_PDF.PNG.11a7ad09f5c39b2a6c93c35f90991e38.PNG)
Affinity Designer 1.8.5.703 EMF and WMF export is broken
in V1 Bugs found on Windows
Posted
OK, I have double-tested the EMF bug in Microsoft Word 2019 and Excel 2019 16.0.13328.20128 without subscription and everything is fine. Office 2019 products do import SVG files as well, and no subscription is required.
So the issue appears to happen in Microsoft Office 2016.
However I had an opportunity to test EMF created with Affinity Designer latest customer beta 1.9.0.something in Adobe Illustrator CC 2021 25.0.0.60. And EMF appears to be broken:
Inkscape 1.1 beta (and 1.0 release) cannot read Affinity Designer-produced EMF file and display white page. However Inkscape reads Illustrator-produced EMF file perfectly. You should really stop moderating me because of my bug report! Or I will have to ask my money back . I'm attaching files for my bug report with this post in 7z archive.
Black lives matter,
mumbojumbo
EMF bug previewed in Adobe Illustrator CC 2021 25.0.0.60.7z