TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: PDF filenames - include release designation ? From:Ryan Young <ryangyoung -at- gmail -dot- com> To:Margaret Cekis <margaret -dot- cekis -at- comcast -dot- net> Date:Wed, 28 Oct 2015 18:07:32 -0700
On Wed, Oct 28, 2015 at 5:50 PM, Margaret Cekis <margaret -dot- cekis -at- comcast -dot- net>
> One company where I worked that included documentation in the product's
> of materials used a 32-character code on every document that incorporated
> the product, the software version, the document version, and the release
> date. It wasn't part of the file name, but everything was cross-referenced
> to it, and that number appeared on the title page, and the footers of the
> rest of the document.
This made me remember that we briefly had a process that added the git
commit hash to the title page of PDFs (ie, 3726554c...). You could append
that to the filenames to track exactly what changes are in each document.
(But that might be what you meant by "doc revision designation.")
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com