JADE Environment Development Ideas

You can already call Ansi libraries from a Unicode Jade, and as long as none of the extended character set characters that come with Unicode are used it all works fine.  Where it becomes an issue is when extended character set characters are used and it then turns that single Unicode character into two Ansi characters instead, effectively corrupting that part of the text.  The reason for suggesting making it a standard part of the Jade product was for ease of implementation for developers.  I was also hoping that it may be easier for them to implement if they could hook into the existing Windows Spelling Check API.

It would be nice if there was a reusable package for spell checking that we could all use, but that's something which could be achieved via an open source project to share a schema that exports such a package.  What's the benefit of it being made a part of the Jade platform directly?

With regards the Unicode vs Ansi point - Perhaps there's a more general idea here where JADE could be improved somehow to support the use of an Ansi library from a Unicode environment.  What'd also be nice is if we didn't have to duplicate functions or external methods to distinguish Ansi & Unicode entry points, and then write code accordingly to call the appropriate function or method.  If functions & external methods could be enhanced so we can map them to both an Ansi & Unicode entry point, JADE could automatically call the appropriate entry point depending on the installation type.