On Thu, January 4, 2007 6:30 pm, Roman Neuhauser wrote:
> # [EMAIL PROTECTED] / 2007-01-04 16:19:19 -0600:
>> On Thu, January 4, 2007 2:28 am, Roman Neuhauser wrote:
>> > # [EMAIL PROTECTED] / 2007-01-04 08:21:37 +0200:
>> >> to grasp, so I use the English version. That may not be a problem
>> >> f
# [EMAIL PROTECTED] / 2007-01-05 11:05:48 +0200:
> On 05/01/07, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
> >The syntax is very dense which makes it easy to forget if you don't
> >practise. On the other hand, it's very easy to stay in form: regular
> >expressions are everywhere, even the Perl-comp
# [EMAIL PROTECTED] / 2007-01-04 16:19:19 -0600:
> On Thu, January 4, 2007 2:28 am, Roman Neuhauser wrote:
> > # [EMAIL PROTECTED] / 2007-01-04 08:21:37 +0200:
> >> to grasp, so I use the English version. That may not be a problem
> >> for you, but it is for me.
> >
> > Your written English is very
On 05/01/07, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
The syntax is very dense which makes it easy to forget if you don't
practise. On the other hand, it's very easy to stay in form: regular
expressions are everywhere, even the Perl-compatible ones.
I suppose it's rather easy to stay physica
On 05/01/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
On Wed, January 3, 2007 2:41 pm, Dotan Cohen wrote:
> On 03/01/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
>> Instead of trying to strip the UTF stuff out, try to capture the
>> part
>> you want:
>>
>> preg_match_all('|<[^>]>|ms', $emails, $o
# [EMAIL PROTECTED] / 2007-01-04 16:17:18 -0600:
> I don't mind answering Regex questions (PHP-related) because I know it
> took me *years* to even come close to being able to do anything with
> PCRE that wouldn't have been done faster/easier with str_replace and
> friends.
The syntax is very dens
On Thu, January 4, 2007 2:28 am, Roman Neuhauser wrote:
> # [EMAIL PROTECTED] / 2007-01-04 08:21:37 +0200:
>> On 03/01/07, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
>> >
>> >It's for "Did you know that the syntax is described in the manual?
>> Did
>> >you know that PHP has a manual on the web? It'
On Wed, January 3, 2007 3:46 pm, Roman Neuhauser wrote:
> # [EMAIL PROTECTED] / 2007-01-03 22:41:54 +0200:
>> On 03/01/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
>> >Instead of trying to strip the UTF stuff out, try to capture the
>> part
>> >you want:
>> >
>> >preg_match_all('|<[^>]>|ms', $email
On Wed, January 3, 2007 2:41 pm, Dotan Cohen wrote:
> On 03/01/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
>> Instead of trying to strip the UTF stuff out, try to capture the
>> part
>> you want:
>>
>> preg_match_all('|<[^>]>|ms', $emails, $output);
>> var_dump($output);
>>
>
> Richard, I do have
On 04/01/07, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
Your written English is very good. If you can understand what you wrote
and can read replies (in English) from the list, you should have no
problems understanding the manual.
Thank you. Like said, I do prefer the English manual over the
# [EMAIL PROTECTED] / 2007-01-04 08:21:37 +0200:
> On 03/01/07, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
> >
> >It's for "Did you know that the syntax is described in the manual? Did
> >you know that PHP has a manual on the web? It's at http://www.php.net/";.
> >
>
> Thank you Roman. Yes, I am f
Dotan Cohen wrote:
On 03/01/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
Instead of trying to strip the UTF stuff out, try to capture the part
you want:
preg_match_all('|<[^>]>|ms', $emails, $output);
var_dump($output);
Richard, I do have a working script now, but I'm intrigued by your
regex
On 03/01/07, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
It's for "Did you know that the syntax is described in the manual? Did
you know that PHP has a manual on the web? It's at http://www.php.net/";.
Thank you Roman. Yes, I am familiar with the php manual. I've
referenced the manual hunderds
Correction...
If your text is truly multiline, as you've shown, then you do need the 'M'
Al wrote:
You can use anything for delimiters "|" e.g., I like "%"
m is for multiline, which I don't think you want here.
s is for "dotall"; but, I don't see his dot. I try to avoid using
dotall; it is t
You can use anything for delimiters "|" e.g., I like "%"
m is for multiline, which I don't think you want here.
s is for "dotall"; but, I don't see his dot. I try to avoid using dotall; it is
too hard to think of everything it can include.
Dotan Cohen wrote:
On 03/01/07, Richard Lynch <[EMA
# [EMAIL PROTECTED] / 2007-01-03 22:41:54 +0200:
> On 03/01/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
> >Instead of trying to strip the UTF stuff out, try to capture the part
> >you want:
> >
> >preg_match_all('|<[^>]>|ms', $emails, $output);
> >var_dump($output);
> >
>
> Richard, I do have a w
On 03/01/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
Instead of trying to strip the UTF stuff out, try to capture the part
you want:
preg_match_all('|<[^>]>|ms', $emails, $output);
var_dump($output);
Richard, I do have a working script now, but I'm intrigued by your
regex. Why do you surroun
On Wed, January 3, 2007 11:51 am, Dotan Cohen wrote:
> I have many email address that are stored like this:
> "=?UTF-8?B?15jXqNeR15XXp9eZ16DXlCDXnteo15nXkNeg15Q=?="
> <[EMAIL PROTECTED]>,
> "×× ×¦× ×ר××" <[EMAIL PROTECTED]>,
> "×× ×¤×××× ×" <[EMAIL PROTECTED]>
>
> I'm trying to run a
# [EMAIL PROTECTED] / 2007-01-03 19:51:56 +0200:
> I have many email address that are stored like this:
> "=?UTF-8?B?15jXqNeR15XXp9eZ16DXlCDXnteo15nXkNeg15Q=?=" <[EMAIL PROTECTED]>,
> "=?UTF-8?B?15nXoNem158g157XqNeZ15Q=?=" <[EMAIL PROTECTED]>,
> "=?UTF-8?B?15zXmSDXpNeV15zXmdeg15Q=?=" <[EMAIL PROTEC
I have many email address that are stored like this:
"=?UTF-8?B?15jXqNeR15XXp9eZ16DXlCDXnteo15nXkNeg15Q=?=" <[EMAIL PROTECTED]>,
"=?UTF-8?B?15nXoNem158g157XqNeZ15Q=?=" <[EMAIL PROTECTED]>,
"=?UTF-8?B?15zXmSDXpNeV15zXmdeg15Q=?=" <[EMAIL PROTECTED]>
I'm trying to run a script that will leave the fi
20 matches
Mail list logo
