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.
Set up a file name convention which maps the GUI language
version, GUI elements, system status or whatever property
may be of interest to an abbreviation used in the file name.
Everyone else working with these screenshots can refer to the
file name convention and easily determin the graphic contents
without having to view it.
The file name convention also allows you to easily find
certain graphics, for instance searching for all offline
english versions (*e*o*.gif).
Example: file name 10emso01.gif
10 = Software version 1.0
e = English
m = Main window
s = Subsystem tab
o = Offline
01 = Graphic 1
can anyone give me a proven and economic method for naming graphic
files (screenshots in this specific case), which will be referenced
in FrameMaker 5.5.2 (in German)? The FrameBook is modularized
merely into TOC, Contents and Index. The Technical Manual will be
translated into 4 languages.
I would like to
- rename as little as possible
- know as immmediately as possible from the file name what the
graphic represents
- have as few problems as possible with graphic file(name)s in
FrameMaker
Here is the situation:
I am describing a software application which runs on a proprietary
OS. The GUI is visualized using screenshots and parts of screenshots
(subaspects of the original screenshots).
For technical reasons
1) I can use merely the program CaptureIt 2.2 for screenshots
2) which numbers the screenshots as *.cap from pict0001.cap upward
3) writing the files to a PCMCIA card (only "disk") in batches of
approximately 50 shots until the card is full (the complete OS of the
computer is on this card!). I then move the files to my work station
and convert them via CAP2GIF to Gif files. The next session again
starts with pict0001.cap.
My first question on this list -- hope I got it right to you.
With best regards and wishes
