On Sat, 2006-02-25 at 15:07 +0000, Chris Weiss wrote: > anyway to make it optional? this is something that will definatly > confuse the hell out of a lot fo people. >
Not really. if you are just using ascii encoding you might be able to get away with it. Everything will be hardcoded to use unicode, so we have end to end unicode support. Docs and release notes are the key here. btw it should be a non issue for new installs. Cheers Dave > On 2/25/06, Dave Hall <[EMAIL PROTECTED]> wrote: > > On Sat, 2006-02-25 at 09:02 +0000, Guillaume Courtois wrote: > > > Yep but that will be necessary, because I don't think saying to people > > > they > > > have to upgrade their db themselve would be very good, no ? > > > > > > > It can't really be avoided, it is a charset translation, not something > > schema_proc can really do. iconv is pretty good for it :) > > > > Cheers > > > > Dave > > > > > Chris Weiss ([EMAIL PROTECTED]) écrivait: > > > > > > > > On 2/23/06, Dave Hall <[EMAIL PROTECTED]> wrote: > > > > > I think we should include some notes for people upgrading in the > > > > > release > > > > > notes too. It would be best if people run the dump and reimport > > > > > before > > > > > install new langs etc. > > > > > > > > how hard would it be to run the data though at upgrade time? guessing > > > > it would take a long time > > > > > > _______________________________________________ Phpgroupware-developers mailing list [email protected] http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
