Lines Matching refs:charsets
61 * available in the current Java virtual machine. Support for new charsets can
117 * <p> Some charsets have an <i>historical name</i> that is defined for
129 * its canonical name must be the name listed in the registry. Many charsets
144 * <h4>Standard charsets</h4>
149 * following standard charsets. Consult the release documentation for your
150 * implementation to see if any other charsets are supported. The behavior
151 * of such optional charsets may differ between implementations.
153 * <blockquote><table width="80%" summary="Description of standard charsets">
180 * <p> The <tt>UTF-16</tt> charsets are specified by <a
187 * <p> The <tt>UTF-16</tt> charsets use sixteen-bit quantities and are
196 * charsets interpret the initial byte-order marks as a <small>ZERO-WIDTH
214 * may or may not be one of the standard charsets. The default charset is
219 * standard charsets.
324 /* The standard set of charsets */
327 // Cache of the most-recently-returned charsets,
393 // The runtime startup sequence looks up standard charsets as a
428 /* The extended set of charsets */
441 // Extended charsets not available
442 // (charsets.jar not present)
546 // Fold charsets from the given iterator into the given map, ignoring
547 // charsets whose names already have entries in the map.
562 * two or more supported charsets have the same canonical name then the
569 * enumerate all of the available charsets, for example to allow user
576 * virtual machine. In the absence of such changes, the charsets returned
590 put(standardProvider.charsets(), m);
593 put(cp.charsets(), m);
769 * <p> Nearly all charsets support encoding. The primary exceptions are
770 * special-purpose <i>auto-detect</i> charsets whose decoders can determine
772 * input byte sequence. Such charsets do not support encoding because
774 * Implementations of such charsets should override this method to return
900 * <p> Two charsets are equal if, and only if, they have the same canonical