nwhit

His answer seemed to indicate that he "meant" to say switching WITHIN Publisher (thus, the Photo Persona. When he said "Starting APhoto separately lets the menu entry appear again." seems to be in agreement with your instruction, Walt. Think he just isn't clear on the difference in the terms "Persona" versus full App.

Be pretty easy (and free) to simply download the 30-day free trial and give it a go. Easy way to test it.

As a media production firm, we've been running CS6 in a Parallels VM (Sierra for max compatibility for a bunch of software) for the last couple years with no real issues. Runs fast, works, shares files with the main OS, etc. Allowed us to upgrade the main host OS for newer software like Affinity.

Ah, yes. Driven past there many times! Amazing that a company this size can turn out such fantastic software with such great and personable support. Thanks to all involved! Good people!

Yes, I'm aware of that, but thanks for the reminder of that feature. It does, of course, assume that a person ALWAYS starts with a rectangular picture frame, which is often not the case. And I am unaware of a way to convert an oval/circle picture frame to square. Additionally, changing an existing rectangular frame to a circle using the corner option still requires a bit of tweaking in order to actually get it back to a circle or decent oval, and time = money for clients. Thus the Feature Request to have a simple toggle to go back and forth. Just be very, very handy for layout work. I would literally use it multiple times a day since several of our clients incorporate both round and square graphic items in numerous pubs.

I run into this all the time in Publisher. When revising previous publications or doing rough layouts, I have a need to change existing picture frames from square to round and vice versa. And, yes, I also routinely create shapes, then convert to picture frame. But when working on layouts, like to try an image contained in a rectangle, but also would like to easily be able to see it in a circle without having to start from scratch. And I don't want to go to the complexity of converting the frame into curves, then dealing with that. Just a simple toggle between square and round. Hopefully this would be a simple thing to implement. Thanks. And here we are in 2022 and hard to believe how long it's been since I've worked in ID!!! Actually since the first version of APub! Started with v1 of PageMaker, so been a long path to get to 2022!

Thanks @Dan C. I normally participate fairly deeply in the betas as these new features are added, but when PDF Passthrough happened, I was too busy to get more than superficially involved. Thus I missed the discussion on the ramifications for Preflight. Also seems odd that something so critical (the Preflight errors show virtually all the time due to the default being for an X-PDF) wasn't covered in the new video tutorial for the new PDF Passthrough/Placement. It would seem that most all users would get a preflight error after placing a PDF for passthrough since using PDF-x output isn't all that common except for users working with prepress requirements. I'm guessing most users simply ignore the errors (or don't use Preflight) because trying to find out the actual meaning of the preflight error is very difficult to ascertain. Perhaps it should be added to a Publisher FAQ section until it is better described in the Help. I watched the progress of PDF passthrough with great interest during the beta process since I used to have a background in print shops, newspapers, publications, etc. where it is a critical feature for modern publishing. I realize that it is still a work in progress with some rough edges still, so can understand how this might have been overlooked. Hoping at least the presence of this thread will help others who, like me, are initially baffled by the preflight error messages and can't find much of any info on the errors. Pretty simple to fix, assuming you know where to look!! 😉 Overall, Affinity apps just keep getting better and better. A few bumps along the way, but so refreshing as compared to the old standard apps. I was an Aldus PageMaker v1 user and trainer, so it's been a long journey to get to this point. While Publisher still has some glaring missing things, it is today highly competitive with far greater customer support. Thanks again.

Okay, after a whole bunch of searches and reading, finally found an answer in a beta thread. 1. In Preflight panel, need to click the Edit Profile in the little Actions menu (top right of pane). 2. Go down to PDF Passthrough, then select the minimum type of PDF you're wanting to Place. 3. Will need to Create a Preset for that setting since the Default seems to be a minimum of X-1a:2003. Otherwise you will always see the error message if you are Placing regular v1.7 PDFs. Overall, doesn't seem like a very intuitive or smooth way to do this preflighting. Would think there would be a better way, but who knows. Maybe in upcoming versions. Just wish that this would be explained on the need and how to do this in the online Help for the app! The Help says there is a Preflight for PDF Passthrough, but doesn't explain how it works and the need to set it to what you want in the Edit mode.

Just watched the Affinity video on placing content including PDFs, but like the online Help, it does not explain what kind of PDFs will actually passthrough instead of rasterizing. Rasterizing a placed PDF is not acceptable under most situations, so one would think that if there is a limitation on the kind of PDFs that will work, that info should be readily available in the Help. It's just hard to imagine that PDFs created in Designer won't work. I thought that might be a bug, but apparently it isn't. Sure could use some help on this since I have a publication that needs to be finalised.

Not sure how this got moved from Bugs to Questions. I've looked in the online Help for Publisher regarding the recent feature to Place PDFs as Passthrough, but I cannot see anything in the entire online Help that says what kind/type of PDF will actually passthrough without rasterizing on export (thus, not really passthrough). As per my original post, a PDF created in v1.10 of Designer apparently cannot be used for Passthrough in Publisher v1.10? That doesn't seem to make any sense, thus the question if this is a bug. Placing a Designer PDF shouldn't end up getting rasterized when exporting a PDF of the Publisher document, at least I wouldn't think so since that would be of little use. Right now, I cannot seem to locate any information of what is allowed to be Placed as a Passthrough PDF if I want to avoid the Preflight error message that it will be rasterized. If Passthrough doesn't work with Designer-created PDFs, then how do I create a PDF that can be Placed for Passthrough in Pub?

Working on a doc in 1.10.0 and have a couple PDF's exported from ADesigner. Have them marked as PDF Passthrough. Yet Preflight is warning "Placed PDF version (PDF-1.7) is not compatible with the PDF export version. The PDF will be rasterized on export." I haven't tried exporting yet, but the warning concerns me. I've tried exporting from Designer in both For Print and For Export, but get the same warning. If I place the Designer doc instead of the exported PDF, I don't get a warning. Obviously, I don't want the placed PDFs to rasterize. Is this a bug or is this newer feature just a bit more complicated than simply placing a PDF and having marked as Passthrough? Haven't tried exporting from Designer in PDF-x formats, but would think a "normal" PDF for Print or Export would be "compatible" in Publisher. But obviously I'm doing something wrong.

Aha! Think I may have found the workaround! According to this article by a prepress guy, apparently one of the font managers (TypeFace) can actually shut off/deactivate the OS11 System/Library/Fonts/Supplemental fonts, which are 283 fonts, many of which are seldom used by some people. Assuming this is true (I hope!!!), I can thus use TypeFace to create actual sets that would only include the fonts I want, plus it has to include the 73+ system fonts that cannot be deactivated. That would really help clear up the All Fonts dropdown!! http://www.jklstudios.com/misc/osxfonts.html UPDATE: Just tried to deactivate one of the Supplemental fonts and it worked! And it no longer showed up in APub All Fonts!!! Looks like I may have found the magic solution! Plus TypeFace is only $35, so a lot more affordable than some of the other options, which according to the article, none of the others can deactivate these 283 Supplemental fonts. Thank goodness!!

So in other words, the font sets/groups you create in a font manager become the only active fonts showing in apps??? But not clear on how can they not show (deactivate) the 355 "permanent" fonts in OS11 that can't be deactivated? Is a font manager app actually moving fonts out of fonts folders, or trying to deactivate fonts not in a group?? But that, of course, can't be done in OS11 with the 355 fonts in System/Library/Fonts. I guess I'm still not seeing how what is created as sets within the font manager apps affects what I see as font lists within apps. Old age, I'm thinking!! 😂

Old thread, but have a question. I've downloaded a few free trials of these mentioned font manager apps, but for the life of me I cannot see how to use them within Affinity apps! None of their documentation explains how to use the managers within an app, only how to organize fonts. Can anyone explain how to use TypeFace, FontBase, RightFont, etc. Like I said, adding and organizing looks easy. But how are these used within the Affinity apps themselves to select and set type? Thanks.

Forgot to answer your question. NONE of them can be turned off!!! They now put those fonts into the System/Library/Fonts directory and move your personally installed fonts into the Library/Fonts and ~/Library/Fonts folders. The workaround that I finally figured out is to use Font Book's font collections with only your own fonts/styles. In the collections, you can Disable the numerous OS11 installed fonts and styles. Helps clean up an otherwise huge font dropdown containing these new "permanent" fonts that a person might not ever use.

Thanks Bruce. As you can read in the other thread in Publisher Bugs (with much more detail), we've tried that. The permanent/locked Futura installed by OS11 is a very limited one with only a couple actual styles. As you can read in the other thread, since cleaning out the "antique" Futura fonts I used to use for many, many years, then installing the two new good Futura font families (reg and cond), I now have all the various styles available. And when I load an Affinity app, when I first look at the All Fonts listing, it is correct, listing 17 Futuras, 10 Fut Cond and a single Impact. The 17 Futuras includes a couple duplicates from Big Sur in the All Fonts list, so easy to discern. But in my font collections created in Font Book (newly edited, created, etc.), in Affinity apps (but not any other) those font collections show up to 41 styles of Futura, a bunch of Condensed, up to 4 styles for Impact, etc. I can use the Reset Fonts within Affinity and a whole bunch of other things as per the other thread, and it still shows wrong in Affinity apps. And worse, once I open a font "collection" in Affinity apps with the dups, when I go back to the All Fonts view, I now have even more styles!!! Amazing!! Never seen this since the fist Affinity apps, so don't know what's going on. Only started with my switch to the new iMac with Big Sur, coming from Catalina, so thinking it must be related. But I have gone down the path of looking at OS11's built in fonts and isolated that issue. And as I said, none of the other apps that show collections have this issue. Just Affinity apps. And as Jon has said on the other forum, Affinity apps are supposed to be flushing each launch, but they aren't flushing the collections listings. I had really hoped one of us old timers had seen this before and had a quick cure!

@Callum We're working on this over on the Publisher Bugs on MacOS. We've found that the issue is that since my update to OS11, my Affinity apps (1.9.3 and newer betas) are not clearing/renewing the font Collections cache upon loading. Thus, I'm getting multiple duplicates of several fonts including the key font of Futura. As you'll read, I replaced a very old set of Futura font families with a new pair (Futura and Futura Cond), but none of the Affinity apps will clear the old styles and also show numerous duplicates of several of them in the Collections groups of fonts. If you have any ideas on how to fix this issue, sure like to hear them! Very frustrating since I cannot do a lot of client work until I get this resolved since I use the main affected font (Futura) and another problem one (Impact) extensively for several clients. Thus every doc and artwork I open is messed up until I can go through and "fix" the fonts, styles, etc. But with the font menus in Affinity apps showing 2-3 times the right number of styles, pretty tough to be sure I select the right ones to replace and update the files! Very strange issue!

I was having issues with fonts in Big Sur, so tried a Control-Open for Publisher (Affinity Store version) to let the first 3 items reset including prefs. Made a copy of ~/Library/Application Support/Affinity Publisher first. That didn't resolve the fonts problem, so wanted to restore my prefs/presets. etc., so moved the original Affinity Publisher folder back into the App Support folder, replacing the new one. But all my pref setting are gone. Lost my Studio preset, all my regular pref settings, etc. I even tried grabbing a copy from a day ago Time Machine backup, and that didn't bring back the prefs or presets. I even renamed it and restarted Pub to create a new virgin prefs folder, then copied over items from the original one, but still my prefs/presets were gone. Has something changed in Big Sur as far as storing the prefs and presets? I thought everything was in that folder in App Support. The Publisher folder I now have in there has a "presets" folder with what appears to be my Studio preset named com.seriflabs.Studio.Preset.Data2Layout-tab.Basic Startup 1.preset, but it neither is there upon opening nor in the Studio Preset menu. And none of my other presets are there. The assets and keyboard shortcuts seem to be there, however. HELP! How can I get my prefs back so that I can go back to work?? UPDATE: Found there was a com.seriflabs.affinitypublisher.plist in the ~/Library/Preferences. I had been under the impression all was within the Application Support folder, but I assumed wrong!

I did just try to use Reset Fonts in APub prefs, then restarted APub. I modified the "faulty" text style, and tried to reapply that, but it messed up the entire paragraph, then the entire text frame. I then copied all text from the frame, pasted into Text Edit as plain text, then back in APub, created a new text frame, pasted the plain text into that, then applied the main para text style to the first few paragraphs and the edited character style to a sentence within. That worked, thus leading me to believe that the entire existing text frame is "contaminated" or something. That doesn't look good if all our existing docs will need all text reset once I resolve the duplicate fonts issues! 😵

Just upgraded to a new iMac with Big Sur (came from Catalina) and have now opened an existing client APub doc (v1.9.3). I noticed that one of the Text Styles looked wrong. The font used was Futura Light, but it now shows it with a "?" next to Futura (pic attached). Nowadays I simply use Font Book for font management and do have fonts from as far back as the 80s, so a bit of a mess, but it has worked just fine until Big Sur (with minor straightening out along the way over the years). In looking at Font Book, it is showing Futura now has duplicates, and reading further about Big Sur, I understand that they now install a bunch of fonts into the System/Library/Fonts/Supplemental folder that apparently aren't supposed to be disturbed. So I see that I now have those fonts, plus the Library/Fonts and my user ~/Library Fonts folders. In looking at the newer version of Font Book in Big Sur, I see the dialog for duplicate fonts (pic attached). However, I have not used this newer duplicate resolution, so am not 100% sure how to best proceed so as to not mess up my existing Affinity documents. I have to get the client's document finished quickly, so don't want to have to tie up my computer for days trying to sort out this new font issue with Big Sur. And I also found out that if I simply try to change the font within the document, whether by editing the Style or simply changing the font, it destroys the entire paragraph (pic attached) or even the entire text frame. So, I'm hoping that someone who had had to resolve this issue with Big Sur and APub (and other Affinity apps) can guide me on the CORRECT way to get back to business. If I resolve duplicates in Font Book, do I just use the automatic button? Can I simply deactivate the duplicate Futura font set located in the System/Library/Fonts/Supplemental folder and not mess up my existing files? Once I correct for duplicates, what do I need to do within Affinity to get my fonts working again? I do see the Pref for Reset Fonts, but I didn't want to click that until I understand the implications of doing that. I don't want to destroy the typesetting in all my previous Affinity files! We do use Futura a lot, so would have a HUGE impact if I do it wrong! And speaking of Impact, I also see that the Impact font now also has duplicates! And it is also used heavily. Hoping someone can provide me a correct step-by-step to get me back to having the right fonts showing/available. Not worried about sorting out old or corrupt fonts since everything I've been using has worked for as far back as I can remember until I switched to Big Sur, so it appears it is just an issue of resolving duplicates and making sure Affinity documents retain their correct formatting. Thanks in advance! I've read some of the other threads and websites related to OS11 and fonts, but none had a clear resolution to the issue. Thus I thought I would ask the great, experienced Affinity users for guidance in order to get my client's work done ASAP.

This feature is in APhoto 1.9 beta that is pretty close to coming out. They're working out the last few bugs, but you can try it yourself by installing the beta from the beta thread. Installs side-by-side with the release version, so nothing harmed by trying it. I also need this feature VERY badly, so am pleased it is finally here. This is the Mac beta: https://forum.affinity.serif.com/index.php?/forum/19-photo-beta-on-mac/

Thanks for this! I just last week started playing with the new beta and was perplexed on how to work with a merge, even after reading the Help file! Hopefully the release will have much clearer instructions similar to what you've presented!

That would be VERY welcome, and I'm sure by many, many pro users. Been spoiled with so many media production apps that have had that, I think many were surprised when the Affinity suite didn't have it. Let's hope you're right. I'm suspecting that it might be awhile before we see the next betas due to the ongoing situation, especially in the UK. But keep our fingers crossed. It's one of the reasons I didn't feel badly at all about paying an extra $50 for a new copy of Photo to solve my needs, especially given how generous/wise Serif have been about the multiple upgrades this last few years.

DANG!!!!! I had looked at the "normal/old" preferences and saw those, but totally forgot to copy/paste one from either the beta or MAS 1.8.3! But in looking at it right now, and referencing a Time Machine backup of the Prefs folder from before my migration, I do wonder if the workspace is actually stored in that plist file since I already had that file in the Preferences folder that was there from the MAS version. Even with it there, it did not bring in the workspace. I had to create from scratch (one more time, again, and again, and again. 😣). Where it is actually stored seems to still remain a mystery! The workspace thing has always been a real pain and has been a Feature Request for a looooong time. I think there are sooooo many people who want the ability to set up multiple workspaces, plus be able to easily restore a workspace if things get disrupted. And without a clear pref file that can be backed up and restored, to me it remains a very bad "mystery"!

Thanks for your encouragement. Based on your PM, I did the screenshots for virtually everything just in case some things didn't transfer. Was a bit of a pain, but for my needs with Eye Candy, it was well worth it. Was simply getting a little nervous about having to rely on using betas, especially with my intent to soon upgrade from Mojave to Catalina, thus requiring me to use my CS5 PS within a Parallels Sierra virtual volume. That works, but it is slower and has a couple minor bugs that don't help everyday productivity.