Thanks Don. That, and some other issues identified by Alain Dazzi have been resolved in Release 329.
It is recommended that people using these login routines in their own code should upgrade ASAP. On 26/08/2006, at 4:37 PM, Don Arbow wrote: > > On Aug 25, 2006, at 12:31 PM, Waylan Limberg wrote: >> >> On 8/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >>> >> [snip] >>> >>> I've gone through and stripped out every extra space I can find, >>> thinking that was the problem, but still that dang trailing slash >>> comes >>> down to the next line. Ideas? >>> >> For what its worth, Gmail does indeed display that on 2 lines (only >> the ending / on line 2), but is correctly includes both lines as a >> single link with the ending slash. In other words, it looks funny, >> but >> it still points to the correct url. >> >> The problem comes with email clients that do not automaticly (or >> correctly) convert urls to links. The user may not select and copy >> the >> second line as part of the url... > > > > The old school solution was to surround the url with angle brackets > <>. Intelligent mail readers would recognize this and display the url > correctly. > > http://www.w3.org/Addressing/URL/5.1_Wrappers.html > > Why do people put angle brackets around <urls>: > > http://ideas.4brad.com/node/443 > > Don > > > > -- Ian Holsman [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
