Forum OpenACS Q&A: Response to Dealing with non-Roman character sets

Collapse
Posted by Don Baccus on
It kills "LIKE" optimization in PG.  While that's not a big deal for OpenACS 4 per se, it might be for custom code based on the toolkit.

I'm not sure what the distros are doing regarding PG RPMs (or other packages) shipped and installed by default.  I've not tried to follow this.  We might want to follow their lead.  But I think we'd want Henry's patches first ??? (if "their lead" means "use UTF-8"?)

Tcl 8 is always UTF-8 - that's what broke ns_uuencode, for instance.