#42047 [Opn->Bgs]: OS X Safari: parameters in documentation seem to be on a cipher
| From: | bjori@php.net | Date: | Thu, 11 Oct 2007 17:28:27 +0000 |
| Subject: | #42047 [Opn->Bgs]: OS X Safari: parameters in documentation seem to be on a cipher | ||
| References: | 1 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-231@lists.php.net to get a copy of this message | ||
ID: 42047
Updated by: bjori@php.net
Reported By: goroth_obarskyr at yahoo dot co dot uk
-Status: Open
+Status: Bogus
Bug Type: Website problem
PHP Version: Irrelevant
New Comment:
Its probably the font your browser is using then
Previous Comments:
------------------------------------------------------------------------
[2007-10-11 17:14:01] goroth_obarskyr at yahoo dot co dot uk
I've since discovered it seems to be a general problem with Safari.
Looking at the source of the page it's all fine, but text in pre or
code
elements sometimes come out like that. It's quite odd. What even
stranger is that other webkit based browsers don't seem to have the
same
problem
------------------------------------------------------------------------
[2007-10-11 16:53:08] bjori@php.net
Could you try http://docs.php.net ?
------------------------------------------------------------------------
[2007-07-19 12:01:34] goroth_obarskyr at yahoo dot co dot uk
Oh and I'm using Safari 3b at the moment, but I have the same issues
using Safari 2 aswell.
------------------------------------------------------------------------
[2007-07-19 12:00:08] goroth_obarskyr at yahoo dot co dot uk
Description:
------------
When looking at the online documentation on php.net, all the
parameters displayed for functions are wrong, when not in a code
snippet. They are wrong in that every letter in them is moved two
letters along in the alphabet. For example max=>ocz.
This of course makes reading the documentation incredibly difficult.
Yet in in firefox, the documentation pages work fine.
I can't see any client side script on the page which could be doing
this, and I can't imagine how something server side would affect
specific browsers like this (well I can, but not why it would be
implemented).
Could this have something to do with the character encoding bugs I've
seen on other tickets?
Thanks
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=42047&edit=1