REPLY: 294.fidonet_linux@1:138/397 2ca66b59
MSGID: 2:240/77 6841b0da
CHRS: LATIN-1 2
TID: hpt/lnx 1.4.0-sta 09-04-05
Hello Grant!

04 Jun 25, Grant Weasner wrote to Maurice Kinal:

 GW> In my original post I had chosen 64 columns wide is from the link
 GW> below, so my gopher pages could have enough width left over to pretty
 GW> some of the text with boxes.

This display/format/layout problem is the reason why markup languages have
been invented. For example css within html or markdown on github readme.md
files.

If you are not looking for a one time conversion then text processing workflow
may be a good idea. You could keep two text files, one for easy human editing
and the output of text processing for the gopher files.

troff/groff have its own markup language. For example:
.ll 67
sets the line lenght to 67 chars
.sp 2
insert two blank lines.

The groff system can do macros. Some examples and better than mine
explanations can be found here:

https://www.davebucklin.com/play/2018/03/04/gopher-groff.html

For the manpages format there is an existing macro set called "groff an.tmac"
macro package or man macro package. I think it comes with man usually, because
on my outdated system it can be found with "man 7 man". There are macros for
relative margin indent and indented paragraph macros.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
 * Origin:  Monobox  (2:240/77)
SEEN-BY: 18/200 50/22 103/705 105/81 106/201 124/5016 128/187 129/14
SEEN-BY: 129/305 153/757 7715 154/10 30 110 203/0 218/700 221/0 6
SEEN-BY: 226/30 227/114 229/110 111 114 206 275 300 317 400 426 428
SEEN-BY: 229/470 550 616 664 700 705 240/77 1120 5411 5413 5824 5832
SEEN-BY: 240/5853 5890 263/1 266/512 280/464 5003 291/111 292/854
SEEN-BY: 292/8125 301/1 310/31 320/219 322/757 341/66 234 342/200
SEEN-BY: 396/45 423/120 460/58 256 1124 5858 467/888 633/280 712/848
SEEN-BY: 770/1 902/26 2432/390 2454/119 5020/400 545 5054/30 5075/35
PATH: 240/77 5832 280/464 460/58 229/426