From: east coast, usa
why not fix the manual so it's clear.
We talked about his last month and it generated little response, so I'll re-post what I said here. I'll also clarify that this is something that we the community should do, not something we should expect the developers to do [they maintain a What's New file].
We need to make a new PDF, copy and paste relevant passages from the original manual, add in new rules, add in clarifications, keep the manual graphics where appropriate, eliminate fluff and repetitions where possible. It wouldn't be officially distributed by Matrix [but would need their consent due to use of original parts of the manual and consent from Bob for use of his What's New], that way it wouldn't be necessary for Bob to proof read every passage [he can if he wants and it would be nice, but we don't want to go into anything expecting it]. Someone would need to maintain it, most likely on a thread here. Everyone could suggest clarifications/additions and obviously we would have no problem reaching a consensus on all matters
So, somebody with PDF talents start a thread and let's get to it !