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
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
Steve Hall wrote:
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.
This must have changed in 7.0, 6.4.10
On Sun, Apr 30, 2006 at 09:19:01PM -0400, Steve Hall wrote:
In every beta of gVim I've tried on Linux/GTK2 (through 70g) I get the
following error with :hardcopy :
E673: Incompatible multi-byte encoding and character set.
This is with utf-8 and latin1. My binary is feature-full, it
On Mon, 1 May 2006 08:39:25 -0400
Benji wrote:
On Sun, Apr 30, 2006 at 09:19:01PM -0400, Steve Hall wrote:
In every beta of gVim I've tried on Linux/GTK2 (through 70g) I get the
following error with :hardcopy :
E673: Incompatible multi-byte encoding and character set.
This is
On Mon, 2006-05-01 at 08:39 -0400, Benji Fisher wrote:
On Sun, Apr 30, 2006 at 09:19:01PM -0400, Steve Hall wrote:
In every beta of gVim I've tried on Linux/GTK2 (through 70g) I get
the following error with :hardcopy :
E673: Incompatible multi-byte encoding and character set.
This
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
