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.
One technical suggestion: while Excel is one of those "least common denominator" programs, it would be more useful to store the information in some form where it would be easy to export the glossary as XML. That would facilitate using it in publications, etc. If it is in Excel and has local formatting (bold, italic, etc.), it will be difficult to get the correctly formatted data out of Excel and into your publishing software. Please let me know if you have any questions or comments. Thank you very much.
Carmen Publishing Inc.
rick -at- frameexpert -dot- com
From: techwr-l-bounces+rick=rickquatro -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+rick=rickquatro -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of wondersofone
Sent: Thursday, August 13, 2015 3:57 PM
To: TECHWR-L Writing
Subject: Business Glossary
Hi All. We currently have terms and definitions scattered within individual policy & procedure docs. The company is looking to create a central glossary to eliminate contradicting definitions.
What is best practice in terms of using and maintaining a glossary like this? May end up as an Excel file.
Should all terms within a P&P doc simply reference the glossary going forward?
And what if there are differences in the definition of a term due to context? We do have different lines of businesses within the company. Just define only using the most common "denominator" in the glossary?
Appreciate any insight.
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW