IAmMatt

I'm somewhat baffled by this request. Are people using Publisher as a word processor? Isn't the way to use DTP software to write the text in a dedicated word processor and then typeset it in the DTP software? That would mean it has to be able to gracefully handle import of texts written with citation managers but surely it doesn't need any direct support of them, since they are most useful at the composition stage. I'm fairly certain newspaper reporters didn't used to type their copy directly into a Linotype machine.... This is my complaint with footnotes: I write my texts in Word and if Publisher simply imported footnotes as static text without any linkages, rather than stripping them out completely, that would be fine, at least as a stopgap measure. That's exactly how it handles citations created by citation managers right now (at least for Zotero, which I use) and I think that's perfectly adequate. Of course, if it actually shows field codes for Mendeley then that is unacceptable. In Zotero it is possible to unlink the citation style, so it becomes static text rather than dynamic fields. Maybe that's an option for you, Michel7, before placing into Publisher?

The original question was about creating PDF bookmarks with Publisher. This is possible as of version 1.9: https://affinity.serif.com/en-us/tutorials/publisher/desktop/video/494086515/ Your question seems to be about something completely different, the unexpected behaviour that bookmarks are stripped out of imported PDFs.

If we are in the process of doing kremlinology I am much more excited about this article, which suggests the team are working on book publishing features, something that might or might not involve footnotes but either way is more relevant to me than glossy magazines:

Thanks, I'll keep that in mind. From a quick test I think I can live with 125% at least while using Publisher

PPPS: I have just found out that Windows uses automatic scaling on smaller displays. This is automatically set to 150% and causes this issue. If set to 100% the issue disappears (see screenshot and note the size of every window compared to the previous one). So this issue is caused by the interaction with Windows 10 scaling, not by Publisher itself. I would still like to suggest that the boxes should be resizable. After all that Windows scaling feature is a necessary one on small displays. I found that I couldn't work at 100% scaling, as everything becomes tiny.

PPS: I know that DPT software isn't really supposed to be used on tiny laptop screens but this is the computer my employer issued me and at times I need to do something without having access to bigger screens, especially right now.

Hi, I am usually using Publisher at my office, where I have two large monitors set up. However, since working from home I often find myself using my small work laptop. It has a 14'' screen and I run into a problem every single time I use Publisher on it: When I want to edit a text style by right-clicking on "Edit Text Style" the window/box (unsure about the correct terminology here, please see the attached screenshot) that opens is larger than the upper and lower limits of my screen, cutting off the lower controls, such as "OK", "Cancel", and the "apply style" checkbox behind my Windows taskbar. Ordinarily that would be no problem: I would just resize the box to be slightly smaller and then move it up to reach the bottom buttons. However, Publisher doesn't let me resize this box, there are no handles on the side which make the cursor change into the resize cursor. This way there is no way for me to reach the OK and Cancel button on the bottom. I can move the box down, because I can grab it with the cursor at the upper edge, but I can't move the box up, since my cursor hits the upper edge of the screen and doesn't go further. This is happening both in fullscreen and windowed mode. The screenshot I'm attaching is with the main Publisher application resized into a smaller window, in order to show that the problem exists even then. I have tried setting the windows to floating, this doesn't help. I have not been able to find any other setting that would solve the problem. I can still change text styles this way because pressing Enter is basically the same thing as pressing the hidden "OK" button in the UI but I can't use the "Cancel" or "apply style" functionalities. I can configure my taskbar to automatically hide when not in focus but this is a very tedious workaround. A suggested solution for this would be to simply make these windows/boxes resizable or, if not, to make them slightly smaller by default, so they fit on screens when taking the taskbar into consideration. (This is Publisher 1.9.1.979 run on Windows 10 on a 19'' display at 1920x1080 resolution) PS: despite my complaint here and the one about footnote support I still think Publisher is amazing software. I just wanted the Dev team to know they're doing great work. I'm sure it must be crushing sometimes to only read bug reports and complaints all day.

Again, that is the point I was making: this is completely correct but only for English-language publications.

Thanks everyone for the kind words. I was reading a book yesterday and had to think of what I was saying about German (and other) publishing practices again. This is what it looked like. This isn't a page spread that was carefully chosen for its egregiousness, they literally all look like that in this c. 800 page book. You will see the spread begins with a footnote flowing over from the last page and it ends with the last footnote flowing into the next page. All in all the book has 2385 footnotes (if I counted correctly, since the numbering restarts with every chapter). This is just to underscore what is the normal situation in many writing cultures around the world, something that those in the English-speaking world might not be as aware of, which might lead them to consider footnotes nonessential.

As one of the many people who have come to this thread after having found out in disbelief that this basic functionality is not (yet) supported I actually think your third option would have been the fair thing to do. It doesn't have to be huge red letters but a "Here's what you need to know before purchasing" page that includes a point along the following lines would have been nice: "Please be aware that Affinity Publisher does not currently support footnotes and is therefore not suitable for academic use; however we are working on implementing this functionality and hope to be able to offer it by X (or "in version X")." Honestly, having read through this entire thread I am beginning to think that there are several cultural disconnects here that prevent effective communication between people. One of these disconnects is between professional developers and users, where those that develop software for a living know how complex it is to implement certain things and how unrealistic the timelines and features are that some users request. On the other hand those that write and/or lay out text for a living know how absolutely essential it is to be able to deal with footnotes and cannot understand how this point isn't obvious. Some people here have compared this to selling a car without shocks or without seats. I think a better analogy would be a car without headlights: perfectly functional for a lot of users, who won't even notice anything is missing, but utterly useless to many; and even those that bought the car to only drive during the day might find out sooner or later that they need it at night from time to time. Another disconnect I see is one of nationalities and therefore writing styles. The English-speaking world is a culture of endnotes (even if there will be many in this thread that rightly say they need footnotes to work effectively in English as well), and endnotes, while still a PitA to handle manually, are doable that way. However, many countries' academic and even non-academic writing cultures rely on footnotes a lot more. Earlier in this thread someone cited a Hannah Ahrendt text as an example. I would content that that text is only exceptional because it is an easily accessible translated version of a German text. In reality almost every German academic text looks exactly like that example (as do those of many other cultures, including the French and most of Central Europe), with multiple footnotes that flow to the next page and often with footnotes taking up more than half the page. I think this may explain the frustrations of some users here and the perceived lack of understanding on the part of the developers and marketing team of Serif. I don't have a solution for this problem but I also don't want this thread to die because it is a useful reminder that this is still a pressing problem for many people.