On Sat, Sep 11, 2010, Tadziu Hoffmann wrote:
>
> > What's needed is a macro that can be called inline in arg
> > 3 to start underlining, and another macro in arg 4 to stop
> > underlining. Even if ul.tmac could be coerced into behaving
> > this way (I've tussled with it, without success), it seem
On Fri, Sep 10, 2010, Ted Harding wrote:
> I made a serious attempt myself some years ago to try to crack the
> underlining problem. The basic issue, of course, is that .cu, or .ul,
> as you say, simply switches to "underlined font" (which in general
> is italic).
> ...
> One has the feeling that o
> What's needed is a macro that can be called inline in arg
> 3 to start underlining, and another macro in arg 4 to stop
> underlining. Even if ul.tmac could be coerced into behaving
> this way (I've tussled with it, without success), it seems
> to me that the macros in ul.tmac are an awful lot o
On Fri, Sep 10, 2010 at 09:35:54PM +0100, Ted Harding wrote:
> :
> One has the feeling that one could reach out and grasp it, but it
> always seems to be just a few inches further away than the length
> of one's arm ...
“Ah, but a man's reach should exceed his grasp, or what's a heaven for?”
On 10-Sep-10 18:51:22, Peter Schaffter wrote:
> Can someone quickly remind me why .cu for the PostScript device
> can't be made to behave like .cu when it's called for a TTY? In
> other words, it underline glyphs and spaces rather than converting
> text to italics?
>
> Werner's ul.tmac is really
Can someone quickly remind me why .cu for the PostScript device
can't be made to behave like .cu when it's called for a TTY? In
other words, it underline glyphs and spaces rather than converting
text to italics?
Werner's ul.tmac is really clever, but I can't see how to get it to
work in all the c
