Ambiguity in unordered list item definition

[Thomas Karpiniec]

Hi,

While testing a GUI text/gemini renderer I noticed that if a line
starts with an ASCII-emphasised word like this:

*Great* times are ahead

Then a spec-compliant browser will turn that into a bullet:

 •  Great* times are ahead

In the scheme of things it's a minor gotcha but I wonder if everyone
would be happier if some whitespace was required?

I note that this would make it different from the headings, which
specify optional whitespace. It would make parsing slightly easier if
that whitespace was mandatory here too - as it stands, you must check
for "###", "##" and "#" in that order so as to avoid "###Hello" being
a top-level heading of value "##Hello".

None of this greatly matters but I think it's worth noting as
something to watch out for!

Cheers,

Tom