Lines Matching full:normalized
90 * It allows to work on strings that are not necessarily normalized
103 * already conform to FCD and do not need to be normalized (NFD) for such a process. The FCD quick check will
113 * Beyond collation and string search, normalized strings may be useful for string equivalence comparisons,
119 * Unicode text needs to be normalized to NFC.
183 * The string will be normalized according the specified normalization mode
213 * Indicates that string is not in the normalized format
217 * Indicates that string is in the normalized format
221 * Indicates that string cannot be determined if it is in the normalized
232 * string is in the desired normalized format, UNORM_NO determines that
233 * argument string is not in the desired normalized format. A
235 * the user may have to put the string in its normalized form and compare the
238 * @param source string for determining if it is in a normalized format
331 * Another example: When one wants to concatenate two normalized strings and get a
332 * normalized result, it is much more efficient to normalize just a small part of
355 * string ends need to be normalized together.
380 * is to be normalized (TRUE) or just copied (FALSE).
413 * is to be normalized (TRUE) or just copied (FALSE).
435 * Concatenate normalized strings, making sure that the result is normalized as well.
445 * With the input strings already being normalized,
448 * Only the concatenation of these end pieces will be normalized and
507 * Canonical equivalence between two strings is defined as their normalized
