[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:	DOCUMENT T1.0
Notice:	New notesfile (DOCUMENT.NOTE) now available (see note 897)
Moderator:	CLOSET::ADLER

Created:	Mon Feb 09 1987
Last Modified:	Thu Oct 31 1991
Last Successful Update:	Fri Jun 06 1997
Number of topics:	897
Total number of notes:	4397

538.0. "<COMMAND_SECTION> running heads don't work." by DSSDEV::FISHER (Work that dream and love your life.) Mon Jun 22 1987 09:45

BUG:  <COMMAND_SECTION>(running_head)  doesn't work.  Also, the 
      documentation states that, by default, the current chapter title is 
      the running head; this also doesn't work.

USING:  doctype: layered
        devices: mail/ln03
        template: Command Template


I can't get the <COMMAND_SECTION> running heads to work correctly.  
The documented default doesn't work (the chapter title being used as 
the running head), and specifying a running head as an argument 
doesn't work (nothing is output as the top running head; commands or 
subcommands still produce the second running head).

SUGGESTION:  If you are going to use the chapter title as the default, 
you may want to consider giving us the option of specifying that we 
don't want any running head at all.  Some doctypes have the chapter 
title at the bottom of the page and it would be ridiculous to repeat 
the title in two places on the same page.

This error should be reproducible using any input.  Drop me a line if 
you can't reproduce it.


					--Gerry


[I tried to find out if these bugs and suggestions have been reported, 
but I may have missed previous notes.  This file is so huge!]

T.R Title User Personal
Name Date Lines

538.1 DSSDEV::FISHER Work that dream and love your life. Mon Jun 22 1987 11:05 17

T.R	Title	User	Personal Name	Date	Lines
538.1		DSSDEV::FISHER	Work that dream and love your life.	`Mon Jun 22 1987 11:05`	17
	I reread the documentation. It correctly states, in the <SET_TEMPLATE_COMMAND> argument description of DOUBLERUNNINGHEADS, that, if the doctype does not call for running top titles, then the default is that there will be no top running head. The documentation implies that the doctype design can ignore the <COMMAND_SECTION> running-title argument, but it never says so directly. If this is true, how come LAYERED allows me double running heads when I use the <SUBCOMMAND_SECTION> tag with the running-title argument (the second header is the individual subcommand title)? Why won't this doctype allow me a <COMMAND_SECTION> running head along with the individual <COMMAND> name as the second running head? --Gerry


I reread the documentation.  It correctly states, in the 
<SET_TEMPLATE_COMMAND> argument description of DOUBLERUNNINGHEADS, 
that, if the doctype does not call for running top titles, then the 
default is that there will be no top running head.

The documentation implies that the doctype design can ignore the 
<COMMAND_SECTION> running-title argument, but it never says so 
directly.  If this is true, how come LAYERED allows me double running 
heads when I use the <SUBCOMMAND_SECTION> tag with the running-title 
argument (the second header is the individual subcommand title)?  Why 
won't this doctype allow me a <COMMAND_SECTION> running head along 
with the individual <COMMAND> name as the second running head?


						--Gerry