Everyone else is giving the surface answer, but there’s a deeper rationale too: the number of “characters” is a difficult-to-define question and can be surprisingly expensive to compute, whereas a length property should be fast. Why is it difficult to define? Well, there’s a few options and none are really more valid than another: The … Read more
NSString literals and strings-files use different escaping rules. NSString literals use the same escape sequences as “normal” C-strings, in particular the “universal character names” defined in the C99 standard: \unnnn – the character whose four-digit short identifier is nnnn \Unnnnnnnn – the character whose eight-digit short identifier is nnnnnnnn Example: NSString *string = @”Espa\u00F1ol – … Read more
See, http://en.wikipedia.org/wiki/Unicode_control_characters You might want to look especially at C0 and C1 control character http://en.wikipedia.org/wiki/C0_and_C1_control_codes The wiki says, the C0 control character is in the range U+0000—U+001F and U+007F (which is the same range as ASCII) and C1 control character is in the range U+0080—U+009F other than C-control character, Unicode also has hundreds of formatting … Read more
mbstowcs() and wcstombs() don’t necessarily convert to UTF-16 or UTF-32, they convert to wchar_t and whatever the locale wchar_t encoding is. All Windows locales uses a two byte wchar_t and UTF-16 as the encoding, but the other major platforms use a 4-byte wchar_t with UTF-32 (or even a non-Unicode encoding for some locales). A platform … Read more
Use parse, but don’t evaluate the results: x1 <- ‘pretty\\u003D\\u003Ebig’ x2 <- parse(text = paste0(“‘”, x1, “‘”)) x3 <- x2[[1]] x3 # [1] “pretty=>big” is.character(x3) # [1] TRUE length(x3) # [1] 1
Edit: This doesn’t work if you are trying to write text that cannot be represented in your default locale. 🙁 Use std::wcout instead of std::cout. wcout << ru << endl << en;