|
From: Ethan M. <merritt@u.washington.edu> - 2008-01-10 17:40:18
|
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? -- Ethan A Merritt |