Conference vaxuum::online_bookbuilding

    Are you using the CUP/ASG file DOC$SETUP.COM? If so, you can try
    commenting the following line in your LOGIN.COM:
    
    	@DOC$ROOT:[SETUP]DOC$SETUP
    
    Or, try this fix that just appeared (I haven't tested it yet):
    
From:	DICKNS::FRIEDMAN "Marty 223-3446  01-Aug-1989 1444"  1-AUG-1989 14:48:05.06
To:	AITG::SAMEL,AITG::ISEN,AITG::WARNER,UGLEVICH,BENNETT
CC:	
Subj:	fyi doc$setup.com

From:	MARTY::DICKNS::TEDFORD "It's all in the TEXnique.  01-Aug-1989 1351"  1-AUG-1989 14:40:02.03
To:	@CUPASGKIT.DIS
CC:	
Subj:	new cupasg$local_elements.tex available on DICKNS

Hi,

Apparently, CUPASG$LOCAL_ELEMENTS.TEX, as supplied with the
DOCASG012.A that you installed, causes some DOCUMENT jobs to abort with
a "main memory exceeded" message. I have reduced the size of
this file and have been able to build books that I could not
previously build using a variety of doctypes including  CUP_REFERENCE,
ONLINE_HANDBOOK, and REPORT.

The new CUPASG$LOCAL_ELEMENTS.TEX file is available from
DICKNS::DOC$LOCAL_FORMATS.

After replacing DOC$LOCAL_FORMATS:CUPASG$LOCAL_ELEMENTS.TEX,
your users  should be able to restore the execution of the command
file, DOC$ROOT:[SETUP]DOC$SETUP.COM to their login.com files.

Bob

    

    If the advice in .1 does not apply, please send me rbsds_sbg_index.tex
    file. What version of DOCUMENT and the online tools are you running?
    
    Thanks,
    
    Mary

The following text contains extracts of MAIL that led to the resolution
of the problem ('till the next version of ONLINE tools don't use <EMPHASIS>
in index entries [as arguments to <X> <Y> <XAPPEND> etc.tags]).

**************************
Mary
***********
The problem is the italics in the <xappend> arguments to some of your
index entries. When I remove them, the index tex file processes fine. I will
look at the tag defs to see why this is happening and fix it, but the fix
won't be available til the next version of the online tools. Meanwhile,
to get your book to build for  online, you could remove the italics
(<emphasis> tag) from the index entries.

**************************
John
***********
That's fixed it thanks. I saw the note about the same sort of problem with the
glossary and used the <DELAYED> tag to see if that would fix it - but it didn't
work so I thought it must be something else!


**************************
Mary
***********
No, <delayed> would not help in this case.

What happens is, I pick up that append string and use a tex \special control
sequence to pass it to the converter (I don't really need that info but it
comes with the page number, which I do need, so I don't have any choice in the
matter, unless I figure out how to parse tex arguments, which I've never been
able to do).

For reasons that are unclear to me, TeX really goes bonkers
(as you have witnessed) when it's told to do a font change in a
\special. But since I don't want a font change there anyway, the solution
is to turn off bolding and italics in the tag defs, or turn off the append
string which I can't use anyway - given the way we currently do indexing
in both DOCUMENT nad the Bookreader. (We've talked about making changes
that would allow append strings but it would take changes to the indexer
at least.)

Mary
                                                                      

 One slight correction to .3: <emphasis> tags are OK in the index entry
    itself, just not in the <xappend> string.

    You can say:

    <X>(Index <emphasis>(entry))

    But NOT:

    <X>(Index entry\<XAPPEND>(<EMPHASIS>(whatever))

    Mary