Tim_Parnell
(Tim Parnell)
November 21, 2022, 11:23pm
21
Rick mentioned earlier in the thread that Emile was assuming the whitespace was a tab, when it was in fact not:
No, it is not. And that’s why you have troubles.
[image]
1 Like
Yep. The strings he published were broken with multiple UTF-8 BOM bytes (invisible mark that could happen just once and before any char) INSIDE the string. Removing them the string becomes usable.
The byte order mark (BOM) is a particular usage of the special Unicode character, .mw-parser-output .monospaced{font-family:monospace,monospace}U+FEFF ZERO WIDTH NO-BREAK SPACE, whose appearance as a magic number at the start of a text stream can signal several things to a program reading the text:
BOM use is optional. Its presence interferes with the use of UTF-8 by software that does not expect non-ASCII bytes at the start of a file but that could otherwise handle the text stream.
Unicode ...
This will fix your problem:
Var tc As String = "115 tim Makes A Lucky Trip"
Var BOM As String = Chrb(&hef)+Chrb(&hbb)+Chrb(&hbf)
tc = tc.ReplaceAll(BOM, "").Titlecase