| It's been my experience that DOCUMENT does not automatically center .tex
files. The easiest way to fix the problem is to simply add the
necessary hard spaces in your .pmd file, and reprocess with picmode.
It might take you several passes to get it right.
Now, a question for you. I'm curious as to why you used an
<include_tex_file> tag to include the .pmd file, rather than the
<include> tag which is probably more appropriate for "markup" purposes.
The code I would use would look like this:
<figure>
<condition>(laser)
<include_tex_file>(file)
<endcondition>
<condition>(line)
<line_art>
<include>(file.pmd)
<endline_art>
<endcondition>
<endfigure>
Does using <include_tex_file>(file.pmd) let you get around using
<line_art> as I do?
Thanx
Rose
|
| >Now, a question for you. I'm curious as to why you used an
><include_tex_file> tag to include the .pmd file, rather than the
><include> tag which is probably more appropriate for "markup" purposes.
oops, just a mistake in my code example, sorry...
actually i just use an <include>(file.PMD) w/o the <line_art>
but... sometimes i run into trouble because of the "<" and ">" characters
in the .PMD, does using the <line_art> tag fix this problem?
lastly, what is a "markup" purpose?
-max-
p.s. hardcoding space into the .PMD might work but it seems to be an awkward
solution. shouldn't any file that's included get aligned according to the
current settings?
|
| >>> but... sometimes i run into trouble because of the "<" and ">"
>>> characters in the .PMD, does using the <line_art> tag fix this problem?
Yes, <line_art> will resolve that problem for you.
>>> lastly, what is a "markup" purpose?
SDML is an acronym for Standardized Document Markup Language, or
something real close to that. It should be described somewhere in
the documentation; probably the UG1 or the Step-By-Step.
The "markup" in the language refers to using tags to label a
particular text element with its proper name. Consider the tags
<emphasis>, <new_term>, and <gref>. They have essentially the same
behavior for final output, italicizing the tag argument (in most
doctypes).
You would use <emphasis> to mark words that you
want to stress because the idea or concept they present to the
reader are important, such as <emphasis>(warning).
You would use <new_term> tag to mark words that are being
introduced to the reader for the first time, such as
<new_term>(hierarchical database).
And you would use <gref> to mark words that will appear in the
glossary, such as <gref>(cardinality). Obviously you get
into a problem when you want to include a <new_term> in the
glossary (do you mark it <gref> instead?) -- but that's another
subject for another note if it ever bothers me enough to get
on a soapbox!
The "markup" is transparent to the reader for final output; the
good philosophy behind it becomes apparent when you have many people
working on many parts of the same document or of the same
document set.
Patti or any of the other developers/documenters are welcome to
qualify or add to anything I've written here; I know they have
tried very hard to stress the concept of a "markup" language.
>>> p.s. hardcoding space into the .PMD might work but it
>>> seems to be an awkward solution. shouldn't any file that's
>>> included get aligned according to the current settings?
Well, picmode is an unsupported tool. Patti has stated that
there are no plans to support it, though she has also stated
that they won't deliberately do anything to make it unusable.
So, for the .tex file to get centered correctly you need to
hard code the spacing in the .pmd file. Code it in one place,
get it in both.
But it does bring up an interesting question: what about plain
old text files used with <line_art> and not depending on any
unsupported tools? Should we have auto centering for these
cases? Someone correct me if I'm wrong, but I think that
<figure_file> centers sixels; it's just the top and bottom that
have to be fiddled with.
Rose
|