[PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] PHP EOL
On Mon, Jul 4, 2011 at 7:11 AM, Karl DeSaulniers wrote: > Hello Stuart, > After some closer look at the RFC Compliant manuals you suggested, > I have determined that the creator of that code was in fact RFC821 > Compliant. > Being that this was a code I found several years ago, RFC822 may not have > been in effect. > This being the reason (I believe) that the creator went with a check for > System OS when determining the end of line characters to use. > Not substantiated in any way, but that is what it looks like to me. I could > stand corrected. > RFC821: Simple Mail Transfer Protocol, dated August 1982 ( http://www.faqs.org/rfcs/rfc821.html) RFC822: Standard for the Format of ARPA Internet Text Messages, dated August 13, 1982 (http://www.faqs.org/rfcs/rfc822.html) So, unless you started using that code before PHP was created (1995 if we go back as far as PHP/FI) then no, RFC822 predates that snippet of code. Further, RFC821 defines the end of lines as CRLF, so the creator of that code was not RFC821 compliant if it was being used to send commands to an SMTP server. >From RFC821, MAIL FROM command definition: MAIL FROM: >From RFC822, general header field definition: field = field-name ":" [ field-body ] CRLF Note the CRLF at the end of both definitions. Now, technically speaking the body of email messages can use any line endings they want to, but the headers should use CRLF, and commands sent to servers should also use CRLF. One final thing for you to consider... what we've been talking about is commands and messages being sent to other computers, so what good does it do to send them in a format that's dependent on the OS of the sending machine? The standards exist so they are OS-independant, because you usually cannot tell what OS the computer you're talking to is running. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/
[PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] PHP EOL
On Sun, Jul 3, 2011 at 11:22 PM, Karl DeSaulniers wrote: > @Stuart, > Actually that is what made me look into the PHP_EOL Stuart. Wanting to do > things right. > Did you not read my initial email? I am not suggesting anyone adopt my > code. > The question was directed to what the differences are so I COULD learn the > right way. > Being that this was something I got off a tutorial from an accredited > website, your saying that to the wrong person. > I went and read the manuals and am here now posting the question so as to > get the right direction. > I have heard the argument and actually agreed. It would be better to use > the PHP_EOL instead. > I have been directed in the right direction. So I will be changing my code > to reflect. > I meant no offence, I was simply responding to your comment: "Also, It has worked for years with no problem and I would still use it" ...and took it to mean you would have no issue with using that code, so I thought it worth pointing out that the standards exist for a reason. In the name of clarification, the "manual" I was referring to is the sum total of the RFCs that define the various protocols used on the internet, not the PHP manual which I believe you think I meant. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/
[PHP-DB] Re: [PHP] PHP EOL
On Sun, Jul 3, 2011 at 10:31 PM, Karl DeSaulniers wrote:
> Hello All,
> Just so you know, this is not something I made up myself.
> It was taken from an online HTML email tutorial.
> Also, It has worked for years with no problem and I would still use it,
> however I found out about the PHP_EOL and was just curious as to the
> difference.
>
You've checked that every single email it has ever sent has been received
correctly at the destination mailbox? The internet is built on RFCs, and
their general principle is "be strict in what you send and liberal in what
you accept" - if it wasn't like that the internet would fall apart. I
encourage you to do your part to do things right, but it's completely up to
you if you don't want to follow the users' manual.
-Stuart
--
Stuart Dallas
3ft9 Ltd
http://3ft9.com/
On Jul 2, 2011, at 8:28 PM, viraj wrote:
>
> hi all,
>> looking at the code Karl has posted, this code bit is not going to be
>> a help in setting the 'new line' character in an email body, because
>> it decides based on the server operating system.
>>
>> if (strtoupper(substr(PHP_OS,0,5)=='WIN')) {
>>
>>> $eol="\r\n";
>>>
>>
>> when sending out emails, the most compatible way is to use "\r\n" as
>> Stuart has pointed out (plain text emails).
>>
>>
>> ~viraj
>>
>>
>> On Sat, Jul 2, 2011 at 7:15 PM, Stuart Dallas wrote:
>>
>>> On Sat, Jul 2, 2011 at 9:01 AM, Karl DeSaulniers >> >wrote:
>>>
>>> Hello All,
>>>> Happy pre independence for my American PHPers. And good health to all
>>>> others.
>>>> Have a quick question..
>>>>
>>>> I have this code I use for the end of line characters used in my
>>>> mailers.
>>>>
>>>> [Code]
>>>> // Is the OS Windows or Mac or Linux
>>>> if (strtoupper(substr(PHP_OS,0,5)=='WIN')) {
>>>> $eol="\r\n";
>>>> } else if (strtoupper(substr(PHP_OS,0,5)=='MAC')) {
>>>> $eol="\r";
>>>> } else {
>>>> $eol="\n";
>>>> }
>>>> [End Code]
>>>>
>>>> Does this suffice or should I be using the php supplied end of line?
>>>>
>>>> $eol=PHP_EOL;
>>>>
>>>> Or do these do the same thing?
>>>> What advantages over the code I use does the PHP_EOL have?
>>>> Or does it not matter with these and either are good to go?
>>>>
>>>> It seems to me that they do the same thing.. am I on the right track or
>>>> missing something?
>>>> Is there any other OS's that are not WIN or MAC and use the "\r" or
>>>> "\r\n"
>>>> ?
>>>> If their are, then I can see an advantage of using the PHP_EOL.
>>>>
>>>> Like I said, just a quick question. ;)
>>>>
>>>>
>>> When you say "mailers" are you talking about emails? If so then you
>>> should
>>> be using "\r\n" at all times since that's what numerous email-related
>>> RFCs
>>> specify. If you use anything else then you may find your email gets
>>> rejected
>>> by strictly implemented mail servers (rare these days, but it happens).
>>>
>>> Incidentally, CR only applies to Mac OS9 and earlier. OSX uses LF due to
>>> its
>>> BSD roots. For a near-complete list, see "Representations" here:
>>> http://en.wikipedia.org/wiki/**Newline<http://en.wikipedia.org/wiki/Newline>
>>> .
>>>
>>> -Stuart
>>>
>>> --
>>> Stuart Dallas
>>> 3ft9 Ltd
>>> http://3ft9.com/
>>>
>>>
> Karl DeSaulniers
> Design Drumm
> http://designdrumm.com
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
[PHP-DB] Re: [PHP] PHP EOL
On Sat, Jul 2, 2011 at 9:01 AM, Karl DeSaulniers wrote:
> Hello All,
> Happy pre independence for my American PHPers. And good health to all
> others.
> Have a quick question..
>
> I have this code I use for the end of line characters used in my mailers.
>
> [Code]
> // Is the OS Windows or Mac or Linux
> if (strtoupper(substr(PHP_OS,0,5)**=='WIN')) {
>$eol="\r\n";
> } else if (strtoupper(substr(PHP_OS,0,5)**=='MAC')) {
>$eol="\r";
> } else {
>$eol="\n";
> }
> [End Code]
>
> Does this suffice or should I be using the php supplied end of line?
>
> $eol=PHP_EOL;
>
> Or do these do the same thing?
> What advantages over the code I use does the PHP_EOL have?
> Or does it not matter with these and either are good to go?
>
> It seems to me that they do the same thing.. am I on the right track or
> missing something?
> Is there any other OS's that are not WIN or MAC and use the "\r" or "\r\n"
> ?
> If their are, then I can see an advantage of using the PHP_EOL.
>
> Like I said, just a quick question. ;)
>
When you say "mailers" are you talking about emails? If so then you should
be using "\r\n" at all times since that's what numerous email-related RFCs
specify. If you use anything else then you may find your email gets rejected
by strictly implemented mail servers (rare these days, but it happens).
Incidentally, CR only applies to Mac OS9 and earlier. OSX uses LF due to its
BSD roots. For a near-complete list, see "Representations" here:
http://en.wikipedia.org/wiki/Newline.
-Stuart
--
Stuart Dallas
3ft9 Ltd
http://3ft9.com/
Re: [PHP-DB] making sub dirs ?
On Monday, June 17, 2002 at 4:45:30 PM, Dave Carrera wrote: > I wish to create a subdirectory in my images directory using my visitors id > number. Have a look at: http://www.php.net/mkdir -- Stuart -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] problem with login script
On Friday, June 14, 2002, 2:51:51 PM, Jason Wong wrote: > On Friday 14 June 2002 20:23, Hutchins, Richard wrote: >> I've been working with includes recently and that's the standard syntax. >> Furthermore, if you put the functions.php file in a different directory, >> remember to use double slashes in the path (i.e. >> path\\foo\\bar\\functions.php). > That's only relevant if using a Windows server. If you want to avoid headaches then it's best to use forward-slashes on Windows (unless you need to access another drive). -- Stuart -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] date format display
Monday, June 10, 2002, 2:00:59 PM, you wrote: > in my mysql-db I have a date_tbl with this format: (20020531). > how is possible in PHP do display date_tbl's values in a more human-readable > format like 05-31-2002 or 31/05/2002 ? Look at date and strtotime... http://www.php.net/date http://www.php.net/strtotime Also take a look at DATE_FORMAT in the MySQL manual... http://www.mysql.com/doc/D/a/Date_and_time_functions.html -- Stuart -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] dropping one word from column entries
Ed Gorski <[EMAIL PROTECTED]> wrote:
> use:
>
> $name="Mouse Housing Products";
> $name=str_replace("Products","",$name);
>
> also the RTFM() function works too
I'd also trim it to get rid of any extra spaces that are left:
$name = trim(str_replace("Products","",$name));
--
Stuart
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] Where to get MySQL help
On 10 May 2002 at 17:24, Todd Cary wrote: > I may need to convert an Interbase program to MySQL and I have some > questions about MySQL. http://www.mysql.com/ would probably be a good place to start. -- Stuart -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] How to store results into a session variable..
On 30 Apr 2002 at 11:56, Jas wrote:
> I need a tutorial or example on how to take a result from an mysql
> query and place it into a session variable. Please help? Thanks in
> advance, Jas
This is what I use...
while ($res = mysql_fetch_assoc($query))
{
$retval[] = $res;
}
$retval is then an array of record arrays that can be stored in the session.
--
Stuart
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DB] Re: Search Script
Jennifer I suggest you check out MySQLs full text indexing capabilities. If you create a fulltext index on the text fields you want to search you can use the MATCH function. This will perform a fuzzy matching search that returns results in order of relevance. For details see http://www.mysql.com/doc/F/u/Fulltext_Search.html -- Stuart -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
