I agree with make the bizarre behavior a "compatible" feature.
This discussion explains oddities I never figured out and got out of use
brute force.
Mike
On Tue, Apr 21, 2009 at 08:50:28AM +0200, Werner LEMBERG wrote:
>
> Folks,
> Joachim told me that in the original documentation of the AT&T troff
> the addition
>
> ...but all processing ceases at the next page eject
>
> in the description of the `em' request is missing. He thus suspects
> that this bug has been raised to be a feature; instead of fixing it
> they just documented it.
>
> What do you think about enabling this bizarre behaviour of `em' only
> in compatibility mode? As already mentioned, I can't think of any
> useful application. This would save us from introducing the proposed
> `em1' request.
>
> Werner
--
Mike Bianchi
Foveal Systems
973 822-2085 call to arrange Fax
mbian...@foveal.com
http://www.AutoAuditorium.com
http://www.FovealMounts.com
