dr_who

Agreed. I can't wrap my head around what this has to do with "design". I understand that images beyond 32,767px are a pretty niche thing but within the UI/UX realm, you sometimes need very large sprite sheets. As things currently stand, I have to export my sprite sheets as tif files and then have them converted to png files via an online service. Which I find needlessly convoluted.

Any updates on this issue? Ran into it a while ago, the same ordeal: rasterizing a group yields blurry results if there's an instance of the Unsharp Mask filter on the layer stack. While it's perfectly avoidable once you're aware of it, it can be a bit of a trap to an unsuspecting eye. Not fun discovering the issue further down the line with a project, when it's already too late.

Thanks. I’m considering pulling the trigger on this one while it’s still on sale. Don’t know how it’s managed to fly under my radar up until now.

Can anyone summarize the features VectorStyler has that AD lacks?

Yeah, I uninstalled the whole font family and then only reinstalled the TTF version, seems to be working perfectly now. Thanks a bunch! Hopefully this is of use to others facing similar issues.

I’m pretty sure I’ve got the GitHub version as the font has a couple of weight variations. Seemingly, all the weight variations have both OTF and TTF versions, the TTF versions being currently disabled according to the macOS Font Tool. Could this perhaps play into it? Thanks for the suggestions, I’ll be sure to try them out!

Hi, On exporting to PDF, all texts with the font Bebas Neue become corrupted. I'm using the 'PDF (for print)' setting. Does anyone have any idea what could be causing the issue? In Publisher, the font appears as it is supposed to, it only gets corrupted during the export.

+1 for vector fills.

Ok, so if my document is set to (for example) ’CMYK_Profile1’ and then I convert it to ’CMYK_Profile2’ during export, all my native CMYK bits will get converted as well? If that’s the case, then I’ll try and avoid doing that. Fortunately, I’ve already received the preferred profile from the printhouse and it’s very unlikely that I would have to change it to something else further down the line. As for the RGB stuff, I almost always use sRGB exclusively (unless I’m dealing with 3D rendered stuff, in which case it’s usually in the EXR/linear format) and I certainly intend to stick to that workflow this time around as well.

Thanks! You've been very helpful. Aside from making sure all my settings etc. are correct, the transition from ID to Publisher has been a breeze so far. Astonishingly so, in fact.

Thanks a bunch for your answer! So in my case, I do have several passthrough PDF's - and if I understood you correctly - I should therefore refrain from using the PDF/X setting? (And choose the Press Ready setting instead.) And just to be clear, even though my document is in CMYK mode, I can still import images in RGB mode? I prefer to keep my images RGB while I'm still editing and adjusting them (curves, levels, color balance etc.) and only convert them to CMYK at export. So if I've turned off the profile embedding option, Publisher should only convert the images at export and leave the native CMYK bits (essentially vector elements created within Publisher, text etc.) untouched? I still have Acrobat Pro installed, so I'll be sure to inspect my PDF with it once I'm done with the document.

Hi! To cut to the chase right away - coming from InDesign - I've normally done my RGB->CMYK conversion at export, with the following settings: Color Conversion: Convert to Destination (Preserve Numbers) Destination: Whatever color profile I've received from the printhouse Profile Inclusion Policy: Don't Include Profiles How would one go about emulating the above settings in Publisher?

+1

Couldn’t agree more! I really feel for the OP. Imagine you’re on a tight deadline, having worked hard the whole day and when you’re finally about to output the deliverable pdf you’re faced with this issue... Yeah, wouldn’t make me laugh either. I love this app to death which is why this thing is really killing me. But you’re right, having a feature at your disposal that is only going to betray you in the end is bordering something I don’t even want to say out loud.

That’s one option but to me, even when tracing a high-res image, the results always seem more or less wonky... Depends highly on what’s being traced, though, and is definitely worth a shot.