Jump to content

Unicode strings: Difference between revisions

m
Line 1,338:
#:Unicode support is good. There is one missing function: while it's easy to get the character from the numeric value of a Unicode code point, with the [https://www.stata.com/help.cgi?uchar() uchar] function, the converse is not easy. However, it's possible to convert a Unicode string to ''escaped'' hex values, e.g. <code>ustrtohex("Ж")</code> returns "\u0416", and the converse operation is done with [https://www.stata.com/help.cgi?ustrunescape() ustrunescape].
# What encodings (e.g. UTF-8, UTF-16, etc) can be used?
#:Data and code are stored in UTF-8. I/O with CSV data files can be done in any encoding supported by Java, which includes UTF-8, UTF-16 and UTF-32 with and without BOM.
# Does it support normalization?
#:Yes. See the help for the [https://www.stata.com/help.cgi?ustrnormalize() ustrnormalize] function. It supports the NFC, NFD, NFKC, NFKD and NFKCCNFKD [https://en.wikipedia.org/wiki/Unicode_equivalence#Normalization forms].
 
=={{header|Tcl}}==
1,336

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.