Conference vaxuum::document_ft

I can answer some of your questions:

>>>2)This must be doable : I don't want to give footnotes a specific
>>>  number, but instead have DOCUMENT start the numbering on each page
>>>  with no 1.   I think RUNOFF could do it. I really don't know where

??? you want DOCUMENT to number each page with the *no.* 1?
??? or you you want to use characters such as daggers in footnotes
??? instead of numbers?

>>>  Document decides to  start a new page. 

>>>  This could be due to the fact that I do not clearly know what 'callout' means
>>>  to VAX-Document. Could someone clarify ?

The only meaning for "callout" that I know of is that it is a 
reverse-print number; usually displayed in final output as a white 
number inside a black box.


>>> 4)What does it mean, when it says : <PAGE> produces device-specific output. ??
>>>   It starts a new page and it would look the same on a LN03 and a LN03R.

The final output may look the same for LN03 or LN03R, and even 
the LPS40, all of which output proportional characters and spacing.  But
it will look very different for terminal or lineprinter output because
those devices use monospaced characters.  For monospaced devices, your
pages will still occur everywhere you specified <page>, but you will
also get pages in places that didn't get them for the LN03.  Why?
Because monospaced devices use up more space than devices that provided
proportional characters and spacing. 


>>>5)I would like to design a doctype , who looks the same as our Travel-Claim,
>>>means a table like :


>>>   +------------------------------------------------------------
>>>   I  Hotel   I   Fuel   I   etc.  I
>>>   +------------------------------------------------------------
>>>   I  1234.56 I  45      I .....
>>>   +-----------------------------------------------------------
                .
                .
                .

I believe the limit on number of columns in a table is 9; the expense 
vouchers have more columns than that.  You can get rules (solid lines
between rows), but you can't get vertical bars between columns.  I'm not 
sure what, if anything, you were asking about tables in particular, so I 
just guessed that this information would be useful to you.

>>>  Second, I would like to write a program to take DECALC-PLUS output of my
>>>  expenses and merge that with a template and generating a sheet, which
>>>  looks like a Travel-Claim.

Sorry, can't help you with this one.


Rose

 Re. footnote numbering:

  I agree that there ought to be a way to have Document number my
  footnotes automatically. Preferably by chapter, as this would
  avoid problems rebuilding parts of books.

  I do see a problem if update pages suddenly have footnotes that
  were not there previously, and Document renumbers all footnotes
  in that chapter. It may cause identical footnotenumbers on 
  updated and old pages...

  Still, why do I have to do the counting? TeX can do it easily for
  me if wanted. The option of user-specified counters must be kept
  of course...

Theo

    If DOCUMENT did automatic footnote numbering, we would have
    to allow footnote symbols, so that the <footref> tag would be
    able to make reference to a footnote whose number is not known
    to the writer.  If the numbering were done at tag translation
    time, the symbol could be added to the symbol table, but if the
    numbering were done on a page-by-page basis, as requested here,
    the symbol would be handled only by TeX, which at this point
    is not handling "symbols."
    
    THis is just a "scope of the problem" reply, not a solution or
    a promise to do it.  All I am saying is that it is not a simple
    problem.
    
    bill

    By the way, I once asked an experienced editor where I could find
    the definition of "callout", since it is not in any dictionary that
    I have seen, and is not in the Chicago Manual of Style.  It seems
    to be undefined printer jargon, which is used for reverse printing
    and or the use to which the reverse printing is put.  I claimed
    that if we couldn't find a definition anywhere, we shouldn't use
    the term, but we couldn't come up with an alternative.
    
    bill

    
    1. There was a problem with some of the doctypes writing specific
       English text. Was this BL8 or V1.0? What doctype? (Note we
       are still tracking down all the English gremlins, with help
       of our patient European users...)
    
    2. Automatic numbering of footnotes is on the wish list for a future
       update to document. As Theo and Bill suggest, it's not as
       straightforward as it seems, because we do need to use the
       symbol table to handle multiple references. Also, some writers
       might want footnotes at the bottom of the page, some at the end
       of each chapter in a book, and some at the end of the entire
       book. 
    
    3. A test-page function is also on the wish list.
    
    4. The information on <page> is, as Rose says, a warning that you
       might not like what you get on all devices.
    
    5. I believe Rose was on the mark, as usual, in helping with this
       one.
    
    patti anklam
    

First of all : Thanks for your support !

>    1. There was a problem with some of the doctypes writing specific
>       English text. Was this BL8 or V1.0? What doctype? (Note we
>       are still tracking down all the English gremlins, with help
>       of our patient European users...)
    
I reported such a problem on BL8 somewhere in this notesfile. Most of them have
gone away with V1.0. But the one I mentioned in .0 still exists.

	gerold

    
    Oh, so you did. It appears that SOFT.GUIDE defines the contents
    headings, overriding the text strings. Will fix as soon as I can.
    Meanwhile, if you create a local doctype based on soft.guide,
    you can include the following to set the table of contents headings:
    
    \gdef\TOCtablehead{heading-you-want}
    \gdef\TOCfigurehead{heading-you-want}
    \gdef\TOCexamplehead{heading-you-want}
    
    I will definitely get out my scouring brush before the next update
    for the language strings.
    
    Again, I apologize for my short-sightedness.
    
    patti