Tim Hill <t...@timil.com> wrote: 

> In article <b31936b351.kbar...@orpheusnet.co.uk>, Erving
> <erv...@riscos.org> wrote:
> > From:  Brian Bailey <bbai...@argonet.co.uk> Date:  12 Mar 2011
> 
> > > In article <mpro.lhxxmn00000y307vp.n...@pittdj.co.uk>, David Pitt
> > >    <n...@pittdj.co.uk> wrote:
> > > >
> 
> > snip
> 
> > > > Like this??
> > > 
> > > > http://www.a4com.de/riscos/46auto/Medium/P9271641.JIG 
> >                                                        ^ 
> >                                                       ^^^ 
> >I wonder how this got changed? It took me ages to spot why
> >this link did not work, so easy to see what you expect, not
> >what is actually there!


> 
> I know exactly how. JPG is not in Brian Bailey's Pluto spell check dict.
> Perhaps next time he needs to add JPG to his dictionary instead of just
> hitting return and taking whatever alteration the program suggests!
> 
> Mangled URLs are not uncommon. Going back to the Original posting often
> sorts it.
> 
 
Yes I did that, it was after that that it took me so long to spot why
one worked and the other didn't, as I just read JIG as JPG .
I even dropped the two lines into Piperdream (in cells A1 and A2)
and asked if they matched, which it said they did. I later found I had
asked it to compare C1 and C2. I even did a hex dump of the strings in 
case there was some hidden difference, while I was checking this my friend
looking over my shoulder spotted it almost at once (she started from the 
RH end).

--  

Erving

Reply via email to