RE: Implementing a glossary

Subject: RE: Implementing a glossary
From: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 2 Nov 2005 10:44:45 -0500

Way back in March 2001, David McClelland wrote an article showing how to
use Dreamweaver to create an XML-based Glossary Manager. The teaser can
be found at
-- I didn't shell out $17.25 to read the whole article.

> -----Original Message-----
> From: Sean Hower
> Sent: Wednesday, November 02, 2005 10:07 AM
> Subject: re: Implementing a glossary
> > I'm currently compiling a glossary to accompany our next software
> > release. Once we have the content gathered, I need to
> > figure out how
> > to get this information out to the user.
> > 1. There is no user guide.
> > 2. There is a feature guide and a dev guide.
> > 3. The content is context sensitive.
> > 4. Project size.
> This sounds like a job for XML! Because you are dealing with
> context-sensitive content that will be accessed by users who
> are already working online, you should be able to use login
> or other user information to filter an XML-based glossary
> similar to the one that I have on my Web site:
> This uses XML, XSL, JavaScript, and HTML. All definitions are
> located in a single XML file and the JavaScript filters out
> and displays selected definitions based on the glossary you
> click. There are even a handful of "duplicate" terms that
> have different definitions depending on which glossary you're
> viewing. You might consider something similar--filtering on
> the context instead.

This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.


Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here:

Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more.

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.


Previous by Author: RE: Stopping automatic repagination of Word
Next by Author: RE: Exporting Outlook folders
Previous by Thread: re: Implementing a glossary
Next by Thread: Editorial/Press Release - What are some points to consider while writing?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads

Sponsored Ads