pbasdf

Hi Steve, Difficult to tell from the video, but could this be a result of Publisher applying the same scale, rotation and relative placement to the new image as was applied to the old image? That's certainly behaviour that I experience and have to remedy. To save resetting them one by one, does this work: 1. Select the Picture Frame Tool (shortcut F) 2. Use Select --> Select Object --> Picture Frames (from the menu bar) 3. In the Context Tool Bar, select Properties and then set scaling and anchor for all the picture frames

I haven't tested it, but I think this might be covered in Settings -->Tools --> Create Text with Blend Gamma:

Might this work for your situation - leave the lines as black strokes, select them all and apply a Gradient Overlay FX? You can set the orientation to 90 degrees so the overlay is applied vertically. You can fine tune the FX on one line and then use Copy/Paste FX to apply it to all the others. There are a couple of downsides: 1. The "length" of the gradient is set relative to each particular object, so the "top" of a line will always be one end of the gradient and the "bottom" will be at the other end - even if the absolute height difference is much less than for the other lines. Even a perfectly horizontal line will have the top edge in one colour and the bottom edge the other (see pic). You might be able to finesse this with the scale and offset adjustments in the FX panel. 2. I believe using FX will result in rasterisation on export.

I can get "Snap to Object Geometry" to work when using the node tool, but not the move tool. No luck with "Snap to Shape Key Points".

I believe the issue stems from Blender using a different DPI setting for its SVG import. They use 90 (see for example https://projects.blender.org/blender/blender/issues/107130#issuecomment-928885), whereas Affinity uses 72 in the export. 72/90 is 0.8, which explains why your 1m square in Affinity ends up as 0.8m square in Blender. So the solution might be to change your export DPI in Affinity to 90.

Hi Kip, Are you using any adjustment layers or FX? They can cause the text to be rasterised (even if the export options don't).

Hi Peter, I looked at the PDF for the green text/green background that you posted above. From what I can see (but I'm no expert), it sets the fill colour only once and uses that colour for both the rectangle and the text. See below (Comments after # are mine): /GS0 gs # set the 'graphics state' - in this case just configuring overprint /GS1 gs # ditto - in this case clearing any SoftMask 0.623529 0 1 0 k # Select CMYK colour space and set the current fill colour to 62%C 0%M 100%Y 0%K 70.8661 638.012 453.543 133.042 re # Draw a rectangle f # Fill it with the current colour 70.8661 638.012 453.543 133.042 re # Draw another rectangle (the stroke 50pt stroke) 120.866 721.054 m # move to the inside edge of the stroke 120.866 688.012 l # draw round the inside 474.409 688.012 l # ditto 474.409 721.054 l # ditto h # close the inside of the stroke f* # fill that with the current colour /GS0 gs /GS1 gs q # Save the graphics state 1 0 0 1 88.3058 687.353 cm BT # Begin text /F0 48 Tf # Select the font 0 0 Td # Set the text position [()-0.2()-0.2()0.2()-0.2()-0.5()-0.2()-0.1()-0.5()0.1()0.2( )0.2(\n)0.2()-0.2]TJ # Write out the text ET # End text Q # Restore the graphics state Line 3 appears tome the only line specifying a colour. So I suspect the problem must lie with your printer driver. Are you using the most up-to-date driver from Canon's website? Are you using the Postscript driver or another one? Phil

FYI, in case it's relevant and helpful, I have had similar issues with a publisher file with linked resources on Google Drive. I have G Drive configured to sync locally so the files should all be available - and thanks to the menu bar icon animation, you can see when G Drive is syncing: nothing showing at the time. I've also had similar unexplained delays when creating Packages. The only other culprit i had in mind was fonts: I still get occasional spinning beach-balls when opening the font list in publisher, which normally clear after a while (usually tens of seconds, occasionally longer). I wonder if the export process kicks off a similar hunt for font files which for some reason stalls? I'm running Publisher 2.4.0 on Sonoma on 27" iMac, btw.

As of 2.4 (I think) you can use the new "Make Same" option in the Alignment Panel. Select the object you wish them all to align with, then select all the others (using shift to add to the selection) then use the "Make same Rotation" option in the Alignment panel:

As a quick visual check, you can switch to the Photo persona, then in the Channels panel, switch off visibility for the K channel. Then scroll through all the pages. If you have any rich black text/images, they will still be visible. Everything that is pure K will disappear. Remember to switch the K channel visibility on again before switching back to Publisher persona - I always forget that. That won't overcome the export conversion issues highlighted above and elsewhere, but it will at least give you a visual check that you are starting the conversion process with pure K in the right places.

Just to note that you mention Fogra 39 but your screenshot is Uncoated Fogra 29.

Have you accidentally activated X-ray view mode? Resetting to Vector with View -->View Mode --> Vector should bring the colours back true.

Slightly - see this answer to a previous question:

In V2, in the Character Panel, click the Collection box (typically showing "All Fonts"). From the list of Font Collections that is displayed, select "Missing Fonts"). Then click the down arrow on the right of the Font Family box. It should then show the list of missing fonts. This is in the Help file for the Character Panel: "About the Character panel The Character panel is unique in providing the ability to: List typefaces within particular collections (including Missing Fonts)."

@David Rich Just a thought. I notice in your second screenshot that iCloud is showing the symbol which indicates that it is syncing your Mac with the cloud. Could it be that process is taking some time? If you download the file first, does Publisher then open it correctly?

@SteveMcDonald, This may be irrelevant, but... In the screenshots, you appear to have the text frame selected, so the text wrapping settings are those of the text frame itself, not the image. Select the drop cap image, and check the text wrap settings for that. From @firstdefence's post, it looks like the image might have text wrapping set to Edge.

One suggestion - in the character panel, check whether you have "No break" enabled - that forces text to ignore the frame boundary.

If you apply a Black and White Adjustment layer to your photo, it will be rendered as Pure K. Note though there are various posts about pure K being converted to rich black at export time. To avoid the conversion, ensure that your export profile is the same as your document colour profile.

In your workflow, would it work to use Expand Stroke on the separate curves, and then Geometry Add to combine them?

You can reset the rotation. AFPub: View menu: Rotate: Reset Rotation AP: View Menu: Reset Rotation AD: View Menu: Reset Rotation If you "right click" on the canvas, the context menu includes "Reset Rotation". There are also keyboard shortcuts for it (the default seems to be Ctrl-Shift-Cmd R in AP/AD). You can also disable trackpad rotation in (Affinity) preferences: Tools: Enable Canvas Rotation with Trackpad. See here for more information: https://affinity.help/designer/English.lproj/pages/DesignAids/rotateCanvas.html

From a quick (and possibly ill-informed) look at the PDF log, it seems like the problem lies with the embedded ICC profile in an image named "PdfIm_804.jpg" (though that might be an internal name for an embedded image??).

Regarding (3), could you make your own crop marks, as follows: In your master page(s), create a rectangle which extends from the very top left of the current bleed area of your spread to the very bottom right. For example, if your current (and desired) bleed is 3mm (top, bottom, outside) and 0mm (inside), and your page size is A4 (210 x 297mm), then the rectangle will start at (-3,-3) with dimension (426, 303). Give this rectangle a transparent fill and a narrow stroke in a distinctive colour, to act as a visual (and possibly snapping) guide when placing items that extend beyond the edge of the page. In the document setup, increase the size of the bleed, to say 10mm (top, bottom, outside) and 0mm (inside). With the pen tool, draw short vertical lines from the very top of the new bleed area down to the top edge of the rectangle, placed in line with the left- and right-hand edges of the spread. Repeat at the foot of the spread. Likewise draw short horizontal lines from the very left of the new bleed area to the left-hand edge of the rectangle, placed in line with the top and bottom edges of the spread. Repeat on the right of the spread. (The picture shows the crop marks and the (red) rectangle marking the original bleed area, and the new bleed area in lilac). When you export now, in the export options, include bleed but not crop marks (nor any other printers' marks). The niggle with this will be if you have any page content which currently extends so far into the new bleed area that it overlaps and obscures the crop marks. You might need to juggle the layer order in those cases, or create equivalent marks local to the page rather than on the master.

Do you have any hyperlinks in your document? I believe there’s an ongoing issue which causes exporting to fail if the document has any invalid hyperlinks (eg. poorly formatted email or web URL).

I don’t think the text frames are moving per se - but by inserting one page, a LH page becomes RH and vice versa. So what was inner margin becomes outer margin (and vice versa), which makes it look like they moved.

Which app are you using, Publisher, Designer or Photo? How did you create the ellipse text? Did you start from scratch, or have you used a template or other file from somewhere else?