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.
>A âpublishedâ document is any document that has been through our review process and is approved to be delivered to customers (electronic, print or both). Revisions are incremental updates developed in-house during the review process. For example, someone may do a technical review of revision âCâ, which may then get amended and become revision âDâ. However, no document is used by a customer until it is published.
Oh, I see. Different terminology usage :-). So in my case, Iâm using ârevisionâ to mean an update to a doc thatâs been delivered for a given release. And Iâll be distributing the revision to customers before the next software release is ready (the release number stays the same and the revision will increment). So thatâs why I want the revision number/letter to be in the PDF filename and understandable to end users.
Interesting how it seemed like we were talking about the same thing, but then it turned out we werenât quite.
Thanks for clarifying,
-Monique
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
