RoyMcCoy

My problem was that particularly the seemingly pointless "workspace" (?) covers everything behind it, but it's okay now that I've given up on any other solution and figured out a workaround using the Keyboard Maestro Mac accessory. I nearly always launch or switch to Affinity Photo (as to most apps) using a macro, which up to now was quite simple: Triggered by any of the following: The Hot Key ⌃⌥⌘F12 is pressed Will execute the following actions: Activate Affinity Photo 2 I added the following to this today: Pause Until All Conditions Met Application “Affinity Photo 2” is at the front If All Conditions Met Menu with name “Save As...” is not enabled Execute the Following Actions: Type the ⌘W Keystroke In other words, if no document is open KM immediately dismisses the UI, which I get back whenever I open a doc or create a new one. At this moment I'm thinking I'll disable the added steps, however, since the background doesn't bother me when I launch the program and want to do something with it. The problem was rather as I described, when I closed the last document window and still had that dumb white space looking at me and serving only as a nuisance and a hindrance. I took care of this, the actual problem, with a completely new macro launched in Photo by cmd-w, the standard command for closing a window: Triggered by any of the following: The Hot Key ⌘W is pressed Will execute the following actions: Select Menu Item in Affinity Photo 2 Select: File ⇢ Close 
 Pause for 1.0 Seconds [unfortunately necessary but no big deal] 
 If All Conditions Met Menu with name “Save As...” is not enabled Execute the Following Actions: Type the ⌘W Keystroke picking up the if/then command from the first macro. So now, when I close the last document window, the unwanted white space goes away on its own. Hallelujah. Thanks to all for the help.

That's right, and I continue to see no sense in it at all. But it's okay now – see my reply to Walt.

Thanks, but it's not the monitor brightness level, which makes no essential difference. Neither do the sliders, except Text Contrast as I said to prophet. If I put it on the Dark setting it just makes the background black rather than white, which still undesiredly covers everything else. I open three files, hit cmd-w three times and am looking at the white background. If – Mac users! – can open three files, hit cmd-w three (not four) times and then see the desktop, I'd like to see it. If they can do it then I should be able to also.

Thanks, but I adjusted my settings to match those shown in your screenshot and still had the white. None of those sliders seems to change it except Text Contrast, which will turn the background to solid black and then it's hard to make it white again (not that I want it white, or black, or any shade of gray – I don't want it at all).

This is interesting. I hope you can provide a key to how to avoid the white background.

Thanks Old Bruce, but then it's a matter of cmd-w cmd-h rather than cmd-w cmd-w, which is hardly an improvement. Nor does it make any difference, since the second cmd-w hides the toolbar, context menu and palettes the same as cmd-h. Is there anyone from Affinity here who might want to defend the white window against at least two users who don't want and are annoyed by it?

This issue of the white background is still current for me. In a nutshell, it remains an annoyance that more or less every time I close a document window, I have to hit cmd-w a second time to make the damn white background disappear. I don't want it and it serves no purpose that I can even imagine. Is this hard to understand? I want to close the document I was doing something with, but not the program. With the program not in the foreground and momentarily not being used, why would I want its big blotch of white filling up my screen? And why should I have to hit cmd-w a second time to get rid of it, especially when I never wanted it in the first place? I write this in the hope of change. If it's already been changed and there's now an option not to have the white background, somebody please inform me, thanks.

Thanks again, @Hangman. No, switching to the Designer and Photo Personas isn't what I have in mind here, especially since I have no idea what you're talking about. (Please don't tell me, thanks.) The PDF editing problems I alluded to were never very serious, since if I made the PDF myself I could make the desired change in the originating program, and if it was coming from someone else what business did I have changing it (or why would I have to)? All I really want to do is juggle pages occasionally, and I've now found that Preview does that just fine. Shortcuts? I see it's on my relatively new MacBook Air, but I never noticed it till now. Keyboard Maestro will do about anything I want, so I think I'll leave Shortcuts alone unless I eventually want to use voice commands with Siri – which might be fun but I've never gotten into it.

Many thanks, @Hangman, for taking the time and going to the trouble of laying this all out for me. My only remaining question still regards what exactly can be done with text in an imported PDF in Publisher using Interpret. I used to be able to edit PDF text in Acrobat Pro (though not in InDesign, as you correctly point out), but there were always strict limitations as to what I could do and I was generally limited to only the simplest of edits, often not even being able to make those. (I vaguely recall it would say something about a missing system font.) I'd like to see an example of a PDF text edit one can do with Interpret in Publisher that one can't do in Acrobat Pro. If it's around the the same level of capability, I may never be much interested (particularly since I'm not working and am hardly doing anything anymore anyway :-). By the way, I just found out yesterday that I don't need to buy a PDF editor to replace Acrobat Pro on my old Mac (which I don't feel like firing up anymore, particularly with its unrepaired battery and keyboard problems). I was at the point of buying PDF Expert, but when looking for reviews of it on the web I discovered that I can do everything I normally want to with a PDF (combining files, adding and deleting pages) using the Preview app that comes free with the Mac. So I can not only save some bucks, but also avoid making the icons on my Dock even tinier by adding yet another app to it.

Interesting, thanks.

This sounds like a boilerplate comment that could be defensively made about anything, with the bad guy being the one insisting that the Affinity apps behave exactly like the Adobe ones. But that's not what I'm doing. I have no objection to setting or switching a preference, and in fact I'm assuming that there is some advantage to not importing PDF fonts that led Affinity to not do so originally. I just still don't know what that advantage is or was, exactly. I also (more than) suppose there are gross disadvantages that pressured it to later add the ability to import the fonts. But, er, wait a minute. Interpret may have been the original Publisher mode, but Passthrough has apparently been the default since I acquired the program. So PDF fonts are imported in it, right? They always were, until I was prompted to "fix" the compatibility problem that had never been a problem previously by switching to Interpret; only then did Publisher not import the fonts. Whoa, you're right. I don't know how I missed that this preflight check has "Disabled" too, but apparently I did. Part of my problem with this appears to have been that I couldn't get the "Custom" profile to persist outside of the doc in which I changed its settings. When I just now created a new "Universal" preset, however, it does persist and when I switch a doc to it the doc is okay and doesn't give the unwanted alert anymore. I wonder if that's the difference between a (document?) profile and a (program-wide?) preset. In any event I'm set on this now and know how to get rid of the unwanted "Placed PDF version" alert if I see it again. Thanks!

Thanks @Hangman. I understand this. What I don't understand is that I used Aldus PageMaker, Adobe PageMaker, and Adobe InDesign for decades and there was never any question (at least as far as I knew) of whether PDF fonts were imported with a PDF file or not – they simply always were. You could decide whether or not to include fonts when you created a PDF, but there didn't seem to be any Passthrough vs. Interpret option on importing and I don't remember that the lack of something like this was ever noticed. It therefore seems to me that it was the Interpret rather than the so-called Passthrough option that was designed and put into Publisher. It may be that I'm not sufficiently appreciative of Interpret, which may well allow more manipulation of imported PDF text than had previously been possible – I don't know. I get this too. But the Wall Street Journal doesn't care about lost features that it doesn't use in its simple crossword PDFs (presumably preferring maximum backwards compatibility), and I don't either. I don't see why I can't turn this check off in a profile if I don't want it – and, yet again, I don't know why Publisher suddenly started hassling me about it when it hadn't before. I guess I can finally suppose that it's "just one of those things". Yes, but I'm not creating these PDFs. I'm not sure it's persistent. Thanks again.

Thanks, Walt and Oufti. Walt: Yes, it was always on Passthrough before, though I was completely unaware of Passthrough vs. Interpret and never set one or the other. It was still on Passthrough when the "Placed PDF version (PDF 1.4) is not compatible with the PDF export version" alert started appearing for some as yet unknown reason, the "fix" of which switched to Interpret and messed up the fonts. Again, I'm sure I didn't change anything, particularly not a profile as I'd also never touched those. It might imaginably be that a program update triggered the change, though the problem occurred before I updated to v. 2.1.1. I notice that the PDF Passthrough compatibility check can't be turned off in the Custom profile, so I can't stop the alert by doing that. None of the files that worked with no problem earlier are doing so now; they all give the Placed PDF Version alert, though they didn't before. Switching to Interpret is no fix, unless I want to go looking for fonts like DJ5RetinaCD-Light and succeed in finding them. Oufti: This is a helpful explanation of font substitution and of why I got the bad letterspacing, thanks. I don't think I'll ever have to pick fonts I have to replace ones I don't have, though, since Passthrough will give me the PDF fonts and I can deal with the PDF version compatibility although it's an annoyance.

Thanks Walt, but I'm still confused about this. (1) My understanding is that fonts are usually if not always included in PDF files, and if so why should I have to find and install "missing" fonts now when I never had to before? (2) Publisher was working fine without this problem before. Do you or anyone have an idea as to why the change occurred? (3) Edit Document does show the "missing" fonts (missing in my system but not in the PDF), and after clicking on it (but not before) these fonts also show in the Font Manager window when I select a font in the Preflight panel and click on Fix. Furthermore, Edit Document only shows the Document Contains Missing Fonts alert once, the Assigned Profile alert is transient, and sometimes the Document Contains Missing Fonts alert is transient also. This all seems rather strange and could possibly use some improvement, but if all the missing fonts are being substuted by Helvetica as the Font Manager window indicates, why am I getting the bad letterspacing? Is the font substitution not really working, or what? I don't see why I should have to switch to Passthrough, edit my Preflight profile to specify a different PDF level, or make any color-setting adjustments when all this was working fine before. Is restoring the previous correct behavior impossible? Or maybe I was already set for Passthrough and had the right PDF level and color settings before, they got messed up somehow and now I have to figure out how to restore them? Apparently the Publisher files are already set for Passthrough, and they switch to Interpret only when I click on Fix in response to the "Placed PDF version (PDF 1.4) is not compatible with the PDF export version" alert. The Profile is set to Default as it presumably always was, so there's still the question of what changed and why. When I change the PDF Passthrough Compatibility setting to PDF 1.4, I lose the "Placed PDF version" alert but get another one, "Placed PDF has objects of a color different to the document colorspace. The PDF will still pass through." Colors are not very important in these docs and I don't know how to appropriately readjust the document colorspace anyway, so I unselected "Check color space matches document" under Image Color in the Edit Preflight Profile window. This doesn't get rid of the unwanted color alert, however, also when I click on Check Now. I did another one of these and got a good printout with proper letterspacing. Moreover I lost the unwanted Preflight color alert when printing, though I get it back if I click on Check Now even with the modified profile (why is the same thing apparently called a preset?). I guess this will get me by (especially since I'm going to be printing out these PDFs without Publisher), so thanks indeed. There are still some mysteries and apparently sketchy behavior, however. I'd still like to know what may have gone wrong, and I still think printing should continue to work normally with the Default profile.

I'm posting in this old thread because I'm having the same problem now in June 2023 (Ventura 13.4.1 on M2 MacBook Air, all Publisher versions 2), namely the "Placed PDF version (PDF 1.4) is not compatible with the PDF export version" alert. I'm certain I didn't change anything that should have caused this; it just started happening. There have been certain oddities besides this basic one. For one, I'm not seeing the "Placed PDF version" alert anymore, but rather just a list of six allegedly missing fonts. For another, last night I wasn't seeing the list of missing fonts either, but the Publisher file with the imported PDF still printed out with bad letterspacing, which is the bad result of this, the letters themselves looking okay. When I see the list of missing fonts, select one of them and click on Fix, I don't see the name of the font or anything else in the Font Manager window, so apparently there's no way to substitute and I wouldn't want to have to do that with six fonts in every similar doc anyway. I'm retired so this isn't a work thing. The PDFs are saved/downloaded from https://chall.us/hex/hex_all_wsj.html. I open a copy of the previous crossword, select its PDF, click on Replace Document and select the new one. Sample files attached. For me it's showing the missing fonts as DJ5EExchange-Semibolditalic, DJ5RetinaCd-Bold, DJ5RetinaCD-Light, DJ5RetinaNr-Bold, DJ5RetinaNr-Medium and DJ5ZapfDingbats-Regular. It's not so bad that this has happened since I now realize I can just print the PDF out with Fit selected and without importing (I think the printout was clipped at the bottom before and that's why I started placing the PDF in Publisher), but I'd like to get the problem resolved for the future. Thanks. rising and falling.pdf rising and falling.afpub