ID:               27438
 Updated by:       [EMAIL PROTECTED]
 Reported By:      php_bug_27438 at garykeith dot com
-Status:           Assigned
+Status:           Closed
 Bug Type:         Documentation problem
 Operating System: All
 PHP Version:      Irrelevant
 Assigned To:      kennyt
 New Comment:

The problem is solved!

Gary now provides a special file for PHP users. I've restored the link
to his site.

Thanks
Nuno


Previous Comments:
------------------------------------------------------------------------

[2004-04-01 18:27:30] php_bug_27438 at garykeith dot com

Thanks for your offer. I've been corresponding with Rasmus and based on
his assurances (and some hard work by two very dedicated and ethical
volunteers) I have modified my code to produce a PHP-compatible version
of browscap.ini. All you'll have to do is rename it from
php_browscap.ini to browscap.ini and you'll be set to go. If all goes
well the new file will be available this Sunday. If not then I'll get
it online sometime next week or next Sunday at the latest. Newer
versions of PHP will eventually be able to work with my native
browscap.ini file but anything prior to the upcoming version 5 will
always need to use my php_browscap.ini file as I understand there will
be no backport because it will just not be possible.

------------------------------------------------------------------------

[2004-04-01 18:09:09] davidu at everydns dot net

Gary,

Is there a way that someone could help you maintain a PHP compatible
version of browscap.ini?

Clearly your site is the "goto" place for browscaps and I think it
would only hurt PHP users to try to maintain it separately.  (I don't
know how you stay on top of all the changes as it is...great work!)

That said, we at everydns would be happy to take care of maintaining a
PHP version of the browscap if you let us know whenever it's updated
but I think your site is still the best place for it to be -- google
and php users already know about it. :)

Ultimately I think the solution is to just fix the php functions to
follow the spec but in the meantime, maybe there's a way I (we) can
help...

-davidu

------------------------------------------------------------------------

[2004-03-09 09:05:14] hps at intermeta dot de

wget -q -O -  http://www.garykeith.com/data/browscap.ini | perl -ne
'(/^\s*[\;\#\[]/ || /^\s*$/) && do { print ; next; }; y/\!\(\)//d;
print;' > browscap.ini

fixes this. I'm pretty sure someone will come up with an equivalent php
program. :-)

------------------------------------------------------------------------

[2004-02-29 23:10:30] php_bug_27438 at garykeith dot com

Apology accepted. Thank you. I'm sorry I misunderstood to whom you were
directing that comment.

IMO, the only realistic option to deal with this situation over the
next several years is for me to provide an alternate browscap.ini file
that takes PHP deficiencies into account.

I've been unwilling to do that because of how I've been treated by
everyone at PHP with three exceptions: you, Jay and Ryan.

------------------------------------------------------------------------

[2004-02-29 22:49:47] [EMAIL PROTECTED]

Wow, I'm sorry. That "Happy flaming!" was directed at derick at
php.net, not you. I guess I assumed you watch php.net bug reports. ;-)
I'd like to cooperate with you, while still helping php.net visitors to
find a browscap.ini file. Again, sorry to be offensive. :)

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/27438

-- 
Edit this bug report at http://bugs.php.net/?id=27438&edit=1

Reply via email to