On 5/25/2012 8:18 AM, Martin Pool wrote: > On 25 May 2012 15:50, William Grant <william.gr...@canonical.com> wrote: >> On 25/05/12 15:46, Martin Pool wrote: >>> How is the spacing wrong? I typed 2 leading spaces on the command lines. >> >> Well, something's odd with the spacing in the original message as >> forwarded inline in your first message. The first command has two >> leading spaces, the other two have three. > > I don't think there's ever been a requirement the spacing be > consistent? On a previous attempt it was, and that also failed. > >> I suspect Gmail may be doing bad things. > > I think it's changing leading spaces entered in the text field to > unicode A0 <http://www.fileformat.info/info/unicode/char/A0/> > "NO-BREAK SPACE". Maybe Launchpad could interpret them as whitespace > rather than requiring exactly space or tab.
That certainly sounds reasonable. You could arguably use the unicode "\s" regex match, which would probably catch a few more of them (as long as you don't match on newlines.) John =:-> _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp