bug-groff
[Top][All Lists]
Advanced

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

[bug #61423] [libgroff] allow paths in "name" directive of font descript


From: G. Branden Robinson
Subject: [bug #61423] [libgroff] allow paths in "name" directive of font description file, restoring historical groff behavior
Date: Tue, 4 Oct 2022 04:32:23 -0400 (EDT)

Update of bug #61423 (project groff):

                Severity:              3 - Normal => 4 - Important          
              Item Group:          Feature change => Documentation          
                  Status:               Need Info => In Progress            

    _______________________________________________________

Follow-up Comment #20:

Proposed text.


diff --git a/NEWS b/NEWS
index a28db5864..2a5f15f56 100644
--- a/NEWS
+++ b/NEWS
@@ -74,6 +74,11 @@ o New requests `stringdown` and `stringup` are available. 
These change
 o The `ab` request no longer writes "User Abort." to the standard error
   stream if given no arguments.
 
+o The `fp` request no longer accepts file or font names with slashes in
+  them as arguments.  All font description files are expected to be
+  accessible within the directory of the output device for which they
+  were prepared.
+
 nroff
 -----
 
@@ -580,6 +585,11 @@ o The 'doc' Make target has been eliminated.  'all' (the
default Make
   manual's sources are modified; the distribution archive now provides
   copies of the manual in Info, plain text, HTML, DVI, and PDF.
 
+o The "afmtodit" utility no longer writes file names with directory
+  information in them to the "name" directives of the font descriptions
+  it generates.  (The `fp` request no longer accepts such names; see
+  "troff" above.)
+
 o groffer has been deleted from the distribution.
 
 o grog no longer supports the "--warnings" option; the one diagnostic



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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