3darkman

I came here to join the requests for this functionality.

I loved the new separator specifications to improve the index format, unfortunately they still don't suit me completely, so I'll leave two suggestions for new separators: separator between subtopics, as today a line break is always used. separator between the topic and its subtopics, as today a line break is also always used. also an option to choose the position of cross-references, which by default are coming before the subtopics, but I would like them to come after.

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. 😞

OMG!!! I hadn't noticed that there were two spaces in the separator field. Your answer made me check it again and I finally noticed the spaces. tks!!! Really what i needed now was just that i could change the line break between subtopics.

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.

Hello, Today I am facing the same bug. I reopened a project from last year to continue it, when I expand the body style hierarchy, the app freezes and its memory usage constantly goes up in the task manager (from 1gb of use, it has changed to 8gb). I was going to try to attach the memory dump, but it was 6gb in size. Update: if I uncheck "show samples" before clicking on the hierarchy it doesn't freeze, even if I enable this option later. But if i expand another hierarchy, it freezes again.

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.

I really don't understand why something so requested is neglected. Be it the column span or put the definition of columns in the paragraph itself and not in the text frame.

+1 for GREP styles! This was something I asked for in the forum as soon as aPub was launched, but from what I see so far we still don't have the functionality, it's the main reason I haven't used it until now. I tried again to use it and again I stop because of an obstacle with grep styles, this time that cannot be solved with find replace. Various paragraph styles that I use in some books, need the first letter of each word to be of a larger size. Including texts defined as a field on the master page, which we cannot change individually. The only solution i see for this, is instead of using the automatic fields, having to manually type in each page and change the text style with a find / replace. Something totally unviable for books of 100 to 300 pages.

Although I really like the Affinity application suite, this problem occurs with all of their applications (Publisher, Design e Photo) on all of my machines, since the beta, and has never been resolved. Today I finally discovered a simple workaround that solves the problem on demand. This problem only occurs if you open the application without any documents. if you open a document, be it an image to be edited in it, an .afphoto file through windows explorer (or through the start menu), the program will be able to open without closing.

humm .... I got it, it does not get to be something automatic like the GREP Style linked to the paragraph style, but it is already better than doing everything manual, thank you.

Hello, I've been working with some diagramming in which the formatting rule for some headers and in the table of content works as follows: 1 - adds a character style to all uppercase letters in the text 2 - puts all the letters of the text in uppercase. In the ID I would use the GREP Style to do item 1, but I noticed that in aPub does not have this functionality, so what would be the recommended way? doing it manually is really impractical.

+1 to request column spanning.

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