On Sun, Oct 15, 2006 at 04:50:15PM -0500, Andrew Dunstan wrote: > Tom Lane wrote: > > I wrote: > >> It looks to me like basically everywhere in plperl.c that does > >> newSVpv() should follow it with > >> > >> #if PERL_BCDVERSION >= 0x5006000L > >> if (GetDatabaseEncoding() == PG_UTF8) > >> SvUTF8_on(sv); > >> #endif > > > > Experimentation proved that this was insufficient to fix Vitali's > > problem --- the string he's unhappy about is actually a hash key > > entry, and there's no documented way to mark the second argument > > of hv_store() as being a UTF-8 string. Some digging in the Perl > > source code found that since at least Perl 5.8.0, hv_fetch and > > hv_store recognize a negative key length as meaning a UTF-8 key > > (ick!!), so I used that hack. I am not sure there is any > > reasonable fix available in Perl 5.6.x. > > > > Attached patch applied to HEAD, but I'm not going to risk > > back-patching it without some field testing. > > Hmm. That negative pointer hack is mighty ugly. > > I am also wondering, now that it's been raised, if we need to issue > a "use utf8;" in the startup code, so that literals in the code get > the right encoding.
That would be a reason to go to 5.8, as 'use utf8;' is tricky at best in 5.6. Cheers, D -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote! ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
