On 11.03.25 15:29, Steve Litt wrote: > How do I specify the font size when using groff? It defaults to a very
> small font size. Yep, seems to default to 10p, which is too small for me too. Disclaimer: I began learning about groff, from scratch, last night, so the following is merely the result of study - not checked out in practice. There are several standard macro libraries. One which seems to be not incompatible with general fontified typesetting, up to doing a book, I suspect. It becomes available with the groff parameter "-ms". But even common troff syntax allows setting internal registers, using: .nr reg value # Set reg to value. If reg doesn’t exist, GNU troff creates it. Registers include: \n[PS] # type size of the body text. Default: 10p. Effective: next paragraph. which fills the request, but these might also be of interest: \n[VS] # vertical spacing (type size plus leading). Default: 12p. Effective: next paragraph. \n[LL] # line length, in inches. Effective: next paragraph. \n[PD] # space between paragraphs. Default: 0.3v (1v on low-res devices). Effective: next paragraph. \*[FAM] # font family used. Effective: next paragraph. Default: defined by the output device; often ‘T’ (see ms Body Text) That seems do be some of what you're looking for. There are doubtless other ways to do it, but at my current level, I'm happy to start with one. If you add a "title" line, either as header or footer, it'll default to proportionality, IIRC, but be separately settable. (I was happy to find a simple way to put page numbers into the L, M, or Right part of a title line, just before midnight.) Some others are: \n[PO] # page offset (i.e., the left margin). Effective: next page. \n[LT] # title line length, if different, in inches. \n[HM] # header top margin height. Default: 1i. Effective: next page. \n[FM] # footer bottom margin. Default: 1i. Effective: next page. \*[CF] # center footer text. Default: empty. Effective: next footer. \*[RF] # right footer text. Default: empty. Effective: next footer. There are more at: https://www.gnu.org/software/groff/manual/groff.html.node/ms-Document-Control-Settings.html My plan is to use a few lines of Awk to convert e.g. {this stuff} to italics, by substituting: <- newline .I this stuff <- newline before piping to groff. (If I ever have to escape a real '{', then I'll figure out how to do it.) A few one-minute hacks seem likely to be more than enough to implement a custom markup language with minimal overhead, negligible workflow intrusion, and minimal impact on source text readability. (As opposed to the ugly troff stuff.) ~ -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/62c14413-dad0-4ecd-aa10-b0a89dac6bd3%40localhost.
