[bug #64501] grohtml(1): confusing sentence in "Bugs" section

[G. Branden Robinson]

Follow-up Comment #7, bug #64501 (project groff):


[comment #6 comment #6:]
> [comment #5 comment #5:]
> > [comment #4 comment #4:]
> > > the user might want lines in the HTML source broken in
> > > reasonable places for easier handling in a text editor.
> > 
> > But that's not the source form of the document, so why
> > would they bother?
> 
> Who can understand the inscrutable actions of users?
> 
> But point taken; a more realistic reason might be for easier viewing in
"less".  Sometimes it's a little easier to work with lines of manageable
length, and if the HTML renderer doesn't care, why not let groff generate the
easier-for-humans thing?

I agree, but it's a value-add.  Not necessarily to be postponed until
everything "more important" is done, but a task to be snatched when it
promises to be easy to resolve.
 
> > >  To an HTML renderer, a space and a newline are equivalent,
> > 
> > Except when <pre> is used.
> 
> Also a good point.

I'd like to make it a moot one instead; bug #61915.
 
> > > I see no downside to this for the vertical dimension.
> > 
> > I see none for the horizontal dimension either,
> 
> It's admittedly a nicety, but one that can certainly be punted down the line
until the software stops referring to itself as beta code.  There are much
bigger grohtml fish to fry.  (And some of its most glaring limitations seem to
not even have Savannah tickets.)

Yeah. :(

> But all this seems far afield of the original bug report and perhaps ought
to have its own ticket.

I think resolving this one amounts to understanding _why_ the unintended
hyphenation occurs.  I have a hypothesis in comment #3, but it needs testing. 
If it's easy to fix, then this ticket morph into a code defect rather than a
documentation defect.  If it's hard, we'll at least be able to update the man
page with enough understanding to guide the user to a workaround.


    _______________________________________________________

Reply to this item at:

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

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