stri_trans_nfc(str)
stri_trans_nfd(str)
stri_trans_nfkd(str)
stri_trans_nfkc(str)
stri_trans_nfkc_casefold(str)
stri_trans_isnfc(str)
stri_trans_isnfd(str)
stri_trans_isnfkd(str)
stri_trans_isnfkc(str)
stri_trans_isnfkc_casefold(str)
stri_trans_nf*
functions return a character vector
of the same length as input (the output is always in UTF-8).On the other hand, stri_trans_isnf*
return a logical vector.
The following Normalization Forms (NFs) are supported:
Note that many W3C Specifications recommend using NFC for all content, because this form avoids potential interoperability problems arising from the use of canonically equivalent, yet different, character sequences in document formats on the Web. Thus, you will rather not use these functions in typical string processing activities. Most often you may assume that a string is in NFC, see RFC\#5198.
As usual in stringi, if the input character vector is in the native encoding, it will be converted to UTF-8 automatically.
For more general text transforms refer to stri_trans_general
.
Unicode Format for Network Interchange -- RFC\#5198, http://tools.ietf.org/rfc/rfc5198.txt
Character Model for the World Wide Web 1.0: Normalization -- W3C Working Draft, http://www.w3.org/TR/charmod-norm/
Normalization -- ICU User Guide, http://userguide.icu-project.org/transforms/normalization (technical details)
Unicode Equivalence -- Wikipedia, http://en.wikipedia.org/wiki/Unicode_equivalence
stri_trans_char
,
stri_trans_general
,
stri_trans_list
,
stri_trans_tolower
stri_trans_nfd("\u0105") # Polish a with ogonek -> a, ogonek
stri_trans_nfkc("\ufdfa") # 1 codepoint -> 18 codepoints
Run the code above in your browser using DataCamp Workspace