[bug #64155] specifying -fZD on command line generates warnings

2024-03-04 Thread Peter Schaffter
Follow-up Comment #24, bug #64155 (group groff):

The restriction does conflict with mom's supplementary styles, however  the
conflict is not unique to mom.  Any user-installed family may not have all of
R/I/B/BI and, if a user gets creative with .sty, may not, in fact, have any of
them.  I have dozens of partial families, and plenty with just .sty's taken
from mom's offerings


___

Reply to this item at:

  

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




[bug #64155] specifying -fZD on command line generates warnings

2024-03-04 Thread Dave
Update of bug #64155 (group groff):

 Assigned to:deri => PTPi   

___

Follow-up Comment #23:

[comment #21 comment #21:]
> this code:-
...
> Copied the corrupt file rather than the correct file in
> ./font/devpdf. What is the purpose of this?

This issue being unrelated to this ticket's original purpose (which was fixed
and closed with comment #17), I opened bug #65415 to address it separately.

> I am going to leave this open so that you can reply to 
...
> whether you think this change will affect mom's use of .fam.

This seems to be the only other question keeping this ticket open now.  Ping:
Peter.  (Also assigning the bug to him for now, since Deri has withdrawn from
gropdf work.)


___

Reply to this item at:

  

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




[bug #65415] [gropdf] Do the correct font description files get installed?

2024-03-04 Thread Dave
URL:
  

 Summary: [gropdf] Do the correct font description files get
installed?
   Group: GNU roff
   Submitter: barx
   Submitted: Mon 04 Mar 2024 06:23:13 PM CST
Category: Driver gropdf
Severity: 2 - Minor
  Item Group: Warning/Suspicious behaviour
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
 Planned Release: None


___

Follow-up Comments:


---
Date: Mon 04 Mar 2024 06:23:13 PM CST By: Dave 
In bug #64155, Deri pointed to this snippet of
[http://git.savannah.gnu.org/cgit/groff.git/tree/font/devpdf/devpdf.am
font/devpdf/devpdf.am]

  if test -f $$f; then \
$(INSTALL_DATA) $$f $(DESTDIR)$(devpdffontdir)/$$f; \
  else \
$(INSTALL_DATA) $(top_builddir)/font/devpdf/$$f \
  $(DESTDIR)$(devpdffontdir)/$$f; \
  fi; \

as the culprit of an install problem he experienced: "I had a corrupt copy of
U-TR in my build directory so this code copied the corrupt file rather than
the correct file in ./font/devpdf."

This snippet in question dates back to
[http://git.savannah.gnu.org/cgit/groff.git/commit/?id=87046b294 commit
87046b294], in which gropdf was first added to the groff tree.  The current
version of the snippet is substantively unchanged from then.  (Some variables
have been renamed, and the code was relocated from its original
[http://git.savannah.gnu.org/cgit/groff.git/tree/font/devpdf/Makefile.sub?id=e68ea4591
font/devpdf/Makefile.sub].)

Git credits this commit to Werner (and he may have been responsible for the
updates to the Texinfo manual and other integration tasks) but the ChangeLog
entry credits Deri, and Deri's name appears as the author of the new source
files, including Makefile.sub.

This historical tour is relevant because when Deri encountered the
corrupt-file propagation in 2024, he asked of the offending lines of code,
"What is the purpose of this?", revealing that even the code's original author
no longer recalls what it was intended to do.

So from the viewpoint of today, does this code do something useful, and the
corrupted file getting copied was collateral damage?  Or should it be
revamped?







___

Reply to this item at:

  

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




[bug #64484] [troff] .device and \X don't behave the same

2024-03-04 Thread G. Branden Robinson
Follow-up Comment #10, bug #64484 (group groff):

Already reopened, but for the record..


commit 190d01502ec8f8caab05bd3eb11ee04411c1e332
Author: G. Branden Robinson 
Date:   Mon Mar 4 00:14:39 2024 -0600

Revert "[troff]: Fix Savannah #64484."

This reverts commit 9dbf227a5b3870a19c1e6d90e5b619c4ae3e7f3e.

Reopens Savannah #64484.

Test src/roff/groff/tests/device-control-special-character-handling.sh
fails at this commit.




___

Reply to this item at:

  

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