Re: Annoying punctuation in cross-references

[Jo Baer <jbaer@xxxxxxxxxxxxxxxxxxxx>]

Thanks, Thomas. Actually this turned out to be a conversion problem,
which Ed Malick solved for me. The document was converted from
WordPerfect (possibly via Word--I didn't do the conversion) and it
turned out that there were TWO colons after each term: the one that was
converted, and the one applied by Frame as default run-in heading
punctuation. As Ed pointed out, Frame is smart enough to display only
one of the colons, but the "extra" converted one was showing up in the
x-refs. He suggested I do a find and replace, which worked. My x-refs
now look normal. 


> 
> > I have a glossary with the terms formatted as run-in heads with a colon
> > as the default punctuation. (I know that was a terrible sentence; I'm in
> > a hurry.) In some cases, I want to list a term, then send the reader to
> > the "real" or "official" term for the definition, and I want to do it
> > with a real cross-reference. So, what I want is something like
> >
> >     Brupnik: See "Sploitbrau."
> >
> > What I get instead is
> >
> >     Brupnik: See "Sploitbrau:."

Thomas Michanek wrote:
> 
> Here's an odd idea:
> Skip the colon in the run-in paragraph. Instead, define the glossary
> terms as having an autonumbering of ": ". The visual effect will be
> the same, but your cross-refs to the run-ins will be without colon.
> If you need to cross-ref the actual glossary term texts, the
> autonumber will not be included in a cross-ref format using <$paratext>,
> so it shouldn't cause any problems.

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **