bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #46914] breaking behavior inconsistent within a .ce block


From: G. Branden Robinson
Subject: [bug #46914] breaking behavior inconsistent within a .ce block
Date: Sun, 30 Apr 2023 08:39:12 -0400 (EDT)

Follow-up Comment #14, bug #46914 (project groff):


[comment #13 comment #13:]

> Whether .ce should break input lines as a general rule is the topic of
#60731; the bug you're currently reading is only about the _inconsistency_ in
breaking behavior given specific inputs.  This inconsistency needs to be dealt
with regardless of what #60731 decides groff's general breaking behavior
should be.
> 
> So if you want to make the case that groff should follow AT&T troff .ce
behavior, #60731 is the place to do that.

These might in fact turn out to be the same issue given the point below...

> [comment #12 comment #12:]
> > The request has to know where the "right margin" is (what the
> > line length is) to know where the centerline of the page is.
> 
> Whether that's true depends on whether text is being centered within the
current column or on the page -- a distinction that actually seems to not be
documented in the info manual.  (This should probably be a separate bug
report.)

The formatter has no conception of columns.  There is only a line length.  See
the example in the groff Texinfo manual for how to write your own columnation
macros.

Columns are achieved by manipulating the line length and page offset, making
the former smaller and the latter (progressively) larger, and by `mk` marking
a vertical location on the page and `rt` returning to it to advance to the
next column (at which point the page offset is increased).

> > This ticket should be retitled.  Dave, any suggestions?
> 
> I put a suggestion in the Summary that seems to be to reflect what this
ticket is about, but not being certain what shortcoming you were noticing in
the original Summary, I don't know whether this addresses it.

I'm still at sea too.  Oh well.

I'm sticking with my stance in comment #9 until given a reason to alter it.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?46914>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]