Doug Turner wrote:
> At today's API review, we took a look at nsIFile and friends. The
> conclusion was some serious changes to this interface which will effect
> all callers. By some napkin calculations, we estimated at least 3 weeks
> of work for this complete task. I will present what was proposed.
>
> In Generally, the changes are:
>
> Factoring nsIFile into two pieces.
> Removing non unicode functions.
> Removing explict symlink function.
>
> These changes are all independant of one another, but probably should be
> done serial by one person.
>
Once the APIs are finalized, I think the work on each platform chould be
then be passed off to a file system maven on each platform.
-snip-
>
> The first additional comment is that we should remove the non unicode
> version of all methods. I believe that i18n will be happy with this.
> However, I am not sure how this will effect most users. Looking over
> the codebase, most places we are dealing with unicode anyways, however,
> there may be places which will have to convert from ansi to unicode.
>
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?
-Conrad
