Home | History | Annotate | Download | only in unicode

Lines Matching full:strings

96  * It allows to work on strings that are not necessarily normalized
100 * It is not a normalization form because it does not provide for uniqueness of representation. Multiple strings
110 * return UNORM_YES for most strings in practice.
119 * Beyond collation and string search, normalized strings may be useful for string equivalence comparisons,
316 * Another example: When one wants to concatenate two normalized strings and get a
420 * Concatenate normalized strings, making sure that the result is normalized as well.
422 * If both the left and the right strings are in
430 * With the input strings already being normalized,
432 * to find the adjacent end pieces of the input strings.
434 * then concatenated with the remaining parts of the input strings.
465 * Both input strings are assumed to fulfill FCD conditions.
481 * Compare strings in code point order instead of code unit order.
488 * Compare two strings for canonical equivalence.
492 * Canonical equivalence between two strings is defined as their normalized
494 * This function compares strings incrementally instead of normalizing
495 * (and optionally case-folding) both strings entirely,
498 * Bulk normalization is only necessary if the strings do not fulfill the FCD
499 * conditions. Only in this case, and only if the strings are relatively long,
501 * For FCD strings and short non-FCD strings there is no memory allocation.
518 * Case-sensitive comparison in code unit order, and the input strings
531 * Set to compare strings case-insensitively using case folding,