Follow-up Comment #42, bug #63074 (group groff): Here's my attempt to explain this new feature in the "NEWS" file.
* 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; see
groff_diff(7) for details. 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)).
This feature change has been the single hardest thing to land for _groff_
1.24.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63074>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
