* [TUHS] Re: formatting 1981 troff today?
[not found] ` <20250721121530.2894F21F15@orac.inputplus.co.uk>
@ 2025-07-21 13:16 ` Larry McVoy
2025-07-21 15:10 ` arnold
0 siblings, 1 reply; 4+ messages in thread
From: Larry McVoy @ 2025-07-21 13:16 UTC (permalink / raw)
To: Ralph Corderoy; +Cc: tuhs
On Mon, Jul 21, 2025 at 01:15:30PM +0100, Ralph Corderoy wrote:
> Hi Arnold,
>
> > > Could you use a late-edition Unix as an alternative?
> >
> > No, I don't have any kind of SimH setup and that's overkill.
> > In particular I want to be able to use Git so that I can make changes
> > if necessary.
>
> I was thinking the native makefile would update a disk image, then have
> the simulated system mount that ???disk???, run the hosted make, and
> unmount. Or any other means to sync the native files to the old system
> just for the build step.
>
> But I agree that could be a faff if you just want to get the book built.
> Heirloom's a good starting place.
Have you just tried groff? I'm guessing you have, it produced something,
but you are not sure it is correct?
For me, groff tends to just work.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [TUHS] Re: formatting 1981 troff today?
[not found] <202507211104.56LB4eZn016130@freefriends.org>
[not found] ` <20250721113945.95EBB22010@orac.inputplus.co.uk>
@ 2025-07-21 14:10 ` Clem Cole
1 sibling, 0 replies; 4+ messages in thread
From: Clem Cole @ 2025-07-21 14:10 UTC (permalink / raw)
To: arnold; +Cc: tuhs
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
On Mon, Jul 21, 2025 at 7:04 AM <arnold@skeeve.com> wrote:
> I will be working on Linux, Ubuntu 24.04.
>
Can't speak for Linux, but the original ditroff kit from AT&T troff
toolchest and the original Adobe transcript just compiled on macOS the last
time I tried.
That said, I have mostly switched to groff as Larry mentioned, but I have a
couple of things that I don't want to introduce artifacts, and when I did
that, I always used the real thing.
One thing to be careful of is that if you are creating PS (or later PDF),
you might want to consider transcript, although later versions of ditroff,
AT&T included dpost(1troff). Depending when the book was built, the
original AT&T ditroff tables only supported the Meganthaler, the APS5 and
/C/A/T and you needed to purchase Transcript from Adobe to get the psdit()
command and the tables [At Masscomp to cut down on support at the time, we
ate the binary redistribution for both and just included them both as our
standard troff kit].
Groff added -Tpdf, which is lacking in Transcript, but PS was de rigre in
those days, particularly with Display PostScript, so systems like macOS's
"preview" could open them directly [not so today]. You need Acrobat or a
replacement to convert [again today, I use ps2pdf from Ghostscript, but
again for things that I want as close to the original as possible, I leave
them as -Tps from ditroff and psdit.
Clem
[-- Attachment #2: Type: text/html, Size: 2804 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* [TUHS] Re: formatting 1981 troff today?
2025-07-21 13:16 ` [TUHS] Re: formatting 1981 troff today? Larry McVoy
@ 2025-07-21 15:10 ` arnold
2025-07-21 16:41 ` Dan Cross
0 siblings, 1 reply; 4+ messages in thread
From: arnold @ 2025-07-21 15:10 UTC (permalink / raw)
To: ralph, lm; +Cc: tuhs
Larry McVoy <lm@mcvoy.com> wrote:
> On Mon, Jul 21, 2025 at 01:15:30PM +0100, Ralph Corderoy wrote:
> > Hi Arnold,
> >
> > > > Could you use a late-edition Unix as an alternative?
> > >
> > > No, I don't have any kind of SimH setup and that's overkill.
> > > In particular I want to be able to use Git so that I can make changes
> > > if necessary.
> >
> > I was thinking the native makefile would update a disk image, then have
> > the simulated system mount that ???disk???, run the hosted make, and
> > unmount. Or any other means to sync the native files to the old system
> > just for the build step.
> >
> > But I agree that could be a faff if you just want to get the book built.
> > Heirloom's a good starting place.
>
> Have you just tried groff? I'm guessing you have, it produced something,
> but you are not sure it is correct?
>
> For me, groff tends to just work.
For me too. I haven't tried anything yet. My gut feel is that using
original troff will be the fastest path, but I may try groff.
As to Plan 9 troff, I don't have a Plan 9 system, and don't want to
spend the time right now to climb that learning curve.
Thanks everyone,
Arnold
^ permalink raw reply [flat|nested] 4+ messages in thread
* [TUHS] Re: formatting 1981 troff today?
2025-07-21 15:10 ` arnold
@ 2025-07-21 16:41 ` Dan Cross
0 siblings, 0 replies; 4+ messages in thread
From: Dan Cross @ 2025-07-21 16:41 UTC (permalink / raw)
To: arnold; +Cc: tuhs
On Mon, Jul 21, 2025 at 11:17 AM <arnold@skeeve.com> wrote:
> For me too. I haven't tried anything yet. My gut feel is that using
> original troff will be the fastest path, but I may try groff.
Heirloom is certainly a viable way to go to start.
> As to Plan 9 troff, I don't have a Plan 9 system, and don't want to
> spend the time right now to climb that learning curve.
I can appreciate that, but just a quick reminder about and a small
plug for "Plan 9 from Userspace", where most of the libraries and
tools have been ported to Unix-y style systems, including troff and
the associated pieces: https://github.com/9fans/plan9port/
- Dan C.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-07-21 16:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <202507211104.56LB4eZn016130@freefriends.org>
[not found] ` <20250721113945.95EBB22010@orac.inputplus.co.uk>
[not found] ` <202507211152.56LBqGD2019247@freefriends.org>
[not found] ` <20250721121530.2894F21F15@orac.inputplus.co.uk>
2025-07-21 13:16 ` [TUHS] Re: formatting 1981 troff today? Larry McVoy
2025-07-21 15:10 ` arnold
2025-07-21 16:41 ` Dan Cross
2025-07-21 14:10 ` Clem Cole
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).