Jump to content

Dee

Members
  • Content count

    7
  • Joined

  • Last visited

About Dee

  • Rank
    Newbie

Recent Profile Visitors

67 profile views
  1. Okay, I did some digging, and it looks like if there's a hyperlink on Spread 1 that goes to an anchor on spread 5, when you export the pages that include those two spreads, Affinity Publisher doesn't know how to map the anchors to their new page numbers, and so it errors out during export. For now, removing the hyperlinks and anchors fixed the problem for me. But this is something the devs probably ought to look at.
  2. I'm trying to export my afpub document to pages so that I can publish it, but I get an error during the export. The error only appears if I export with the selection "All Pages"; if I select "All Spreads", or even "Current Page", the file exports just fine (but is unusable for my purposes). I saw somewhere someone pointed out a way to get a log file to generate on Windows; is there a similar solution for macOS? Or, ideally, a known solution for this particular issue?
  3. I've used it for three published projects now, with a fourth on the way. It has some limitations, and bugs, but nothing show-stopping yet.
  4. I do layout work for TTRPG (tabletop roleplaying game) designers, and this week I decided to give Affinity Publisher an honest go of it. I took two commissions, and put both of them into Publisher. I'm pleased to say that it mostly went smoothly, but I have a few things that would have made the experience even better. A lot of us in the TTRPG industry are looking at Affinity Publisher as a more manageable alternative to Adobe's subscription model, and we bring with us some very specific needs that would be great to accommodate. I put a thread up on Twitter talking about them, which I'll link at the bottom of this post, but here's the bullet list of things we'd like to see: Impovements to the Place tool when used with text--specifically, we need the styles to map consistently every time a given file is placed--or, more preferably, a menu to appear prompting us to map the styles in the source file to the styles in the Publisher file, with additional options to keep or discard any style changes from the source file. Place tool support for Markdown (.md) files--right now we have to use Pandoc to generate a docx file in order for it to work with Publisher, which adds a layer of complexity that can cause problems. Let us skip that step. Export/Persona for HTML output--this is a big one for me, but web designers could get a lot of mileage out of this application if it could generate HTML code. I've been wanting to create interactive character sheets for games, with trackers and toggles and text fields and menus. Being able to do all of that within Publisher would be awesome, but being able to add those things to the HTML output would be a nice first step. Export/Persona for ePub output--this would be good for generating multiple versions of a document without having to maintain multiple source files. Those are the big-ticket items for me as a TTRPG designer and layout artist for the industry. I know there are others who would also benefit from these things.
  5. Moderators can delete this topic, I re-posted it in the correct section.
  6. (Sorry for the cross-post; I'm realizing this is less of a bug report and more of an ask for help/suggestion for improvement.) I'm importing a .docx file that I generated from a Google Doc, and it doesn't map the body paragraphs to the Body text style, nor the lists to the relevant Bullet List / Numbered List styles that are included in Publisher. Same thing with the headings; it creates new heading styles and assigns the headings to those, instead of using what's already there. Is there a way to make Google Doc or Word use styles that can be recognized, or alternatively is this something in the Affinity dev pipeline that I can expect to see in a future build? This is already leaps and bounds better than before, but if I have to re-update all the styles every time I load in a new draft that's going to seriously slow me down. As an added note, after I updated the imported styles from the docx file, I then imported the same docx file again--and the newly imported text from the same file still didn't respect the styles I had updated.
  7. I'm importing a .docx file that I generated from a Google Doc, and it doesn't map the body paragraphs to the Body text style, nor the lists to the relevant Bullet List / Numbered List styles that are included in Publisher. Same thing with the headings; it creates new heading styles and assigns the headings to those, instead of using what's already there. Is there a way to make Google Doc or Word use styles that can be recognized, or alternatively is this something in the Affinity dev pipeline that I can expect to see in a future build? This is already leaps and bounds better than before, but if I have to re-update all the styles every time I load in a new draft that's going to seriously slow me down. As an added note, after I updated the imported styles from the docx file, I then imported the same docx file again--and the newly imported text from the same file still didn't respect the styles I had updated.
×