Jump to content

BillKress

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Page numbering doesn’t work. It’s an Affinity Publisher bug regardless of what is suggested in this forum. I had a complex 350 page book with many chapters and TOC, and did the following to manually to get around the bug: in Books, top right corner, click on the 3 horizontal lines: Turn off Update Numbers Before Output and make sure the two other items are also unchecked. Another bug is that you cannot uncheck update TOC Before Output. Yet another bug is that these get reset every time you generate a book. That is, unclick everything you can. Consectively, for each of your chapters, use Window -> Section Manager to manually input the correct “Start page numbering at”. If you’re going to add a TOC at the beginning, do this (using Books) and update the associated front matter. My TOC was within the Roman Numeral'd front matter. Check again that the unchecking items noted in #1 above is correct. Create a new Book and add (can drag and drop) chapters. Do not click Update Page Numbering. It’s broken and will mess up your numbering. There are actually a number of bugs I found while generating the PDF necessary to upload to the publisher (which I successfully did). I don’t think Affinity has developers who have ever created a complex book with figures, images, running headings, and non-contiguously developed chapters. While working (now retired) I had written dozens of US Patents using InDesign and hope that A. Publisher will enter that league within a near-future upgrade. Attached is the final, sucessfull Book before PDF output to Publisher. Hope this helps. Bill
  2. Thank you for your reply. Your PDF was informative and useful. You describe a work-around for a bug in A. Publisher. We agree that Page Number Options is a manual method required to properly number the pages of a book. But what is needed is for Book to do this automatically for selected sections. For a more precise description of the bug, look at my first attached screen grab. When I added Section 7, the page numbers were stuck without any way to correct them other than manual Page Number Options. I define that as a bug. The Book application can become more robust. Adding an observation to your PDF page 184-first paragraph. Some books involve multiple writers (collaborators) who contribute content in the form of chapters or sections (groups of chapters). I did this when writing US Patents (using InDesign). It is expected that the resulting Book capability of A. Publisher could evoke continue numbering as needed automatically. Or provide an override for previously numbered pages in that section. Maybe all those Adobe patents inhibit some obvious Affinity refinements? Regards -
  3. For Books, page numbering does not work correctly. “Continue Numbering” is grayed out on Section Manager Panel. Changing numbering by opening individual chapters and forcing works for individual chapters but when the book is constructed, numbering is “corrected” wrongly. That is, Update Page Numbers and Numbers Before Output does not correct the problem. Uploaded file 01-Book with numbering problem between 6 and 7.jpg shows errors 274 -> 271. Nothing corrects this automatically. The only way to “fix” page numbering is within the Books panel, select Page Number Options… and manually correct the numbering. That fixes the numbering, but is tedious. Page numbering is a bug that needs to be addressed. InDesign doesn’t have this problem. Uploaded file 02-Page numbers after manual changes.jpg shows the result of manually correcting page numbers via Page Number Options. Please have your developers generate a complex book with header, footer, many chapters, many photos with captions, and address page numbering, text wrap, page addition and deletion within a chapter, and other details that work in InDesign but don’t work well with A. Publisher. A good learning exercise would be to write a series of A. Publisher users’ manuals, many chapters and compiles with Book. Thanks -
  4. PC: Windows 11/64 Application: Affinity Publisher 2.2.0 also with previous versions of Publisher. When PDF files (attached) is dragged into Publisher, I get the Error message: This file type is not supported. Same error when right click on PDF and Open With Publisher and with Publisher Open -> File -> pdf file Note that the attached PDF files can be opened by the newest Acrobat Reader for PC (2023.006.20320). It cannot be opened by older versions of Acrobat Pro (e.g., 9). Affinity Publisher can open older versions of PDF files. family_tree_magazine_nov-dec-2022.pdf family_tree_magazine_jul-aug-2023.pdf
  5. I have arranged several images on a page to make a montage. Then grouped the image to make one continuous square image. When I select the entire montage and draw a stroke around the entire grouped image, the stroke is around not the entire image but the last image that was grouped. Affinity Publisher bug. _Boot-Camp-Presentation-6-Jun-2022-Slide-31-Affinity-Problem.pdf
  6. Windows 10 Pro, version 1709, OS Build 16299.1029, 16.0 GB RAM, Intel Cor i7-4770 Cannot save new document. Cannot repeat. Had to save it as PDF (this worked) and import the PDF to start again. After one failure, it did not happen again. I tried to start a new document, import text styles as before, but could not get save failure to repeat (sorry). But this was definitely a bug with the new 1.10. Thanks,
  7. Affinity Publisher Bug: The attached FontTest.afpub has 8 different fonts -- both serif and sans serif. When exporting to PDF (Export Settings: PDF (for web), 72 dpi, preview...), and the PDF sent via iTunes to with the iDevice's Books application or Acrobat application, font failure happens. We tested an iPhone 7 and 7+ (OS 12.4) and an older iPad (OS 10.3.4). What happens is that the letters ff, fi and others starting with f will not print using several fonts: Verdana, Arial, Georgia, Times New Roman. All works correctly using Garamond, Calibri, Myriad Pro, Adobe Caslon Pro. (We didn't test additional fonts.) All looks correct when the PDF is viewed on a PC, but not on our iPhones or iPads. FontTest.afpub
×
×
  • Create New...

Important Information

Terms of Use | 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.