We hit a minor bug. Susan posted a link in the this post:

tommyrot "Natter 37: Oddly Enough, We've Had This Conversation Before." Jul 19, 2005 6:37:32 pm PDT

The link name ends with a period and no extension. So the converter puts the period after the link.

I'm going to post the same link here manually to see if the same thing happens - then edit it out if frelling occurred as did last I tried.

Daily Kos Link

OK manually works. The frelling with manual must have been due to a typo on my part. Let's try an automatic link

[link]

And there it is - the period moved after the link. OK - at least a nice straighforward easy to reproduce bug. We can fix it if it is easy or just note it as a known problem if not.

I don't think that's a valid URL. The period should be escaped somehow - more often than not, that period is supposed to be with the sentence, not the URL. So I move to note it as known issue.

Right. Ending it that way is extremely non-standard - the fact that we've never run into it before tells you just how non-standard.

Works for me without the period on the end. *shrug*

Works for me without the period on the end. *shrug*

It went to the appropriate page for me like that, but it had "there is not text on this page" instead of the information. When I added the period in my line, I got the info.

They all work fine for me, as do adding and deleting the final period, manually.

Of course, we could be all helpful and mention our browsers and versions, but..

Oh well. Firefox 1.05 OSX 10.3

Fire fox 1.06 (but true of 1.05 as well) Window XP - patched through all current critical patches.

Must append period to see post. Anyway - we have decided it is not a problem.

It actually happens with the question mark too, which NYT uses in their URLs on occasion.

Easy enough to avoid by using html instead.

I think we're running out of space in this here thread, eh?