On Sun, Feb 23, 2025 at 8:52 PM G. Branden Robinson
wrote:
> At 2025-02-24T03:36:28+0100, onf wrote:
> > I think the point is that such filenames aren't being used,
>
> No, that's not "the point". It's _your_ point,
Hey, originally it was *my* point :-P
> > so breaking compatibility (and making
On Sun, Feb 23, 2025 at 9:41 PM G. Branden Robinson
wrote:
> Please refrain from offering advice in areas beyond your expertise, at
> least without admitting the same.
>
> You're getting into Bjarni territory here. (That's the groff
> community's version of the Dunning-Kruger syndrome.)
This com
At 2025-02-23T20:13:59+0100, onf wrote:
> Removing the -ms makes the issue disappear. The issue must originate
> in ms's definition of the TS macro,
No.
> since adding
> .ds TS
>
> at the beginning of the document fixes the issue even when -ms is
> included.
>
> By the way, your table data in
Hi Francesco,
At 2025-02-23T19:00:17+0100, Francesco Ariis wrote:
> a question about table width and line width.
>
> Attached is an MRE which displays my problem, which you can
> run with `groff -ms -t -Tpdf test.ms > out.pdf`
>
> In the document:
> 1. line width is set to 17cms
> 2. I inser
At 2025-02-24T03:36:28+0100, onf wrote:
> On Mon Feb 24, 2025 at 2:36 AM CET, G. Branden Robinson wrote:
> > [...]
> > My lodestar on this point is that we can use C and the shell to create
> > files named with trailing spaces, so there's no reason *roff, as a bona
> > fide programming language, sh
On Mon Feb 24, 2025 at 2:36 AM CET, G. Branden Robinson wrote:
> [...]
> My lodestar on this point is that we can use C and the shell to create
> files named with trailing spaces, so there's no reason *roff, as a bona
> fide programming language, shouldn't be capable as well--as long as it's
> not
At 2025-02-24T02:44:35+0100, onf wrote:
> On Mon Feb 24, 2025 at 1:09 AM CET, G. Branden Robinson wrote:
> > [...]
> > diff --git a/src/roff/troff/input.cpp b/src/roff/troff/input.cpp
> > index 2656ff236..cf750bc73 100644
> > --- a/src/roff/troff/input.cpp
> > +++ b/src/roff/troff/input.cpp
> > @@
On Mon Feb 24, 2025 at 1:09 AM CET, G. Branden Robinson wrote:
> [...]
> diff --git a/src/roff/troff/input.cpp b/src/roff/troff/input.cpp
> index 2656ff236..cf750bc73 100644
> --- a/src/roff/troff/input.cpp
> +++ b/src/roff/troff/input.cpp
> @@ -6405,12 +6405,14 @@ void line_file()
> {
>int n;
[re-titling sub-thread again]
At 2025-02-22T17:59:10-0600, Dave Kemper wrote:
> I still suspect that that benefit stands even if the file-opening
> function is modified to chop trailing spaces from the name. That
> would prevent groff from opening a file named "trailing space ", but
> any real-wo
At 2025-02-23T23:52:07+0100, onf wrote:
> I would argue that the fact the second argument to lf is not used by
> groff to access the file system doesn't change its semantics of being
> a filename. Especially since soelim emits lf requests for all the .so
> calls it replaces, meaning that whatever
At 2025-02-23T17:23:35+0100, Benno Schulenberg wrote:
> > Regarding the hyphenation problem, the lump in the carpet moves
> > after groff 1.22.4. Because HTML output now produces −
> > entities rather than hyphens from *roff minus special characters
> > (`\-`), [...]
>
> Ouch! I don't like the l
On Sun Feb 23, 2025 at 11:38 PM CET, G. Branden Robinson wrote:
> At 2025-02-23T21:21:37+0100, onf wrote:
> > For all the other requests which use filenames (hpf, hpfa, lf -- am I
> > mistaken, or did we forget about lf? --, nx, so), it treats spaces as
> > an argument separator.
>
> No, I didn't f
At 2025-02-23T21:21:37+0100, onf wrote:
> For all the other requests which use filenames (hpf, hpfa, lf -- am I
> mistaken, or did we forget about lf? --, nx, so), it treats spaces as
> an argument separator.
No, I didn't forget about `lf`. See comment #0 ("original submission")
to Savannah #6510
At 2025-02-23T20:22:38+0100, onf wrote:
> On Sun Feb 23, 2025 at 5:23 PM CET, Benno Schulenberg wrote:
> > > Regarding the hyphenation problem, the lump in the carpet moves
> > > after groff 1.22.4. Because HTML output now produces −
> > > entities rather than hyphens from *roff minus special char
On Sun Feb 23, 2025 at 1:50 PM CET, Dave Kemper wrote:
> On Sat, Feb 22, 2025 at 7:29 PM onf wrote:
> > I won't mind too much if this change ends up in groff as it's
> > currently being proposed. I would just find it unfortunate, because
> > I am pretty sure neatroff won't adopt it as it currently
Hi Benno,
On Sun Feb 23, 2025 at 5:23 PM CET, Benno Schulenberg wrote:
> > Regarding the hyphenation problem, the lump in the carpet moves after
> > groff 1.22.4. Because HTML output now produces − entities rather
> > than hyphens from *roff minus special characters (`\-`), [...]
>
> Ouch! I don
Hi Francesco,
On Sun Feb 23, 2025 at 7:00 PM CET, Francesco Ariis wrote:
> Attached is an MRE which displays my problem, which you can
> run with `groff -ms -t -Tpdf test.ms > out.pdf`
>
> In the document:
> 1. line width is set to 17cms
> 2. I insert a table and would like it to fill the whole 17
Dear groff users,
a question about table width and line width.
Attached is an MRE which displays my problem, which you can
run with `groff -ms -t -Tpdf test.ms > out.pdf`
In the document:
1. line width is set to 17cms
2. I insert a table and would like it to fill the whole 17cms
3. this does
Hello Branden,
Regarding the hyphenation problem, the lump in the carpet moves after
groff 1.22.4. Because HTML output now produces − entities rather
than hyphens from *roff minus special characters (`\-`), [...]
Ouch! I don't like the look of them on the HTML page: they are
"enormous", loo
On Sat, Feb 22, 2025 at 7:29 PM onf wrote:
> I won't mind too much if this change ends up in groff as it's
> currently being proposed. I would just find it unfortunate, because
> I am pretty sure neatroff won't adopt it as it currently stands.
I'm in favor of cross-roff compatibility whenever pos
On Fri, Feb 7, 2025 at 3:06 AM G. Branden Robinson
wrote:
> At 2025-02-06T23:23:57-0600, Dave Kemper wrote:
> > The info file documents it the same way it documents everything else:
> > any attribute associated with an environment has this association
> > explicitly stated; attributes without this
21 matches
Mail list logo
