We would like to store a set of PDF documents in a SharePoint library under major/minor revision control. I understand how the major/minor versioning system in SharePoint works, but our problem is that we would like to match the version with what is stated on the document.
We don't need custom version numbers; we are happy to use Microsoft's scheme. Unfortunately, as I understand it, the draft version that is approved becomes the next major version. So if we upload a series of drafts with "0.1", "0.2", etc. literally printed on the document and then finally approve version "0.4", it will become version 1.0 and say "0.4" on the document.
Perhaps I'm not understanding the process. How do we ensure that the printed rev on the document matches Microsoft's major/minor scheme if the version number of the final approved document changes in the system upon approval?
EDIT - It has been suggested that we simply create a "physical version" column to store the rev level of the physical document. We would like very much to retain the automated assignment of version numbers inherent in SP if possible.