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.
Maybe I'm missing something, but if that is how the GUI element
appears, why shouldn't it match? Besides..it's not three periods, it's
an elipsis, which is an actual character
On Wed, Nov 17, 2010 at 3:29 PM, Anon TWer <anon_twer -at- hotmail -dot- com> wrote:
> Editing a manual that says, in part, "To open a new <thing>, click <b>Open... </b>. The UI element is Open... in the software. I changed it to Open (without the three ...) because I thought having three bold periods, then a single unbolded period, looked really dumb.
> Got my redlines back. Nope. Manual has to match the software. If it says Open... in the UI, it has to say Open... in the manual. The ... means that there is another window that displays on the screen and, also, if it was translated - have zero experience with translation - the UI and the manual have to match, or something along those lines.
> How does Open... help the user complete their task?
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-