From: | Vsevolod Lobko <seva(at)sevasoft(dot)kiev(dot)ua> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Patch for pl/tcl Tcl_ExternalToUtf and Tcl_UtfToExternal |
Date: | 2001-09-06 10:33:53 |
Message-ID: | 20010906133042.S76896-100000@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Now i'm looking on using pg_do_encoding_conversion from
/src/backend/utils/mb/mbutils.c instead of tcl conversion functions.
So we can do a), without breaking b) :))
On Thu, 6 Sep 2001, Peter Eisentraut wrote:
> Reinhard Max writes:
>
> > So basically there are two possibilities:
> >
> > a) Patch pl/tcl and PgTcl to do the code conversion, but do it right
> > by using the Database's encoding instead of Tcl's system encoding.
> >
> > b) Require databases to be in UNICODE if they are to be accessed
> > from Tcl >= 8.1 so that the strings that come out of the database
> > are already UTF-8.
>
> Could you summarize how that affects the proposed patch? (The patch is
> already in, but I'm still not sure if it's not just an arbitrary
> workaround.)
>
> --
> Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
>
From | Date | Subject | |
---|---|---|---|
Next Message | Reinhard Max | 2001-09-06 10:47:38 | Re: Patch for pl/tcl Tcl_ExternalToUtf and Tcl_UtfToExternal |
Previous Message | Peter Eisentraut | 2001-09-06 10:30:21 | Re: Patch for pl/tcl Tcl_ExternalToUtf and Tcl_UtfToExternal |