Re: Proposed nsIFile and nsILocalFile Changes - MUST READ

[Doug Turner]

> I think this will improve i18n file name handling a lot. Problem is, the
> way the unicode->file sys char set conversions are done now requires uconv
> and is undefined when XPCOM_STANDALONE=1. What can we do about the standalone
> case if it's all unicode, all the time?

Your right.  We can't support XPCOM_STANDALONE if we change the nsIFile interface
to exclusively use the unicode calls.

Thoughts?