The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Toby Thain <toby@telegraphics.com.au>
To: Milo Velimirovic <milov@cs.uwlax.edu>, Angelo Papenhoff <aap@papnet.eu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Reconstructed and newly set UNIX Manual
Date: Sat, 27 Oct 2018 10:56:26 -0300	[thread overview]
Message-ID: <304c9202-18fb-fc61-5a02-7ebe58f10697@telegraphics.com.au> (raw)
In-Reply-To: <D980BC1E-288D-4679-AB86-8028FA5B1E2E@cs.uwlax.edu>

On 2018-10-27 10:07 a.m., Milo Velimirovic wrote:
> 
> 
>> On Oct 27, 2018, at 7:28 AM, Angelo Papenhoff <aap@papnet.eu> wrote:
>>
>> On 27/10/18, Doug McIlroy wrote:
>>>> Now it could be that v7 troff is perfectly capable of generating the
>>>> manual just like older troff would have.
>>>
>>> On taking over editorship for v7, I added some macros to the -man
>>> package. I don't specifically recall making any incompatible
>>> changes. If there were any, they'd most likely show up in
>>> the title and synopsis and should be fixable by a minor tweak
>>> to -man. I'm quite confident that there would be no problems
>>> with troff proper.
>>
>> I didn't mean the macros. They are not problematic at all.
>> It's the idea how much a point is compared to an inch that has
>> changed over time i think.
>>
>> aap
> 
> From my experience in the world of prepress 723pts == 10in.
> 
> Then Adobe unleashed PostScript on us and redefined the point
> so that 72pt == 1in.
> 
> I’m unaware of any other definitions of a point.
> 
> -Milo
> 


 Wikipedia lists historical definitions, but the only definitions I've
used myself are TeX's and PostScript's.

https://en.wikipedia.org/wiki/Point_(typography)

--Toby

  reply	other threads:[~2018-10-27 14:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 11:59 Doug McIlroy
2018-10-27 12:28 ` Angelo Papenhoff
2018-10-27 13:07   ` Milo Velimirovic
2018-10-27 13:56     ` Toby Thain [this message]
2018-10-27 15:19     ` Ralph Corderoy
2018-10-27 15:53 ` Clem Cole
2018-10-27 16:25   ` Larry McVoy
2018-10-27 19:45   ` Lars Brinkhoff
  -- strict thread matches above, loose matches on Subject: below --
2018-10-27 14:18 Nelson H. F. Beebe
2018-10-26 19:46 Angelo Papenhoff
2018-10-26 19:57 ` Jim Capp
2018-10-26 20:41 ` Clem Cole
2018-10-26 21:05   ` Angelo Papenhoff
2018-10-26 21:58     ` Bakul Shah
2018-10-26 20:59 ` Warren Toomey
2018-10-27 17:15   ` Angelo Papenhoff
2018-10-27 17:41     ` Angelo Papenhoff
     [not found] ` <20181026214308.GA20796@minnie.tuhs.org>
     [not found]   ` <20181026221153.GA19920@indra.papnet.eu>
2018-10-26 22:29     ` Angelo Papenhoff
2018-10-26 23:06       ` Warner Losh
2018-10-26 23:46         ` Larry McVoy
2018-10-28 22:57 ` Angelo Papenhoff
2018-10-29  0:15   ` Clem cole
2018-11-01 17:21 ` Angelo Papenhoff

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=304c9202-18fb-fc61-5a02-7ebe58f10697@telegraphics.com.au \
    --to=toby@telegraphics.com.au \
    --cc=aap@papnet.eu \
    --cc=milov@cs.uwlax.edu \
    --cc=tuhs@tuhs.org \
    /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).