Funny. I was just writing a similar script the other day for a similar problem (its for something else I'm working on). If you're interested the bad range of ascii codes are 130-159. And in case if it is helpful
my point was that these codepoints are also quite legitimate chars in encodings other than iso-8859-1 & unicode like windows-874/tis-622 (thai) or windows-turkish, etc. if you're applying this filter w/out any regard to the encoding being used you're going to garbage the content pretty good. of course, you can solve all these issues if everybody "Just Used Unicode" or even if everybody "hinted early & hinted often" when it comes to encoding. however most doorknobs don't consider this kind of stuff too deeply ;-)
And if you're really bored you can read more on that site why the ascii versions are bad for i18n.
didn't see anything specific to i18n there, did i miss something?
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
