T.R | Title | User | Personal Name | Date | Lines |
---|
432.1 | unclear... | VAXUUM::UTT | Mary Utt | Mon Jun 03 1991 17:26 | 35 |
| I find your note almost totally mystifying: you keep referring to
"indexes" and I'm almost you're not trying to document error status
codes in the index of the book...
I extracted your fragment of code and created three <message_section>s,
each preceded by a <head1>. Each <head1> had a TOC entry;
<message_section> does not generate a TOC entry so only the <head1>s
were in the TOC.
When I processed the extracted file using DOCUMENT V2.0, all the
sections were output exactly alike: nothing disappeared for the
first section that appeared in the second and third.
If you click on one of the TOC entries, the topic window shows only
the <head1> text. You must click on Next Topic to see the error
messages. This is a known problem with message and glossary entries.
You can create TOC entries for ranges of <msg>s by specifying
<set_online_topic>(master). See the documentation for this tag. Note
that in your file, you will need to use <delayed> around the
<emphasis> in your <msg> tags:
<msg>(<delayed>(<emphasis>(SNA3270_S_OK,...)))8
If you create a cross reference, you can only do so to the <head1>:
<message_section> and the individual message tags do not take symbol
args and so cannot be referred to.
If none of this sheds any light on your problems, please create
a reasonably small file that exhibits what you describe and send me
a pointer to it.
Thanks,
Mary
|
432.2 | Glossary and the online topic window | DECWET::GETSINGER | Eric Getsinger | Wed Jun 05 1991 14:31 | 13 |
| >>If you click on one of the TOC entries, the topic window shows only
>>the <head1> text. You must click on Next Topic to see the error
>>messages. This is a known problem with message and glossary entries.
Since the problem is known, the solution is not far behind, I hope.
:?)
While we're at it, there is another problem with Glossaries: The
online topic window presents the first term in the glossary. Shouldn't
it just contain 'Glossary?'
Eric
|
432.3 | Another first-entry problem | HEART::ETHOMAS | | Thu Jun 13 1991 09:47 | 44 |
| This issue (topic window and first entry in a glossary) sounds as
though it might be related to a problem I've encountered with
<hotspot_target> tags in a glossary. The first hotspot target
becomes, in Bookreader, the Glossary itself in the topic window,
subsequent ones are popups.
Am I doing something wrong here? I'm guessing about the code, as
<hotspot_target> isn't documented in the user docs, and the
Release Notes (if it _is_ documented there) aren't on Bookreader.
I append a test file that shows the problem. Thanks for any help.
Bob
----------------------------------------------------------------
<FRONT_MATTER>
<TITLE_PAGE>
test
<ENDTITLE_PAGE>
<CONTENTS_FILE>
<ENDFRONT_MATTER>
<CHAPTER>(Text\text)
<P>
I went out to <hotspot>(market_gloss\market) and in my little
<hotspot>(basket_gloss\basket) I <hotspot>(put_gloss\put)...
<GLOSSARY>(Glossary\glossary)
<hotspot_target>(market_gloss)
<GTERM>(Market)
<GDEF>(Place for buying/selling.)
<endhotspot_target>
<hotspot_target>(basket_gloss)
<GTERM>(Basket) <GDEF>(Place for putting things in.)
<endhotspot_target>
<hotspot_target>(Put_gloss)
<GTERM>(Put) <GDEF>(Place)
<endhotspot_target>
<ENDGLOSSARY>
|
432.4 | bug | VAXUUM::UTT | Mary Utt | Wed Jun 19 1991 16:00 | 10 |
| There is an error in the tag definition file. It will be fixed for
the next release of the new toolkit. If you are desperate for a
workaround, let me know by mail and I will send you the corrected
tag definitions.
The tag *is* documented in the release notes.
Thanks for finding this.
Mary
|