Endnotes can be helpful for those willing to flip to the extra end pages (or hyperlink over) to read them, but to match them to the change there still needs to be a tag at the change itself.BrianC wrote: I agree it can get ugly. I do report documentation all the time and when I make a report document change. I simply add a line to the change page at the end and say what I changed and when.
If the goal is to help people find what's new since they looked at it last with the minimum overhead for the writer, I've found that using a code consisting of the rev date (11 characters) is the most foolproof and fire-and-forget tag, particularly if more than one person may make revisions. Harder to mix up than revision number schemes and you never have to change the tag. (2008.1106)
Anyway it works, just knowing when a FAQ/errata line was entered tells me whether it's more recent than the last time I copied over to the book.
Cheers,
Mike
