3darkman

Quoting from a comment from 2019 for publisher v1
this would be great to have in v2 of publisher

This is an old need, since the publisher beta version was released, almost 5 years ago, with 10 pages of comments here on the forum, how long will the affinity team ignore users on this issue?

I created this new topic so that the other one does not continue to be forgotten, since it is in the feedback archives of version 1, but it remains a necessity in version 2.
 
 

Updated for Publisher 2.4 (February 2024)
This free in-depth manual is filled with steps, tips, and recommendations for:
Documents, Pages, Master Pages, Sections, and Baseline Grid Character and Paragraph Formatting Text Styles (paragraph and character) Text Frames, Text Flow, and Stories Images and Picture Frames Books and Chapters Cross-References, Table of Contents, and Index Notes - including Footnotes, Sidenotes, and Endnotes Fields - including Page Numbering, Running Headers, and Custom Variables Anchors and Hyperlinks Printing and Exporting Settings This manual does not cover objects, drawing, photo editing, or the other artistic features.
Download:
Publisher Manual Feb 26 2024.pdf
Q&A
Is this really free? Yes, I'm making it available free of charge. It's copyrighted to prevent others from publishing it as their own. Is there a longer manual I can purchase? No, this is it. Is there an iPad version? No, the steps and screenshots are for the macOS and Windows versions. Is there a version for Designer or Photo? No, but many of the features are the same so you should still find it useful. Why does it use a print layout if it's a PDF? It's a demonstration of how to use the features it describes to create a print book. Previous version for 2.3:
Publisher Manual Nov 29 2023.pdf

This is an old need, since the publisher beta version was released, almost 5 years ago, with 10 pages of comments here on the forum, how long will the affinity team ignore users on this issue?

I created this new topic so that the other one does not continue to be forgotten, since it is in the feedback archives of version 1, but it remains a necessity in version 2.
 
 

This is an old need, since the publisher beta version was released, almost 5 years ago, with 10 pages of comments here on the forum, how long will the affinity team ignore users on this issue?

I created this new topic so that the other one does not continue to be forgotten, since it is in the feedback archives of version 1, but it remains a necessity in version 2.
 
 

This is an old need, since the publisher beta version was released, almost 5 years ago, with 10 pages of comments here on the forum, how long will the affinity team ignore users on this issue?

I created this new topic so that the other one does not continue to be forgotten, since it is in the feedback archives of version 1, but it remains a necessity in version 2.
 
 

This is an old need, since the publisher beta version was released, almost 5 years ago, with 10 pages of comments here on the forum, how long will the affinity team ignore users on this issue?

I created this new topic so that the other one does not continue to be forgotten, since it is in the feedback archives of version 1, but it remains a necessity in version 2.
 
 

if v2 doesn't have that now, at release, we'd better wait and see if it appears in v3.  😞 

By default the publisher separates the subtopics of a topic through the line break, but it would be interesting if we could inform what would be the character of this separation, for example ";" which is what I'm using in a book and I'll need to edit it manually.

Another important point is that it separates the topics/subtopics from the page number with a space, but I would like to add a comma. It allows you to define a specific character, but it always puts that character after a space, it's one more thing I need to change manually.

Just for reference, these two features are available in InDesign.

For your other one, I agree some more flexibility would be nice.
 

I was talking about an automatic field on the master page, in my case, the Section Name, it doesn’t let me select just one character from the automatically generated text.

Hi johs,
 
Just go to the Export Persona, change to the 'Layers' panel and select all the layers in there and click 'Create Slice' and then go to the 'Slices' panel. Notice that you have now create an exportable slice for each layer. You can select each one and choose its export format and properties. Now you can either select 'Export all' or just click each one to export it individually :)
 
Hopefully that's what you're after? :)
Matt

If I understand you correctly you want to take this
Text Example One
and turn it into
TEXT EXAMPLE ONE
I am pretty sure you can do it in Publisher, the GREP is in the Find and Replace section. You should set up a couple of Character Styles for the replacement and search for the Head style plus Caps and then lower-case. So it would be two operations.

Columns in text boxes is good, but option to Span columns, so that a title can span the 2 columns of text it's above, without having to make a separate text box for the title please.

It would be interesting that when importing a docx text, the AP would not create new text styles if the styles with the same names already existed in the document.
Currently, if there is already a style with the same name, it creates a new one added from a sequential, eg title 1

I have posted this before but not in this forum so I am adding to this thread.
 
I am well aware that macros are a work in progress so I shall presume that these remarks may be premature …. but ……
 
It would be hard to make this palette less legible if you tried. It is almost impossible to see when the buttons are pressed or not and other text and icons are on the extreme edge of legibility as well. This really needs looking at. Coloured buttons following the well established universal code of Red/Record, Green/Play, Grey Stop/Pause perhaps?
 
As you make the recorders abilities more sophisticated so will the complexity of the macros grow. A single step replay to help debug problems would be very helpful.
 
And, on the subject of macros, can you please make them assignable to keyboard shortcuts?