Lines Matching full:fromunicode
22 * - it is possible in fromUnicode() to directly deal with simple
27 * Remaining limitations in fromUnicode:
79 * The MBCS_OPT_FROM_U flag indicates that most of the fromUnicode data is omitted from
82 * (and UTF-8-friendly) fromUnicode conversion for Unicode code points up to maxFastUChar.
85 * utf8Friendly also implies that the fromUnicode mappings are stored in ascending order
93 * With only roundtrip mappings in the base fromUnicode data, this part is fully
131 * - new data structure for single-byte fromUnicode
137 * - 2-byte and 4-byte fromUnicode results are stored directly as 16/32-bit integers
190 * Typically, such mappings occur only in fromUnicode mapping tables because
294 * The conversion data structure for fromUnicode is designed for the known
513 /* skip byte sequences with leading zeros because they are not stored in the fromUnicode table */
1182 * There used to be code to enumerate the fromUnicode
1259 /* reconstitute omitted fromUnicode data ------------------------------------ */
1838 /* fromUnicode */
