Re: [PATCHES] client side syntax error position (v3)

2004-03-15 Thread Tatsuo Ishii
> > > scroffset += 1;/* XXX fix me when we have screen width info */ > > > > > > with calls to a get-the-screen-width-of-this-character subroutine should > > > do the job. I have committed changes adding "PQdsplen()" which should do the job above. Quick test with EUC-JP indicates

Re: [PATCHES] client side syntax error position (v3)

2004-03-15 Thread Fabien COELHO
Dear Tom, > > scroffset += 1;/* XXX fix me when we have screen width info */ > > > > with calls to a get-the-screen-width-of-this-character subroutine should > > do the job. > > I also looked into it, and it is also a little bit more complex, as the > extract width must be though

Re: [PATCHES] client side syntax error position (v3)

2004-03-15 Thread Fabien COELHO
> I have applied this patch, Thanks! > after some considerable whacking around to make it ready to cope with > multicolumn Kanji characters. It does not actually cope yet, since the > necessary knowledge is not available from the character encoding logic. > But replacing the two places that say

Re: [PATCHES] client side syntax error position (v3)

2004-03-13 Thread Tom Lane
Fabien COELHO <[EMAIL PROTECTED]> writes: > New submission... after suggestions by Tom and others, the current result > looks like the following: > psql> CREATE foo; > ERROR: syntax error at or near "foo" at character 8 > LINE 1: CREATE foo; >^ > psql> I have applied this patch,

[PATCHES] client side syntax error position (v3)

2004-03-12 Thread Fabien COELHO
Dear patchers, New submission... after suggestions by Tom and others, the current result looks like the following: psql> CREATE foo; ERROR: syntax error at or near "foo" at character 8 LINE 1: CREATE foo; ^ psql> There may still be issues about some mb encodings, especially with