patrickfoster

Thanks to everyone who put some thought into this; I'll be testing these out for my work and will let you guys know which one worked out. Thanks again!

Thanks to everyone who put some thought into this; I'll be testing these out for my work and will let you guys know which one worked out. Thanks again!

Thats not accurate in my experience; working with individual files for chapters makes managing books much easier. 

Working on a book, 30.1MB, text only. A few limited embedded vector files. Worked great til yesterday, now Publisher crashes on an attempt to save. 

Anyone have any ideas?

With iOS 13.4 that is coming out on 23rd of March iPads will get full mouse and trackpad support. How is Designer looking with keyboard support and can we expect mouse and trackpad support soon?

Thats not accurate in my experience; working with individual files for chapters makes managing books much easier. 

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

A lot of work needs doing, for sure, at least from our perspectives as users. That said, I've been using Publisher to build out novels for a client since its release this past summer, and while there are some extra steps, it's more than made up for by not having to pay Adobe every month. 

Would I like Publisher to do more of the stuff I want it to do? Surely. Will I manage until it does (or if it never does)? Absolutely.

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

Have been hanging on using InDesign CS6 waiting for Publisher. Very excited by the beta process and purchased Publisher on day one.
Have completed several small projects successfully in Publisher but without an indb-style function in Publisher,  InDesign has to remain our prime publishing software. Would be good to know if this function is/will not be part of Publisher. If it will be we can hang on a while longer. If not, we need to (holding nose) go to Adobe CC. Even a vague indication would be helpful.

Hi—

Mac OS, 10.14.5. 2015 MacBook Air, 2.2Ghz Core I7, 8GB ram, 256GB storage.
Initial failure was trying to save  30.1 MB afpub file; 99.5% text with some small vector embeds. Was working fine, until it suddenly wasn't. All saves to my internal SSD, no external saving. 

Pasting crash was from trying to move a text box from the original document to a new, smaller afpub file (ended up recreating the book as individual chapter files, rather than one long one.)

Also, had three random crashes yesterday, from no discernible action, when using smaller files. The only pattern was that I had two afpub files open at each time it crashed.

Thanks for the help.

pf

Working on a book, 30.1MB, text only. A few limited embedded vector files. Worked great til yesterday, now Publisher crashes on an attempt to save. 

Anyone have any ideas?

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

I have to get that on a persistent clipboard here. [smiley-face emoticon]
I do like that idea of moving sections but I honestly don't know how it could be implemented without messing up its current usefulness. We need some sort of Book/Chapter divisions and I do hope that comes along. 
Import an .afpub file "As Chapter, converting page number markings and section numbering"  then just place it in the middle or at the end or replace a marked/selelcted set of pages. It would be great. 

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

Somewhere (I'm trying to ascertain where) there is a roadmap from Affinity that mentions when a Create Book feature will be coming. Would hope this very critical feature would be at the top of the list. Even building a 150-200 page book benefits when individual files built on the same document setup can be worked on then combined. Sadly, my old copy of InDesign CS 5.5 will still need to be used. At the same time, I'm learning all I can with Publisher. Wasn't involved in the beta process, so I'm excited to have this new software in my arsenal. Thank you Serif Affinity and someday soon goodbye Adobe.

The ease of re-purposing sections (chapters) for multiple custom books is advantageous for us. So maintaining split chapters as individual files is highly desired.
 

I find that making each chapter a separate file prevents a lot of confusion. For example, scanning through 150-200 pages at a preferred viewing size (big) can be tedious.
All the "Book" utility in InDesign does for me--aside from allowing focus on one chapter at a time--is keep track of page numbering across chapter files, as well as some TOC and index stuff. It would be nice if Publisher had something similar.

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

Not at all;  and I couldn’t agree more. Anything that gets us all to the tools we need is fine with me. 

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it. 

The InDesign feature I use most—weirdly—is the INDB book feature, where InDesign creates a container file of sorts to hold a pile of individual InD files that make up an entire book, as well as manage their page numbers. Being able to manage chapters individually is vastly easier than working on a 300+ page single file. Would love to see this implemented—or something like it.