On Thu, 10 Jan 2008, Ethan Merritt wrote:
> On Wednesday 09 January 2008 17:28, Allin Cottrell wrote:
> > What I'm suggesting here is that "set encoding CP1254" is a
> > setting that, quite defensibly, could be acted upon only by emf term.
> Could you explain your logic a little bit further?
> It would seem to me that if the user needs a particular encoding
> at all, presumably because the input data or scripts use that
> encoding, then *all* output modes need to match. Why would emf
> be a special case? If it's a matter of running under Windows,
> wouldn't support for win.trm be at least as important?
You're right, I had forgotten about win.trm, that should be
I'm thinking of the situation where, say, somebody is using
gnuplot on a Windows PC in Turkey, using CP1254, and wants
accented characters in a graph. The most likely output modes are,
I suppose, win and emf. If she wants PostScript output, she could
try specifying iso8859-9 and actual text should come through OK.
If she's using an output mode that employs UTF-8 internally, what
happens if she does "set encoding locale"? Do the UTF-8 terminals
then automagically get a correctly recoded version of the CP1254
Department of Economics
Wake Forest University, NC