Follow-up Comment #40, bug #63074 (group groff):

[comment #38 comment #38:]
> One could envision three levels of support for encoding arbitrary
> characters.
> 
> 1.  By Unicode code point.  Reusing _groff_'s own syntax for Unicode special
> character escape sequences was irresistibly tempting, so that's what I
> implemented.  We have that in Git HEAD.
> 2.  By (simple) _groff_ special character escape sequence, like \['o'] (in
> "Cicerón").  We have that in Git HEAD too.
> 3.  By composite special character escape sequence, like "\[o aa]", which we
> might also use to write "Cicerón"--"Cicer\[o aa]n".  We don't have that.  It
> proved to be difficult.  (The formatter warns if it encounters this syntax
> where it can't handle it.)

If you implement (3) you realise that searching a document for "Cicerón"
(which was formed using \[o aa]) may not be found. So I prefer not allowing
composites, unless you have a zinger argument for them.

> Enough has been done that Deri is happy with the feature, and characterized
> level #3 above as a goal I set for myself, not a response to user demand.
> And that's true.
> 
> I reckon it's better to move on toward a _groff_ 1.24 release than try to
> satisfy my own goals involving perfectly composable orthogonal features.
> 
> The changes to the `\X` escape sequence are already documented in groff(7),
> groff_diff(7), and our Texinfo manual.  All that really remains is to write a
> NEWS item for this.
> 
> The `output` request and `\!` escape sequence remain for those who wish to
> bypass this mechanism.

Yes, both of these work perfectly:-

printf "Caf\\['e]\n.br\n.output x X ps:exec [/Dest /pdf:bm1 /Title (Eat at
Joe's Caf\\['e].) /Level 1 /OUT pdfmark\n" | test-groff -T pdf | okular -

printf "Caf\\['e]\n.br\n.device ps:exec [/Dest /pdf:bm1 /Title (Eat at Joe's
Caf\\['e].) /Level 1 /OUT pdfmark\n" | test-groff -T pdf | okular -




    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to