At 04:44 AM 19/10/2011, Paul Vinkenoog wrote: >Hi Norman, > >> Sorry, I cannot type: >> >> > I'm wondering if this is something we might need to fix. I have had a >> > look in rlsnotes20/install/Compatibility20x.docbook where at least one >> > section has an id="compat-sql" but I can find no cross refernce (or xref >> > tags) to it anywhere. >> That should of course read : >> >> ... >> > section has an id="rnfbtwo-compat" but I can find no cross refernece ... > >Really? ;-)
Can't think of any reason we'd ever want to build release notes all together. However, anyone who has this desire is welcome to do it after my death. ;-) Over the years release notes are a mish-mash of stuff from multiple sources. Things didn't start to come "together" until Paul sorted out the docbook framework during one of the Fb 1.5 sub-release cycles. At that point I spent a lot of time backporting Word and RTF sources into the framework for both Fb 1.5 and Vulcan. (AFAIR, the Vulcan release notes never made it into CVS.) A new mess began with v.2.1, when the notes that were done were a merger of new stuff in 2.1 and the stuff to date in 2.0.x. At that point, there were no Lang Updates so the merger was done to meet demand and the Ref Manual project was being subjected to a lengthy assassination. At that point also, the 2.0.x series was still being treated as an interim step towards the evolving new architectures. There was no expectation that 2.0.x would have six sub-releases and 2.1 would still be alive in 2011! It was further complicated by breaking out the bug fixes and compatibility/migration notes into separate documents. That was done to appease the kit builders who were complaining about the size of the PDF. Since then, it's not so relevant as I have NitroPDF and can shrink PDFs if there are complaints about their size. Furthermore, they took to including the Lang Updates in the kits and *those* are not getting any smaller! The id duplications occur (mostly) because the earlier 2.0 tags are repeated in the 2.1 notes and I gave up trying to catch them eventually. I doubt I ever will now - it's enough trouble and heartache trying to capture and verify content. ;-) Helen ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
