Home | History | Annotate | Download | only in unicode

Lines Matching full:normalized

96  * It allows to work on strings that are not necessarily normalized
109 * already conform to FCD and do not need to be normalized (NFD) for such a process. The FCD quick check will
119 * Beyond collation and string search, normalized strings may be useful for string equivalence comparisons,
125 * Unicode text needs to be normalized to NFC.
189 * The string will be normalized according the specified normalization mode
217 * string is in the desired normalized format, UNORM_NO determines that
218 * argument string is not in the desired normalized format. A
220 * the user may have to put the string in its normalized form and compare the
223 * @param source string for determining if it is in a normalized format
316 * Another example: When one wants to concatenate two normalized strings and get a
317 * normalized result, it is much more efficient to normalize just a small part of
340 * string ends need to be normalized together.
365 * is to be normalized (TRUE) or just copied (FALSE).
398 * is to be normalized (TRUE) or just copied (FALSE).
420 * Concatenate normalized strings, making sure that the result is normalized as well.
430 * With the input strings already being normalized,
433 * Only the concatenation of these end pieces will be normalized and
492 * Canonical equivalence between two strings is defined as their normalized