Somnus Posted May 24, 2021 Posted May 24, 2021 Hello everyone, I'm having an issue where I took a screenshot of some staff notation and put it into a document. If I try to export document as a PDF now, Publisher is changing all the musical notes in the screen shot image into gibberish in another font. It's like Publisher is trying to read the image and turn text it finds into editable text or something, but again, it's only changed on the export. I've included the affinity file, the PDF, and screen shots. Thanks for your help guys! Encomia_rev.pdf Encomia_rev.afpub Quote
walt.farrell Posted May 24, 2021 Posted May 24, 2021 52 minutes ago, Somnus said: I'm having an issue where I took a screenshot of some staff notation and put it into a document. If I try to export document as a PDF now, Publisher is changing all the musical notes in the screen shot image into gibberish in another font. There's something about that description that seems incorrect. If it was a screenshot it would be an image, and there would be no text to change into another font. What you actually have in your sample .afpub file (thanks for providing it) is a page with 3 embedded PDF files with text, not screenshot(s). It is puzzling that the exported file comes out wrong, though, as you've Placed them in Passthrough mode, which should not require access to the fonts. With a bit of playing around I can say that it is the clipping rectangles that you have nested in the PDFs layers that is causing the problem. Without them, the fonts survive the Export process properly (though the layout is very messed up at that point). Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
benwiggy Posted May 25, 2021 Posted May 25, 2021 Sigh. There are just so many needless quirks to Affinity's PDF handling, that make it unreliable for this kind of work. lepr and lacerto 2 Quote
Alfred Posted May 25, 2021 Posted May 25, 2021 Maybe it’s just me, but I don’t regard this as having “no problems”! Look at the splits in the staves. (I also think it’s potentially confusing to talk about “cropping by clipping”, since cropping and clipping work the opposite way around from each other and can produce visually different results.) Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)
Alfred Posted May 25, 2021 Posted May 25, 2021 38 minutes ago, Lagarto said: i think it may be just you ;-). Did you comment a low-res JPG screenshot of an image that Affnity apps use to represent a PDF to be passed through? Oops! I guess that’s exactly what I did!! 39 minutes ago, Lagarto said: As for correct terminology, I do not think I am the first one on this forum to use the term "crop" to refer to using only part of an imported image (and hiding the rest). A good point well made, as they say. lacerto and William Overington 1 1 Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)
Somnus Posted May 25, 2021 Author Posted May 25, 2021 19 hours ago, walt.farrell said: There's something about that description that seems incorrect. If it was a screenshot it would be an image, and there would be no text to change into another font. What you actually have in your sample .afpub file (thanks for providing it) is a page with 3 embedded PDF files with text, not screenshot(s). It is puzzling that the exported file comes out wrong, though, as you've Placed them in Passthrough mode, which should not require access to the fonts. With a bit of playing around I can say that it is the clipping rectangles that you have nested in the PDFs layers that is causing the problem. Without them, the fonts survive the Export process properly (though the layout is very messed up at that point). Thank you for taking a look! I was under the false impression that they were screenshots, since that's what I normally do. Once you pointed that out to me I was able to get it taken care of. Thanks! William Overington and walt.farrell 1 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.