Bobbob
Members-
Posts
22 -
Joined
-
Last visited
Everything posted by Bobbob
-
Perfect!* I hadn't thought of using Ghostscript (only ever used gs to convert from PS to PDF, didn't realise it worked the other way around too). Just checked and gs -sDEVICE=tiff32nc does the trick, and confirms it's just 100%K that overprints automatically. You've just saved me an Acrobat subscription 😄 *well, more perfect would be having basic vital functionality like this implemented within Affinity but I think Serif have made it pretty clear they have no intention of catering for even the occasional prepress user.
-
Hi, what counts as "black" for automatic overprinting of black in Publisher? Is it just 0%C 0%M 0%Y 100%K, or will any colour with 100%K automatically overprint? And is there any way to check that overprint is set correctly in the output PDF without Acrobat Pro? thanks Currently using 2.2.0 on Win 10
-
It would be very useful to have an (optional) preflight check to flag vector layers which will be rasterised on export. There are times when you want vector layers to be rasterised (e.g. using some blend modes, pixel-based masks/effects etc.) and other times when you really don't. Background: I recently found a bug that was causing some vector layers to be rasterised on export, but this could just as easily happen through user error. Now I have to go through several very large documents and manually check layer by layer to make sure it's not happening anywhere else. Which is going to take a while... On the other hand, I can quite see that such a check would very often throw up lots of results for layers that you're quite happy to be rasterised, so you would need to be able to turn it off.
-
Hi @Dan C thanks for getting back to me. Here's a minimal demonstration: The text "UNGROUPED" on p1 is not rasterised on export but the text "GROUPED1" on p2 is (I set 36DPI in the export dialogue to make it clear). The two text objects seem to have the same relationship to the adjustment layers below them, but only the one that is in a group is rasterised on export. The text "GROUPED2" is not rasterised, which is as I would expect as in this case the adjustment layer is attached to the image. I used soft proof layers to demonstrate because that's how I initially found this behaviour and also I thought they weren't supposed to do anything on export. If this is how things are supposed to work that's fine, but it seems a bit weird and I wish I'd noticed before I sent an expensive job to print... Steve goup_text_test.pdf goup_text_test.afpub
-
I have a group which contains a number of vector layers and a pixel layer as the lowest for the background. If I add an adjustment layer to the pixel layer it only affects the pixel layer and the other layers render as expected. However, if I (accidentally) move the adjustment layer to be immediately above the pixel layer, it only adjusts the pixel layer but it causes all the vector layers above it to be rasterised on export. Is this the expected behaviour? It's kind of a pain. Publisher 1.8.4.693 on Win 10
-
I'm sending a job to a printing company from an RGB colour space publisher file. If I export as PNG then #000000 black prints as rich black, but if I export as PDF then #000000 black seems to print as 100% K. If I send them a non colour-managed PDF from inkscape then #000000 black prints as rich black, so I'm guessing it's something about the way publisher exports to PDF rather than anything their end. Is it possible to change this behaviour? I can see how this might be helpful sometimes, but it's not helpful right now. And yes, I know I could/should just work in CMYK, but there are reasons why I'm using an RGB file in this case.
-
I'm with the OP on this. It can be useful, if not strictly necessary, to go backwards and forwards between single/double spreads. This is an area that Publisher doesn't handle well imho. And no, I wouldn't arrange pages out like that in Quark either, but I would appreciate the freedom to be able to do so.
-
This applies to both Publisher and Designer. Publisher 1.8.3.641 on Win 10. If I add a stroke outline to text, weird things happen as I increase the stroke weight. The outline/halo ends up with lots of holes in it, particularly at high stroke widths. Interestingly this only happens for "solid" stroke style. Some fonts are worse than others. If I change to "dotted" stroke with curved end caps then I get a solid outline, i.e. what you would expect from "solid" stroke style. Sometimes the holes in the outline disappear on PDF export, sometimes not. textoutlinetest.afpub
-
Publisher 1.8.3.641 on Win 10 I have a project that was designed as facing pages. When I untick "facing pages" to change to single page spreads, some objects are given crazy coordinates, e.g. x=2147483648 mm y=-145257464098.7 mm. This then causes an error if I try to export as pdf. This seems to happen specifically to vector objects which are groups and which were created by "magic" duplication. Objects which were vector cropped are also moved and resized but not as dramatically. I've not managed to recreate this with a simple example I'm afraid.