bug-groff
[Top][All Lists]
Advanced

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

[bug #64484] [troff] \X escape sequence should read its argument in copy


From: G. Branden Robinson
Subject: [bug #64484] [troff] \X escape sequence should read its argument in copy mode
Date: Wed, 7 Aug 2024 09:52:12 -0400 (EDT)

Update of bug #64484 (group groff):

                 Summary: [troff] .device and \X don't behave the same =>
[troff] \X escape sequence should read its argument in copy mode

    _______________________________________________________

Follow-up Comment #12:

[comment #11 comment #11:]
> Postponing; I don't have hope of getting this sorted out in time for _groff_
1.24.

But there's some good news.
 
> Two differences between the `device` request and `\X` escape sequence
concern me and, at the very least, should be documented.
> 
> 1.  `device` reads its argument in copy mode; `\X` doesn't.

This is documented.


     The 'device' request processes its arguments in copy mode (*note
     Copy Mode::).  An initial neutral double quote in CONTENTS is
     stripped to allow embedding of leading spaces.  By contrast, within
     '\X' arguments, the escape sequences '\&', '\)', '\%', and '\:' are
     ignored; '\<SPC>' and '\~' are converted to single space
     characters; and a self-escaped escape character is output as a
     backslash '\'.  So that the basic Latin subset of the Unicode
     character set(2) (*note Postprocessor Access-Footnote-2::) can be
     reliably encoded in device control commands, seven special
     character escape sequences ('\-', '\[aq]', '\[dq]', '\[ga]',
     '\[ha]', '\[rs]', and '\[ti]') are mapped to basic Latin
     characters; see the 'groff_char(7)' man page.  For this
     transformation, character translations and special character
     definitions are ignored.(3)  (*note Postprocessor
     Access-Footnote-3::) The use of any other escape sequence in '\X'
     parameters is normally an error.


> 2.  `\X` is accepted, and works, at the beginning of input; `device` does
not.

This was bug #65977 and is now fixed.

Retitling.  GNU _troff_ at present has no mechanism enabling _any_ delimited
escape sequence to read its arguments in copy mode (`\?` does, but uniquely
uses itself as a "delimiter".)  So this remains postponed past 1.24.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature


reply via email to

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