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.
>Apparently there has been some confusion over where to place
>spaces when they are typing in these commands. Does anyone have any
>ideas on how I can show them where the spaces (and how many) appear in
>each line? Using an underscore won't work, because that is actually
>used for directory names, etc.
Gone are the days when we had to start our statements exactly at column seven,
because columns 1-5 were for the line number and column 6 was the continuation
column. Nowadays, input software can and should allow users broad latitude.
If users are doing something that makes perfect sense to them, the software
ought to make every effort to understand it. It can then translate the input
into whatever rigid internal format the system requires. ...RM
Richard Mateosian <srm -at- cyberpass -dot- net>
Review Editor, IEEE Micro Berkeley, CA
