[groff] 26/26: Fix Savannah #63074.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 635cd005577c8aa76fe6acf86e9d3af578a471d4
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Thu Nov 14 10:30:17 2024 -0600

    Fix Savannah #63074.
    
    * NEWS: Explain changes to `\X` and `.device` argument processing.
    
    Fixes <https://savannah.gnu.org/bugs/?63074>.  Thanks to Nikita
    Ivanov for the report.
---
 ChangeLog |  8 ++++++++
 NEWS      | 16 ++++++++++++++++
 2 files changed, 24 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 5c4e58b4e..452facb64 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2024-11-14  G. Branden Robinson <g.branden.robinson@gmail.com>
+
+       * NEWS: Explain changes to `\X` and `.device` argument
+       processing.
+
+       Fixes <https://savannah.gnu.org/bugs/?63074>.  Thanks to Nikita
+       Ivanov for the report.
+
 2024-11-14  G. Branden Robinson <g.branden.robinson@gmail.com>
 
        * src/devices/grops/psrm.cpp (resource_manager::output_prolog)
diff --git a/NEWS b/NEWS
index e9485954c..6957031d8 100644
--- a/NEWS
+++ b/NEWS
@@ -71,6 +71,22 @@ troff
    We recommend using brace escape sequences `\{` and `\}` to ensure
    that your control flow structures remain maintainable.
 
+*  GNU troff now performs some limited processing/transformation of the
+   argument to the `\X` escape sequence and its counterpart `device`
+   request, to address the requirement that some documents have to pass
+   metadata that must encode non-ASCII characters in device extension
+   commands.  (For example, a document author may desire a document's
+   section headings containing non-ASCII code points to appear correctly
+   in PDF bookmarks.  Further, GNU troff encodes its output page
+   description language only in ASCII.)  This change is expected to be
+   of significance mainly to developers of output drivers for groff;
+   groff_diff(7) describes the transformations.  If you have been using
+   `\X` or `.device` to pass ASCII data to the output driver as a device
+   extension command and require that it remain precisely as-is, use the
+   `\!` escape sequence or `output` request, and prefix your data with
+   "x X ", the device-independent troff means of expressing a device
+   extension command (see groff_out(5)).
+
 *  In nroff mode (in other words, when producing output for devices that
    claim to be terminals), the formatter now reports warning diagnostics
    regarding certain output problems using units of lines instead of