PaoloT

Exporting DOCX files would help this situation as there would be no need to copy them.

v.2.4.0.2256
Hello everyone.
There is currently a gap in the process of copying text from Affinity Publisher into Word. Footnotes are not automatically transferred, forcing users to manually take them from Affinity Publisher and insert them one by one into Word.
This can be a time-consuming, tedious and error-prone task. For example, it took me around 2 hours for 110 notes, or roughly 1 to 2 minutes per footnote. Automating it will be a great help to anyone who has to resend a Word version in addition to the PDF to those who have (obviously) reworked it in Affinity Publisher.

Affinity Publisher 2.3.1 Windows 10 22H2 19045.3930 With pad/merge AP will attempt to add/merge pages to maintain correct left/right page layout between chapters (or at least that's what it appears to do).
One would expect that when AP adds a page that the new page would have the first master page from the selected style source chapter applied to it. But this does not happen. To the contrary, a completely blank page is inserted to pad which really just ruins the layout of any particular book rendering the Book feature a non-feature.
The tool should at a minimum apply the first master page found in the style source chapter to the new page inserted to accomplish the padding.
A better option would be to allow selecting which master page should be applied from the style source chapter.
This seems to be a basic oversight on the part of the feature planning department. Its hard to imagine actually being able to use the Book feature in its current state to go directly to a published book.
PS. I have read the several threads in the other forums regarding a number of issues with the Book tool. This one fix would seem to address several of the symptoms described in those threads.
 

While you may like it, there are several places in the UI where there are known issues with icons either not showing at all or showing with so little contrast between them & the background that that are effectively invisible.
There also have been numerous user complaints, starting with the very first release of AD for Macs before there were even any Windows versions, about low contrast in various places in the UI making it difficult to tell if something is selected, deselected, grayed out, etc.

Like we can customize tools and toolbar I would like to have an option to customize the context toolbar. There are some icons I would like to rearrange, like bringing the leading icon next to the font size icon, etc.

Lack of scalability and generally poor UI (contrast in particular) are starting to take their toll on Serif @Patrick Connor
Patric one rhetorical question: Have any lessons been learned from the many complaints about UI?

PDF is obviously better for sending to clients/printers etc than the Affinity native format, but it's pretty useless if you need to save the file to continue working on the project, or to keep to edit or reuse later! As such (IMHO) the best default format to save files is the Affinity native format, then export as PDF (or, depending on the project,) another common file format, when sending to clients etc.

Hi @mogsie,
The two files exported from Publisher use a Greyscale D50 colour profile, and the one exported from Adobe Pro 9 uses a CMYK Uncoated FOGRA29 colour profile.
Your source Publisher file uses a U.S. Web Coated (SWOP) v2 colour profile which as @Old Bruce mentions uses text that is CMYK mix rather than K100.
If the intent is to provide a CMYK file with K100 text using a U.S. Web Coated (SWOP) v2 colour profile then you need to change the text so it is K100 and then export using the same profile.
If the intent is to provide a Greyscale file with K100 text then change the Colour Profile of your Publisher document to Greyscale D50, then change your text to Grey 0 and export using the same profile.

K100.mp4

Hi - I need to be able to find files by searching for text within the file (see forum thread 'Searching for a document containing specific text')   On this thread 'Oufti' suggests 'Affinity should provide a Spotlight importer plugin, a small piece of software that could interpret the content of these files and report it to the macOS search engine'  - and 'Bures' suggests   'Can you add an option to applications to "Save indexable text with the file", after which the application would traverse all text fields and other specified text and save it to a file.'  I've copied their comments because they know the tech lingo better than I do!

Hi, I want to export multiples layers into png. I watch tutorial about how to slice and exports layers. However, my results does not show the same as the tutorial. Only one or two layers can be exported with the "png" extension, the other does not have the extension. Is there any setting I have to set to be able to export the sliced layers correctly?

Here is the file after exported. Only two are correct. The other has not extension.
I use Affinity 2.4 beta version.

Most similar software uses it's own native file format, just like Affinity does!
It doesn't really matter if you call it "Save" or "Export". Affinity files have very few options, so can be saved without needing to change settings. On the other hand, there are many varieties and options for PDF files, so you need to open a dialogue box to make sure you are using the correct settings.
It's also worth remembering that an Affinity file can easily be reopened and then "saved" as a PDF. It is not possible to reopen a PDF file in Affinity and regain all the original features and settings.
 

Ah, please read what I wrote once more. I fully answered the question from the perspective that in every aspect, it is difficult, impractical, and virtually impossible, regardless of one's preferences. On that basis, Serif cannot accommodate the way customers work. Not with PDF.

To receive a different answer may require a different question to be asked.
You made a suggestion and received fair minded explanations of why that suggestion may not be very sensible.
That is a bold and very probably inaccurate assumption. I am often very supportive of feature requests, but I cannot support this one.

What Miketo states is that it is neither technically feasible, practically sensible, nor at all meaningful from any perspective to use PDF as a native file format in Affinity. And he is absolutely right.

Hi, PDF is a file intended for document distribution, not for saving, and doesn't support the full feature set of Designer. You would lose so much. This is the same reason that Adobe Illustrator doesn't save in PDF, users would lose so much when re-opening their files.
For example, PDF doesn't support text styles, so all paragraph and character styles would be lost. PDF doesn't support text frames, so every line of text would be separate. Design does attempt to join lines of text into paragraphs and put them in frames but this isn't perfect.

Hi @Storyteller58, yes, Publisher can definitely handle that. I'm slowly writing a long history book with several hundred pages and several hundred images and Publisher handles it without any issues. And I'm creating it as a single document and not as a "Book" made up of separate "Chapter files". While the Book feature is great, it adds complexity and I'd prefer to avoid that if the app can handle it which it does. But if you do take the Book approach, Publisher will handle the indexing for you. There are some limitations of the Book feature though so I suggest reading the Book chapter of the free manual I've written for Publisher - it's available as a PDF download from my signature below. And it's an example of a book written in Publisher as a single file.
There's an expanded version of the manual coming for 2.4 so when that's released return to the forum to download the updated manual.
Cheers
 

Until the end of January (so hurry if you want it!!!) the ON1 Effects app & its plugin (which works with AP) are free. It includes a variety of color film presets you could use to simulate various Agfa, Fujifilm, Kodak, & several other film looks.
The UI is weird enough that it may take quite a while to figure out how to do things with it but there are tons of videos to help with that.

Look into the forum Resources section after "film LUTs" or search the forum after those etc.
... and so on ...

They could also provide a QuickLook plugin that would enable better previews, but they don't. Sadly, I've come to accept that Affinity files are simply blackboxes that are largely invisible to the operating system, which then requires the user (ahem, me) to add 'metadata/files' (such as the Word doc that was imported, Finder metadata, readme files, preview.jpgs/pdfs, etc) around the files in hope of making them a little less… obscure obtuse.

HI Everyone, 
I am a bit of a newbie to the affinity suit so please forgive me if this is an obvious question.
I have a LOT of image frames in a large family history book I am working on, and I am concerned that if I need to make changes to styling of these frames, I am going to have to go through the entire book and adjust them one at a time.
I was looking for something like text styles where I could centrally manage a particular style for frames, but so far haven't found anything. 
Maybe I should be trying to do this through master pages in some way?... the trouble is I just want it applied to a particular set of image frames within a page.
Any suggestions?
-Sheldon  

In professional contexts, it's now well recognised in my experience. There are several things to use it for, but the really positive thing about slug area is the simplicity and that the information reaches the right people in the right place at the right time. When the printer receives the file, they have all relevant instructions and information immediately available on the document itself, streamlining the process and reducing the risk of misunderstandings or errors.
When you collaborate with others on a regular basis and learn to include information you know they'll ask for, you're more likely to leave work on time, whistling and happy.

It depends. If the page layout document is something like a narrative book or a manual, and not something like a brochure, the structure is the same: an uninterrupted flow of text and images going from start to end.
One may want to export a Word file from Publisher for several different reasons:
- reusing the text for different types of document (advertising, video script…)
- converting the project to an eBook via an external tool (Apple Pages, for example, is excellent, and can read Word files very well)
- reusing the material for a web site
- proofreading the text by removing all the distracting graphic elements
Exporting to PDF is the worst way of doing it, since the desired structure (based on the style sheet) is not preserved.
Some of us, in particular Publisher users, are not dealing with graphic-prevelent documents, but with text-prevalent ones. Hence the need for exchanging file formats dealing with text and structure.
Paolo
 

Only, I want to go into the opposite direction: Publisher —> Word!
Paolo
 

It is definitely a useful feature (and sometimes an essential one) in a professional page layout app and especially in complex multi-editor workflows, even if only supported at RTF level. In certain situations it can even be used as an exchange tool e.g. to give an RTF file for revisions and then import it back, keeping practically most if not all formatting changes already made in the layout, or even just to indicate changes made in the layout between two time points (often much more useful than a PDF comparison, which on the other hand can show the exact locations of changes in the layout).

I have seen a bunch of requests for DOCX export so hopefully we will get it soon. It will be very helpful for me so patiently waiting for it.