| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 243.1 | maybe <LITERAL>(\) | ATLAST::BOUKNIGHT | Everything has an outline | Sun Apr 12 1987 23:21 | 3 |
| What about hiding the backslashes with the LITERAL tag?
jack
|
| 243.2 | and <lowercase> | CLOSET::ANKLAM | | Mon Apr 13 1987 09:43 | 16 |
|
The <TAG> documentation shows only three arguments, so that is
why only two arguments are output. The tag works the same in
all doctypes. You can use the <lowercase> tag to put text in
lowercase:
<tag>(figure_space\20\P<lowercase>(ut your figure here))
You can probably also use <literal> to put in more, if you need
to.
Not all the examples in the user's guide used the <tag> tag. Some
were done using <literal> within monospaced examples.
patti
|
| 243.3 | Consider this, then reconsider please... | COOKIE::JOHNSTON | | Fri Apr 17 1987 15:24 | 51 |
| Re: .1
Thanx, I tried <literal> and <backslash> and am happy with either.
Re: .2
Using <lowercase> is ok for the particular example I gave; but consider
this:
input
-----
<tag>(figure\Santa Claus In The Year 2000\santa_claus_fig)
vs.
<tag>(figure\S<lowercase>(anta) C<lowercase>(laus)
I<lowercase>(n) T<lowercase>(he) Y<lowercase>(ear) 2000\santa_claus_fig)
output
------
<FIGURE>(SANTA CLAUS IN THE YEAR 2000\SANTA_CLAUS_FIG)
vs
<FIGURE>(Santa Claus In The Year 2000\SANTA_CLAUS_FIG)
I didn't have the time (and admittedly the inclination) the use
<lowercase> in all my examples. As antcipated, several students saw my
incorrect examples and assumed that DOCUMENT converted lowercase to all
uppercase for table, figure, example captions, chapter and head titles,
ad nauseum. I wasn't even through introducing the <figure> tag, let
alone explaining to students that what they saw on the overhead was
misleading and why. They popped the question before I had a chance.
Let me restate my desire to have literal output; it's more than a
personal issue. I was trying to demonstrate DOCUMENT's capabilities to
new users and general interested parties. I had more than 100
overheads. I am certain that many others will be using <tag> for the
same reason, internal as well as customers.
Now let me restate my desire to have literal output to include *all* of
the <tag> arguments (this is contrary to .0). One, because it will
probably be easier for the developers to do this than to isolate one or
two arguments for <tag>. Two, because it's a good one to demonstrate in
overheads that document in not case-sensitive.
Rose
|
| 243.4 | Why did <literal> not work?? | COOKIE::JOHNSTON | | Wed Apr 22 1987 14:07 | 21 |
| Why did <literal> not work in the following example?
<tag>(title\<literal>(Guide To Alaska Atlas) )
The output of this was:
<TITLE>(GUIDE TO ALASKA ATLAS)
Using <lowercase> got what I wanted, e v e n t u a l l y...
<tag>(title\G<lowercase>uide T<lowercase>(o) A<lowercase>(laska)
A<lowercase>(tlas) )
Thanx
Rose
|
| 243.5 | text formatter does uppercasing | CLOSET::ANKLAM | | Wed Apr 22 1987 14:33 | 5 |
|
<literal> doesn't do anything about the case; the uppercasing in
the output of the <tag> tag is performed at the text formatter level.
|
| 243.6 | 2� | CUPOLA::HAKKARAINEN | Crisis? What crisis? | Wed Apr 22 1987 14:54 | 3 |
| One vote, if we're voting, for having the casing of the text as is.
It's particularly crucial, as the earlier notes have mentioned, when
documenting tags.
|
| 243.7 | can do | CLOSET::ANKLAM | | Thu Apr 23 1987 16:46 | 3 |
|
will add to the list of things to do.
|