[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
529.0. "Problems With Document?" by CLARID::TURNBULL () Fri Jun 19 1987 11:00
I am a Technical Author working in the Service Engineering Group,
Valbonne, France. I have been using version T1.0 of Document for
a couple of months (mostly with the SOFTWARE doctype). I have noticed
the following problems. Can anyone tell me whether these problems are
know, are already fixed, are there ways round them?
o <contents_file> and <index_file> don't work in MAIL or LINE
doctypes.
o <literal> ... <endliteral> doesn't work very well. Is there
no tag to temporarily switch the formatter off (like .literal
in DSR+)?
o Pagination is not as good as it could be; sometimes headers
appear as the last line of a page. Couldn't we have widow and
orphan tags?
o The CHECKENDS utility doesn't seem to work for me.
o Page numbering of the preface is incorrect if the table of
contents is over one page long.
o <PAGE> and <ENDSYNTAX> need a <P> after them to stop the text
moving back into the left margin. Why is the left margin so
wide in SOFTWARE anyway?
o MANUAL doctype could do with some of the tags allowed in
SOFTWARE. (MANUAL has a better visual appearance in my opinion.)
o If you do:
<endmark>
<P> (or some small text)
<mark>
Document appears to hang up (at least I think it's this that
is causing the problem.
o <mark> doesn't always do it's job. If you have a multi-page
table, the first page will be marked but subsequent ones will
not. The same problem can occur with large figures.
o Two large figures (done as <include_tex_file>) together can
cause a blank page to be printed between them.
These are the only things I can think of at the moment; if anyone
has any ideas I would be grateful. Also, what is the status of the
DSR to GNC converter? Thanks, in advance, for any information.
Greg Turnbull.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 529.1 | | CUPOLA::HAKKARAINEN | with hasty reverence | Fri Jun 19 1987 11:34 | 40 |
| > o <contents_file> and <index_file> don't work in MAIL or LINE
> doctypes.
Known and documented limitation. See sys$help:doc010.release_notes
for more info about restrictions.
> o <literal> ... <endliteral> doesn't work very well. Is there
> no tag to temporarily switch the formatter off (like .literal
> in DSR+)?
<code_example> or <interactive>, whichever is most appropropriate.
Literal only suppresses translation of tags; it has no effect on
formatting.
> o Pagination is not as good as it could be; sometimes headers
> appear as the last line of a page. Couldn't we have widow and
> orphan tags?
Discussed elsewhere in this file.
> o The CHECKENDS utility doesn't seem to work for me.
Checkends has gone to software heaven. The functionality of checkends
is built into the first pass of the tag translator.
> o Page numbering of the preface is incorrect if the table of
> contents is over one page long.
You need to provide a starting page number as an argument to the
<preface> tag: <preface>(5).
> o <PAGE> and <ENDSYNTAX> need a <P> after them to stop the text
> moving back into the left margin. Why is the left margin so
> wide in SOFTWARE anyway?
The key to this problem is that the text is a paragraph; without
the <p>, it becomes stuff that's formatted randomly. The objects
need to be identified; <page> or <endsyntax> and many other tags
shouldn't presume what objects will follow.
|
| 529.2 | Problems with <MARK> | CLARID::TURNBULL | | Mon Jun 22 1987 07:48 | 15 |
|
Thanks for the help. I'm still having problems with the <mark> ...
<endmark> tags. This time I had a chapter of a few pages - some
sections were marked, others were not. I then decided to mark the
whole chapter as changed, so I put a <mark> after the chapter title
and <endmark> at the end of the text. During formatting I got some
unidentified TeX errors and formatting ended (previously it had
been OK). The formatter suggested I make like H. Poirot and sort
out the problem myself (useful help). Finally I put my <mark> tags
after each new header - this appeared to work. Has anyone else had
problems with these tags? (By the way I had the <revision> tag at
the top of the file).
Any help appreciated. Cheers, Greg.
|
| 529.3 | workaround is to use more of them | CLOSET::ANKLAM | | Mon Jun 22 1987 19:19 | 14 |
|
Sorry you have stumbled over a complex component of DOCUMENT. It
is not always possible to handle the marks correctly when they
encompass a wide range of text elements and cross page boundaries.
You have come across the correct way to work around this: use
more <mark> and <endmark> tags.
There is no solution to this in V1.0, I'm sorry to say. However,
the messages that occur from TeX are a good deal friendlier and
will not stop a job from processing.
patti anklam
|