Dmitry wrote: >>> * We have /rlsnotes generated as monohtml while all the rest is >>> multi-file html. Is there any specific reason?
>> Ask Helen :-) > I've also noticed that if the complete book is generated as mono-html, > it lacks index.html which exists when multi-html version is created. But > mono-html doesn't mean single file! For the relnotes, we have a few > resulting html files but without their index. index.html should only appear if you build the entire <set>. And we don't use it (actively). Anything below that - <book>, <article>, whatever - gets the name of the top level id in the file. For monohtml, this means you get one HTML file, e.g. rlsnotes25.html, plus a copy of firebirddocs.css, plus the images folder. It's not single-file, but it is single-page, and every browser can save it to the user's computer in its entirety. The several HTML files you see in the /rlsnotesh folder were each produced separately, at a different time. For multi-page html, the main file again has the name of the top-level id, and all the other files are named after the id of *their* topmost element (usually a level-1 section). E.g., for the 2.5 Quick Start Guide you get: qsg25.html (main file with the index and the introduction) qsg25-firebird-licenses.html qsg25-classic-or-super.html qsg25-kit-contents.html etc. >> Actually, we had plans to add monohtml as a standard output format anyway, >> so readers would have three choices for each document: >> - Multi-page HTML, for online browsing >> - Single-page HTML, for online reading and download >> - PDF/other, for online reading and download > I have no objections, although the demand in the downloadable HTML version is > IMHO over-estimated. I have no idea how many people prefer it to multi-page html. Anyway, I'm in no hurry to implement it as a standard format. It's not even a lot of work, but I happen to think that we have more important things to do! :-) Cheers, Paul ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs