----- Original Message ----- > From: Robin Burchell <[email protected]> > 2012/4/24 Thiago Macieira <[email protected]>: >> My recommendation is a variant of options 3: we document that it accepts > only >> US-ASCII and that it has undefined behaviour when the input isn't > US-ASCII >> compliant. That way, we can make it be equal to toLatin1() and avoid having > to >> write code for checking the high bit. > > I'd agree with that. I don't know what the pain of making it > strict-ASCII would be in existing code (at least, I've seen it used > far more often than I like), but we can teach people to use it > properly at the very least.
Question: is there are reason not to support the US-Extended ASCII (128-255)? I know it's not used often, but sometimes those characters are very useful. Ben _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
