At 14:32 02/03/2001 -0800, Daniel Veditz wrote:
>Frank Tang wrote:
> > >  Why do we need unicode paths on the nsIFile?
> >
> > File name do contains non ASCII characters. And in general we should use
> > wstring/PRUnichar* for all XPCOM interface for any text which are human
> > readable. We also want to hide the details of what charset are used in
> > the file system from the caller.
>
>While I agree that Unicode is best inside Mozilla (and REQUIRED for
>scriptable interfaces), embedding apps may find native code paths easiest to
>work with. Why force them to convert to Unicode only to have nsLocalFile
>convert them right back?

This is important, embedded apps may be running on restricted hardware 
platforms for hardwired character encoding, presuming that unicode has to 
exist will just make Mozilla as a whole unusable on those kind of platforms 
unless there are native code replacements.

Simon

>-Dan Veditz

===================================================
If I'd known I would spend so much time sorting and rearranging boxes
I'd have paid more attention at kindergarten

S.P. Lucy


Reply via email to