Hi! On Tue, 2017-08-22 at 11:09:37 -0700, Jonathan Nieder wrote: > Sean Whitton wrote: > > On Tue, Aug 22 2017, Guillem Jover wrote: > >> This version has lost the distinction between a single policy html and > >> the one with different files per chapter. This will break links. > > > > This was intentional. The single page output is much more useful to > > casual readers wanting to look something up.
When I want to search for something in an on-line document I also select the single-page document if it's available. Otherwise when I want to navigate the document or read specific parts, I find the multi-page way more pleasant and clear, because each chapter is contained so I know how much there is to finish it, and scrolling or using say the Ini/End key take you to the expected boundaries, and it tends to have a global and intrapage TOCs to go to specific parts. > I don't completely understand. The old rendering had both single page > and multi-page versions. If I understand what you're saying, it is a > reason that the single-page version is useful, but why does that > preclude also providing the multi-page rendering? I guess there are two problems here, one is indeed completely losing the multi-page rendering from the package. The other is the default change in the web site. IMO the best solution, and what is customary, is to present both (or more) rendering and let the user select: [HTML one-page] [HTML multi-page] [PDF] [EPUB] Thanks, Guillem