> Was hoping you would chime in with exactly those thoughts :) Am I right > in thinking we'd all be best served by sticking exclusively to unicode > and working on getting a patch for the editor?
yes. though i thought we tested the "built-in" soEditor & it passed (after we cleaned up thr db, etc. stuff)? are some folks having issues with it? > Or are there some benefits in making charset a config item that defaults > to Unicode? that could get sticky as you'd be running against mx's default utf-8 encoding--"go with the flow" is probably a good idea. it won't matter one bit to latin-1 folks (well unicode will actually help those euroland folks who can't find the euro symbol in iso-8859-1) & make things much simpler for everyone else, especially if you have to support many languages. though i suppose current/older mysql backends might benefit from codepage encodings (even then, i guess mysql will sooner or later become fully unicode capable, so it would be a wash in the long run). --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
