Re: (off topic?) Docbook? Re: manlint?

A little late to the party, but I do have some experience here. > I assume the reference to Docbook, which might indeed capsize > like an overweight freighter, but XML is such a simple and robust > form of structuring documents that it's going to outlast us all. I’m not going to pronounce Docbook

Re: (off topic?) Docbook? Re: manlint?

James K. Lowden wrote: >> Complain about Markdown all you will, and use weird-arse corner cases >> to show it?s Bad, but GFM can handle a lot of everyday text. > > If you limit the feature set to what markdown does, -ms macros are > readable too. It's a little tricky to set up an auto-increme

Re: (off topic?) Docbook? Re: manlint?

John Gardner wrote: > Ironically, modern HTML isn't too dissimilar to nroff(1) output. True. Upon seeing HTML for the first time (around 1986 if IIRC) I was struck by the similarities between it and the -mm macros. > … instead of trying to preserve fonts, colours, margins and columns when > g

Re: Learning troff - where to start?

Damian McGuckin wrote: > > The UTP Revival Project recreated the source code because Tim and Sale were > unable to locate a copy of the original source. It is located at: > > http://home.windstream.net/kollar/utp/ > > What an undertaking! > > There is a sentence on that page > >

Re: Learning troff - where to start?

Deri wrote: > The UTP Revival Project recreated the source code because Tim and > Sale >> were unable to locate a copy of the original source. It is located at: >> >>http://home.windstream.net/kollar/utp/ > > > There is a version with clickable contents and index here:- > > https:/

Re: Learning troff - where to start?

> On Oct 16, 2020, at 6:49 PM, Deri wrote: > > On Friday, 16 October 2020 04:23:21 BST Larry Kollar wrote: >>> There is a version with clickable contents and index here:- >>> >>> https://github.com/DeriJames/UTP-1.1/raw/master/utp_book.pdf >> >

"can't transparently output node at top level"

I pulled the latest down, and did “make.” Things went OK until I got down to the documentation: > GROFFcontrib/mom/examples/letter.pdf > troff: contrib/mom/examples/letter.mom:12: error: can't transparently output > node at top level > GROFFcontrib/mom/examples/mom-pdf.pdf > troff: c

UTP Revisited: scoping the project

To be honest, I can’t believe over a fourth of my life has gone by since we started the transcription. Now, with sources where everyone can grab them, maybe we should talk about what we want to do for UTP Revisited. These are just off the top of my head: - Update Chapter 3 to cover Vim (includ

Re: UTP Revisited: scoping the project

Marc Chantreux wrote: > > hello, > >> - Update Chapter 3 to cover Vim (including gvim) > > please don't! > > what's nice about reading UTP is to discover the elegance and simplicity > of it all … > > i'm a vibrant fan of vim but i have to admit that even to me, vim don't > belong to this w

Re: UTP Revisited: scoping the project

Ingo Schwarze wrote: >> I've not used another editor where you can pipe chunks of >> text *ad hoc* through scripts or even awk/perl one-liners. > > That doesn't require vim(1) at all. I do that all the time > with vanilla vi(1), for example "!}fmt" to automatically > line-break a paragraph of

Re: "can't transparently output node at top level"

be > ignored. OK, that’s good. Can you suggest what caused the “unrecoverable error” from Ghostscript at the end of the make run? Thanks, — Larry > ‐‐‐ Original Message ‐‐‐ > Le mardi 20 octobre 2020 06:19, Larry Kollar a écrit : > >> I pulled the latest down, a

Re: [groff] 03/09: tmac/an-old.tmac: Stop remapping ` and '.

John Gardner wrote: > It's called Sun Gallant Demi (or simply "Gallant", as no other weights or > variations of it exist). It's the default console font of SPARC > workstations and SunOS/Solaris; OpenBSD used to use it, until they switched > to a much blander console font

Re: [groff] 03/09: tmac/an-old.tmac: Stop remapping ` and '.

Werner LEMBERG wrote: >>> There's a Linux version too, if you're interested: >>> https://github.com/talamus/solarize-12x29-psf >> >> A pity there’s no OpenType version. > > Attached :-) Bitmap font embedded in a TTF? Looks nice at its native size, anyway. — Larry

Re: What is the difference between GNU groff and Mac OS X groff

Michail Vidiassov wrote: What options are needed to make GNU groff behave the same as Mac OS X groff? > >>> Do >>> export GROFF_NO_SGR=yes >>> in the shell and then try your groff command again. > >> OK. This works. Thanks. >> So, that is the change between 1.19.2 and 1.22.4? > >

Re: [DRAFT] Revised groff ms manual for review

G. Branden Robinson wrote: > Happy Halloween! > > Ready for something on the gory and disturbing side? I got six staples in my head, day before Halloween. They’re out now, but I had a live-action creepshow going for the day. Bring it. :D > I feel like I'm about 40% of my way through a huge u

Re: .EM found missing

\G. Branden Robinson wrote: > > At 2020-11-15T14:13:38+, Dorai Sitaram via wrote: >> UTP strongly hints that the -ms macros have the end-of-input trap .em >> pre-set to a defined macro called .EM, with the implication that if >> the user wants to affect end-of-input behavior they can append

Interesting articles

Sometimes, my Twitter feed coughs up some cool articles, like this one: "Performance comparison: counting words in Python, Go, C++, C, AWK, Forth, and Rust” https://benhoyt.com/writings/count-words/ The Awk solution was by far the shortest by line count. Since the runtime for all the different so

Re: Interesting articles

> On Mar 26, 2021, at 4:03 AM, Ulrich Lauther > wrote: > > On Thu, Mar 25, 2021 at 10:30:57PM -0400, Larry Kollar wrote: >> Sometimes, my Twitter feed coughs up some cool articles, like >> this one: "Performance comparison: counting words in Python, >&g

Re: "point size" is not usable as a term

Thank you, Peter and Keith, for saying what I was about to say, and saying it far better (not to mention “bringing receipts” as the cool kids put it). Everyone I know in the tech writing world uses “point size,” including myself. Sure, when one thinks about it, it’s like saying “inch length.” But

Re: Auto-resize paper size during document run?

James K. Lowden wrote: > >> Of course, I can typeset the table separately and assemble the pdf >> pages by hand, but a solution totally controlled from within the >> groff file would be great. > > Not an answer, but in ancient times, your output would have gone a > printer, which might have had

Re: man-intro (was: getting more out of man pages with less(1) )

James K. Lowden wrote: > Attached is a straw man 1st draft of what an introduction to the man > system might look like. If it clears the threshold of raspberries, > perhaps we can mold it into something useful. > > I think the page should be called man-intro, or intro-man. (Need > help?

Re: [Groff] tbl for html?

> 1. Does anyone have a satisfactory version of tbl that will work with groff > and produce html tables? I wrote an awk script that processes a subset of tbl markup and outputs proper HTML tables. Whether it's satisfactory or not is up to you. ;-) http://home.alltel.net/kollar/groff/htbl.tar.g

Re: [Groff] groff html output, eqn and journals

Frank Jahnke wrote: > I have a paper set in groff, and I wish to submit it to a journal for > publication. Their standard line is to submit in DOC or RTF formats; > needless to say, that is not helpful, particularly since it is full of > differential equations. > > One option that I tried is to

Re: [Groff] problem with current snapshot

Joerg van den Hoff wrote: > I've tried to test the current snapshot (under OSX 10.4.8.). I encountered the > following problems: > > 1.) > contrary to earlier versions, this one did initially _not_ compile due to a > probably > simple problem: > utilities such as `xpmtoppm' which are used dur

Re: [Groff] problem with current snapshot

what seems buggy is the following: I now get "numeric overflow" errors/warnings for each `.PSPIC' call although the generated output looks alright. It has been that way for a long time. I have the Makefile redirect stderr to a file where I can check for stuff that *really* needs to be f

Re: [Groff] eqn plugin for MS Word??

Frank Jahnke wrote: I am writing a highly-technical review article with a colleague who knows only MS Word on the Mac (and so is not particularly computer-savvy). I've agreed to use Word, for which I don't much care, but it seems to be the only way to go at the moment. Of course I am doing

Re: [Groff] Groff editor.

Karee, Srinivas wrote: I care about the font/bold/italics as this is a document which will be sent to the customer and we cannot afford to send a plain text document to customers. Today we are sending a formatted document with all bold headings (multiple subsections), italic content and use

Re: [Groff] Fw: Small bug in groff 1.19.2 footnote number control?

Oh, I also get a segmentation fault in grohtml if I try to convert my wife's thesis to html with -Thtml (in contrast to -Tps). If you're interested, I can provide you with the data files. grohtml works well for me in other uses, but I can believe that my wife's thesis would trigger bugs (it

Re: [Groff] groff Image Formats

Frank Jahnke wrote: What image formats can be used with groff? To date, I have used encapsulated Postscript (.eps) and PSPIC with the -ms macro package, but I am having increasing difficulty doing the conversion of some complex images to eps. Are there alternatives that can be used, like .p

Re: [Groff] groff Image Formats

Gunnar Ritter wrote: > In general, it is rather pointless to request that > groff -Tps accepts images in formats other than EPS > since it would have to convert them internally to > a representation effectively identical to EPS in any > case. Thus, hacking groff to convert images e.g. > using the

Re: [Groff] Groff Version in Debian and [K]ubuntu

Robert Thorsby wrote: Does anyone know why the latest version of groff in Debian and [K] ubuntu is 1.18.1 (incorporating version 1.1.4 of Peter Schaffter's mom macros)? Is there a later deb package available anywhere? for the whole of groff? or for a later, compatible, version of mom? When I

Re: [Groff] Converting man pages to PDF and links

Keith Marshall wrote: I'd guess if you're viewing file:///home/andre/man/man3/malloc.pdf and it has a link to ../man1/vgrind.pdf then that would work? Yep. `.pdfhref L -F path/to/vgrind.pdf -- "text for link hot spot"' The "fun" starts if you want to make this at all general. A q

[Groff] Bug report: interaction between tbl and string variables

Here's a minimal example. See the attached PNG for output. .\" groff -t -ms tblbug.ms >tblbug.ps .\" auto-generated cross-refs .ds xref:controlwaniso:txt Controlling the WAN Isolation State .ds xref:controlwaniso:pg 79 .ds xref:setipv6fwd:txt Setting IPv6 \%Forwarding .ds xref:setipv6fwd:pg 80 .ds

Re: [Groff] Bug report: interaction between tbl and string variables

Ralph Corderoy wrote: It's something to do with tbl not correctly copying the whole string register name into the troff output. ... [example deleted] ... Given tbl is a preprocessor and looks at the text you give to work out alignment, it's probably not surprising? I suppose tbl's logic coul

Re: [Groff] Bug report: interaction between tbl and string variables

Werner LEMBERG wrote: Indeed. tbl sees that you want to format a numeric field, but you don't give numbers but string registers. To align numbers on the decimal point it has to interpret the number since this must be done by tbl itself, and during this process the string register name gets tr

Re: [Groff] spaces in file names

Werner LEMBERG wrote: how does, say, .so foo bar.ps behave in other troff versions? With groff, it currently tries to load `foo', ignoring the rest of the line. To be more precise, it is impossible to have a space within a file name at all! Basically, all other requests are affected too

Re: [Groff] Why is it...

I've been watching & reading, waiting until I had a little time to say my piece Part of the issue is that *roff languished as a proprietary software package for far too long. The Free world developed several subsets, usually with -ms or -man (or some completely different thing) hard-

Re: [Groff] spaces in file names

Werner LEMBERG wrote: I wonder whether this should be changed to the behaviour of the least surprise so that `foo bar.ps' gets loaded instead. It's bitten me before, although I never mentioned it. I'd like if it recognized the `\ ' construct, the same way most *nix shells escape spaces in fil

Re: [Groff] How to switch off line filling?

Dan H wrote: As my job frequently requires me to write highly structured, long emails, I’ve discovered groff to be the perfect tool for me. This email is an example of how I use groff with the mm package (because it is, as far as I know, the only one that offe

Re: [Groff] Eqn trouble in 1.19.2 on a new Mac Pro

Robert Marks wrote: > Never seen anything like this -- suggestions? > > Input file testeq: [snip] My suggestion would be to compile groff from CVS and install over the shipped version. The magic incantation on OSX: ./configure --mandir=/usr/share/man --prefix=/usr make sudo make install The

Re: [Groff] Fw: groff and Vista privileges

> ... I just got an new Dell XPS laptop with Vista. On > this machine with this operating system I cannot get > groff to complete. ... > I think that the program is trying to write > intermediate files in the C:/ directory. Groff does generate some temporary files. I'm not sure how the enviro

Re: [Groff] New PS Fonts package

Michail Vidiassov wrote: > given the Unicode capabilities of the upcoming 1.19.3 it would be nice to > create a set of fonts descriptions for some family of "unicode" fonts > (with most of the glyphs groff can typeset - extended latin and cyrillic) > and, may be, > include it as an optional or

Re: [Groff] Fw: groff and Vista privileges

John W. Smay wrote: Your reply looked like just the ticket, so logical ... but after defining GROFF_TMPDIR and noting that the others you mentioned in the docs were already defined in places I have no trouble writing, still no go !! smay7% pwd C:/Users/jws/jws.t smay7% echo $HOME C:/U

Re: [Groff] Fw: groff and Vista privileges

John W. Smay wrote: After a week of thrashing I have found Vista's User Access Control (UAC) and that it can be disabled. This allowed all my gnu programs, groff.exe, enscript.exe, to run satisfactorily, but of course disables this important security of Windows Vista. 8-o Kind of like

Re: [Groff] Program Bugs

Werner LEMBERG wrote: The two programs, groff.exe and enscript.exe would not run under user logins on Vista, producing errors of "Permission Denied" and " .. requies elevation." [...] This has been discussed recently on the list. Please look it up. Since groff creates temporary files it

[Groff] Another tbl tip - conditional rows

If you have a row in a table that you want to include only when a condition is met, you need to add a "\c" to the end of the if statement: .TS box tab(#); cb cb l l . Name#Description _ NORMAL#No special features. NCS#Uses NCS. .if \n[SIP] \{\c SIP#Uses SIP. .\} EURO#Special load for Europe.

Re: [Groff] vim syntax file for groff -- treatment of .ig

Dorai Sitaram wrote: This is for Alejandro Lopez-Valencia, if he's still fielding reports on his very useful and tasteful nroff.vim syntax file. This synax file currently highlights a .ig environment as a comment, but assumes that the .ig will always be closed by a double- dot (..), even

Re: [Groff] Headers with text and images

Louis Guillaume wrote: > So far I have had very good success formatting my documents the "normal" > ms-macro way using .TL etc., putting my logo above the .TL with .PSPIC. > Like this... > > .PSPIC mylogo.eps 2in > .TL > .nf > .LG > PROPOSAL > > \f(BIREAL TITLE HERE\fP > .SM > > ETC ETC. >

Re: [Groff] Fw: problem with pic

> I'm forwarding this bug report to the list here; can someone please > test grap with non-GNU pic? > > Ted, have you ever tried to run grap with, say, Dwight's dpic? What > about heirloom's pic implementation? Aha... that might explain the problems I was having with grap when I tried it yeste

Re: [Groff] groff as a wiki langauge?

Zhang Weiwu wrote: It's not clear to me why you get such bad formatting results. Partly because it's difficult to strip away the non wiki content from the web page (navigation bar, advertisement on the corner, "feed back" input textarea); If the wiki structures the HTML properly, all the vari

Re: [Groff] Changing font in ".FG"

Randall Allemang wrote: I am a casual user of release 1.18 and would like to change the font in the figure title macro ".FG" . it is currently Times Roman and the normal font registers used by headings and other macros don't seem to have any effect. I have read through the pertinent section

Re: [Groff] eqn troubles

Try recompiling from source. I know there was an issue in the 10.2 days, but they might still be around. I think the end of the PROBLEMS file has the magic words to make good OSX binaries. -- Larry Sent from my iPhone On Sep 29, 2008, at 9:22 AM, Miklos Somogyi <[EMAIL PROTECTED]> wrote:

[Groff] Bug in soelim

The manpage for soelim (and groff) says of the -I option: "specify a directory to search for files (both those on the command line and those named in .so requests). The current directory is always searched first." Reality (with foo.ms in the current directory and in /usr/share/groff/site-tmac/

Re: [Groff] .als problem

Werner LEMBERG wrote: "With other words" is a direct translation of the German idiom. It seems stilted in English, where the idiomatically correct expression is "In other words". Aah, I wasn't aware of this, thanks! Don't sweat it; your English is better than that of many native speakers

Re: [Groff] Bug in soelim

Werner LEMBERG wrote: Is there a workaround I can use to force groff/soelim to read foo.ms in the current directory? I'm very sorry about this, it's a documentation error on my side -- I've never touched the logic of the related source code. No problem, I realized after sending my report th

Re: [Groff] groff lacks lbl - I found the sources

\Maybe lbl can even be included in the groff suite, The NOTICE file says: | Permission is hereby given for its free reproduction and modification | for non-commercial purposes, provided that this notice and all embedded | copyright notices be retained. Commercial organisations may give

Re: [Groff] Line continuation

Miklos Somogyi wrote: When one needs to break a long line, the continuation needs to start at the beginning of the next line. This spoils the readability of the file. I would like to have something like this: xxx \X ww where \X woul

Re: [Groff] blm blues

Miklos Somogyi wrote: I am trying to produce a macro for request blm that would set space as a given fraction of the current vertical spacing. I did the following: --- .de blank . nr blankreg (c;\\$1) this wo

[Groff] Signaling diagrams?

Is there a program to generate signdling diagrams out there? I sure could use one right now -- Larry

Re: [Groff] Signaling diagrams?

Jon Snader wrote: Is there a program to generate signdling diagrams out there? I sure could use one right now What kind of signaling diagrams? Trains, cells, ...? For some applications, I've found Graphviz makes an excellent front end to pic (or you can generate ps, etc. directly).

Re: [Groff] Signaling diagrams?

Ted Harding wrote: Is there a program to generate signdling diagrams out there? I sure could use one right now What kind of signaling diagrams? Trains, cells, ...? For some applications, I've found Graphviz makes an excellent front end to pic (or you can generate ps, etc. directly). Telep

Re: [Groff] Creating Word/rtf output

Robert Goulding wrote: ... this isn't so different from opening up the HTML in OpenOffice, changing the HTML "styles" to standard document files and then saving as an rtf/doc. Indeed, that's the way I've handled requests for a "Word version" of docs at work. I've set up my macros to spit ou

Re: [Groff] Adding bookmarks to custom macro

Scott Moore wrote: i am wondering how to translate the pdfmark syntax into a custom macro that serves to create the bookmark pane and a table of contents, with the option to link within the TOC to the page view. I have been through the docs, looked at the samples, and am one degree, argueably,

[Groff] Translations

One of the manuals I maintain in my day job is in groff, and (to my surprise) I had to have it translated. The translators managed to not muck up things *too* badly -- there were a few lines that got run together in error and a couple macro and cross-ref names that got translated, but they

[Groff] Re: Translations

I've attached a tar file containing es.tmac, along with the (converted to Latin-1 encoding) hyphen.es - thanks, Werner, for the help! I converted the encoding using: % textutil -inputencoding utf-8 -encoding Latin1 -stdout -cat txt hyphen.es (Textutil seems to be a MacOSX command line utility,

Re: [Groff] inability to process german umlauts

Jan-Herbert Damm wrote: I like to use "groff -mom" for typesetting. Recently i set up a new system changing the locale from iso-8859-1 to utf8. I use vim to write texts. German umlauts now produce the following errormessages: Try adding the -k option to groff. This calls the preconv pr

Re: [Groff] Re: Mysteries of .em request

Werner LEMBERG wrote: ... my summary of the whole issue is that I'll probably implement an `.em1' request which doesn't have this silly restriction -- or can someone name any reason for this bizarre behaviour of `.em'? I'm guessing the original intent and assumption for .em was to make sure

Re: [Groff] multiline footer?

Joerg van den Hoff wrote: currently I try to get a multiline footer at the page bottom (in my case only on page one but it could be a running footer, too). I'm using the `ms' macros. I tried to modify the BT macro as such: .de BT .if \\n%=1 \{\ . sp -2v . so footer.tbl . bp \} .ie o .tl

Re: [Groff] Typesetting Software

John¹ wrote: > Many years ago, when type used to be set by hand, I was one of those who > did the typesetting. I am now looking at the methodology of using either > Groff or LaTex to produce print ready text. Can anyone briefly tell me if > Groff does the same job as LaTex? > > Obviously there wi

Re: [Groff] Typesetting Software

Joerg van den Hoff wrote: >>> groff is a single pass formatter, LaTeX is multi-pass. >> >> Not sure what you mean by this, but groff and TeX are >> pretty much the same in this regard. Both are single-pass >> formatters... both require multiple >> invocations to enable forward references at all.

Re: [Groff] Setting pdf document properties

brian m. carlson wrote: Page Extraction: Not Allowed Commenting: Allowed Printing: High Resolution Changing the document: Not Allowed As a practical matter, these settings are ignored (or can be ignored) by many non-Adobe viewers. Therefore, setting them is merely an inconvenience that ir

Re: [Groff] PDF navigation hyperlinks

Ken Smith wrote: Is there a way to conditionally define the .XN macro so that, when I'm building my HTML document, it is a no-op that returns its arguments verbatim to be considered as content? Something like this should work (I haven't tested): .rn XN XN-old .de XN .ie '\*[.T]'html' .nop \\

[Groff] Typesetting humor

http://www.roguedesigns.ca/blog/wp-content/uploads/2009/06/i-shot-the- serif.jpg -- Larry

Re: [Groff] gro html problem

Chuck Robey wrote: I was told this is the best place to ask grohtml questions ... I'm having problems, The macro set I use is mm (please don't just tell me to use ms, I LIKE mm), but a fairly basic thing in there doesn't seem to be working: the use of the list macros, like the .AL/.LI/.LE

Re: [Groff] grohtml

Chuck Robey wrote: > ... I was > stating that I have no problem whatsoever with the mm macros when they're > going > to postscript or ascii, but when I have them as html output, the mm list > macros > show up very, very, badly. It looks like there isn't any leading spacing > allowed after I u

Re: [Groff] A little Greetings card

Jan-Herbert Damm wrote: > I removed trailing whitespace saved as "picture" and processed simply with > groff picture > picture.ps > > it shows some text and some ellipsises, probably not what is intended. > > Sorry for this ignorant novice question: > How do I invoke groff correctly for this

[Groff] node.cpp needs patch?

Environment: MacOSX 10.4.11 (Intel), gcc 4.0.1 I'm not a c++ expert in the least, but I couldn't get the CVS (from an hour ago) to compile without getting rid of the "inline" keyword from node::~node() as follows. Is this a problem on my end? -- Larry Index: src/roff/troff/node.cpp ==

[Groff] A few misc. patches

A little housekeeping, mainly. Some of this stuff was kicking around for a while & I'd forgotten to submit it. -- Larry PROBLEMS: some OSX solutions and tips. tmac/www.tmac: turn on orphan control for list items. contrib/hdtbl/groff_hdtbl.man: added a missing @ to "@MAN1EXT" instance. Index: P

Re: [Groff] groff on Intel platform

Miklos Somogyi wrote: I upgraded my old PPC with a new iMac 'cause I need Snowleopard. However, I don't have working gs gv groff etc. anymore. They could have been on the computer in Intel forms, but I used the Migration Assistant to copy my things over, and PPC software may have overwritten

Re: [Groff] mmhtml.tmac with Werner's fixes

Chuck Robey wrote: Mike, I had a local computer emergency, had to rebuild a bunch of stuff (which I like doing anyhow) so I didn't get down to fixing this until today. I found that I only needed to replace every instance of .HTML with the no- spacing version, .HTML-NS, and that seems to ha

Re: [Groff] node.cpp needs patch?

brian m. carlson wrote: I'm not a c++ expert in the least, but I couldn't get the CVS (from an hour ago) to compile without getting rid of the "inline" keyword from node::~node() as follows. Is this a problem on my end? This has been reported several times. For some reason, Mac OS X has a

[Groff] A large hdtbl patch

I started fidding with the hdtbl macros, to see whether I could use them in place of tbl syntax, and have run into several issues. The attached patch does some serious hacking, so Joachim might need to bless this before committing it. The biggest change is to hdmisc.tmac. I broke out all th

Re: [Groff] A not strictly groff question

I use vi/vim and have lots of map commands in my .exrc file, however, I never used the "ab" abbreviation capability. I didn't have any wisdom to contribute, but this *did* prod me to have a look at what "ab" is capable of, and I created several very useful things for my own work. So thank

[Groff] Another hdtbl patch

Actually, to "groff_hdtbl.man" to include details about what needs to be initialized before creating tables. -- Larry groff_hdtbl.man.patch Description: Binary data

[Groff] New tbl warnings in CVS version

I'm now seeing warnings like this when I runoff a manual containing tbl tables that use the "expand" global option: ./Installation.ms:3: warning: numeric expression expected (got `i') warning: around line 35: table wider than line width warning: around line 35: table squeezed horizontally to fit

[Groff] Link to "flo" manual

I thought some of us were looking for this a while ago. I found a link: http://se.uwaterloo.ca/~dberry/FTP_SITE/reprints.journals.conferences/flo.conference.paper.pdf -- Larry

Re: [Groff] New tbl warnings in CVS version

Denis M. Wilson wrote: > I would support making tbl warnings optional, > to be in line with troff, and other reasons, > for example if a table is deliberately wider > than the line width. A new flag -w to enable > warnings? I was thinking maybe a global option like "nowarn" -- the warnings are

[Groff] www.tmac patch

This fixes a bug in -mwww where a long ordered list has item 10 incorrectly indented. I think that's all of my patches... for now. ;-) -- Larry Index: www.tmac === RCS file: /sources/groff/groff/tmac/www.tmac,v retrieving revision

Re: [Groff] Another hdtbl patch

Werner LEMBERG wrote: Actually, to "groff_hdtbl.man" to include details about what needs to be initialized before creating tables. Thanks! However, documentation of the `pv' macro is still missing. Honestly, I'm not really happy about pv's strange calling sequence to use it for initializatio

[Groff] Re: once more hdtbl

Joachim Walsdorff wrote: thanks for spending your time to improve hdtbl. It's a good idea to seperate hdtbl- and example stuff into hdmisc.tmac respectively common.roff. But some little things now seem to be wrong. 1) In fonts_x.in und fonts_n.in: .so examples/common.roff is missing. Fix

[Groff] Toward a convention for namespaces

Mike Bianchi wrote: On Wed, Feb 03, 2010 at 02:08:47PM -0500, Larry Kollar wrote: : This actually brings up something that has been bugging me for a while, and I think deserves its own thread: we should come up with some namespace guidelines for macro packages, especially for

Re: [Groff] New tbl warnings in CVS version

Werner LEMBERG wrote: I was thinking maybe a global option like "nowarn" -- the warnings are generally useful, but once a particular table has been debugged you wouldn't want to hear from it again. This should be quite easy to implement, and I would include it into groff if someone (you?) is

Re: [Groff] New tbl warnings in CVS version

Werner LEMBERG wrote: > > I'm seeing these warnings in tables that *aren't* breaking the right > > margin as well as ones that are. > > Hmm. Perhaps the overshoot is very small, thus not visible to the > eye? Perhaps I can add some user-controlled fuzziness (similar to > TeX). If you don't t

[Groff] tbl patch - add global "nowarn" option

Figured out my obvious logic error, this works now. Please test. -- Larry tbl.patch Description: Binary data

[Groff] Drop shadows in pic

I looked for "drop shadows" in the archives, and didn't see anything. Is there an easier way to do them than to lay down the shadows first, then draw more boxes on top of them like this? .PS 4i .ft HB .ps -1 linethick=1; # lay down drop-shadows first box wid 2 ht 1.5 color "slateblue"; move to

[Groff] Another namespace issue (tbl vs. hdtbl)

Multi-page tbl tables don't like getting hdtbl pulled in -- both of them use .TH and groff hangs at the first tbl usage of .TH. Yes, there are situations where you might want to mix tbl and hdtbl tables in a single document -- for example, in a transition from one to another, or you might m

Re: [Groff] Extending .tm to allow for file handles

Tom Borawski wrote: I was wondering if their is any possibility having .tm write to anything other than STDOUT ? It would make managing forward references (when used with 2 groff passes) much easier. In my Makefile, I use 2> to redirect stderr to a file: groff $(FLAGS) -rTocGen=1 -z

Re: [Groff] A question about vertical indentation of displays

Werner LEMBERG wrote: Secondly, I couldn't find where the DD register is documented. It's present neither in the MS man page nor in the groff online manual... Agreed; there needs to be an entry in the "Document control registers" section of 'man groff_ms' (which does have an entry for PD, etc

[Groff] Horizontal positioning, .nr vs \R

I have some long headings that run two, sometimes three, lines in my table of contents. The heart of the macro I'm using to set these lines looked like: . ie (u;\w'\\$*'+\\*[ind:0])>(u;\\n[toc:colwid]-0.25i) \{\ . ll (u;\\n[LL]-0.25i) . nop \\$* . nr toc:horiz \\n[.k] . ll \\n[LL]u

Re: [Groff] Hanging headings in MS

On Mar 31, 2010, at 6:04 AM, Anton Shepelev wrote: Hello all, Is it possible to modify the MS macro package (by adding some macro (re)defintions) so it would make all headings stick out to the left by the same abount of space? 1. Heading One text text text text ... I can emulate such

<    1   2   3   4   >