Conference tnpubs::nacleaf

    I am having some problems getting the critter started. A command
    procedure is called in to setup the environment. The procedure, copied
    to the desktop, checks the group logical name tables and tries to
    update same. Few users will hav grpnam priv. 
    
    Will talk with Interleaf to get some clarification on how to handle
    this.

The Interleaf->Bookreader still has some problems that have kept me from putting
the testing into place. I hope to have a more cooperative package next week.

    I just converted a document that contains a Symbol_B right arrow (it's
    on the ' key).  In the bookreader file it shows up as a double quote
    (") character.

    The topic window (where the text is displayed) is about half as wide as
    my document, so I have to use the horizontal scroll bar to read the
    right side of the page.  The window should open up wide enough for the
    entire width of the page.

A document that originally failed with the "failed to make chunk" error
was successfully converted after I purged masters for which the document
had no instances (see Interleaf Basics vol 1, page 27).

Courier 9 and Times 10 italic in my Interleaf document is showing up
as sans-serif 12 bold in bookreader.

The contents of a full-page underlay frame in my Interleaf document
do not show up under Bookreader.

    My original Interleaf document used 14 pt Helvetica for Topics and 12
    pt Helvetiva for para.  When converted to bookreader, the document had
    the following problems:
    	1. Bullets came out as w's
    	2. Italics (all my book titles) came out as bold text
    	3. The para text came out bold, while text in the bulleted lists
    	was ok
    	4. Line endings were poor -- for example DECnet/OSI was split after
	the slash
    	5.  In the bulleted lists, the top of characters in the first line
    	of a list item was missing.  It looks like the rules between the
    	list items are overwriting the following line of text.
    	 
     

    Looks like point size is significant in conversion of special
    characters.  My Symbol_B 12 pt bullets came out OK, but the same bullet
    in 10 pt came out as a "w".

    I converted a sample document with level 1 and level 2 heads.  On one
    page there was one level 1 and two level 2 heads.  They came out all
    right, but there were two blank pages before that page.  (There were no
    blank lines in the TOC.)

    I converted a sample document with index hits.  The sort sequence used
    by the conveter differs from the Interleaf index generator, and is
    wrong.  I got sequential entries in this order:
    
    	OSI
    	entity

If the user has defined a symbol for delete, such as the following;

$ DELETE :== $ DELETE/CONFIRM

then the converter will use that value for delete. This may cause batch 
processing to fail and will certainly be annoying when the procedure cleans up
its dozens of workfiles.

The fix would be to have the converter set a local copy of DELETE within the
context of the procedure. 

This may apply to other symbols as well. 

    Karl, is DELETE/LOG OK?  My DELETE is so defined.  (Well, I guess it
    must be; it has worked.)
    
    I tried and failed to convert a file.  The first time, the generator
    created 249 work files totalling 6,747 block and crapped out, leaving
    the files behind.  (I don't know how large the input file was.)
    
    I shortened the input file to 385 blocks.  The second time, the
    converter created 330 work files totalling 5,382 blocks and crapped
    out, leaving the files behind.
    
    I notice from watching the output that the converter seems to be
    loading the input file at least five times.  I am not impressed by
    that.

    Delete/log is ok. It will simply display the results of each delete
    command. (Your batch log files or interactive screen may get noisy on a
    very large book.) I have my delete defined as delete/log.
    
    Re: files not processing. Yes, a tremendous number of workfiles are
    created. Can you capture one of those processing sessions or post a
    batch log file so we have something to show John Clemens?

    The PL2IMG portion of the converter has been working on chapter 2
    of _DECmcc Introduction_ for 70 hours now.  MONITOR shows that the
    process is still alive.  The document contains a scanned-in image.
    
    I have copied the document to
    I2B_DISK:[VIEW40.trouble_files]SCANNED_IMAGE_PL2IMG.DOC;1

    re: .7
    
    Underlay frame problem file is in 
    I2B_DISK:[VIEW40.TROUBLE_FILES]UNDERLAY_FRAME_BUG.DOC;1

    After I run the converter, I cannot start up Interleaf again from a
    Session Manager menu the first time.  I have to select it twice.

    I have left a troublesome file in [VIEW40.TROUBLE_FILES].

    One of my files produced the following message:

    Warning! Badly formatted invocation option Chap3_p6.img
    CLIP-F-NOSUCHFILE, unable to open Chap3_p6.img

    I opened Chap3_p6.img in Interleaf and the only thing the file
    contained was a carriage return keytop figure (represented as RET with
    a box around it).

    I removed all of the keytops in the original file and the converter worked 
    the second time.
                     

    I have cobbled together a test document containing a little of
    everything we do in DECmcc.  (The log file of the conversion is posted
    as Note 47.20, ad nauseum.)  This file contains one complex table, one
    complex drawn object, one scanned-in bitmap, and an index.
    
    The complex table is badly formatted, probably because of the font
    mapping.  The lines run past the right margin and the leading is
    inadequate.  The table has two columns, but the left column is not
    reproduced at all.
    
    The complex drawn object is good, but text extending past the right
    margin is truncated.  I didn't realize there *was* any text past the
    margin; perhaps it's being scaled somehow.
    
    The bitmap seems fine.  As the author of the chapter Mike Quinn
    described earlier, I suspect it's not the type of image but the number
    of images the converter is choking on.
    
    The index works to two levels, but I note hyphens are being reproduced
    as "x1e," viz::
    
    	Circuit Onx1eStarting
    
    I plan to use this as a test suite document.  I shall be very pleased
    when the converter can handle it successfully.

    I was wrong about the index.  It has a number of second-level entries,
    but the enclosing box is wrong.  For example:
    
    	Circuit Onx1eStarting
    		VMS Symptom
    		diagnosing
    		syntax
    
    Place the cursor on "syntax" and the box surrounds that one word.
    Place the cursor on "diagnosing" and the box surrounds that one word.
    Place the cursor on "VMS symptom," though, and the box surrounds both
    that entry and the level 1 entry above it ("Circuit Onx1eStarting").

I ran into a bug that should be classified as level A.

The converter crunched on a >100 page 500-block Interleaf chapter for over 
3 1/2 hours and then crashed my workstation.

My DECterm window showed that it seemed to be in the final stages of the 
conversion where the Postscript-type display is scrolling in the window.

Then the workstation DECterm, LAT sessions, and LAT window all crashed.

The refuse left on my desktop is from the one failed chapter:

Grand total of 1 directory, 426 files, 11791 blocks.

    Lest some poor fish stumble upon Note 47.20 (a very long log file) in
    DECwindows Notes, I've set Note 47.20 hidden. I've also extracted the
    note and will place keep it handy as a reference. I'm glad that the
    processing worked, and fairly quickly, it seems.
    
    If you need to make very long (>1000 lines) log files available, send
    me or post a pointer to the file. I'll fetch from there.

    Karl, I'm glad you set my reply hidden.  42,000+ lines of console
    output is not useful.  Of course, you DID ask me to post it in .14:
    
    >>                          Yes, a tremendous number of workfiles are
    >> created. Can you capture one of those processing sessions or post a
    >> batch log file so we have something to show John Clemens?
    
    I guess you didn't think it would be THAT bad 8^)  And that is
    precisely my point.

    Mike Quinn and I have discussed the way the converter looks for level
    heads, and between us we have a suggestion.
    
    Right now, the converter expects us to change the name of our level 1
    head components to "topic1" (or to contain that string, I don't recall
    which).  Why is that?  Why not "head1" or "level1" or "hd:hline"?  Why
    should we change our components to suit the software when we could more
    easily change the software to suit our components?  While we're at it,
    perhaps the name of the level heads the converter seeks should be a 
    switch that someone like Karl should have control over.

    I took a two-page file with one level head and no graphics and ran it
    through the converter:
    
    2 pages input	20 blocks output	6:48 elapsed time
    
    I copied and pasted that one level head and its associated paragraphs
    until I had 20 pages and converted it:
    
    20 pages input	296 blocks output	24:09 elapsed time
    
    I cloned the text until I had 100 pages and tried to convert it:
    
    100 pages input	1391 blocks output*	1:45:00 elapsed time*
    
    After 1:45, the converter ACCVIO'd, viz:
    
    Access violation, reason mask=00, virtual address=0000003D,
    PC=0001636A, PSL=03C
    00000
    Symbolic stack dump follows
    module name     routine name                     line       rel PC   
    abs PC
    
    BWROUTS         bw_close                         1635      00000162 
    0001636A
    PL2BWI          main                             1658      000001EA 
    0000F5F2
    uncial:
    
    I note that the rate of conversion seemed admirably consistent, but it
    failed on a not unreasonable quantity of text.  (OK, OK, I would have
    pushed it until it failed anyway 8^)  Our books average over 100 pages.

    
    I tried stringing together four chapters at the converter invocation in
    an attempt to produce one book and came up with the following message:

    %RMS-E-PRV, insufficient privilege or file protection violation
    %TRACE-E-TRACEBACK, symbolic stack dump follows
    [then the stack dump output]

    My workstation did not crash like last time. The compile time was 1 hr.
    
    All four chapters build fine individually and display on Bookreader. I
    only get the error message when I try to put them together as one book.

    I simplified the test document I used in .27.  I removed all index
    hits, and padded it with text so that there was one level 1 head on
    every new page.  As before, it had no graphics apart from the rule
    under the chapter title.  When I repeated the stress test, it did
    better, but not great:
    
    Input	Output		Clock
    Pages	Blocks		Time
    
     10		 139		  12:37
     50		 691		  43:58
     99		1367		1:29:49
    200		----		(ACCVIO)
    
    I suspect some data structure is overflowing, but who knows what?  If
    it's the TOC, I have a problem, because we have an engineering
    document with some hundreds of level 1 heads.

    During a multi-chapter book build, the converter terminated when it
    hit a chapter that contained an overlay frame for a syntax statement
    with oversized braces. The message:

    ArSavDg: error in diagramming format, diagram skipped
    ArSavDg: fatal error reading diagram, program terminated

    Does it always terminate when it meets an overlay?

I successfully compiled a 50-page user manual with 4 chapters and 2 appendices.
There was no art and I removed the syntax overlay that killed it the first
time.

The run time was 1:40. (1:15 compiling, 0:25 writing to the .DECW$BOOK file)

The process finished with the following message:

RMS-W-RTB, 262 byte record too long for user's buffer
    
I fed the files to the converter using a file spec that read down through the
desktop into two book icons -- one for the chapters and one for the appendices.
I was trying to preserve the chapter numbers in the section heads in the
Bookreader output. However, the Bookreader output produced chapter 1.n and then
reset it to 1.n again for chapter 2, 3, and 4. Appendix A was OK, but Appendix
B reads A.n. 

    I found a page where text that appears on the Interleaf file dropped
    out during the conversion to Bookreader. The first three words of a
    paragraph appear, but the rest of it is missing. 

    The Interleaf file shows that there is an index token after the first
    three words. Nothing after the index token came over to Bookreader.

    Steve-
    
    	This is an interesting suggestion, and it begs the question: why
    	wasn't the converter designed to recognize the names we've set up
    	in our catalogs in the first place?
    
    	The answer is two-fold. The first part of it has to do with the
    	differences between the hardcopy environment, with its paragraph-
    	and-page orientation, and the Bookreader environment, which
        consists solely of Topics. We had to devise a convention for 
    	component names that would enable to converter to parse the TPS
    	file into discrete Bookreader topics. I chose the name Topic, in
    	preference to the more generally used "head," or some variation
    	thereof, as a way of encouraging users to THINK about the BR
    	environment while preparing their TPS files for display within it.
    	In short, the intent was to develop a convention that would
        explicitly link TPS file preparation with the goals it is supposed 
    	to serve.
    
    	Another reason for this choice derives from a longer-term view of
    	the application and its probable future within Digital. Believe it
    	or not, other groups, lots of other groups, have been asking for
    	this thing. When it is complete, and meets our acceptance criteria,
    	Kathleen intends to make it available throughout the corporation.
    	Thus is made sense for any naming conventions to be based on 
    	Bookreader's structure, rather than on the "language" of T & N's
    	hard-copy catalogues.  
    
        Hoping the layoff passes over me, 
    
    chris
    	

    Mike, et al-
    
    	I should have notified everyone about this earlier, but did not.
    	The converter will not handle overlay or underlay frames, period.
    	This was something agreed to during the design stage of this
    	beastly beast. Perhaps I should ask Karl to put out a note
    	informing everyone of this limitation-
    
    chris

    Jim-
    	Building chapters into books is an area we'll have test
    	extensively over the next few weeks. Sometimes it works,
    	and sometimes-- we do not know why --problems occur. 
    
    	Mark Kimball and I built the files you refer to into a book,
    	and had no problems. However the TOC entries in that book
    	were scrunched together...talk about frustrations!
    
    chris

    Following are two more problems to add to our burgeoning list:
    
    1) Bookreader's live scrolling feature does not work at all on
    	books or chapters processed by the converter. This may be
    	a DECwindows bug, but we do not know at this time.
    
    2) I have repeatedly (though not recently) sent a small but
    	fairly complex file through the converter, and received
    	problematic output. The file is called Tan_news_tweak.doc,
    	and it is a proto-type of the T&N Technical Newsletter.
    	I will include a copy of this file in the trouble_file
    	directory Karl has established.
    
    
    chris

    A chapter from _DECmcc Director Use_ returned the %PL2BWI-F-CHUNKFAIL
    error, even though I purged unused components, etc (a workaround which
    solved the problem before).  Fatal error, no bookreader file was
    output.
    
    I'll copy the file and a partial log to the trouble_files area.

    Anent .33: Chris, I appreciate your forward thinking about what the
    documents of the future should look like.  Being a pioneer often means
    getting arrows in your back.  I have a couple to shoot.  The current
    software requires me to rename all my level heads.  Well, I've got
    thousands of pages and scores of documents to fix, and I don't like the
    "futuristic" solution as proposed.  I prefer one from the past.
    
    What is the corporate standard naming convention for level 1 head tags?
    Why, there is none, of course.  In DSR it's .hl 1, in DOCUMENT it's
    <HEAD1>, and in our Interleaf shop it's hd1 (for some documents,
    anyway).  Should we revise all our documentation source files to fit
    the converter's expectations?  I say no.  The converter needs to know
    what we are expecting of IT.
    
    What the software needs is a management interface, as DOCUMENT and
    Interleaf have, allowing a Bette Jean to define for a particular copy
    of the converter what it should convert to a TOPIC1, a TOPIC2, etc. 
    Define it once and you're set for that shop or that doc type.  It is a
    trivial matter of programming; I could probably code it myself.  This
    would make the converter much more attractive to other groups than
    leaving the TOPIC1 requirement in (or, frankly, doing what I suggested
    before).
    
    Let's make the computer do our work for us, not the other way around.

    Anent .34: Chris, I'm confused.  We have identified underlay and
    overlay frames as Interleaf features that we use in our books and thus
    require the converter to handle.  In Karl's test plan, he lists this as
    a Class B problem (i.e., one that must be fixed before we will accept
    the converter).  Now you say, "The converter will not handle overlay or
    underlay frames, period. This was something agreed to during the design
    stage of this beastly beast."
    
    I apparently don't know what was agreed to at the design stage.  I
    would have expected the list of features supported to be the Interleaf
    master index, or at least derived from examination of the various
    tricks we've used in T and N to write Interleaf books.  This is in our
    books.
    
    We spent several hours this morning creating screen dumps of problems
    we've had, as Karl requested.  If some Interleaf functions are not
    supported by agreement, perhaps this work is not needed.  Perhaps it
    would save everyone time if we knew what other features are not to be
    supported.

Ref previous:

While Interleaf did state that underlays wouldn't be supported in the converter,
I don't think we realized how important that feature was to our environment.
For that reason, while Interleaf does say that it can't be done, I think we
ought to keep after them to make it work. (The spec doesn't really spell out 
why it couldn't be done.)

As far as I know, there are no other limitations that have not been acknowledged.
I will update the spec to reflect that this is a known problem as reported by
Interleaf. There is another, that of running Interleaf and the converter at the
same time. As with the underlay problem, I find this an unacceptable limitation
and will keep after them to fix the problem.

Jon Parson of CUIP Engineering suggested that we try to view the convertered 
files with Bookreader V3. This may point out any latent incompatibilities with
some of the Motif features. I will check some of the converted files in the next
couple of days.

An aside on Interleaf, Motif, et al.

Interleaf currently does not run under Motif, mostly due to some problems with
the display. I have been able to run the converter from a system running V3 and
to view those files in a V3 Bookreader environment. The resultant files don't
take advantage of all of the new Bookreader features, but there are some things
that we get for free (different structure to the TOC, multiple open windows) 

I converted the body of the DECmcc Master Doc Plan, running twenty-five pages or
so, with a couple of figures and four large tables.  I set up topic1 and topic2
components, purged unused master components, frames, autonumber streams, and
tables, saved the file in ASCII, and ran the converter.  Judging from the
output, the conversion worked.  I then ran the Bookreader and saw the document
on the shelf.  But when I tried to open the book, the Bookreader crashed.

I tried this from my workstation and from WORDY.  Here is the result on WORDY;
it was the same on my workstation.

wordy: run sys$system:decw$bookreader
Access violation, reason mask=00, virtual address=00000000, PC=000236D9, PSL=03C
00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                00000002
                 00000000                00000000
                 00000000                00000000
                 000236D9                00000000
                 03C00000                00000000
                                         00000000
                                         00020004
                                         00200338
                                         00000000

        Register dump

        R0 = 00000000  R1 = 0020AF88  R2 = 0001C71C  R3 = 00000000
        R4 = 7FEF6278  R5 = 00000000  R6 = 00009D30  R7 = 00000000
        R8 = 00000001  R9 = 0001C7AC  R10= 00009D38  R11= 0001C178
        AP = 7FEF60C0  FP = 7FEF6080  SP = 7FEF60FC  PC = 000236D9
        PSL= 03C00000

wordy:

By the way, I have copied the deadly doc to:

	I2B_DISK:[VIEW40.TROUBLE_FILES]BODY.DOC

It is *very* proprietary 8^)

I created a two-page document to test conversion of sidebar frames.  
I cut two pages (one spread) out of one of our structured documents.
When I made them into a free-standing document, I was momentarily surprised
to see that the sidebars were reversed, but I quickly realized they were defined
to sit against the inner and outer page boundaries.  So I created a topic1 head
with no text following it.

When I tried to convert the document with an empty topic1, the conversion
failed, viz:

	uncial: il2b nms$disk:[jong.desktop]sidebars.doc
	Created NMS$DISK:[JONG.DESKTOP]BOOKPARAMS.TXT;1
	DKB200:[JONG]BOOKPARAMS.TXT;1 deleted (0 blocks)
	Opening nms$disk:[jong.desktop]sidebars.doc;1 ...
	Creating SIDEBARS_P.DOC ...
	Creating SIDEBARS_P.COM ....
	Creating SIDEBARS_P1.DOC ...
	Creating SIDEBARS_P2.DOC ...
	Error opening NMS$DISK:[JONG.DESKTOP]SIDEBARS_P.COM; as input
	File not found
	uncial:

When I put a one-line paragraph under that dummy topic1 head, it converted OK.

However, the sidebars did not appear.

    Steve-
    	
    	I think I understand your point of view here. Casey has made
    	suggestions along the same lines. She too feels that the 
    	converter should accomodate whatever naming conventions its
    	users wish to adopt. At this point, we do not have this
    	flexibility, and the tool will certainly be more useful once
    	we add it.
    
    	Okay then: let's make this a level c request (e.g., something
    	we would like to see) and give it a place on Karl's omnibus list
    	of problems.
    
    	Not totally impervious to arrows, I remain-
    
    chris
    

    
    
    Ref Karl's reply-
    
    	I agree with Karl, and have to absorb the blame-- if this helps
    	anyone --for not communicating this limitation to our user
    	community. I accepted this limitation early on, without knowing
    	that o/u frames are used fairly broadly in our group. In any
    	case, I do not think it would be easy to program this limitation
    	away. But we'll see.
    
    	Once again, I am sorry not to have communicated this restriction
    	earlier. I do not believe there are any others.
    
    chris

    Anent .45: Chris, that sounds reasonable.  Tell Karl naming flexibility
    is a C problem.

From:	DECWRL::"[email protected]" "To someone with a hammer everything looks like a nail." 24-FEB-1991 16:08:39.63
To:	wordy::hakkarainen, [email protected], [email protected] 
CC:	
Subj:	status 

        Dear Karl,
 
        Here is the current status.
 
        Need from you:
 
        1. Is redirection to another Interleaf desktop using logical
           DESKTOP, adequate to solve your problem of work file space?
 
        2. Index collating sequence.
 
 
 
                AS BEFORE WITH SOME NEW COMMENTS
 
 
          A     Unexplained ACCVIOs. The mes-   Developer will pro-
                sages that the users receive    vide improved error
                are not sufficient for them     handling and messages.
                to determine what they did
                wrong, if anything
>
>       At least one cause of ACCVIO's has been corrected; a number of
>       changes have been made to improve error handling and messages.
>
          A     Table of text dropped out by    Developer to fix
                converter. Text after an in-
                dex token was lost
>
>       Unless I am blind (pass on page number), there is no missing text
>       after an index token in my conversion of QUINN_INDEX_TOKEN.DOC, although
>       this document had another problem which is now fixed after some
>       information received from Interleaf has improved my sizing of frame
>       to contents.
>
 
          B     Privilege violation causes      Same as ACCVIO re-
                stack dump                      port above. Devel-
                                                oper to fix.
>
>       Up-front checking of file accessiblity has been added
>
          B     Users cannot run Interleaf      Known Interleaf is-
                and converter in same desk-     sue that cannot be
                top at the same time; both      corrected by the con-
                processes hang.                 verter. If this is
                                                a continuing, we will
                                                need to lobby with
                                                Interleaf for a change
                                                to their file lock-
                                                ing procedures.
>       No Comment
 
          B     Large number of work files.     Developer will pro-
                The disk usage for large files  vide a procedure for
                may exhaust resources on some   defining a desktop
                disks.                          on an alternate disk.
>
>       The logical name DESKTOP can be used to re-direct work files,
>       but it must be pointing at a valid Interleaf desktop directory -
>       Is this acceptable?
>
          B     Messages must be delivered      Same as ACCVIO notes
                in a standard VMS format, along above. Developer to
                with documented recovery pro-   fix.
                cedures.
>
>       For all executables I can control (TPS and PL2IMG I cannot)
>       there are now VMS style error messages.  Recovery procedures
>       will appear in future documentation (not done yet).
>
          B     No version numbers on prod-     Developer to provide
                uct components                  a version ID when the
                                                converter is started.
>
>       Done.
>
 
          B     Table of contents overwrit-     Developer to fix.
                ing lines
>
>       I have no document that reproduces this problem.
>
          B     Index collating by pure ASCII   T&N Pubs needs to de-
                order                           fine the collating
                                                sequence for index;
                                                developer will then
                                                implement according
                                                to our requirements.
>
>       You still owe me on this one.
>
          B     User defined symbols inter-     Developer to fix.
                act with converter. (DELETE/CONFIRM,
                for example, will cause the
                converter to fail in batch.)
>
>       Fixed
>
          B     Cannot restart Interleaf from   Not reproducible.
                Session manager menu after
                running converter
>
>       No comment
>
          B     Multiple heads on same page     Developer to fix.
                generate blank pages
>
>       Am addressing some causes of blank pages; another cause is frames
>       which extend below the bottom margin. I can't fix that easily but
>       will provide cautionary documentation.
>
          B     Failed to handle clip arts      Developer to fix.
                for keys
>
>       I have no file that reproduces this problem
>
 
          B     See also contents of [View40.troAbtape of the con-
                files] directory                tents of the trou-
                                                ble_files directory
                                                was delivered to the
                                                developer on 30-Jan.
>
>               Trouble File Summary
>
>       QUINN_INDEX_TOKEN - no missing text after index token but there is
>                           a disfigured screen caused by my miscalculation
>                           of frame sized to contents. In the latest version
>                           this is computed correctly after info from
>                           Interleaf. This disfigurement was on one of the
>                           paper screen images you gave me.
>
>       RUTH              - Chunk Fail error caused by no topic on first page;
>                           have corrected the program to give a meaningful
>                           error message and exit fatally.
>
>       PL2BWI_F_CHUNKFAIL_QUINN - same as RUTH
>
>       BODY              - crashes bookreader. this was caused by two topics
>                           on one page which causes an empty topic. This
>                           condition is mow detected and the program exits
>                           with a meaningful error message.
>
>       UNDERLAY_FRAME_BUG - produced an ACCVIO (although it had nothing to
>                           with underlay frames). It will not do that in
>                           the current version.
>
>       SCANNED_IMAGE_PL2IMG - infinite loop in PL2IMG caused by misestimate
>                           of frame sized to contents. In the latest version
>                           this size is correctly computed based on Interleaf
>                           information.  This conversion now completes.
>
>       QUINN_WHITE_SPACE    - has extra white spaces which in for some
>                              places I am fixing (others caused by frame
>                              below bottom margin.
>
          B     The contents of a full-page     Bookreader limita-
                underlay frame in a Inter-      tion. I-Team needs
                leaf document do not show up    to define alternate
                under Bookreader.               strategies for han-
                                                dling frames; scan-
                                                ning pages is an op-
                                                tion.
>
>       No Comment
>                                                
 
          B     Scanned image took 70 hours     Developer to fix.
                to process
>
>       It really took forever (see comment re SCANNED_IMAGE_PL2IMG).
>       Now it does not.
>
 
          B     Hot Spots not always correct    Developer to fix.
                in Index groupings
>
>       Will fix, possibly today.
>
          B     Job terminates, apparently      While overlay frames
                when it encounters an over-     will not be supported,
                lay                             the developer will
                                                improve the error han-
                                                dling of the frames.
>
>       I have no file that reproduces this problem. I doubt that the
>       presence of overlay frame causes job termination, but have no
>       doubt that other things might.
>
 
          B     Job terminates with RMS-W-      Developer will fix.
                RTB error on 262 byte record
>
>       I have no file that reproduces this problem.
>
          B     VMSINSTAL kit required to al-   Developer will im-
                low installation as other DEC   prove installation
                sites.                          procedures and doc-
                                                umentation, which may
                                                or may not require
                                                a VMSINSTAL kit.
>
>       Will be working on this.
>
          B     Suppressed numbers at top of    Developer will fix.
                each topic
>
>       Fixed.
>
          B     Preserve multi-line topics      Topic names will be
                names.                          preserved as writ-
                                                ten. The names will
                                                not wrap to the win-
                                                dow size.
 
>
>       Done.
>
          B     Preserve chapter title when     Developer will pro-
                Topic1 begins a Chapter         vide an external table
                                                that can be use to
                                                define any element
                                                as a topic for the
                                                purposes of the con-
                                                verter.
>
>       New development not yet addressed
>
          B     Build Bookreader TOC to re-     As with the index,
                flect Bookreader style: Con-    T&N Pubs needs to de-
                tents, Copyright Page, Pref-    fine the style re-
                ace elements, plus Examples,    quirements for these
                Figures, and Tables entries     elements; developer
                                                will then implement
                                                the style.
>
>       Not yet addressed
>
 
          B     Correct formatting errors in    Duplicate. Developer
                TOC: lines overwriting          to fix.
>
>       I have no file that reproduces this problem.
>
          B     Font changes in left column     Developer to to fix.
                of two-column design are not
                corrected when text is writ-
                ten in right column
>
>       I am not sure I understand what this is. Need a file that reproduces
>       problem.
>
          B     Live scrolling window does      Developer to fix.
                not display entries in TOC,
                Index
>
>       I talked to Mike Fitzell at Digital about this problem and he provided
>       the solution. Scrolling window provides entries in current version.
>
          C     Users shouldn't have to change  See above regarding
                the names of level 1 heads      topic table.
                to topic
>
>       Not yet addressed
>
          C     Symbol_B right arrow shows      This may be a font
                up as double quote (")          map issue.
>
>       This is a character-mapping issue.
>
          C     Topic window is half as wide    This is a design is-
                as the document. Req's shift-   sue to be corrected
                ing the text area to read the   by T&N Pubs.
                right side of the page
>
>       No comment.
>
          C     Interleaf document used 14      T&N Pubs needs to de-
                pt Helvetica for Topics and     fine a procedure for
                12 pt Helvetica for para.       font mapping and styles.
>
>       No comment
>
          C     Blank pages appearing before    Developer to fix.
                sample pages
>
>       See prior remarks re blank pages
>
 
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by decpa.pa.dec.com; id AA22513; Sun, 24 Feb 91 13:06:26 -0800
Date:    Sun, 24 Feb 1991 16:06:32 EST
From: [email protected] (To someone with a hammer everything looks like a nail.)
Message-Id: <[email protected]>
Subject: status
To: wordy::hakkarainen, [email protected], [email protected]
X-Vmsmail-To: KARL

$!
$!   VERSION 2.0
$!   SYLOGIN.COM
$!    REVISION HISTORY
$!
$!02-May-1989 DpK, Modified for new NaCTS WAN-Server.
$!27-Jun-1990 Png, Added look symbol for phone.
$!14-Aug-1990 GS,  Commented out SECPACK_CHECK_PRIV.COM to bring up cluster
$!---------------------------------------------------------------------
$!
$ WO = "WRITE SYS$OUTPUT"
$!
$ old_control = f$environment("control")
$ vfy == f$verify(0)   ! Save verification flag
28-FEB-1991 08:19:36.38, Batch job BATCH_476 on node LEAF.
$ set noon
$ set noverify
[4]
[3]
[2]
[1]
%MOUNT-I-MOUNTED, .ENG.NAC.PUBS.DOCBCK mounted on _DFSC1012: (INTER)
$ exit
$ ! %ILTPS2BOOK-I-VERSION, Version is 0.1.
$ delete := delete
$ backup := backup
$ purge := purge
$ rename := rename
$ desktop = f$trnlnm("DESKTOP")
$ if desktop .eqs. ""
$	THEN
$ open/write/error=baddesk foo DESKTOP:foo.file
$ close foo
$ delete [HAKKARAINEN.DESKTOP]foo.file;
$ goto testbook
$ testbook:
$ decbook = f$trnlnm("DECW$BOOK")
$ if decbook .eqs. ""
$	THEN
$ open/write/error=badbook foo DECW$BOOK:foo.file
$ close foo
$ delete DECW$BOOK:foo.file;
$ goto batchtest
$ batchtest:
$ if f$mode() .eqs. "BATCH" then $goto batch
$ batch: default = p1
$ process:
$ programs = f$trnlnm("IWS2BOOK")
$ if programs .eqs. "" then ASSIGN SYS$LOGIN IWS2BOOK
$ ar2ar:==$IWS2BOOK:AR2AR.EXE
$ pl2bwi:==$IWS2BOOK:PL2BWI.exe
$ SET DEFAULT DESKTOP
$ params = default+"BOOKPARAMS.TXT;"
$ BACKUP/NEW_VERSION IBM$DISK:[HAKKARAINEN.DESKTOP]BOOKPARAMS.TXT; []/LOG
%BACKUP-S-CREATED, created USER$652:[HAKKARAINEN.DESKTOP]BOOKPARAMS.TXT;3
$ DELETE/LOG IBM$DISK:[HAKKARAINEN.DESKTOP]BOOKPARAMS.TXT;
%DELETE-I-FILDEL, USER$652:[HAKKARAINEN.DESKTOP]BOOKPARAMS.TXT;3 deleted (0 blocks)
$ AR2AR USER$652:[HAKKARAINEN.DESKTOP]USING.DOC;4
%AR2AR-I-FILOPEN, Opening user$652:[hakkarainen.desktop]using.doc;4.
%AR2AR-I-FILECRE, Creating USING_P.DOC.
%AR2AR-I-FILECRE, Creating USING_P.COM.
$ @USING_P
$ pl2img:== $IWS2BOOK:PL2IMG
$ clipbm:== $IWS2BOOK:CLIPBM
$ duh_fonts = f$trnlnm("IWS2BOOK_FONTS")
$ assign NLA0: SYS$OUTPUT
$ SET NOON
$ PL2BWI USING_P
%PL2BWI-F-BADFILE, Can't open using_p.
%NONAME-E-NOMSG, Message number 00000002
$ stat = $STATUS
$ if f$search("DECW$BOOK:USING.DECW$BOOKSHELF") .nes. "" then $ RENAME DECW$BOOK:USING.DECW$BOOKSHELF DECW$BOOK:LIBRARY.DECW$BOOKSHELF
$ DELETE USING_P*.*;,$USING_P*.*;
%DELETE-W-SEARCHFAIL, error searching for USER$652:[HAKKARAINEN.DESKTOP]$USING_P*.*;
-RMS-E-FNF, file not found
$ IF F$MODE() .eqs. "BATCH" THEN $ PURGE IL2B.LOG
$ DELETE BOOKPARAMS.TXT;
$ SET DEFAULT IBM$DISK:[HAKKARAINEN.DESKTOP]
$ PURGE IL2B.COM
$ if F$MODE() .eqs. "BATCH" then $ EXIT %X00000002
  HAKKARAINEN  job terminated at 28-FEB-1991 08:20:00.05

  Accounting information:
  Buffered I/O count:          244      Peak working set size:  1402
  Direct I/O count:            218      Peak page file size:    6114
  Page faults:                4928      Mounted volumes:           1
  Charged CPU time:     0 00:00:10.20   Elapsed time:     0 00:00:26.49

    The new converter, plus my meeting with John Clemens, has let me do
    things I couldn't do before.  I now have a Bookreader file comprising
    the first two chapters of _DECmcc Introduction_.  (Previously, I
    couldn't combine documents, and my Chapter 2 never built.)
    
    I'd like to know how to get at least two levels of hierarchy into by
    Bookreader book.  Right now, all the topics are glommed together.  I
    want to see this:
    
    Chapter 1 -- The Challenge of Network Management
    	[topic]
    	[topic]
    	[topic]
    
    Chapter 2 -- What is DECmcc?
    	[topic]
    	[topic]

    When you use the elevator to slide through the index, entries with
    subordinate entries do not appear, viz:
    
    	entry
    	entry with subitems              ------------
    		a subitem 		|entry	     |
    		another subitem		|later entry |
    	later entry			 ------------
    
    The Bookreader itself does not exhibit this behavior.
    	

    In reply .50 I said I can now build two chapters of my book together. 
    I can, and I can build each of the next three separately, but when I
    try to do them all together, the conversion blows its stack.

    I am trying to build a complete book, piecemeal.  The converter doesn't
    seem to be able to handle the miniature Digital logo appearing in the
    list of copyrights on the copyright page.  This is a boilerplate
    focument, and the logo is, I think, an inline frame.
    
    
    %AR2AR-I-FILOPEN, Opening nms$disk:[jong.desktop]copyright.doc;1.
    %AR2AR-I-FILECRE, Creating COPYRIGHT_P.DOC.
    %AR2AR-I-FILECRE, Creating COPYRIGHT_P.COM.
    %AR2AR-I-FILECRE, Creating COPYRIGHT_P1.DOC.
    Interleaf Viewstation, Rev. 4.2.0.15.
    Copyright (C) 1987-1990, Interleaf, Inc. All rights reserved.
    Unable to open document.
    %AR2AR-I-FILOPEN, Opening nms$disk:[jong.desktop]preface.doc;1.
    %AR2AR-I-FILECRE, Creating PREFACE_P.DOC.
    

    I have placed a file containing a troublesome graphic in
    [.TROUBLE_FILES].

    Anent .53: I am running the conversion again, and again it can't open a
    file.  I guessed that it was a particular graphic file (Mona Lisa file)
    on my desktop, and I copied it and tried to paste it into a document. 
    Lo and behold, I got an Interleaf trap!  "Divide by zero," it said. 
    Surprisingly, I could recover from the error and continue on.
    
    I tried another graphic file at random, and that I could copy and paste
    successfully.
    
    I have saved the naughty Mona Lisa file, if you're interested in it.

    I tried to run my whole book at once yesterday afternoon.  It almost
    made it, but crapped out just into Chapter 10 with an unfamiliar
    complaint:
    
    <penh 4204>~6Ql$c=T1~
    <clipbox topleft = (0, 0), (w, h) = (10795, 13970)>
    <penh 9487>~6Ql$c=t~
    %PL2BWI-I-IMGLOAD, Loading image file chap10_p1.IMG.
    
    <eop 523 1214 current 9996>
    
    <hvsystem origin:  top left axis: unchanged orient: x axis>
    <font 92>
    <color 7>
    <penhv 1308 1520>Digital<spacesize 69><sp>Network<sp>Services<font 87>
    <penhv 1308 1985>Digital<spacesize 39><sp>Network<sp>Specialists<sp>can
    <sp>assist<sp>you<sp>through<sp>all<sp>phases<sp>of<sp>network<sp>devel
    opment<sp>and
    <penhv 1308 2230>purchase.<font 27>
    <penhv 2146 2945>Digital'<penh 2794>s<spacesize 
    53><sp>Networ%PL2BWI-F-INSFDYNME
    M, Can't allocate CE
    Abort
    430 byte record too large for user's buffer
    uncial:
    
    I note that it seemed to fail in the middle of a regular block of text,
    but the next graphic it was about to encounter is among the biggest and
    most complex in my book.  I don't know if that's significant.
    
    Examining my Interleaf desktop, I see that the conversion process did
    make work files for Chapter 10; it just didn't do the conversion. 
    Because it aborted, it left something over 800 work files behind. 
    Wowsers!

    The same book can be constructed through Chapter 9.  As I said before,
    Chapters 10-end build, too.  title-end doesn't.
    
    I notice that the table of contents is formatted at the topic1 and
    topic2 component text appears.  Define a topic1 as Helvetica 24 bold;
    change the actual text to Helvetica 18 roman.  The TOC entry is...
    Helvetica 18 roman!  This is somewhat inconvenient, and we need the TOC
    to be different from the entries on the pages.
    
    When there are multiple references to the same index entry, clicking on
    the entry produces a pop-up box showing all the topics in which the
    entry occurs.  Slick!

    I have taken all the documents that make up my book and put them in the
    TROUBLE_FILES directory as SJ*.DOC.

    An addendum to this trouble report: I ran all my tests over the last
    two weeks without ever logging out of my workstation or even exiting
    Interleaf.  On Friday I exited and restarted Interleaf and tried the
    conversion again for my whole book.  This time it appeared to get
    through Chapter 10 and into Appendix A, the next document, before
    crapping out.
    
    Perhaps this is a tuning problem?

    So let's say I have this software product that's supposed to be
    released under both VMS and ULTRIX, and I'm working toward making
    Bookreader files.  When I have finished my labors and have a perfect
    Bookreader file under VMS, do I also have one for ULTRIX?  If not, what
    more do I have to do to get there as well?

All that I've heard from people who have exchange Bookreader files between the 
operating systems is that the issue is one of converting the file formats from 
VMS to Ultrix or back. The Bookreader is the same. 

I've not done this because I've not had need to. I'll try to cross-post some
notes from the Bookreader conference on exchanges to and from Ultrix. The final
word on this will come from Mike Tardiff, the Bookreader product manager with a
history of Unix fondness. I expect to talk with him on Friday.

Another forum where this can be answered it in the Bookreader meeting scheduled
this afternoon with Michel� Cicalse. He will cover a range of issues and this 
is certainly a fair target.

	2-4 this afternoon in the Gloucester CR

    There's a problem with longer than usual filenames. 

    In one case, I created a file call ABSOLUTE_TORCH_AND_TWANG.DOC. 
    When I try to run the file through the converter, I get an error
    indicating that it cannot find a file. The log file is
    LONG-FILENAME.LOG, posted in the trouble_files directory.

    If I copy the file to another, shorter name, the processing moves
    just fine. See SHORT-FILENAME.LOG

    In this case, I used the USING.DOC file as the test, just changing
    tne ames.

    Karl Hakkarainen

    Using Version 0.4 of the converter, I am at last able to process my
    entire book.  Halleluiah!
    
    The box around hotspots is still usually not sized correctly.

The Symbol_B character that looks like this --> is mapped to what looks like
a capital V with a bar through it.

Using Version 0.4, I am attempting to match the output of a typical 
DOCUMENT->Bookreader file as closely as I can.

A chapter title maps to topic1.  In the Bookreader sample I'm looking at,
it looks like this:

	1. Bookreader

I can't seem to get the space to work; if I enter my chapter
title with a tab and a space the output looks like this:

	1Managing Your Network

The conversion seems to be eating my space.

Yeah, I know, it's probably too late.  But I want it on record for the future
that we would like these features supported:

The Bookreader supports pop-up figures (figures that appear in separate 
windows).  I don't care for them, but I'm some do.  The converter doesn't
support them.

The Bookreader supports live cross-references (for example, in the phrase
"see 'Sample Flags' later in this section for more details," you could 
double click on "Sample Flags" and go there).  The converter does not, to
my knowledge.

    Our "summary" component is spec'ed as right-justified.  When converted,
    it isn't.

    I've got a good one, I think...!
    
    In eight different exhibits (figures) in my converted document, the
    caption was in italics, not boldface.  In every case, the exh:t
    component followed a para component that ended with italicized text
    (document titles, in point of fact).  It seems that the conversion
    process does not always forget about the type mechanicals of the
    preceding component.  Of course, it should.

    Over the last couple of weeks, I have been working exclusively with a
    copy of my document, with every file, even the catalogs, stored in
    ASCII format.  There seem to be a number of small, highly annoying
    little formatting errors that creep in to the Interleaf files.  These
    errors originate in Interleaf, and are carried over in the conversion
    process.
    
    The most common error is to see a bulleted list with the first bullet
    character a point size too small.  Now, these are components defined in
    the catalog, with shared-content prefixes.  Normally, I *cannot* change
    them; so it's not pilot error.  I have been forced to do a number of
    Select -> All of and Change -> Bookreader (my catalog name) -> (same
    name) to get a "pure" copy of the master.  I think there's no reason
    why I should have to do this.
    
    As I said, this is an Interleaf problem, not a converter problem. 
    However, I recommend working with the Interleaf (fast) format files as
    long as possible before saving them as ASCII for the conversion.

    I have a valid cross-reference in a chapter to a page in another
    chapter.  It appears correctly in the (ASCII-format) Interleaf
    document, but when converted, it appears as NO TAG.
    
    I have noticed no problems with cross-references within a document.

Occasionally, as in this example, converted text at the end of components
is spaced out .

I see it here and there, in para componets, particularly those that
end with colons :

I've noticed it in several exhibits, to   o

I can't pin it down.  Perhaps it has to do with index tokens ?

Anyway, it's intermittent, and, as you see, it's distracting .

    Helvetica 14 italic is mapped to Helvetica 14 bold.  Close, but no
    cigar.

    The converter maps text in microdocuments (or text in microdocuments
    in frames, I don't know which) slightly differently from plain text.  I
    can cite two examples, one of which helps me and one of which hurts he.
    
    I haven't been able to get a trademark symbol (TM) to appear anywhere
    in my converted document EXCEPT in one exhibit, where it shows up.
    The exhibit is a frame, in which is a microdocument, in which is a para
    component like all my other para components.  The trademark symbol
    there is, to Interleaf, identical to the one on, say, my title page. 
    But in the frame it translates correctly, while on the title page it
    comes out as an uppercase E.  I have tried copying the entire component
    out of the frame and pasting it on the title page; there both symbols
    come out as Es.  Weird, man.
    
    The second case is an equation that in Interleaf looks roughly like
    this:
    
    			T = (C1 - C0)/(t1 - 10)
    
    where the numerals are subscripted.  The division sign, the slash, is
    translated into a boxed, upside-down question mark.  Again, an equation
    is stored as a frame.

    HA!  I figured it out.  Anything in a frame gets converted to a bitmap,
    including text.  I placed a trademark symbol (TM) and a right arrow
    (->) into tiny frames, and they came out.  So we have a workaround.
    
    This is no substitute for actually mapping the characters to
    appropriate Bookreader font characters; some of my us have hundreds of
    these characters in our books.  But it's a step forward.

    I have a couple of components that produce centered text.  When
    converted, they don't; the text is flush left.

    I have tweaked my strucdoc-to-Bookreader catalog about as much as I
    can.  If you're interested, it's in Interleaf > Communications > MCC >
    12b_catalogs and it's called Bookreader.

    I think it's been implicit in our planning, but let me put it
    explicitly:  On the title page and copyright page, the only way I know
    to get them to appear as separate topics and appear in the TOC is to
    create a topic1 called "Title Page" and another called "Copyright
    Page."  But those strings appear twice on the page.  We don't want that
    to happen.

    
    Just in the event someone else comes back here for help (like I did),
    here are some things I find going wrong:
    
    #1
    ---
    The Seminar notes say to change my hd:un2 components to topic3
    components from the Bookreader catalog, but there ain't no such animal
    as topic3 in the Bookreader catalog! I created my own instances. I
    won't even try to open the can of worms as to who owns the Bookreader
    catalog and should rightfully make changes.
    
    #2
    ---
    The Seminar notes say that only components with the word "topic" in
    them should start a new page, but what it doesn't say is that any
    component with the word "topic" in it MUST start a new page. You get a
    cryptic error message and the conversion bombs if two topics are on the
    same page.
    
    #3
    ---
    Interleaf crashes when I try to open an appendix document with the
    AppBookreader catalog in front of it. I can open the file if I move the
    catalog out of the way first and then move the catalog back after the
    file is open.
    
    #4
    ---
    The properties for the component tbl:t in the Bookreader catalog do not
    export. The Seminar notes say to use topic headers for tables, but I
    haven't tried that yet. Why have a tbl:t component in the Bookreader
    catalog if we aren't supposed to use it??
    
    #5
    ---
    Worst of all, I "cleaned" up my desktop this morning and deleted old
    files that the converter generated. My reasoning was that the converter
    generated them, and since I was just going to run the converter again,
    I didn't need these old files (and there were many) on my desktop,
    whatever they were. Now the converter bombs and I can't figure out why.
    Nobody can. The only indication is that it's looking for an "oldest
    file version" of one of the files that I deleted. Why is IT looking for
    an old version of a file IT generated to begin with? I didn't create
    it. Why doesn't it create it again like it did the ten times I ran the
    converter before this morning????????
                                         

    Ref: #1 - We'll try to get the catalog updated accordingly.
    
         #2 - See also the Using doc (available in Bookreader), which is
              the base documentation for the converter. (The Seminar notes
              don't replicate all of the Using guide.)
    
         #3 - See #1.
    
         #4 - See #1.
    
         #5 - We suspect that this resulted from problems with the job when
              it ran on a node (Verbos) not licensed for Interleaf yet.
              This left the intermediate files in a strange state. The
              problem of cleanup after abnormal exits is a long-standing
              one; it's doubtful that we'll get a quick fix on it.
              

    
    
Hey kids,
    
    I was having a real problem with the converter as you can read below.
    The answer: I did a Copy->Normal of the book I was working with and
    pasted it to my desktop. I rename it and all the documents in it. When
    I ran the converter again it worked.
    
    ========================================================================
    
Hi Karl,

I'm still in the process of converting two manuals to Bookreader. At the end of
last week and yesterday, I was getting a pretty good conversion of my VMS
installation guide. This morning, I decided to "clean up" my desktop and get
rid of all those strange files the converter generates and leaves on the
desktop. It creates a whole bunch. I figured "heck, I'm just going to run the
converter a few more times so I'll get rid of these old files even if they mean
something to the book I currently have in my bookreader library. After all, the
converter will just generate them again and again, right?".

Well, reality is not pretty. The converter has failed every time since. It's
important to know that the converter WAS converting the book very well, and
that I was making cosmetic changes to the Interleaf source documents on my
desktop so the Bookreader version would be primo (read "PREE-mo").

Obviously, it has something to do with the files that I did not create yet
deleted from my desktop. My stupid line of argument said that since the
converter generated them before, it would generate them again and again
whenever I run the thing. Apparently not! When the converter bombs I get these
lines of text in the log file:

$ PL2BWI TITLE_P COPY_P PREF_P CHPT_1_P CHPT_2_P CHPT_3_P CHPT_4_P CHPT_5_P
CHPT_6_P CHPT_7_P APPA_P
***************************title_p******************************************
%RMS-S-FILEPURGED, oldest file version purged
%DEBUGBOOT-W-FNF, file not found
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000218,
PC=0001AD94, PSL=03C00000

Followed by a whole bunch of stack dumps in hex. The converter does generate a
file "title_p" and it's on my desktop. I don't know enough about the converter
to know what it does with "title_p".

Right now I'm very frustrated. I've tried to go back and create the identical
environment I had when I ran the converter the first time, hoping it would
generate whatever file it did way back when and wants now.

Thanks,
Rikk

    
    How do we make our Bookreader books available to other users,
    specifically our editors who would like to edit the on-line version?
    
    Thanks,
    Rikk

    
    Re: .81
    
    To let the editor view the on-line book the writer has created:
    
    The editor redefines a logical in his/her TNPUBS process with the 
    following command:
    
    $ DEFINE/USER TNP$USER_BOOKS target-directory
    
    where "target-directory" is the disk and directory where the on-line
    book currently resides. For example, my editor used this command:
    
    $ DEFINE/USER TNP$USER_BOOKS USER$658:[HALLOWELL]
    
    Then the editor fires up Bookreader as per the seminar notes:
    
    $ @TNP$INFO:BOOKREADER workstation-name
    
    The editor double clicks on "User Shelf". The writer's book should
    appear there for the editor to review.
    
    Rikk