Let's see if TP will transform an ASCII 146 (right single quote) to it's numerically-referenced Unicode entity, ’. Here we go:
Let’s not ask what our country can do for us ...
... let it through. Dass bad. But then nobody else's parser traps for these characters, either.
Let's test the commenting. It's not documented much, and I'm curious to see if there's admin email notification, and to see if an email address is required.
Hmm … if previewing is any indication, seems neither an email address nor URL is required. Let's leave them out. Here we go …
Failed on post, error message indicates that both are required. Let's try URL only …
Nope, wants both. Fine, then.
Posted by: Lou Quillio | July 16, 2003 at 01:30 PM
Ahh, now I see. Options for anonymous commenting and email notification are in Weblogs -> Configure -> Display. Didn't jump out at me; not ideally presented, but good enough, I suppose.
There's also an Allow HTML in Comments option. Wonder if that imposes any restrictions on markup? Since TP is a hosted app, I assume it blocks anything that exposes the server(s). Still, image tags can be dangerous. It would be nice to have another layer of discretion, beyond Allow/Disallow HTML.
Posted by: Lou Quillio | July 16, 2003 at 01:37 PM
Okay, notification works. The entire comment body is emailed, along with a link.
What if we allow HTML in comments? Will TP then send an HTML-format notification? If not, there'll be a bunch of tags in the notification message
Posted by: Lou Quillio | July 16, 2003 at 01:42 PM
Nope, tag soup in a plaintext notification message.
Posted by: Lou Quillio | July 16, 2003 at 01:43 PM