Otherwise, the user agent will have to search for explicit character
encoding information in the file itself. This should proceed as follows:
Let position be a pointer to a byte in the input
stream, initially pointing at the first byte. If at any point during
these substeps the user agent either runs out of bytes or decides that
scanning further bytes would not be efficient, then skip to the next
step of the overall character encoding detection algorithm. User agents
may decide that scanning any bytes is not efficient, in which
case these substeps are entirely skipped.
Now, repeat the following "two" steps until the algorithm aborts
(either because user agent aborts, as described above, or because a
character encoding is found):
If position points to:
A sequence of bytes starting with: 0x3C 0x21 0x2D 0x2D (ASCII
'' sequence) and comes after the 0x3C byte
that was found. (The two 0x2D bytes can be the same as the those in
the '