From: arnold@skeeve.com (Aharon Robbins)
Subject: [TUHS] licence of ditroff?
Date: Mon, 31 Jan 2005 11:39:37 +0200 [thread overview]
Message-ID: <200501310939.j0V9dbJF027523@skeeve.com> (raw)
Instead of starting with 27 year old code, you'd be better
off taking the troff from http://www.swtch.com/plan9port.
This is a port of many Plan 9 utilities to Unix. The troff there
(a) has an explicit license that will probably do for the BSD people
(b) already knows how to produce PostScript
(c) can handle UTF-8 and 16-bit Unicode
Arnold
> Date: Tue, 26 Oct 2004 12:39:47 +0000 (UTC)
> From: Thorsten Glaser <tg at 66h.42h.de>
> Subject: [TUHS] licence of ditroff?
> To: martinwguy at yahoo.it
> Cc: tuhs at minnie.tuhs.org, miros-discuss at 66h.42h.de
>
> Hi!
>
> I would like to know which licence the files at
> http://medialab.dyndns.org/~martin/tape/stuff/ditroff/
> are under.
>
> If it's http://www.tuhs.org/Archive/Caldera-license.pdf
> that would be nice, if not, is there any way to find
> out whose (c) is on the files, and how to contact them?
>
> Reason: I'm developer of a BSD offspring and already
> integrated 4.4BSD-Alpha nroff, neqn, tbl etc. under the
> Caldera licence above into our operating system in order
> to get rid of the less free, written in C++, GNU groff.
> With success. Now I'm lacking postscript output.
>
> Thanks in advance,
> //mirabile
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
next reply other threads:[~2005-01-31 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 9:39 Aharon Robbins [this message]
2005-01-31 17:50 ` Thorsten Glaser
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 9:01 Aharon Robbins
2005-02-01 9:28 ` Thorsten Glaser
2004-10-26 12:43 Thorsten Glaser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200501310939.j0V9dbJF027523@skeeve.com \
--to=arnold@skeeve.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).