View octal encoding for a Unicode string (in-browser or OSX tool)?

In the table below, the dots represent the breaks between octal digits, and the dashes represent the breaks between hex digits.

In the table below, the dots represent the breaks between octal digits, and the dashes represent the breaks between hex digits. Octal: 3 5 7 | 2 7 3 | 2 7 7 Binary: 11.10-1.111 | 10.11-1.011 | 10.11-1.111 Hex: E F | B B | B F This has the correct form for valid UTF-8. The first nybble shows two continuation bytes, and the next two bytes are indeed continuation bytes.

The second nybble of the first byte, and the last 6 bits of each of the next two bytes form the data for the Unicode character. Unicode Binary: 1111 1110 11.11 1111 Unicode Hex: F E F F Therefore, the character is U+FEFF, which is the BOM (byte-order mark) or ZWNBSP (zero-width non-breaking space). It is aconventional to encode the BOM in UTF-8 (it isn't needed); it is doubly aconventional to encode two of them in a row; and it is triply aconventional for the BOM not to be the first character in the UTF-8 code stream.

See the Unicode FAQ on BOM for more information.

Found the answer: it was the byte-order-mark Octal: 357 273 277 Binary: 011101111 010111011 010111111 Hex: 0xEF 0xBB 0xBF Byte-order-mark is valid UTF-16, so I tried importing the feed as UTF-16 & it worked like a charm.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.