9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: Alexander Shendi <9front@9front.org>
Subject: Re: [9front] [NOOB ALERT] Actually using 9front to write things
Date: Fri, 4 Feb 2022 21:20:08 +0000 (UTC)	[thread overview]
Message-ID: <f0c66dc2-1e03-41b7-adf3-710e7d5db2cb@sirjofri.de> (raw)
In-Reply-To: <C7D6A224-6E01-4DE8-BDDC-E28C540CD3ED@web.de>

Hello again,

04.02.2022 21:41:32 Alexander Shendi <Alexander.Shendi@web.de>:

> Hi,
> So I've sysupdated and recompiled the system for amd64 and 386. I have 
> also compiled minischeme and run some of my scheme programs from 
> OpenBSD.
> Now I need to write things (mainly letters conforming to the german 
> "dinbrief" standard). I guess the tool of choice is troff(1). Is there 
> a good intro or example available? I read 
> <http://helpful.cat-v.org/Blog/2019/12/03/0/>, but the linked 
> repositories aren't available anymore.

I wrote most of my documents in din A4, and I also needed to learn the 

First of all, you need to tell your troff system what's the output of 
your page. This is the line length and the length of your body. Troff 
doesn't really know about the physical paper size, so you don't need to 
use it here.

This will be handled using the postscript converters, eg ps2pdf. Here you 
can give it the actual papersize as a parameter and your troff output 
will be cut to fit the paper.

Let me just look at how I did it in my thesis and I can give you the 
technical details.


  reply	other threads:[~2022-02-05  1:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 20:41 Alexander Shendi
2022-02-04 21:20 ` sirjofri [this message]
2022-02-04 21:30   ` sirjofri
2022-02-04 22:07 ` umbraticus
2022-02-04 22:59   ` Alexander Shendi
2022-02-04 23:23     ` umbraticus
2022-02-04 22:12 ` umbraticus
2022-02-05  7:25 ` tlaronde
2022-02-05 16:03 ` Humm
2022-02-12  4:23   ` Stanley Lieber
2022-02-13 11:33   ` Alexander Shendi

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f0c66dc2-1e03-41b7-adf3-710e7d5db2cb@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --cc=9front@9front.org \


* 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).