Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!pcrat!rick From: rick@pcrat.UUCP (Rick Richardson) Newsgroups: comp.text Subject: Re: What features would you like in GNU troff? Message-ID: <780@pcrat.UUCP> Date: 14 Jun 89 11:50:59 GMT References: <742@dtscp1.UUCP> <10959@orstcs.CS.ORST.EDU> <21@nx32s.anduk.co.uk> <779@pcrat.UUCP> <355@wjh12 Reply-To: rick@pcrat.UUCP (Rick Richardson) Distribution: comp Organization: PC Research, Inc., Tinton Falls, NJ Lines: 75 In article <355@wjh12.harvard.edu> bb@wjh12.UUCP (Brent Byer) writes: >In article <779@pcrat.UUCP> rick@pcrat.UUCP (Rick Richardson) writes: >>I want to be able to tell troff that there >>are "holes" in the paper, and to skip the "holes" when justifying >>text: >> This is a test of a >> hole ******** in the >> page ******** being >> skipped magically. >> >>I don't think you can do this with just macros. You'd need a horizontal >>trap. > >Not true. This can be implemented in less than 40 lines of troff. Well, that's a lot of troff. Does it handle the general case, working within *any* macro package? What if there are two holes next to each other? Will a sentence get broken up into three segments across the page? Without seeing your macro to do this, I still stand by my statement that troff itself needs to be modified. I'm sure that lots of people would be interested in this macro, why don't you post it? >>Also, it isn't any great trick to do the actual include of bitmaps. >> >> .BM bitmap_file_name file_type placement > >Yes, this is exactly how Textware's Tplus has done it since late 1986. >And, given that this is on several of the machines at your work (AT&T HO) >location, Rick, I'm pleased that you found the technique enlightening. >( Wouldn't it have been appropriate to give proper credit? ) Brent, I haven't consulted at AT&T for over a year. I never used, nor was I aware of, any bitmap capability in the version of tplus that was available at that site. As far as I know, there is no trademark on the name ".BM" for a macro. I haven't seen yours, and I doubt that mine is the same as yours. Here's mine in case you aren't convinced: '\" '\" .BM filename type resolution justification '\" filename is name of bitmap containing file '\" type is the name of the filter for this type bitmap '\" resolution is 300, 150, 100, or 75 '\" justification is L, R, C, LJ, or RJ '\" .k width of text on current line '\" .d current vertical place '\" .i current indent '\" .o current page offset '\" .l current line length '\" .v current vertical spacing '\" .z current diversion name '\" '\" $Id: tmac.jetroff,v 1.1 88/08/26 23:11:08 rick Exp $ '\" $Log: tmac.jetroff,v $ '\" Revision 1.1 88/08/26 23:11:08 rick '\" Initial revision '\" .nr ## 0 1 .de BM .sy jetroff_bm "\\$1" "\\$2" "\\$3" "\\$4" \\n(.k \\n(.d \\n(.i \\n(.o \ \\n(.l \\n(.v "\\n(.z" >/tmp/jet\\n+(##.\n($$ .so /tmp/jet\\n(##.\n($$ .sy rm /tmp/jet\\n(##.\n($$ .. Yes, all the hairy stuff is computed by a program called jetroff_bm. The source for which is in the comp.sources.misc archives. -- Rick Richardson | JetRoff "di"-troff to LaserJet Postprocessor|uunet!pcrat!dry2 PC Research,Inc.| Mail: uunet!pcrat!jetroff; For anon uucp do:|for Dhrystone 2 uunet!pcrat!rick| uucp jetroff!~jetuucp/file_list ~nuucp/. |submission forms. jetroff Wk2200-0300,Sa,Su ACU {2400,PEP} 12013898963 "" \d\r\d ogin: jetuucp