Îõ³h$.Ø  Á(c) 2016 Harendra Kumar (c) 2020 Andrew Lelechenko BSD-3-Clauseharendra.kumar@gmail.com experimentalNoneÑàÐ unicode-transformsO(n) Convert a   into a 'Stream Char'. unicode-transformsO(n)5 Convert a 'Stream Char' into a decompose-normalized  . unicode-transformsO(n)4 Convert a 'Stream Char' into a composed normalized  . (c) 2016 Harendra Kumar BSD-3-Clauseharendra.kumar@gmail.com experimentalGHC Safe-Inferred3 Ûunicode-transformsºNormalization transforms Unicode text into an equivalent composed or decomposed form, allowing for easier sorting and searching of text. Standard normalization forms are described in  !https://unicode.org/reports/tr15/;, Unicode Standard Annex #15: Unicode Normalization Forms.ÚCharacters with accents or other adornments can be encoded in several different ways in Unicode. For example, take the character A-acute. In Unicode, this can be encoded as a single character (the "composed" form): / 00C1 LATIN CAPITAL LETTER A WITH ACUTE 6or as two separate characters (the "decomposed" form): È 0041 LATIN CAPITAL LETTER A 0301 COMBINING ACUTE ACCENT ØTo a user of your program, however, both of these sequences should be treated as the same "user-level" character "A with acute accent". When you are searching or comparing text, you must ensure that these two sequences are treated equivalently. In addition, you must handle characters with more than one accent. Sometimes the order of a character's combining accents is significant, while in other cases accent sequences in different orders are really equivalent.ÅSimilarly, the string "ffi" can be encoded as three separate letters: æ 0066 LATIN SMALL LETTER F 0066 LATIN SMALL LETTER F 0069 LATIN SMALL LETTER I or as the single character & FB03 LATIN SMALL LIGATURE FFI §The "ffi" ligature is not a distinct semantic character, and strictly speaking it shouldn't be in Unicode at all, but it was included for compatibility with existing character sets that already provided it. The Unicode standard identifies such characters by giving them "compatibility" decompositions into the corresponding semantic characters. When sorting and searching, you will often want to use these mappings.¿Normalization helps solve these problems by transforming text into the canonical composed and decomposed forms as shown in the first example above. In addition, you can have it perform compatibility decompositions so that you can treat compatibility characters the same as their equivalents. Finally, normalization rearranges accents into the proper canonical order, so that you do not have to worry about accent rearrangement on your own.2The W3C generally recommends to exchange texts in â. Note also that most legacy character encodings use only precomposed forms and often do not encode any combining marks by themselves. For conversion to such character encodings the Unicode text needs to be normalized to <. For more usage examples, see the Unicode Standard Annex.unicode-transformsCanonical decomposition.unicode-transformsCompatibility decomposition.unicode-transforms:Canonical decomposition followed by canonical composition.unicode-transforms>Compatibility decomposition followed by canonical composition.(c) 2016 Harendra Kumar BSD-3-Clauseharendra.kumar@gmail.com experimentalGHCNoneÆunicode-transforms!Perform Unicode normalization on Text0 according to the specified normalization mode.(c) 2016 Harendra Kumar BSD-3-Clauseharendra.kumar@gmail.com experimentalGHCNoneÈ unicode-transforms0Perform Unicode normalization on a UTF8 encoded  ByteString0 according to the specified normalization mode.        /unicode-transforms-0.4.0-9oME2VvmSPyJ6wJC4wTvSMData.Unicode.TypesData.Text.NormalizeData.ByteString.UTF8.Normalize%Data.Unicode.Internal.NormalizeStreamNormalizationModeNFDNFKDNFCNFKC$fEqNormalizationMode$fShowNormalizationMode$fEnumNormalizationMode normalizestream text-1.2.3.2Data.Text.InternalTextunstream unstreamC)unicode-data-0.2.0-3z3tlHzDjubIrhWzfPkDTzUnicode.Char.Normalization DecomposeMode CanonicalKompat