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.
at the risk of sounding Platonic, unless you have a specific reason you
don't feel good about it, do what you audience does and call it a marching T
or marching R. You can always include a subparagraph that explains it
quickly and simply. why reinvent the wheel?
From: Kathy10th -at- aol -dot- com <Kathy10th -at- aol -dot- com>
>I'm documenting procedures for a certain department. One of the things
>do involves transmitting and receiving batch files. During the
>of the batch file, a "T" slowly moves across the screen. Once it reaches
>right side, it vanishes and reappears on the left to begin moving across
>screen again. This continues until the transmission is complete. The same
>thing happens when you are receiving, only you get an "R" marching across
>screen (cute, huh?). Since the process can take up to 45 minutes, I need
>note it in my document.
>But, what do I call it? Everyone here calls it the "marching T" (or R, as
>the case may be) but I don't feel good about that.