Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

  • Last visited

Everything posted by Rabari

  1. I remember having similar troubles back in the day with the early versions of Publisher. Then, what helped my situation was to give the app a generous amount of more memory in the preferences (much more than was installed in the machine). And also limiting the undo amount (I don't need 1024 levels of undo). And of course, to always have linked images as the default, not embedded. That preference is now per document - you'll find it in the Document Setup.
  2. A similar feature is actually available, in Photo. It's called "Channels". If you click the Photo persona icon inside Publisher, you can also use the window to check separations inside Publisher documents. I use it all the time to check that text which is supposed to be K only isn't "rich black". It doesn't concern itself with ink densities however, so if that is important to you, it wont help. I do wish the channels window was available "natively" inside Publisher. It's a bit tedious to jump into different ”personas”.
  3. Running headers a la ID would really be nice. I do anthologies with different writers writing on the same subject, but with different headings. A running header makes it easy for the reader to jump around in the book, or to quickly search it without resorting to the TOC. The correct way to insert running headers is not to divide up your book into sections, but to define running headers on the Master Page, which simply are fields that pick up a style, for instance, "Heading 1” and ”Writer Name”, any time they are used in the layout, and with the possibility to insert desired punctuation in between. The end result, with another Style formatting the running header itself, looks like (I usually put them on the upper part of the page): Rabbe Sandelin – On the subject of Running Headers and a few pages foward Sabbe Randelin – Why We Need Running Headers (and Footnotes)
  4. Opening and viewing the Publisher file in Photo, and using the Channels window actually works! Could we please get a Channels window in Publisher?
  5. Ok, I misread that to keeping a key down when opening the app by clicking the app icon. Doing that with option/alt did however reset something, At least the licence info and the initial starting window (which I usually dismiss with "Don't show this") popped up anew.
  6. Interesting: When I chose "Customize Toolbar" the toolbar suddenly slided in from "above" and "left" of my second monitor. So it WAS there, just off-screen. The solution was to toggle the resolution of the second monitor - this moved the toolbar to my main monitor. Problem solved.
  7. No amount of resetting the app (option key on a Mac), or clearing defaults helps. I downloaded the app from my account and installed it again, but to no avail.
  8. I have the same problem after my update to 1.9.3. Regardless of how many times i uncheck/check "Show Toolbar" in the View menu, the toolbardoes not show up. Same goes for the context toolbar. I use Studio in separated mode, and earlier the toolbar has sometimes been lurking under the massive amount of tool panels on my second monitor - but not this time. The toolbar is truly nowhere to be seen. And resetting Studio did not help.
  9. I do mainly page layout and photo editing/restoration, both at my "real" work place, and for my own small company during evenings and weekends. For my own little company even a monthly InDesign + Photoshop subscription would not make economical sense, as work assignments come and go very unevenly and are not especially higly paid, as I mainly work for non-profits and private persons. Just like many others, I was using the last non-subscription version of CS for as long as it was technically possible. So I was very happy when Photo came along, and when more was promised. The complete conversion to Affinity did not happen overnight. I started with Photo and Designer. When Publisher came along at about the same time Apple released Mac OS versions that would not run 32-bit InDesign anymore, the transition became complete. So far, there have been some hiccups and problems, mainly with the early Publisher versions, and mainly because of slightly different way of app ”concepts". User unrecoverable file corruption. I've stated this in many forum posts: the save files have to be completely rock solid, 100 %, no exceptions. Loosing a few minutes of work because of a crash is nothing, but loosing even a days work (my backups don't run continously, and frequent backups can also become unrecoverable) starts to hurt business reputations. Fortunately Affinitys support has, as far as I've seen, always managed to get corrupted files back into some servicable state. I had one of these cases also, and it was not funny, with customers breathing down my neck. crashes during pdf export (turned out to be greyscale graphic files which for some reason were assigned RGB profiles in Photo) color management inconsistencies: a document set up as "greyscale" exported as RGB. Didn't know I was supposed to set up CMYK documents, to output clean K documents But generally I am very happy, especially with the 1.9 versions of Publisher, which feel more solid. I'm however missing a few things, before I can get rid of my Mojave startup disk with ID CS6: Import of, and support for footnotes Tables that can be inserted into text frames, or at least tables that can span several pages (just like text frames)
  10. I see your point, but I often start Publisher when I already have a several other porgrams running, like Affinty Photo, Affinity Designer, Safari, Mail, Apple Photos and a slew of smaller helper apps. At that point there is no available free physical RAM, according to an app like Memory Diag. What kind of memory does MacOS then allocate, and what kind of memory does Publisher use at that point? And how does the settings in the Performance tab relate to a situation like this? It would be really interesting to hear from the devs about this. No app should of course crash. When I experience crashes i try to pinpoint what I was doing. Evidently the last crashes had something to do with me using a few HEIC images. They import and display fine, but seem to cause trouble in memory tight conditions, and also generate errors when exporting to pdf. In another instance I had to change a greyscale tiff (over 5000 px width, but scaled down, so that the Resource Manager could not even display a value for Placed dpi) to a smaller png. Worked thereafter.
  11. Ok, so I seem to have found at least a partial solution: Just allocate a lot of RAM to Publisher! I have 16 GB physical installed, and I had around 7 GB allocated to Publisher. With everything else the same, I bumped Publishers memory allocation to a generous 18 GB (i.e. far exceeding the physical RAM limit) – and everything seems to run smoothly. Publisher also feels much snappier over all, when moving about in big documents. I must have had some old information in the back of my head, telling me to never allocate more than free available physical RAM (with a couple of other programs running at the same time). But this tip seems dated. Apparently virtual memory, or compressed memory, or some other sort of memory management sees to it that this "crazy" setting works.
  12. With more complex Publisher documents, I sometimes experience crashes just moving about in the document.. I have a feeling that the crashes are related to settings in the Performance section of the Preferences, but I can't find anywhere a FAQ or a comprehensive discussion on what the different choices really mean for the stability and performance of the app. A few questions: In the Display section, which is more stable: Metal, OpenGL, OpenGL (Basic) or Software rendering? I suppose Metal is fastest, or am I wrong? Does clicking "Use only integrated GPU" affect anything, especially as I only have an integrated GPU in my Mac Mini. What Does "integrated" refer to: Intel integrated graphics on the chip, or Integrated, as in "internal" as opposed to an eGPU? What effect has lowering or enlarging the RAM usage limit? Is 6 GB enough for more complex documents? Is it a good idea pushing the limit way over installed physical RAM size (I have 16 GB physical RAM installed)? Shouldn't apps allocate memory dynamically, anyway? Why am supposed to fiddle around with this? Does View quality affect the stablity of the app, since one would assume better quality would be more taxing on many resources? Does hardware acceleration/Metal compute really work in any meaningful way on Intel integrated graphics, with its paltry 1,5 GB RAM, which it allocates from main memory? So many questions, I know.
  13. Setting via Hyphenation option. It's great that Publisher finds it, after I manually, and every time the app is updated, install the hyphenation file in the Application bundle. The problem is not that I can't get hyphenation working. My point is that mucking about in the Application Bundle has never been a recommended activity, and certainly nothing you would instruct inexperienced users to do every time the app is updated. So the shipping version should recognize other places. The user/Library/Spelling folder would be better, even if it resides in the (nowadays) hidden Mac Library folder.
  14. I was asking, as creating a Spelling folder inside my user folder did not work. As did not, eventually, using the Spelling folder in the /user/Library folder. I can get hyphenation working only by installing the hyphenation dictionary directly into the app bundle. Tedious.
  15. I'm using the Mac version. Did you mean /Users/user/Library/Spelling/ I tried this. Did not work, other than Swedish showing up as a language choice for text. Hyphenation only works if the sv-SE folder is inside the application bundle. Contents/Resources/Dictionaries
  16. I made a Swedish hyphenation dictionary from the Open source files at Libre Office, but it's getting tedious to install them in the actual application package every time the beta expires and there's a new version available. Couldn't the language dictionaries be stored somewhere outside the app package? For instance in a /Documents/Affinity/Dictionaries/ folder. I attach the Swedish hyphenation dictionary folder for anyone who wants to use it when trying out Publisher. sv-SE.zip
  17. In my case opening old ID files in Publisher would be somewhat useful only for some select serial publications that i layout, and only to save some time during the initial switch. Back in the day, when i started using ID, it seemed important that it could open old PageMaker files, but the conversion most often required so much cleaning up, that starting from scratch would have been just as easy (or cumbersome, depending). Now I've found that copying text from existing ID projects and pasting it into Publisher brings the styles along. This is more often than not quite sufficient for me, as the design principles of the two programs are somewhat different, and things nevertheless have to be updated and adjusted. I understand that for very complicated files IDML import could be a benefit, but then again, the conversion would probably not be a hundred per cent accurate, so a lot of work would still be necessary. So for me, the lack of IDML import is not a dealbreaker for a first version of Publisher. Transitions are always a bit messy, but keeping two programs around is in my opinion not a problem. I even have an old system 9 installation with PageMaker on an old G4 Mac. I have never, ever actually opened PageMaker since I switched to ID, but hey - just in case… More important will be the ability to open 32-bit ID CS6 in the rare cases it will be necessary in the future. So as MacOs progresses, I'll probably keep the Mojave installation with ID around on a separate disk.
  18. I use a two-monitor setup, and it would be essential for Publisher (and for the other Affinity products too) to have the ability to save my palette layout. At the moment, after an update (or a crash), everything resets, and I have to painstakingly recreate my setup.
  19. The ability to Automatically convert tabbed text to tables would be a real time-saver. (This would also go a long way, before Publisher has a robust word processing file importer. Right now, copying an pasting a table from Word to Publisher results in tabbed text) .
  20. docx is the important format. Crucial for the importer to recognize: any soft formatting (so I can change italic and bold to proper character styles) footnotes and endnotes indexes tables
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.