úÎfbÈ  (c) 2016 Harendra Kumar BSD-styleharendra.kumar@gmail.com experimentalGHCSafe 0 6Exception raised when a tranformation operation fails. AOptional modifiers to control the overall transformation behavior >Return an error, if the input contains unassigned code points. 1Unicode Versioning Stability has to be respected.FIndicates that the input is in UTF16 format and so will be the output.Transformation operations.Convert to upper or lower case8Insert bounding marks at Char, Word, Sentence boundaries'Specifies how NLF sequences are handledÃLumps certain characters together (e.g. HYPHEN U+2010 and MINUS U+2212 to ASCII "-"). If NLF2LF is set, this includes a transformation of paragraph and line separators to ASCII line-feed (LF).$Strip "default ignorable characters"vStrips and/or converts control characters. NLF-sequences are transformed into space, except if one of the NLF2LSPSŸLF options is given. HorizontalTab (HT) and FormFeed (FF) are treated as a NLF-sequence in this case. All other control characters are simply removed. Remove the  Diacritic code points!Word or sentence boundary marking_Boundary marking operations Note - This implementation does not handle locale specific cases http://unicode.org/reports/tr29/sInserts 0xFF bytes at the beginning of each sequence which is representing a single grapheme cluster (see UAX#29).&Insert word or sentence bounding marks3NLF sequence (LF, CRLF, CR, NEL) conversion options¡Indicating that NLF-sequences (LF, CRLF, CR, NEL) are representing a line break, and should be converted to the unicode character for line separation (LS).—Indicating that NLF-sequences are representing a paragraph break, and should be converted to the unicode character for paragraph separation (PS).8Indicating that the meaning of NLF-sequences is unknown.UCase conversion. Supports on simple case mapping (no locale specific handling). See 8http://userguide.icu-project.org/transforms/casemappings ÏPerforms unicode case folding, to be able to do a case-insensitive string comparison. Note - This implementation does not provide an option for treating the letter I specially or not for Turkic languages.!!Data type for normalize operation"8Options that can be combined with basic normalization op#@Compatiblity decomposition (i.e. formatting information is lost)$RStrips all character markings (non-spacing, spacing and enclosing) (i.e. accents)%2The basic normalized form - composed or decomposed&)Return a result with composed characters.'+Return a result with decomposed characters.(Constructor for  NormalizeOp.)‰Transform a unicode string according to the requested mode and operations. Multiple modes and operations can be combined together. When modes1 list is empty default modes (complement of the   s) are used.5 * +,-./ !0"#$%&'1234()56789:;<=> +!"#$%&'() *  +,-./ !0"#$%&'1234()56789:;<=>(c) 2016 Harendra Kumar BSD-styleharendra.kumar@gmail.com experimentalGHCSafe0º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  ,http://www.unicode.org/unicode/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): H 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.ESimilarly, the string "ffi" can be encoded as three separate letters: f 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.Canonical decomposition.Compatibility decomposition.:Canonical decomposition followed by canonical composition.>Compatibility decomposition followed by canonical composition.(c) 2016 Harendra Kumar BSD-styleharendra.kumar@gmail.com experimentalGHCNone!Perform Unicode normalization on Text0 according to the specified normalization mode.??(c) 2016 Harendra Kumar BSD-styleharendra.kumar@gmail.com experimentalGHCNone 0Perform Unicode normalization on a UTF8 encoded  ByteString0 according to the specified normalization mode. @   @A       !"#$%&'()*+,-./012%3456789:;<=>?@ABC1unicode-transforms-0.1.0.1-A5Dpb5824MNJbzRCom8KW4Data.Unicode.TypesData.Text.NormalizeData.ByteString.UTF8.NormalizeData.Unicode.UTF8ProcNormalizationModeNFDNFKDNFCNFKC$fEqNormalizationMode$fShowNormalizationMode$fEnumNormalizationMode normalizeTransformError TransformModeRejectNA StableMode UTF16Mode TransformOp CaseConvertMarkBoundaries ConvertNLFLumpStripIgnorableStripCCStripDiacriticNonCharBoundOpBoundingMarksOpMarkCharBoundsMarkNonCharBoundsNLFConversionOpNLF2LSNLF2PSNLF2LFCaseConversionOpCasefold NormalizeOpNormalizationOptionCompat StripMark NormalFormComposed Decomposed mkNormalizeOp transform NormalizeMarkWordBoundsMarkSentenceBounds UpperCase LowerCaseFlagstoCFlagsCFlagsc_utf8proc_map$fExceptionTransformError$fFlagsTransformMode$fFlagsTransformOp$fFlagsNonCharBoundOp$fFlagsBoundingMarksOp$fFlagsNLFConversionOp$fFlagsCaseConversionOp$fFlagsNormalizeOp$fFlagsNormalizationOption$fFlagsNormalForm transformText transformBS