Steve Hall wrote:
> On Mon, 2006-05-01 at 22:15 -0400, Benji Fisher wrote:
> > On Mon, May 01, 2006 at 05:31:47PM -0400, Steve Hall wrote:
> > >
> > > Yes, the bug is in &printencoding. With gvim -u NONE -U NONE,
> > > these lines produce the error:
> > >
> > > :let &printencoding = &encoding
> > > :hardcopy
> > >
> > > This is with the default utf-8, with :set enc=latin1 prior, it is
> > > avoided.
> >
> > Does that mean that the problem is solved now?
>
> Not at all in my mind, this is a bug!
>
> I'm not sure what changed in 7.0, but this was always possible in 6.x.
> Was there actually a conversion happening automatically and Vim now
> refuses to hide it? To me, if &printencoding is not a valid option for
> :hardcopy, automatic conversion with a warning is better than just
> aborting on an error. (Which raises the question, what ARE the valid
> options for &printencoding?)
"utf-8" is not a valid value for 'printencoding'. It must be an 8-bit
character set.
The help mentions that it would fall back to "latin1" when
'printencoding' is not a supported encoding, but this apparently doesn't
happen.
I don't know if the help should be updated (the error can be a useful
hint why printing doesn't work as expected) or that Vim should fall back
to "latin1" and perhaps print something weird. Falling back would be
fine if you use only latin1 even when the encoding is utf-8.
--
BEDEVERE: Wait. Wait ... tell me, what also floats on water?
ALL: Bread? No, no, no. Apples .... gravy ... very small rocks ...
ARTHUR: A duck.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
