Re: translating defined glyphs: docs vs reality

[Dave Kemper]

On 7/17/20, Tadziu Hoffmann <hoffmann@usm.uni-muenchen.de> wrote:
> It may be because you're defining c in terms of itself,
> so you get a (non-terminating) recursive mapping.

Hmm, curious, because it doesn't seem to hold in the general case.
These definitions ought to have the same problem:

.char a dab
.tr ba
bag

But this outputs "daadaag" with no errors or warnings.  And I can
surround the target of this .char definition with \m escapes and it
still works fine.  So something else seems to be going on here.

Thanks for the ideas.  I'll have to keep poking at this.