cris@falc1.ATT.COM (cris) (10/26/88)
I am trying to get Jetroff to work on a 3B2/600 running SVR3.1.1. I am also trying to get this to work on a Laserjet+. First of all, you can compile it for SERIES=1 or SERIES=2 because a Laserjet+ will understand both dots and decipoints. The code as distributed on the net is incorrect for the SERIES=1 case. (The wrong escape sequence is used for decipoints). My problem is this: I can get Jetroff to compile and run clean, but every font I have tried has some specific problems. For example, using jetroff -mm document, the default font (Roman) has trouble with "i", "l", and ligatures of these. Trouble means that the character is printed in the wrong point size, at the wrong location on the page, or not printed at all. Other fonts have other, but similar problems- a missing dash, a missing right paren, etc. Has anybody seen these problems or does anybody have a way to check that the font files I received are, in fact, correct? Any suggestions? Cris Rhea AT&T 3B2 Development (SCSI) att!iwsag!cris -or- att!falc1!cris (312) 979-8179 (human voice)
edf@rocky2.rockefeller.edu (David MacKenzie) (10/26/88)
When I first started working with downloaded fonts (troff2lj, though, not JetRoff), I had problems like the ones you describe - a few errors per font. It turned out that the printer port was expanding tabs and changing returns to newlines, and whenever the binary font data happened to include a tab or return, that bit of the font got corrupted. So I'd check the stty modes on your printer port. ----- David MacKenzie Environmental Defense Fund edf@rocky2.rockefeller.edu (...rutgers!cmcl2!rocky2!edf)
rick@pcrat.UUCP (Rick Richardson) (10/26/88)
In article <122@falc1.ATT.COM> cris@falc1.ATT.COM (cris) writes: >I am trying to get Jetroff to work on a 3B2/600 running SVR3.1.1. >My problem is this: I can get Jetroff to compile and run clean, >but every font I have tried has some specific problems. >Trouble means that the character is printed in the wrong point size, >at the wrong location on the page, or not printed at all. I know of two ways this can happen. One way is a portability bug in the code which was fixed by Patch01. 3B2's are specifically the machines that made the bug show up. Patch01 was previously posted here, and should show up in comp.sources.misc any day now. Also, anon uucp (see signature). The other way this happens is if your line printer spooler is not passing all 8 bits without any additions, deletions, or changes. The symptoms are identical. As far as Series I support goes, I've made a number of changes in that area, but have no Series I to test against. The changes are in Patch02, which hasn't been posted yet, but which can be picked up via anon uucp (see signature). They are also in the Beta 2.1 release that registered users have access to. In fact, Patch02 is waiting for someone, like yourself, to give a little go/no go feedback on Patch02. -Rick -- 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,PEP19200} 12013898963 "" \r ogin: jetuucp