Hello all I have for a long time wondered why we distribute "bightml" (the whole manual in one html file). That file is _huge_, 20mb! My Firefox can't even open it, freezes for a while (eating up few hundreds mb of ram, and taking full control over my cpu) and then either crashes or becomes veery sluggish.
I can't imagine why anyone would want the whole docs in a single file.. So, here is my proposal: Get rid of the bightml in its current form and replace it with "whole chapter/reference/articles in one file". Meaning; we would distribute the whole ref.strings reference (including all the refentries) in one file, the whole migration52 in one file, the OOP5 chapter, the tutorial and so on. That should give us ~220files which would be packed together into one archive. Furthermore I would like to do the same with PDF. I don't think we should distribute the whole manual in a single PDF file, but chunking it into chapters/references/articles seem like a good idea to me. How does it sound? Do you know of anyone using the bightml? Keep in mind these changes will not take effect until our new rendering system is "production ready". -Hannes
