Update of bug#64285 (group groff):
Status: Need Info => None
Assigned to: deri => gbranden
_______________________________________________________
Follow-up Comment #13:
[comment #12 comment #12:]
> If you think fixing a crazy (but well known and documented) "feature" is
more important than maintaining 30 years of groff compatibility,
I pretty much do, yeah. Every crazy feature we keep dragging along with us
makes the language harder to acquire, remember, and work with. Where the size
of the impacted user community is small, as it surely is here--I fear the most
prolific users of drawing escape sequences outside of macro packages or
preprocessors are cargo cultists--it seems an easy choice to make.
For an example of me biting the bullet and restoring backward compatibility in
spite of my strong view that it was the wrong _technical_ choice, see bug
#51468.
> then it would probably make sense for you to do the deed (to libdriver and
gropdf) in the same commit. Just comment out the two lines about 3916 (in
section dealing with "Line Thickness "):-
> $poschg=1;
> $xpos+=$lwidth;
> And test with the code in comment #9. Both paragraphs should be the same,
and with no unusual gap later in the first lines.
Thanks for the fish, there's no telling how long I'd have been out on the
ocean casting my rod and reel fruitlessly for that one. :)
Clearing status and reassigning to self.
Not sure when I'll get to it. I predict low difficulty but the urgency is
also low.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64285>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
