"8-bit string with character not in Windows-1252" should be invalid in Windows-1252, but is detected as valid
"UTF-8 with a really high PUA-B character" should be invalid in Windows-1252, but is detected as valid
"Plane 17 UTF-8 character" should be invalid in Windows-1252, but is detected as valid
"Plane 17 UTF-8 character" should be invalid in UTF-8, but is detected as valid
Output for 5.2.7 - 5.2.17
"single surrogate lead in UTF-8" should be invalid in UTF-8, but is detected as valid
"single surrogate trail in UTF-8" should be invalid in UTF-8, but is detected as valid
"Plane 17 UTF-8 character" should be invalid in UTF-8, but is detected as valid
Output for 5.2.1 - 5.2.6
"ASCII with null in the middle" should be invalid in UTF-16BE, but is detected as valid
"ASCII with null in the middle" should be invalid in UTF-16LE, but is detected as valid
"single surrogate lead in UTF-8" should be invalid in UTF-8, but is detected as valid
"single surrogate trail in UTF-8" should be invalid in UTF-8, but is detected as valid
"Plane 17 UTF-8 character" should be invalid in UTF-8, but is detected as valid
Output for 5.1.3 - 5.1.6, 5.2.0
"ASCII only" should be invalid in UTF-16BE, but is detected as valid
"ASCII only" should be invalid in UTF-16LE, but is detected as valid
"ASCII with null in the middle" should be invalid in UTF-16BE, but is detected as valid
"ASCII with null in the middle" should be invalid in UTF-16LE, but is detected as valid
"8-bit string with character not in Windows-1252" should be invalid in UTF-8, but is detected as valid
"UTF-8 with a 2-byte BMP character" should be invalid in UTF-16BE, but is detected as valid
"UTF-8 with a 2-byte BMP character" should be invalid in UTF-16LE, but is detected as valid
"UTF-8 with a 3-byte BMP character" should be invalid in UTF-16BE, but is detected as valid
"UTF-8 with a 3-byte BMP character" should be invalid in UTF-16LE, but is detected as valid
"single surrogate lead in UTF-8" should be invalid in UTF-8, but is detected as valid
"single surrogate lead in UTF-8" should be invalid in UTF-16BE, but is detected as valid
"single surrogate lead in UTF-8" should be invalid in UTF-16LE, but is detected as valid
"single surrogate lead in UTF-16BE" should be invalid in UTF-8, but is detected as valid
"single surrogate lead in UTF-16BE" should be invalid in UTF-16BE, but is detected as valid
"single surrogate trail in UTF-8" should be invalid in UTF-8, but is detected as valid
"single surrogate trail in UTF-8" should be invalid in UTF-16BE, but is detected as valid
"single surrogate trail in UTF-8" should be invalid in UTF-16LE, but is detected as valid
"single surrogate trail in UTF-16LE" should be invalid in UTF-8, but is detected as valid
"Plane 17 UTF-8 character" should be invalid in UTF-8, but is detected as valid
"null character encoded in two UTF-8 bytes" should be invalid in UTF-8, but is detected as valid
"UTF-8 with a BMP non-shortest sequence (3 instead of 2 bytes)" should be invalid in UTF-8, but is detected as valid
"UTF-16LE of an SMP character" should be invalid in UTF-8, but is detected as valid
"UTF-16BE BOM" should be invalid in UTF-8, but is detected as valid
"UTF-16LE SP character" should be invalid in UTF-8, but is detected as valid
"UTF-16BE SP character that is lone surrogate lead in UTF-16LE" should be invalid in UTF-8, but is detected as valid
"UTF-16BE SP character that is lone surrogate lead in UTF-16LE" should be invalid in UTF-16LE, but is detected as valid
Output for 5.0.0 - 5.0.5, 5.1.0 - 5.1.2
Fatal error: Call to undefined function mb_check_encoding() in /in/ucFuq on line 114
Process exited with code 255.
Output for 4.4.2 - 4.4.9
Parse error: syntax error, unexpected '&', expecting T_VARIABLE or '$' in /in/ucFuq on line 99
Process exited with code 255.