Re: Problems with Enhanced mode and Postscript

[Ethan M. <merritt@u.washington.edu>]

On Sunday 06 July 2008 20:53:53 Philipp K. Janert wrote:

> > Please read the comments beginning at line 2628 in the
> > file term.c.   The intent was to allow escapes of the
> > formatting characters used by the enhanced text mode:
> >
> >      if (strchr("^_@&~",p[1]) == NULL)

> > > Has this been introduced relatively recently? E.g.
> > > as consequence of including support for multibyte
> > > char sets?
> >
> > Nope.  The current code has been this way since 2004.
> > (version 3.8 something).
> 
> That's pretty recent. ;-)
> 
> The docs/psdoc/ps_guide.ps file specifically
> gives examples with curlies, and since it is a
> Postscript file itself, I would have thought that
> Postscript works. 

Sure.  I agree it's a bug, and the simple-minded fix is obvious -
just add curly brackets to the test above.   My concern is that
the simple-minded fix may break some character encodings.
Or maybe not.   The encodings at risk are not ones that I use,
so I can't easily test.

-- 
Ethan A Merritt