Conference vaxuum::online_bookbuilding

> Access to topics through the Table of Contents worked fine;
> however, an attempt to use the index resulted in a blank
> display of index topics, and also the phrase " - New Output"
> appearing on the FileView "status" line.

What was the error message in the Output window?
(click on the "Show Output" button in the status window)

Did you build the book with the "/INDEX" qualifier and the <index_file> tag?
If so, send me a pointer to the .DECW$BOOK and .LOG files and I'll take
a look.

joe

I know it's not bookbuilding, but:

I've also received the "New Output" message recently, but when trying to 
access the DECwindows Calendar and replace with my personal calendar.  The 
task output window calls my attempt an "improperly handled condition", and 
says "image exit forced", followed by a list of signal arguments, stack 
contents, and "register dump".  'Sounds like a bug, as the procedure worked 
fine with previous versions of the calendar.

Re: < Note 13.1 by STAR::KRAETSCH "NeXt Window Please" >

>What was the error message in the Output window?
>(click on the "Show Output" button in the status window)

Here's what appeared when I clicked on "Show Output":

X error event received from server: integer parameter out of range
  Failed request major op code 1 X_CreateWindow
  Failed request minor op code 0 (if applicable)
  ResourceID 0xffff9ac3 in failed request (if applicable)
  Serial number of failed request 925
  Current serial number in output stream 936
%XLIB-E-ERROREVENT, error event received from server
X error event received from server: not a valid window ID
  Failed request major op code 12 X_ConfigureWindow
  Failed request minor op code 0 (if applicable)
  ResourceID 0x5000ce in failed request (if applicable)
  Serial number of failed request 926
  Current serial number in output stream 979
%XLIB-E-ERROREVENT, error event received from server
X error event received from server: not a valid window ID
  Failed request major op code 12 X_ConfigureWindow
  Failed request minor op code 0 (if applicable)
  ResourceID 0x5000ce in failed request (if applicable)
  Serial number of failed request 1018
  Current serial number in output stream 1048
%XLIB-E-ERROREVENT, error event received from server

>Did you build the book with the "/INDEX" qualifier and the <index_file> tag?

Yes.

>If so, send me a pointer to the .DECW$BOOK and .LOG files and I'll take
>a look.

I'll mail you a pointer to these files.

I don't know if anyone has had a chance to look into this
problem yet. I thought of something that might narrow your
search for the solution, though.

The first time I built the BASIC Reference Manual, I was
unaware that there was a symbol definition file (4773GDF.SDML)
that was used in the bookbuild. Thus, my initial bookbuild
got lots of unresolved symbols; but, if I recall correctly,
I was able to use the index with the Bookreader.

Then I built the book again with /SYMBOLS=4773GDF. The build
failed because of an "improper use of <subhead> tag" [I forget
exact error message] in these two lines:

     <DEFINE_SYMBOL>(EX\<SUBHEAD1>(Example))
     <DEFINE_SYMBOL>(ANSWER\<SUBHEAD1>(Output))

So, I commented out those lines, then globally substituted within
the .SDML files, replacing <reference>(ex) with <subhead1>(Example)
and <reference>(answer) with <subhead1>(Output), and then I built
the book again. This seemed to work perfectly for TOC and index access 
for two BASIC manuals, and it caused no problems for TOC access to 
the reference manual -- the only thing I can't do is index access 
to the reference manual.

In looking at the SDML files for the reference manual, I see a lot
of instances like this:

     <description>(Example)
     <enddescription>
     <subhead1>(Example)
     <code_example>
     LIST 200-300
     <endcode_example>

Could it be that there's some problem having a <subhead1> tag immediately
follow an <enddescription>???

If it's not that, then I remain stumped.

P.S. Was there some change in DOCUMENT that made <subhead1> tags within
symbol definitions illegal (whereas they had been legal before)?

    I can't see any reason why <subheadn> tags wouldn't work online;
    they should work the same as for hardcopy. In fact, I believe I
    have run test files with <subhead> tags in them and had no problems.
    I suggest that you try processing the books for hardcopy and see
    if you get the same results. That would indicate that perhaps, as
    you suggest, something in DOCUMENT has changed or there is some
    other (non-online-related) problem.
    
    Is your reference manual index very large? We have had some problems
    with *very* large indexes exceeding an X limitation. The problem
    has been fixed in DECwindows baselevel 11.

Chuck,

I apologize--I still haven't had a chance to look at your book, but from
the mail you sent me and your descriptions here, it sounds like the problem
is what Mary suggested--that the index is too large for the FT2 bookreader.
(It creates a window larger than the architectural limits of the X window
system).  This problem was fixed with a design change in the BL11 bookreader.

I will try to look at it in the next couple days and verify that this is
indeed the problem you are experiencing.

joe

Re: < Note 13.6 by STAR::KRAETSCH "NeXt Window Please" >
>                           -< is it a large index? >-

I believe it is a large index.  Sorry I can't be any more specific,
though, since I don't have a copy of the book handy.

Thanks for any info or fixes you can provide.

I looked at the book on DECWindows FT2 Update and the index looks fine.
It should also work on Bl11.

joe