On Dec 21, 2006, at 18:18 UTC, Meyer Jim wrote: > I think the problem is that "\xnn" only supports ASCII > characters..... the docs say "\xnn Matches an ASCII character of > that hexadecimal value"...... and my value is hex 2029.....
Yes, that would certainly be a problem. I didn't realize you were trying to use \xnn here. (This is the sort of thing where copying & pasting the relevant code snippet would save a lot of time.) However, you can certainly find such characters without encoding them at all. Just include Encodings.UTF8.Chr(&h2029) in your search pattern; or even better, type this character right into your string literal (using something like the OS X Character Palette). To RegEx, it's no different from any other Unicode character. > In reading various RegEx & PCRE web sites it seems new > implementations include a new meta tag "\unnnn" for use on unicode > characters. Well, you could try that. But that seems mostly useful if you're working in a language that's not Unicode-savvy; REALbasic is. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
