Rabari

The topic of this thread is "Please no more new features", so when I said Publisher feels almost feature complete (especially compared to ID), i find the opposition to this statement later in this thread a bit strange. And of course I meant "from my perspective”, as I obviously can't speak for anyone else. So this discussion went from "no more features" to "we want more features!”. Or were lacking features actually considered ”long standing bugs”? I am confused now. Here is my comment to some ”feature requests" mentioned: HTML export from page layout programs will always be a joke compared to real html authoring, and the same goes for e-book export - at least the stuff I used to see from ID. The paradigms ar way to different for there to really be any meaningful overlap,. And if I want to use Acrobat Javascript (I don't), I would use Acrobat.

Not critical to me. E-book could come in handy someday.

I concur that any show-stopping bugs should be prioritised before new features. But with regards to features and speed, Publisher seems about feature complete (and speedy). I'd only like to see a more flexible table tool. For my part, any AI integration can wait, or at least be made optional. I don't want to dismiss anybody's problems, but I have no problem exporting right hand pages (AF-1662), or any arbitary sequence of pages from Publisher. Works with "Current page", or by choosing "All pages", and typing in the page number you want to export. Come to think of it - I can't replicate any show-stopping bugs in Publisher at the moment. Corrupted save files was a huge problem in the beginning, but this seems to have been fixed – the file format seems very robust now. Photo works also for me without problems. I use Designer pretty rarely, so I cant comment on any node problems - they seem very serious and frustrating, and I feel your pain. Is my high confidence in the product due to there being very few alternatives (especially with publishing)? Perhaps? Going back to the main competition is however out of the question. The Affinity suite was a godsend for me an my small company, with a yearly workload of a few, but demanding and technically intricate projects for non-profit clients – which never sustained an app subscription model. With a huge and growing user base I think Serif can pull this one off. And as we really don't now anything, I prefer not too speculate on Serif's developer resources or developer priorities.

I didn't know about the dragging and dropping, thanks! If the topics happen to be similiar sounding and therefore "nearby", it really saves time.

Searched but didn't see this suggested before: I do a lot of name indexing, so a command of "reverse topic indexing" would be great, where I highlight a First name Last name in the text, and the command indexes the name "reversed": Last name, First name with a comma in between. Would save me hours. Speaking of name topics - often the names of persons (especially transliterated names) in a large book are written a bit differently, or people occasionally referred to their nicknames or maiden names. When indexing I don't always notice these connections, so they end up as separate topics, which are laborious to consolidate. Wouldn't it be great if Publisher worked like this: if I give a topic the same topic name as another existing topic in the Index panel, Publisher consolidates the two topics to one topic.

Even more strangely - if I Import the file anew - the index seems to be correct, even though the index marks are after the indexed word… I can now also see all the references when i choose "Show topics and references". These actually weren't there before… Only for the one instance which output correctly. Oh well - just 300 pages…

Turned out the imported word index topic marks ("flags") import after the indexed word. (see pic with E. Nordman exemple) If I move the index mark before the indexed word (like on row 3), this entry outputs correctly from the index panel. Go figure. Now I'm trying to figure out a way to automate this move somehow.

Thanks again for the effort! The imported index shouldn't have page ranges or cross references. Just straight "first level" topics. As I get to work on this project only in my spare time, I'm afraid I haven't had time to try any new approaches or to prepare a sample file. I'll get back as soon as possible

Thanks! I'll try your suggestions and definately will check out your manual! I will also try to figure out a way to make a sample of the file, although I suspect that something in the total index is somehow the biggest part of the problem.

Working on a 300 + page project, with an index originating from the original Word file. Everything looks fairly normal in the layout with a lot of index marks, and an Index panel populated with a fair amount of topics. However, when i click the Insert index button, only one entry appears, and seemingly randomly from the middle of the topic list. There are some potential problems in the index: Many double entries, with the "copy" named the same, but in quotation marks. Many entries begin with a backslash "/" to separate out a different kind of topic - could this be a problem? Some entries were converted to subtopics because a colon ":" somewhere in the topic name had been changed to a forward slash "\" somewhere along the way. Additional question: I cannot find a way to delete a topic, or to merge similiar topics to one topic, by naming them the same way (like in ID).

Sorry for the late answer. What I meant was: At work we have server with different shares. Sometimes I forget to mount all the shares that possibly have som earlier saved Publisher files (could be a file saved a week ago). If this is the case just trying to open the Recents menu hangs the app for a long time, as it searches for the missing shares. When they are mounted, the menu opens just fine, and I can get to the "Clear Menu" option.

It seems the Affinity suite (at least Publisher) tries to locate every file in the Recents menu at startup. This means that if some of the files are off-line, the app appears hanged for a very long time. This should be rectified so that the menu only lists all recent files, but if you try to open a file which has gone off-line, you get an alert to the fact.

I recently took on a 400+ page book project that required sidenotes (notes in the margins, as opposed to footnotes or endnotes). Imagine the relief when I discovered that Publisher V2 does automatic sidenotes (and also converts seamlessly between all three flavours if needed). If I remember correctly the competition only achieves sidenotes with cumbersome anchored frames or other workarounds. Also in the "final nails" category: Running Headers. Big thanks! Also an UI besting of the competition: I always separate out all my panels to my second screen, and in Publisher they remember their position in the Studio setup. If I return to the competition after my screens go to sleep the panel layout is all jumbled up, and has to be manually recreated (choosing the saved panel layout doesn't rectify the situation). Now if only Tables in Publisher could span several pages… If we could insert them I text frames…

Thanks for the effort! As soon as the project has successfully produced a press ready pdf I'll experiment some more. It is really intriguing. Back before I divided up the project in 3 chapters so that what I perceived as the problematic passages would not ruin the whole project, working with the file slowed down after the overlong sidenotes, made text appear randomly, and in the end made the file totally unworkable (ate up all app memory). This was on my old 32 GB Mac Pro 2013, which was used to start the project. The only other anomaly I noticed at the time was that passages containing many diacritic charcters made Scandinavian characters appear wrong - like when you open up a text file with the wrong encoding. The original, placed file was a Word document, saved out as Word format from Apple Pages.

Files provides now. MacOS 13.4.1 R