> Message: 3
> Date: Mon, 15 Dec 2003 11:36:12 -0800
> From: "Chris Johnson" <cjohnson at capcollege.bc.ca>
> To: <xmleditor-support at xmlmind.com>
> Subject: Re: [XXE] glossary elements, index elements
>
> Hey Hussein,
>
> Thanks for the tips - I have read the docs, and I have found the Power
> Users guide to be a bit *opaque* ; >
> I will give it another read, as I would like to customize the editor
> more for the content people (the writers) than for myself (web techie).
>
> I have set up a page with sample files and screen shots to show the
> situation I had described:
>
> http://www.capcollege.bc.ca/test/xml-mind/index.xhtml
>
> The screenshots show the steps I went through to open an external
> glossary that is an entity reference in sample-book.xml (step01 and
> step02). I open glossary.xml by clicking on the "Edit Referenced
> Document" icon beside the node bar (step03). I then see the unstyled
> tree view for glossary.xml (step04). I click on a glossentry to
> highlight that element, and then I right-click on the node bar to insert
> another glossentry after it (step05). I then get a glossentry without
> any access to a text node (step06).
>
> The files all validate, and until now (editing glossary), I have been
> very happy with with XML_Mind's DocBook capabilities. I will try the
> customization you have suggested, and I hope I'm just missing something
> basic here...
I think the most important thing you have to do is add "glossary" to the
list of top-level elements which are recognized as DocBook. You can do
this by adding the following line in docbook.xxe:
<rootElementLocalName>glossary</rootElementLocalName>
Add this where all the other <rootElementLocalName>s are defined. This
will give you the styled view for your glossary.xml document.
After that, the other important thing is to customize your <glossdef>
template like Hussein suggested. After that, everything will work as
planned.
HTH, HAND
Bernd
--
"I'm a doctor, I am supposed to tell people where it hurts (so I can
fix it and make money)."
-- Mark S.
