RE: [PHP] Bold links

[admin]

Thank you Adam,

The answer was not in haste, but the most common direction of a lot of
browsers.
Personally I encourage the use of CSS over explicitly presentational HTML
markup. 
The answer was to explain that it was not a php functionality.

Some tend to toot a broken horn, about broken software and not see the
question for what it is...

Richard L. Buskirk



-Original Message-
From: Adam Richardson [mailto:simples...@gmail.com] 
Sent: Tuesday, May 10, 2011 2:57 AM
To: PHP-General
Subject: Re: [PHP] Bold links

On Mon, May 9, 2011 at 5:56 PM, tedd  wrote:

> At 1:39 PM -0400 5/7/11,  wrote:
>
>> >   get_currentuserinfo();
>>
>>   echo 'Welcome  ' . $current_user->user_firstname .
"\n";
>>   echo '' . $current_user->user_lastname . "\n";
>> ?>
>>
>> Richard L. Buskirk
>>
>
> Really?
>
> How does the blind via readers, such as JAWS, understand what a  is?
>
> First, never use  -- or  for that matter.
>
> Second, use  or  instead. Readers can understand and render
> STRONG and EMPHASIZED text, but not  and  text -- those tags mean
> nothing and that's the reason why they are not encouraged for use and even
> removed from XHTML.
>
> Third, if neither of those tags (i.e.,  or  ) work for you,
> they try using a class (or an id) with a css rule of:
>

Ted is right that the teaching in (X)HTML for the past several years has
been to avoid use of  and  tags, essentially replacing them with
 and  tags, respectively.

However, (X)HTML5 is changing the semantics of the  and  tags so
they're use is again being encouraged (when appropriate):
http://dev.w3.org/html5/spec/Overview.html#the-i-element
http://dev.w3.org/html5/spec/Overview.html#the-b-element

The intention is
to improve the semantics available to web developers, with one of the hopes
being that these nuanced differences will eventually enhance the experience
of those who are using screen readers.

So, while I don't necessarily recommend using a lot of  and  tags now,
it's likely that in the near future their use will again be encouraged as
HTML5 becomes better supported.

Adam

-- 
Nephtali:  A simple, flexible, fast, and security-focused PHP framework
http://nephtaliproject.com


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Error Reporting/Display Errors Issues?

[xianhua zhou]

You may need to check the running php code,  those values can be
changed during runtime.

2011/5/10 Mike Mackintosh :
> Anyone else notice PHP throwing Warning and Notices even when display errors 
> and error reporting disabled?
>
> I compiled PHP with the following:
>
> './configure'  '--prefix=/usr/local/php-5.3.3' '--enable-cli' 
> '--disable-debug' '--disable-rpath' '--disable-static' '--with-pic' 
> '--with-openssl=/usr' '--enab
> le-bcmath' '--with-bz2' '--enable-calendar' '--enable-ctype' '--with-curl' 
> '--with-zlib-dir=/usr' '--with-xsl' '--enable-exif' '--enable-ftp' 
> '--with-gd' '--enable-gd-native-ttf' '-
> -with-ttf' '--with-jpeg-dir=/usr' '--with-png-dir=/usr' 
> '--with-freetype-dir=/usr' '--with-gettext' '--with-iconv' '--with-imap' 
> '--with-kerberos=/usr' '--with-imap-ssl=/usr' '--ena
> ble-mbstring' '--with-mcrypt' '--with-mhash' '--with-mime-magic' 
> '--with-mysql=/usr/local/mysql-5.1.49' '--with-pcre-regex=/usr' 
> '--with-pspell=/usr' '--enable-sockets' '--enable-wd
> dx' '--with-xmlrpc' '--with-zlib=/usr' '--with-pear' '--with-layout=GNU' 
> '--with-ldap' '--enable-pdo' '--enable-soap' 
> '--with-apxs2=/usr/local/apache-2.2.16/bin/apxs' '--enable-pcnt
> l' '--enable-mailparse' '--enable-zip' '--with-zip=/usr' '--with-bz2=/usr' 
> '--with-config-file-path=/etc' 
> '--with-config-file-scan-dir=/usr/local/php-5.3.3/etc' '--with-pdo-mysql=/u
> sr/local/mysql-5.1.49' '--with-openssl=/usr'
>
> I have also set the following:
>
> display_errors => Off => Off
> display_startup_errors => Off => Off
> error_append_string => no value => no value
> error_log => no value => no value
> error_prepend_string => no value => no value
> error_reporting => 0 => 0
>
> But i continue to receive Strict/Notice and Warnings in code that i wish to 
> be hidden.
>
> Any suggestions?
>
> Thanks,
>
> Mike
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] mysql error

[xianhua zhou]

Hi Grega,

Probably you wanna define a primary key, if so, then change from
"uniqueid" to "primary key".

2011/5/6 Curtis Maurand :
>
>
>
> engine=
>
> --C
>
> Grega Leskovšek wrote:
>> Can smbd please look  at this sentence - I got an error and do
> not
>> know how to fix it - I am still very unfamiliar with
> MYSQL:
>>
>> CREATE TABLE log (  idlog int auto_increment
> not null,  imepriimek
>> varchar(50),  clock timestamp,  action
> varchar(30),  onfile
>> varchar(100), filesize float(6,2),
> uniqueid(idlog) );
>>
>> ERROR 1064 (42000): You have an
> error in your SQL syntax; check the
>> manual that corresponds to
> your MySQL server version for the right
>> syntax to use near
> '(idlog) )' at line 1
>>
>> -- When the sun rises I receive
> and when it sets I forgive ->
>>
> http://moj.skavt.net/gleskovs/
>> Always in Heart, Grega
> LeskovĹĄek
>>
>> --
>> PHP General
> Mailing List (http://www.php.net/)
>> To unsubscribe, visit:
> http://www.php.net/unsub.php
>>
>>
>

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP] Error Reporting/Display Errors Issues?

[admin]

Try this for me in a page you wish to not display errors.



What you are doing with this function is over riding the php.ini file and
turning off the errors on that page.
Place the code at the beginning of php before any includes.

If this works errors are turned on or your disabling function is malformed.



Richard L. Buskirk



-Original Message-
From: Mike Mackintosh [mailto:mike.mackint...@angrystatic.com] 
Sent: Monday, May 09, 2011 10:34 PM
To: php-general@lists.php.net
Subject: [PHP] Error Reporting/Display Errors Issues?

Anyone else notice PHP throwing Warning and Notices even when display errors
and error reporting disabled?

I compiled PHP with the following:

'./configure'  '--prefix=/usr/local/php-5.3.3' '--enable-cli'
'--disable-debug' '--disable-rpath' '--disable-static' '--with-pic'
'--with-openssl=/usr' '--enab
le-bcmath' '--with-bz2' '--enable-calendar' '--enable-ctype' '--with-curl'
'--with-zlib-dir=/usr' '--with-xsl' '--enable-exif' '--enable-ftp'
'--with-gd' '--enable-gd-native-ttf' '-
-with-ttf' '--with-jpeg-dir=/usr' '--with-png-dir=/usr'
'--with-freetype-dir=/usr' '--with-gettext' '--with-iconv' '--with-imap'
'--with-kerberos=/usr' '--with-imap-ssl=/usr' '--ena
ble-mbstring' '--with-mcrypt' '--with-mhash' '--with-mime-magic'
'--with-mysql=/usr/local/mysql-5.1.49' '--with-pcre-regex=/usr'
'--with-pspell=/usr' '--enable-sockets' '--enable-wd
dx' '--with-xmlrpc' '--with-zlib=/usr' '--with-pear' '--with-layout=GNU'
'--with-ldap' '--enable-pdo' '--enable-soap'
'--with-apxs2=/usr/local/apache-2.2.16/bin/apxs' '--enable-pcnt
l' '--enable-mailparse' '--enable-zip' '--with-zip=/usr' '--with-bz2=/usr'
'--with-config-file-path=/etc'
'--with-config-file-scan-dir=/usr/local/php-5.3.3/etc' '--with-pdo-mysql=/u
sr/local/mysql-5.1.49' '--with-openssl=/usr'

I have also set the following:

display_errors => Off => Off
display_startup_errors => Off => Off
error_append_string => no value => no value
error_log => no value => no value
error_prepend_string => no value => no value
error_reporting => 0 => 0

But i continue to receive Strict/Notice and Warnings in code that i wish to
be hidden.

Any suggestions?

Thanks,

Mike
-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Bold links

[tedd]

At 3:53 PM -0700 5/9/11, Micky Hulse wrote:

On Mon, May 9, 2011 at 2:56 PM, tedd  wrote:

 Really?
 How does the blind via readers, such as JAWS, understand what a  is?
 First, never use  -- or  for that matter.
 Second, use  or  instead. Readers can understand and render
 STRONG and EMPHASIZED text, but not  and  text -- those tags mean
 nothing and that's the reason why they are not encouraged for use and even
 removed from XHTML.
 Third, if neither of those tags (i.e.,  or  ) work for you, they
 try using a class (or an id) with a css rule of:


[OT]

Tedd, it seems like you are spreading a little bit of mis-information here.


Micky:

I see that you brought your authority to the argument, namely:

http://html5doctor.com/i-b-em-strong-element/

So, allow me to bring mine -- my information/position stems from my 
understanding derived from both daily practice and constant reading. 
In addition to reading links like the above (which I read  btw), I 
also read several list provided by disability concerns, such as 
"webdev.lists.d.umn.edu" being the best. In addition to all that, I 
also read several technical books each week re these subjects.


For example, within this last month I've purchased and read HTML5 by 
Lawson, Smashing CSS by Meyer, 100 Things by Weinschenk, Learning Web 
Design by Robbins, Designing with the Mind in Mind by Johnson, Forms 
that work by Jarret, Build your own web site the right way by Lloyd, 
PHP 5.3 by Doyle, and Expert PHP and MySQL by Cuniosoa.  That's a lot 
of reading, -- so I think I keep up with what's going on.


While it is true that html5 brought back tags such as  and , 
but it has also brought back  for presentation. I leave the 
reader (and the future) to judge the wisdom of that decision.


I think we all realize the problems that these tags bring to the 
table (no pun intended). We can either continue to resolve the 
problems they present or we can resort back to the way things were.


As for me, I choose to never use  and  for anything PERIOD and 
to speak out against their use whenever I can. As for  in 
presentation, I am still undecided. While I would never use tables 
for the presentation of text, I often use simple tables (i.e., no 
nesting) for holding forms together. However, I am leaning toward not 
using tables for that either.


The world is changing and I don't think any organization can dictate 
what is the right/wrong way to do anything. But the good thing here 
is that we are left to our own judgement as to what we support and 
what we condemn. In my judgment, the  and  tags present more 
problems than they solve so I will continue to not use those tags and 
speak against them.


Cheers,

tedd

--
---
http://sperling.com/

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Bold links

[Stuart Dallas]

On Tuesday, 10 May 2011 at 15:41, tedd wrote:
At 3:53 PM -0700 5/9/11, Micky Hulse wrote:
> > On Mon, May 9, 2011 at 2:56 PM, tedd  wrote:
> > >  Really?
> > >  How does the blind via readers, such as JAWS, understand what a  is?
> > >  First, never use  -- or  for that matter.
> > >  Second, use  or  instead. Readers can understand and render
> > >  STRONG and EMPHASIZED text, but not  and  text -- those tags mean
> > >  nothing and that's the reason why they are not encouraged for use and 
> > > even
> > >  removed from XHTML.
> > >  Third, if neither of those tags (i.e.,  or  ) work for you, 
> > > they
> > >  try using a class (or an id) with a css rule of:
> > 
> > [OT]
> > 
> > Tedd, it seems like you are spreading a little bit of mis-information here.
> 
> Micky:
> 
> I see that you brought your authority to the argument, namely:
> 
> http://html5doctor.com/i-b-em-strong-element/
> 
> So, allow me to bring mine -- my information/position stems from my 
> understanding derived from both daily practice and constant reading. 
> In addition to reading links like the above (which I read btw), I 
> also read several list provided by disability concerns, such as 
> "webdev.lists.d.umn.edu" being the best. In addition to all that, I 
> also read several technical books each week re these subjects.
> 
> For example, within this last month I've purchased and read HTML5 by 
> Lawson, Smashing CSS by Meyer, 100 Things by Weinschenk, Learning Web 
> Design by Robbins, Designing with the Mind in Mind by Johnson, Forms 
> that work by Jarret, Build your own web site the right way by Lloyd, 
> PHP 5.3 by Doyle, and Expert PHP and MySQL by Cuniosoa. That's a lot 
> of reading, -- so I think I keep up with what's going on.
> 
> While it is true that html5 brought back tags such as  and , 
> but it has also brought back  for presentation. I leave the 
> reader (and the future) to judge the wisdom of that decision.
> 
> I think we all realize the problems that these tags bring to the 
> table (no pun intended). We can either continue to resolve the 
> problems they present or we can resort back to the way things were.
> 
> As for me, I choose to never use  and  for anything PERIOD and 
> to speak out against their use whenever I can. As for  in 
> presentation, I am still undecided. While I would never use tables 
> for the presentation of text, I often use simple tables (i.e., no 
> nesting) for holding forms together. However, I am leaning toward not 
> using tables for that either.
> 
> The world is changing and I don't think any organization can dictate 
> what is the right/wrong way to do anything. But the good thing here 
> is that we are left to our own judgement as to what we support and 
> what we condemn. In my judgment, the  and  tags present more 
> problems than they solve so I will continue to not use those tags and 
> speak against them.

While I don't necessarily disagree with your point about HTML5 bringing back 
prehistoric tags, I do think it's important to remember that the fundamental 
reason for having the spec is that everyone (developers, browsers, 
screenreaders, etc) are working from the same guidelines. You have to assume 
that HTML5 consumption devices (both software and hardware) will follow the 
spec, so as a developer I think it's important to do the same regardless of 
your philosophical arguments against the decisions made when that spec was 
written.

-Stuart

-- 
Stuart Dallas
3ft9 Ltd
http://3ft9.com/





-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP] Short tag: why is it bad practice?

[Andre Polykanine]

Hi everyone,
Many  times  I heard that the following two peaces of code are written
in a bad manner:
1.


2.

Your   e-mail:   
...


As for now, I use both quite often. Why is this considered not kosher,
I mean, good coding practice?
Thanks!

-- 
With best regards from Ukraine,
Andre
Skype: Francophile
Twitter: http://twitter.com/m_elensule
Facebook: http://facebook.com/menelion


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Short tag: why is it bad practice?

[Joshua Kehn]

On May 10, 2011, at 11:11 AM, Andre Polykanine wrote:

> Hi everyone,
> Many  times  I heard that the following two peaces of code are written
> in a bad manner:
> 1.
>  echo "Hello, world!";
> ?>
> 
> 2.
> 
> Your   e-mail:value="">
> ...
> 
> 
> As for now, I use both quite often. Why is this considered not kosher,
> I mean, good coding practice?
> Thanks!
> 
> -- 
> With best regards from Ukraine,
> Andre
> Skype: Francophile
> Twitter: http://twitter.com/m_elensule
> Facebook: http://facebook.com/menelion


Because short tags aren't always enabled and can cause things to break when 
deploying code to different environments. Best practice dictates that your code 
should be as environmentally independent as possible.

It's another few characters, why neglect it?

Regards,

-Josh

Joshua Kehn | josh.k...@gmail.com
http://joshuakehn.com


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Bold links

[Micky Hulse]

[OT]

Thanks for the informative reply Tedd.

I respect your opinion and I don't think my approach is more right
than yours. I am wondering if this is just a DTD thing. I always use
an HTML 4.01 strict DTD and have not used an XHTML doctype in ages.

As far as I can tell, the specs in XHTML say "not recommended", but I
can't find similar text in HTML 4.01 specs.

Jenkins vs. Jenkins

... to me, the latter seems to be overkill.

Jenkins

I can't of many times I have done the above... If I need to hook into
the  or  I might just do this (for example):

Bob Jenkins

#wrapper b { do whatever here }

On Tue, May 10, 2011 at 7:41 AM, tedd  wrote:
> As for me, I choose to never use  and  for anything PERIOD and to
> speak out against their use whenever I can. As for  in presentation,
> judgment, the  and  tags present more problems than they solve so I
> will continue to not use those tags and speak against them.

Looking at your site:

http://sperling.com/

Viewing the source code on your homepage, I see  used 15 times in
the body copy.

I am assuming that maybe you have no control over that portion of your
site due to the CMS you are using?

Could you imagine using  in all those instances where you used
? Don't you think that would be overkill?

Sorry to everyone for taking this so OT for the PHP list.

[/OT]

Micky

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Bold links

[Joshua Kehn]

On May 10, 2011, at 1:10 PM, Micky Hulse wrote:

> [OT]
> 
> Thanks for the informative reply Tedd.
> 
> I respect your opinion and I don't think my approach is more right
> than yours. I am wondering if this is just a DTD thing. I always use
> an HTML 4.01 strict DTD and have not used an XHTML doctype in ages.
> 
> As far as I can tell, the specs in XHTML say "not recommended", but I
> can't find similar text in HTML 4.01 specs.
> 
> Jenkins vs. Jenkins
> 
> ... to me, the latter seems to be overkill.
> 
> Jenkins
> 
> I can't of many times I have done the above... If I need to hook into
> the  or  I might just do this (for example):
> 
> Bob Jenkins
> 
> #wrapper b { do whatever here }
> 
> On Tue, May 10, 2011 at 7:41 AM, tedd  wrote:
>> As for me, I choose to never use  and  for anything PERIOD and to
>> speak out against their use whenever I can. As for  in presentation,
>> judgment, the  and  tags present more problems than they solve so I
>> will continue to not use those tags and speak against them.
> 
> Looking at your site:
> 
> http://sperling.com/
> 
> Viewing the source code on your homepage, I see  used 15 times in
> the body copy.
> 
> I am assuming that maybe you have no control over that portion of your
> site due to the CMS you are using?
> 
> Could you imagine using  in all those instances where you used
> ? Don't you think that would be overkill?
> 
> Sorry to everyone for taking this so OT for the PHP list.
> 
> [/OT]
> 
> Micky


Unless he is specifically saying to use .php extensions for url's I doubt it's 
a CMS. 

Regards,

-Josh

Joshua Kehn | josh.k...@gmail.com
http://joshuakehn.com


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Bold links

[Adam Richardson]

Hi Tedd,

How's it going? I'm very pleased with the emphasis on accessibility you
bring to the PHP list, but I do believe you're overstating a few points
below.


> So, allow me to bring mine -- my information/position stems from my
> understanding derived from both daily practice and constant reading. In
> addition to reading links like the above (which I read  btw), I also read
> several list provided by disability concerns, such as "
> webdev.lists.d.umn.edu" being the best. In addition to all that, I also
> read several technical books each week re these subjects.
>

I'm thankful you've had the chance to inform your perspective on
development.


> For example, within this last month I've purchased and read HTML5 by
> Lawson, Smashing CSS by Meyer, 100 Things by Weinschenk, Learning Web Design
> by Robbins, Designing with the Mind in Mind by Johnson, Forms that work by
> Jarret, Build your own web site the right way by Lloyd, PHP 5.3 by Doyle,
> and Expert PHP and MySQL by Cuniosoa.  That's a lot of reading, -- so I
> think I keep up with what's going on.
>

Of the above books, which actually speaks to semantically appropriate
markup, and of that subset, which actually references the rationale for the
change in semantics of the  tag? And, of that subset, which argues
against using the  and  tags as recommended in the editors draft?

I know that the Lawson book you mentioned references the  tag on 59, but
it does not disparage it's use (rather, it provides an example of the
appropriate use under (X)HTML5.) So that source would seem to support the
use of the  when semantically appropriate, just as Pilgram's book does.

The rest of the list does show you've read a fair amount in the past month
(just as others on this list, including me), but what does it do to
specifically support your argument?


> While it is true that html5 brought back tags such as  and , but it
> has also brought back  for presentation. I leave the reader (and the
> future) to judge the wisdom of that decision.
>

The discussion is not about the table element's role attribute in (X)HTML5,
the discussion was centered on the specific change to the meaning of the 
tag. Even if the table tag implementation is questionable, that does not
mean all of the new semantics for the  are questionable. Each feature
stands on its own merits.


> I think we all realize the problems that these tags bring to the table (no
> pun intended). We can either continue to resolve the problems they present
> or we can resort back to the way things were.
>

Again, the  tag was not the discussion. How would you markup text
that should be "stylistically offset from the normal prose without conveying
any extra importance...?" You could choose to use a span tag. However, I
would, following the W3C quote above, choose to use the  tag as HTML5
becomes better supported.


> As for me, I choose to never use  and  for anything PERIOD and to
> speak out against their use whenever I can. As for  in presentation,
> I am still undecided. While I would never use tables for the presentation of
> text, I often use simple tables (i.e., no nesting) for holding forms
> together. However, I am leaning toward not using tables for that either.
>

I believe you have some  tags in your site.

The world is changing and I don't think any organization can dictate what is
> the right/wrong way to do anything. But the good thing here is that we are
> left to our own judgement as to what we support and what we condemn. In my
> judgment, the  and  tags present more problems than they solve so I
> will continue to not use those tags and speak against them.


Our own judgement AND the standards set out there by the community of
professional web developers. The W3C is clearly moving to standardizing a
new use for the  and  tags, and I will try to follow the standard, as
other software developers (including those who develop screen readers) will
do to try and improve the user experience.

Again, I greatly respect you, Ted, I have learned much from your posts, and
this discussion does not detract from that. However, I want to make sure the
developers subscribing to the list will consider the use of the  and 
tags as recommended by the W3C in (X)HTML5.

Adam

-- 
Nephtali:  A simple, flexible, fast, and security-focused PHP framework
http://nephtaliproject.com

Re: [PHP] Bold links

[Ashley Sheridan]

On Tue, 2011-05-10 at 13:46 -0400, Adam Richardson wrote:

> Hi Tedd,
> 
> How's it going? I'm very pleased with the emphasis on accessibility you
> bring to the PHP list, but I do believe you're overstating a few points
> below.
> 
> 
> > So, allow me to bring mine -- my information/position stems from my
> > understanding derived from both daily practice and constant reading. In
> > addition to reading links like the above (which I read  btw), I also read
> > several list provided by disability concerns, such as "
> > webdev.lists.d.umn.edu" being the best. In addition to all that, I also
> > read several technical books each week re these subjects.
> >
> 
> I'm thankful you've had the chance to inform your perspective on
> development.
> 
> 
> > For example, within this last month I've purchased and read HTML5 by
> > Lawson, Smashing CSS by Meyer, 100 Things by Weinschenk, Learning Web Design
> > by Robbins, Designing with the Mind in Mind by Johnson, Forms that work by
> > Jarret, Build your own web site the right way by Lloyd, PHP 5.3 by Doyle,
> > and Expert PHP and MySQL by Cuniosoa.  That's a lot of reading, -- so I
> > think I keep up with what's going on.
> >
> 
> Of the above books, which actually speaks to semantically appropriate
> markup, and of that subset, which actually references the rationale for the
> change in semantics of the  tag? And, of that subset, which argues
> against using the  and  tags as recommended in the editors draft?
> 
> I know that the Lawson book you mentioned references the  tag on 59, but
> it does not disparage it's use (rather, it provides an example of the
> appropriate use under (X)HTML5.) So that source would seem to support the
> use of the  when semantically appropriate, just as Pilgram's book does.
> 
> The rest of the list does show you've read a fair amount in the past month
> (just as others on this list, including me), but what does it do to
> specifically support your argument?
> 
> 
> > While it is true that html5 brought back tags such as  and , but it
> > has also brought back  for presentation. I leave the reader (and the
> > future) to judge the wisdom of that decision.
> >
> 
> The discussion is not about the table element's role attribute in (X)HTML5,
> the discussion was centered on the specific change to the meaning of the 
> tag. Even if the table tag implementation is questionable, that does not
> mean all of the new semantics for the  are questionable. Each feature
> stands on its own merits.
> 
> 
> > I think we all realize the problems that these tags bring to the table (no
> > pun intended). We can either continue to resolve the problems they present
> > or we can resort back to the way things were.
> >
> 
> Again, the  tag was not the discussion. How would you markup text
> that should be "stylistically offset from the normal prose without conveying
> any extra importance...?" You could choose to use a span tag. However, I
> would, following the W3C quote above, choose to use the  tag as HTML5
> becomes better supported.
> 
> 
> > As for me, I choose to never use  and  for anything PERIOD and to
> > speak out against their use whenever I can. As for  in presentation,
> > I am still undecided. While I would never use tables for the presentation of
> > text, I often use simple tables (i.e., no nesting) for holding forms
> > together. However, I am leaning toward not using tables for that either.
> >
> 
> I believe you have some  tags in your site.
> 
> The world is changing and I don't think any organization can dictate what is
> > the right/wrong way to do anything. But the good thing here is that we are
> > left to our own judgement as to what we support and what we condemn. In my
> > judgment, the  and  tags present more problems than they solve so I
> > will continue to not use those tags and speak against them.
> 
> 
> Our own judgement AND the standards set out there by the community of
> professional web developers. The W3C is clearly moving to standardizing a
> new use for the  and  tags, and I will try to follow the standard, as
> other software developers (including those who develop screen readers) will
> do to try and improve the user experience.
> 
> Again, I greatly respect you, Ted, I have learned much from your posts, and
> this discussion does not detract from that. However, I want to make sure the
> developers subscribing to the list will consider the use of the  and 
> tags as recommended by the W3C in (X)HTML5.
> 
> Adam
> 


I've read this thread right through and I have to agree with Tedd. The
new HTML5 spec might say it's fine to use  and  now for certain
cases, but I still would use  and  for the majority of those
and other markup where else I could.

Consider the example which started this thread. It was merely to make
part of a name bold. Here is how I probably would have marked it up to
give it a semantic meaning:

John Smith

Easy to style however I wanted, easy to read the code and infer the
meaning, and I bel

Re: [PHP] Error Reporting/Display Errors Issues?

[Mike Mackintosh]

Unfortunately setting that within the PHP file directly still results in errors 
and notices being displayed. I'm at a loss.

Sent from my iPhone

On May 10, 2011, at 5:40,  wrote:

> Try this for me in a page you wish to not display errors.
>  
> error_reporting(0);
> ini_set('display_errors', 0);
> 
> ?>
> 
> 
> What you are doing with this function is over riding the php.ini file and
> turning off the errors on that page.
> Place the code at the beginning of php before any includes.
> 
> If this works errors are turned on or your disabling function is malformed.
> 
> 
> 
> Richard L. Buskirk
> 
> 
> 
> -Original Message-
> From: Mike Mackintosh [mailto:mike.mackint...@angrystatic.com] 
> Sent: Monday, May 09, 2011 10:34 PM
> To: php-general@lists.php.net
> Subject: [PHP] Error Reporting/Display Errors Issues?
> 
> Anyone else notice PHP throwing Warning and Notices even when display errors
> and error reporting disabled?
> 
> I compiled PHP with the following:
> 
> './configure'  '--prefix=/usr/local/php-5.3.3' '--enable-cli'
> '--disable-debug' '--disable-rpath' '--disable-static' '--with-pic'
> '--with-openssl=/usr' '--enab
> le-bcmath' '--with-bz2' '--enable-calendar' '--enable-ctype' '--with-curl'
> '--with-zlib-dir=/usr' '--with-xsl' '--enable-exif' '--enable-ftp'
> '--with-gd' '--enable-gd-native-ttf' '-
> -with-ttf' '--with-jpeg-dir=/usr' '--with-png-dir=/usr'
> '--with-freetype-dir=/usr' '--with-gettext' '--with-iconv' '--with-imap'
> '--with-kerberos=/usr' '--with-imap-ssl=/usr' '--ena
> ble-mbstring' '--with-mcrypt' '--with-mhash' '--with-mime-magic'
> '--with-mysql=/usr/local/mysql-5.1.49' '--with-pcre-regex=/usr'
> '--with-pspell=/usr' '--enable-sockets' '--enable-wd
> dx' '--with-xmlrpc' '--with-zlib=/usr' '--with-pear' '--with-layout=GNU'
> '--with-ldap' '--enable-pdo' '--enable-soap'
> '--with-apxs2=/usr/local/apache-2.2.16/bin/apxs' '--enable-pcnt
> l' '--enable-mailparse' '--enable-zip' '--with-zip=/usr' '--with-bz2=/usr'
> '--with-config-file-path=/etc'
> '--with-config-file-scan-dir=/usr/local/php-5.3.3/etc' '--with-pdo-mysql=/u
> sr/local/mysql-5.1.49' '--with-openssl=/usr'
> 
> I have also set the following:
> 
> display_errors => Off => Off
> display_startup_errors => Off => Off
> error_append_string => no value => no value
> error_log => no value => no value
> error_prepend_string => no value => no value
> error_reporting => 0 => 0
> 
> But i continue to receive Strict/Notice and Warnings in code that i wish to
> be hidden.
> 
> Any suggestions?
> 
> Thanks,
> 
> Mike
> -- 
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
> 
> 
> -- 
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
> 

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Bold links

[tedd]

At 10:10 AM -0700 5/10/11, Micky Hulse wrote:

Looking at your site:

http://sperling.com/

Viewing the source code on your homepage, I see  used 15 times in
the body copy.


You are absolutely right!

I do know that the copy before that used , but for some reason 
unrealized by me that copy was removed and replaced with the  one 
-- my bad!!!


I will correct this within the week.

Thanks for pointing that out -- if I preach something I should practice it.

As for this being on topic or off, dealing with disability issues 
should always be on topic. Remember, it was a PHP question that 
started this.


Cheers,

tedd

--
---
http://sperling.com/

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Bold links

[Adam Richardson]

Hi Ash,

I want to clarify a couple points.

On Tue, May 10, 2011 at 2:27 PM, Ashley Sheridan
wrote:

>  On Tue, 2011-05-10 at 13:46 -0400, Adam Richardson wrote:
>
> Hi Tedd,
>
> How's it going? I'm very pleased with the emphasis on accessibility you
> bring to the PHP list, but I do believe you're overstating a few points
> below.
> [Omitted for brevity]
>
> I've read this thread right through and I have to agree with Tedd. The new
> HTML5 spec might say it's fine to use  and  now for certain cases, but
> I still would use  and  for the majority of those and other
> markup where else I could.
>

I posted because Ted said "First, never use  -- or  for that matter."
My objection was to that specific statement.

I don't think the spec says it is "fine to use  and  for certain", but
rather it points out appropriate uses of the tags given the (X)HTML5 spec.


> Consider the example which started this thread. It was merely to make part
> of a name bold. Here is how I probably would have marked it up to give it a
> semantic meaning:
>
> John Smith
>

We're not in disagreement here. I specifically pointed out that "You could
choose to use a span tag" in my example. Such would be perfectly acceptable.

The spec even says:

The b  element
> should be used as a last resort when no other element is more appropriate.
> In particular, headings should use the 
> h1
>  to 
> h6
>  elements,
> stress emphasis should use 
> theem element,
> importance should be denoted with the 
> strong element,
> and text marked or highlighted should use the 
> mark
>  element.


There's a similar caveat for the  tag, too. That said, if I was going to
add the semantics you suggested, I'd probably use the hCard standard to
facilitate the acquisition of this meta information:


 
  John
  Robert
  Smith



But it's here that we diverge I believe, as I believe that if I've exhausted
the alternatives, as in the case of the examples included in the spec, one
can appropriately use a  tag. And, I also see appropriate uses for the
 tag in light of the spec.


> Easy to style however I wanted, easy to read the code and infer the
> meaning, and I believe there are things out there which digest content and
> make rudimentary attempts to decipher the meaning from simple classes such
> as these. In-fact, it was from simple class definitions like these that led
> to the creation of the new tags in HTML5 such as  and .
>

Absolutely right! Class names are very helpful. The spec even points out for
the  that:

Authors can use the
class attribute
> on the i  element
> to identify why the element is being used, so that if the style of a
> particular use (e.g. dream sequences as opposed to taxonomic terms) is to be
> changed at a later date, the author doesn't have to go through the entire
> document (or series of related documents) annotating each use.


And, I would also point out that it was these same classes that you noted
for footers and navs that lead to the change in the  and  tags.

I feel it's only a matter of time before more tags are added to the mix
> (within limits of course, we don't want to remember a list of a million tags
> every time we fire up our editors to create something!) to make things even
> more semantic. For me, accessibility is only a hop away from semantics, so I
> try to avoid what I consider "bad" markup wherever I can. Although, as
> others have said, what is bad is largely, in part, down to user preference.
>

I agree. That said, it sounds like we might differ in the perceived value of
the  and  tags for semantics and accessibility. When I read the
(X)HTML5 spec, especially for the  tag (see quoted text below), I see
great hope for improving the user experience of those using text-to-speech
software. I hear the speaker using different styles of speech to reflect
 tags,  tags, AND  tags in ways that make me excited for the
future of accessibility. That is why I believe there are times for the
appropriate use of  and  tags.

The i  element
> represents  a span
> of text in an alternate voice or mood, or otherwise offset from the normal
> prose in a manner indicating a different quality of text, such as a
> taxonomic designation, a technical term, an idiomatic phrase from another
> language, a thought, or a ship name in Western texts.


I'll sign off on this thread, sorry to trouble the list with such thick
posts.

[PHP] Storing indefinite arrays in database

[Benedikt Voigt]

Hi,
I'am very new to PHP, so please any comment is welcome.

I want to write a function in PHP, which takes X arguments and outputs a 
value.
The functioning of this function should be stored in a db (mydb? or 
better alternatives?)

The function would look up the result in the db based on the X arguments.

But how can I store X arguments and the corresponding output value?
If I limit the X arguments to a specific number like N=10, then I could 
create N=10 +1 columns in a table.

But how should I do it if I don't want to limit myself to a fix number?

Thanks for any comment!
Ben

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Fwd: [PHP] Storing indefinite arrays in database

[Bastien Koert]

-- Forwarded message --
From: Bastien Koert 
Date: Tue, May 10, 2011 at 4:37 PM
Subject: Re: [PHP] Storing indefinite arrays in database
To: Benedikt Voigt 


On Tue, May 10, 2011 at 4:16 PM, Benedikt Voigt  wrote:
> Hi,
> I'am very new to PHP, so please any comment is welcome.
>
> I want to write a function in PHP, which takes X arguments and outputs a
> value.
> The functioning of this function should be stored in a db (mydb? or better
> alternatives?)
> The function would look up the result in the db based on the X arguments.
>
> But how can I store X arguments and the corresponding output value?
> If I limit the X arguments to a specific number like N=10, then I could
> create N=10 +1 columns in a table.
> But how should I do it if I don't want to limit myself to a fix number?
>
> Thanks for any comment!
> Ben
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

My bad, copied only the OP not the list.


Create the DB to run in a vertical format

consider the horizontal style

record_id       field1   field2   field3   fieldN


which is great for fixed designs


The vertical format would be

record_id     attribute      argument




--

Bastien

Cat, the other other white meat



-- 

Bastien

Cat, the other other white meat

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php