Please note, this is a STATIC archive of website developer.mozilla.org from 03 Nov 2016, cach3.com does not collect or store any user information, there is no "phishing" involved.

Revision 200916 of nsCStringEncoding

  • Revision slug: nsCStringEncoding
  • Revision title: nsCStringEncoding
  • Revision id: 200916
  • Created:
  • Creator: Biesi
  • Is current revision? No
  • Comment refer to the right functions
Tags: 

Revision Content

{{ Xpcomapi() }}

Summary

The nsCStringEncoding enumeration describes the set of character encodings understood by the NS_CStringToUTF16 and NS_UTF16ToCString functions.

NS_CSTRING_ENCODING_ASCII
Conversion between ASCII and UTF-16 assumes that all bytes in the source string are 7-bit ASCII and can be inflated to UTF-16 by inserting null bytes. Reverse conversion is done by truncating every other byte. The conversion may result in loss and/or corruption of information if the strings do not strictly contain ASCII data.
NS_CSTRING_ENCODING_UTF8
Conversion between UTF-8 and UTF-16 is non-lossy.
NS_CSTRING_ENCODING_NATIVE_FILESYSTEM
Conversion from UTF-16 to the native filesystem charset may result in a loss of information. No attempt is made to protect against data loss in this case. The native filesystem charset applies to strings passed to the "Native" method variants on nsIFile and nsILocalFile.

History

This enumeration was frozen for Mozilla 1.7. See {{ Bug("239123") }} for details.

See Also

NS_CStringToUTF16, NS_UTF16ToCString

Revision Source

 
<p>
{{ Xpcomapi() }}
</p>
<h3 id="Summary" name="Summary">Summary</h3>
<p>The <code>nsCStringEncoding</code> enumeration describes the set of character encodings understood by the <code><a href="en/NS_CStringToUTF16">NS_CStringToUTF16</a></code> and <code><a href="en/NS_UTF16ToCString">NS_UTF16ToCString</a></code> functions.
</p>
<dl><dt>NS_CSTRING_ENCODING_ASCII
</dt><dd> Conversion between ASCII and UTF-16 assumes that all bytes in the source string are 7-bit ASCII and can be inflated to UTF-16 by inserting null bytes. Reverse conversion is done by truncating every other byte. The conversion may result in loss and/or corruption of information if the strings do not strictly contain ASCII data. </dd><dt>NS_CSTRING_ENCODING_UTF8
</dt><dd> Conversion between UTF-8 and UTF-16 is non-lossy. </dd><dt>NS_CSTRING_ENCODING_NATIVE_FILESYSTEM
</dt><dd> Conversion from UTF-16 to the native filesystem charset may result in a loss of information. No attempt is made to protect against data loss in this case. The native filesystem charset applies to strings passed to the "Native" method variants on <code><a href="en/NsIFile">nsIFile</a></code> and <code><a href="en/NsILocalFile">nsILocalFile</a></code>. </dd></dl>
<h3 id="History" name="History">History</h3>
<p>This enumeration was frozen for Mozilla 1.7. See {{ Bug("239123") }} for details.
</p>
<h3 id="See_Also" name="See_Also">See Also</h3>
<p><code><a href="en/NS_CStringToUTF16">NS_CStringToUTF16</a></code>, <code><a href="en/NS_UTF16ToCString">NS_UTF16ToCString</a></code>
</p>
Revert to this revision