Hi, Well first, our current plan with Standalone XPCOM vs. XPCOM in mozilla is for them to be one in the same by Mozilla 1.0. So for the rest of this, I'll refer to "XPCOM" because soon there should be only one.
The rule we've generally been using is that we support unicode strings in XPCOM, but we are doing our best to remove any dependencies that rely on any semantics of unicode itself.. basically our requirement is that XPCOM treats unicode strings (i.e. 16-byte character strings) as opaque buffers.. any code that requires: - character set conversion - case-conversion/comparison - system charset knowledge is not included in XPCOM. However, there are a series of international libraries which can be added on to XPCOM to add support for all of these things. The one exception is UTF8/Unicode conversion. XPCOM itself will continue to support that in different forms throughout the library. As of right now, XPCOM supports MORE than it should, with respect to charset conversion and case conversion. What we're doing is REMOVING that support, a little at a time, and requiring clients of XPCOM to use the international libraries directly. That document does need to be updated, (I'll do that soon) but here are the corrections as it stands right now: Section 5.0, 1) nsCRT no longer does unicode conversion (any APIs that did were removed) The "new" string classes do not do any unicode conversion or case-sensitive compares. nsString/nsAutoString/nsCString/nsCAutoString are the only classes that do case conversion on unicode strings. All APIs which require unicode conversion or case conversion of unicode strings will be removed by Mozilla 1.0 2) nsUnicharInputStream now lives in the international libraries. We have a new stream, UTF8ConverterStream, which does UTF8-conversion, and allows nsPersistentProperties to work. 3) and 4) are still valid. Section 6.0, 1) We're basically there. What we're actually doing is REMOVING support for other conversions. Alec Xiaowei Jiang wrote: > Hi, I'm new to mozilla. I want to use XPCOM for our application development. > One requirement we have is unicode support. However, according to > http://lxr.mozilla.org/seamonkey/source/xpcom/doc/xpcom-standalone.html , > > standalone XPCOM doesn't support unicode yet if I understand correctly. But > it seems to be in the roadmap for mozilla 1.0. Could anyone give me any idea > on when unicode support will be added to standalone XPCOM ? Is there any > ongoing effort on this? Thanks! > > Xiaowei > > > > > >
