On Thu, Feb 20, 2025 at 06:36:29PM -0600, G. Branden Robinson wrote: > At 2025-02-20T19:39:37+0100, onf wrote: > > On Thu Feb 20, 2025 at 5:59 PM CET, Douglas McIlroy wrote: > > > The idea that the argument of .so might contain unquoted spaces is > > > anathema--contrary to groff convention and fortunately not supported. > > > > As far as I know, .so currently doesn't support spaces even when > > quoted. > > That's correct, and true of all troffs known to me. > > GNU soelim has long supported a backslash escaping convention for > spaces, but that convention is not recognized by any known troff, making > for awkwardness; it seems pretty counterintuitive to me to have the `so` > request work differently depending on whether it's soelim or the > formatter that interprets it.
Yeah, I had a lapse of judgement, you and Doug are correct. Would something like .so "/path/to/file with spaces in the name" 2-11 or .so '/path/to/file with spaces in the name' 2-11 be acceptable? My roff-fu is weak these days, I know pic liked double quoted strings but if roff is single quote, that's fine, I don't care. I just know, from supporting software on Windows and Macs, those users sprinkle spaces everywhere. --lm
