Wow, that is indeed neat.  I've been needing the functionality but I had never 
figured it out smoothly.  However, I wonder how this will process... for 
instance, are the "glossary terms" xincludes going to have different output 
formatting than the text around them.  Also, can I put these anywhere in a 
valid document?  

If I understand correctly, I must make a different glossary file for every set 
of text changes that I want.  Then, before I render any output docbook, I 
change the file name of the glossary to be used before opening the xml files 
for formatting.

Is that the correct way to use them?

Thanks for sharing this.  I guess it is time for me to relook at xincludes.

Sincerely,
Shawn Giese


-----Original Message-----
From: [email protected]
[mailto:xmleditor-support-request at xmlmind.com]
Sent: Monday, June 27, 2005 12:00 PM
To: xmleditor-support at xmlmind.com
Subject: XMLeditor-Support Digest, Vol 16, Issue 21


Send XMLeditor-Support mailing list submissions to
        xmleditor-support at xmlmind.com

To subscribe or unsubscribe via the World Wide Web, visit
        http://www.xmlmind.com/mailman/listinfo/xmleditor-support
or, via email, send a message with subject or body 'help' to
        xmleditor-support-request at xmlmind.com

You can reach the person managing the list at
        xmleditor-support-owner at xmlmind.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of XMLeditor-Support digest..."


Today's Topics:

   1. Plugin for handling "variables" (entities) (Claus Rasmussen)
   2. Ooops :o) (Claus Rasmussen)


----------------------------------------------------------------------

Message: 1
Date: Sun, 26 Jun 2005 22:42:12 +0200 (CEST)
From: "Claus Rasmussen" <[email protected]>
Subject: [XXE] Plugin for handling "variables" (entities)
To: xmleditor-support at xmlmind.com
Message-ID: <24224.212.242.203.92.1119818532.squirrel at techwriter.dk>
Content-Type: text/plain;charset=iso-8859-1

Hi folks,

Though it was never intended for public use, the recurring discussions about
entities and the use of "variables" for things like product names, company
names etc. has inspired me to publish a plugin for XXE I've been using to
solve this problem.

The plugin works for DocBook documents only and lets you point to a file
containing a <glossary>. You can then select each <glossterm> from a list in
a dialog, and the one you select will be included using the Include command
in XXE. This is a very non-intrusive way of getting the "power" you used to
get from using plain entities while using the slicker XInclude approach.

I could go on all night about how this isn't really ready for public use,
but to cut it short: The plugin has only been used by me on a single Windows
machine and is not tested or polished in any way, so use it at your own
risk.

That being said, it has proven a huge productivity booster for me.

You can get it here: http://techwriter.dk/tools/xxe/glosstool.html

If enough people show interest, I might be able to find some time to polish
it up a bit and weed out any bugs that show up.

/claus

PS: Hussein, I hold a professional license for XXE, but I assume that a
plugin like this can be used by standard users as well without violating the
license terms?


-- 
Technical Communicator
Web: http://techwriter.dk/
Phone: (+45) 262 000 94
Email: claus at techwriter.dk


------------------------------

Message: 2
Date: Sun, 26 Jun 2005 23:11:01 +0200 (CEST)
From: "Claus Rasmussen" <[email protected]>
Subject: [XXE] Ooops :o)
To: xmleditor-support at xmlmind.com
Message-ID: <24316.212.242.203.92.1119820261.squirrel at techwriter.dk>
Content-Type: text/plain;charset=iso-8859-1

First bug report already: Forgot to say that you need v2.10 for the plugin
to work.

-claus


-- 
Technical Communicator
Web: http://techwriter.dk/
Phone: (+45) 262 000 94
Email: claus at techwriter.dk


------------------------------

 
--
XMLmind XML Editor Support List
xmleditor-support at xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

End of XMLeditor-Support Digest, Vol 16, Issue 21
*************************************************



Reply via email to