> > > or Asian language support > > > > That shouldn't be excessively hard if you stick to storing your files in > > UTF-8 (or 16) and possibly use the output translation routines to convert > > that to encodings that user agents may understand better. > > Actually, for that see the all-new experimental AxExternalEncoding directive, > which will not go into the 1.6 release, however. It will be in 1.6.1 if we > can solve the remaining problems. AxExternalEncoding will smoothe out the > bugs that arise when you are trying to have non-ASCII chars in URLs and in > file names. Browsers can be _very_ unreasonable, and even worse, they > sometimes do the exact opposite of each other when it comes to international > charsets and UTF-8 and URLs and all that. AxExternalEncoding is designed to > solve these issues, so internally, you can pretend the world is a sunny warm > UTF-8 place. Testers are highly welcome.
I'd like to test this feature so what should I do. I work mostly with cyrillic encodings and for now I have to encode and decode by hand in order to process everything successfully. Will this feature enable me to have cyrillic characters directly into my XSP pages? Pavel
