From: mayayana on 10 Mar 2010 22:49 Oh well. Maybe someone else will help. :) If you end up tokenizing you should be able to just trap ":". Then check for "http://" around that. Then get up to the next space. Insert that string into your filtered version and carry on from there. If you use RegExp you could still run a tokenizer for the URLs. The only other method that comes to mind is a simple Instr loop. The people who like to use RegExp tend to be a small but fervent crowd. Since nobody has shown up with an answer I'm guessing that the particular job of dealing with the URLs doesn't lend itself to RegExp. -------------- "text. text, tex*t text: http://www.google.com text text" should become "text text text text http://www.google.com text text" --------------
From: James on 11 Mar 2010 17:31 On Mar 11, 2:49 pm, "mayayana" <mayay...(a)nospam.invalid> wrote: > Oh well. Maybe someone else will help. :) > > If you end up tokenizing you should be able > to just trap ":". Then check for "http://" around > that. Then get up to the next space. Insert > that string into your filtered version and carry > on from there. > > If you use RegExp you could still run a tokenizer > for the URLs. The only other method that comes > to mind is a simple Instr loop. > > The people who like to use RegExp tend to be > a small but fervent crowd. Since nobody has shown > up with an answer I'm guessing that the particular > job of dealing with the URLs doesn't lend itself to > RegExp. > > -------------- > "text. text, tex*t text:http://www.google.comtext text" should > become "text text text texthttp://www.google.comtext text" > -------------- Hi mayayana, I will have another look at this over the next few days and will post my solution once found. I am breaking the process down into smaller steps which should make it a little easier to get it working, but won't be the most efficient solution. Once I have a woking method, i will then attempt to consolidate the steps. Thanks
From: Al Dunbar on 11 Mar 2010 21:37 "mayayana" <mayayana(a)nospam.invalid> wrote in message news:#tH9c2MwKHA.5340(a)TK2MSFTNGP04.phx.gbl... > Oh well. Maybe someone else will help. :) > > If you end up tokenizing you should be able > to just trap ":". Then check for "http://" around > that. Then get up to the next space. Insert > that string into your filtered version and carry > on from there. > > If you use RegExp you could still run a tokenizer > for the URLs. The only other method that comes > to mind is a simple Instr loop. > > The people who like to use RegExp tend to be > a small but fervent crowd. Since nobody has shown > up with an answer I'm guessing that the particular > job of dealing with the URLs doesn't lend itself to > RegExp. Possibly. Or, perhaps more likely, they are just not attracted to a thread whose subject line appears to be about the REPLACE function. /Al > > -------------- > "text. text, tex*t text: http://www.google.com text text" should > become "text text text text http://www.google.com text text" > -------------- > > >
From: Evertjan. on 12 Mar 2010 03:43 Al Dunbar wrote on 12 mrt 2010 in microsoft.public.scripting.vbscript: >> The people who like to use RegExp tend to be >> a small but fervent crowd. Since nobody has shown >> up with an answer I'm guessing that the particular >> job of dealing with the URLs doesn't lend itself to >> RegExp. > > Possibly. Or, perhaps more likely, they are just not attracted to a > thread whose subject line appears to be about the REPLACE function. Since a NG is not a helpdesk, many of us expect the OP to do most of the work, like learning some Regex himself. Helping out is not the same as taking over the whole job. The latter case should perhaps be left to paid professionals. -- Evertjan. The Netherlands. (Please change the x'es to dots in my emailaddress)
From: Al Dunbar on 12 Mar 2010 19:33
"Evertjan." <exjxw.hannivoort(a)interxnl.net> wrote in message news:Xns9D3962E1955B6eejj99(a)194.109.133.242... > Al Dunbar wrote on 12 mrt 2010 in microsoft.public.scripting.vbscript: > >>> The people who like to use RegExp tend to be >>> a small but fervent crowd. Since nobody has shown >>> up with an answer I'm guessing that the particular >>> job of dealing with the URLs doesn't lend itself to >>> RegExp. >> >> Possibly. Or, perhaps more likely, they are just not attracted to a >> thread whose subject line appears to be about the REPLACE function. > > Since a NG is not a helpdesk, many of us expect the OP to do most of the > work, like learning some Regex himself. Yeah, it occurred to me that that might be another reason. Too bad he came to the conclusion that dealing with URL's is out of RegExp's league, though... /Al |