> > Be careful!
> > The translation table between existing character set and Unicode,
> > which is used by Windows filesystem is different from the table
> > defined by Unicode consortium. (Thus, kernel should have to 
> > handle several converstion table between Unicode and other 
> > character sets, since Apple's conversion table is also different
> > from Microsoft's or Unicode consortium's.)
> 
> Apple actually has a lot of them. In hfs+, there is a bit field which
> encodes which of Apple's translations have been used to generate unicode
> names. That way reverse mappings (from unicode) are more likely to work,
> and the system only needs to load the reverse mapping routines for code
> sets which have been used.

Is the bit field defined per filesystem? or, per directory entry?
or something?
--
soda