Online groups, summer 2014

Version numbers for documents

A member is updating a software user guide that is for software developers. What is a good method for version numbering to make sure that the differences in the following types of documents are clear? A simple method that will not cause a large 'document history' section in the user guide is necessary.

  1. 'Draft' document versions that only the writer and the customer see.
  2. 'Minor' document versions for changes or new features that represent a new build of the software, but not a new software version.
  3. 'Major' document versions that are related to a new software release. The software does not have a consistent pattern for versions numbers (the release name is more meaningful than the version number).

Members gave many different examples of numbering methods. Also, they gave this general advice:

One member uses the date to show versions because a reader can immediately see if one document is newer than another document.

Members recommended these resources:

PDF file size

A Microsoft Word 2013 file is two A4 pages. Most of the content is text. The document uses only black and one other standard colour. The file size is 57 KB. When the file is saved as a PDF file, the file size of the PDF file is 207 KB.

Is a smaller file size possible for the PDF file? Why is the file size of the PDF file much larger than the file size of the Word file? What software or methods can decrease the file size of the PDF file?

Typically, to decrease the file size of a PDF file, do these things:

In Word, you can specify things such as the compression of images and the fonts that are embedded.

To decrease the file size of a PDF file, members suggested these products:

When I wrote this review, I found 'How to compress a PDF file' on the Adobe TV website (http://tv.adobe.com/watch/acrobat-x-tips-tricks/quick-tip-how-to-compress-a-pdf-file/).

Capitalization

A member will develop documentation and a related style guide for a new product. The member wants advice about the capitalization of product terms. Some examples are "… names of inputs and outputs to the system, such as External inputs, Channel inputs, Direct outputs and Monitoring outputs, and signal processing features, such as Dynamics modules." However, "…capitalising these words within the text will make them jump out at the reader unnecessarily, making the text seem disjointed."

Ideally, use initial uppercase letters only for proper nouns. However, use the same capitalization as the product.

To emphasize terms that are not proper nouns, use one or more of these methods:

Character formatting can become a problem because much time is necessary, specially if you must use character formatting in many documents.

This is a good time to ask users what they like. Ask the product manager to give you permission to contact some users.

|

RSS feed