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.
Stuart,
thanks for your suggestions.
We do use the Metadata from FrameMaker to display the Document name
rather than the PDF title in the PDFs, It sounds a good idea to add
the version number there too.
The person building the CD and program build is using an automated
process where he replaces a set of existing PDF files with a new set
with the same names, which is automated I think, which is why changing
names causes problems
Maybe your suggestion could work for him, since before we started
making the CDs the PDF file names did change for each version
On 9/6/07, Stuart Burnfield <slb -at- westnet -dot- com -dot- au> wrote:
> Hi Caroline -
>
> I usually do have the product version number in the PDF file name.
>
> Note that you can put a lot of version information in the metadata. If
> you open one of your PDFs in Adobe Reader and select File > Properties
> (or press Ctrl-d), you'll see the Document Properties dialog. On the
> Description tab there are fields for Title, Author, Subject and
> Keywords. A couple of these fields may already have default values.
>
> FrameMaker and AuthorIT (and probably other publishing tools) let you
> set a lot of this information in the source document. >
> Finally, if the person who creates the CD finds it a lot of work, it
> sound like they're manually copying and renaming files.
>
> As long as you are disciplined at naming all the PDFs in a standard,
> predictable way (e.g. <manualname>_<version>.pdf) this should work well
> and will save a lot of time. The build script could be set up so that
> you pass it the version number when invoking it:
>
> buildCD -v2.20
>
> ... and it plugs the version number into the file name when copying each
> PDF.
>
> Let me know if any of this is not clear.
>
> Regards
>
> Stuart
>
>
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-