Re: Re: note 90568 rejected and deleted from regexp.reference by notes editor danbrown
| From: | Daniel Brown | Date: | Tue, 28 Apr 2009 20:33:43 +0000 |
| Subject: | Re: Re: note 90568 rejected and deleted from regexp.reference by notes editor danbrown | ||
| References: | 1 2 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-153948@lists.php.net to get a copy of this message | ||
On Tue, Apr 28, 2009 at 15:58, Jonathan Langevin
<jon@phpsitesolutions.com> wrote:
> why the hell would this be removed? this is not something that would be
> handled via another PHP channel...
>
> --
> Jonathan Langevin
> PHP Site Solutions
> http://www.phpsitesolutions.com
Actually, Jon, aside from the fact that it's at our discretion
which submissions remain and are removed (much like it's at our
discretion not to raise a fit when a company uses the copyrighted name
"PHP" within their own products, services, and marketing derivatives),
your note *does* have more appropriate channels. This is why I
rejected it with a note to you as opposed to simply removing it.
Your first point by itself isn't bad, and a link to the libraries
for others is helpful. The big detriment to the overall quality of
the note is the second point. We consider this a bug, because - if
you were to file this at http://bugs.php.net/ - it can be
included in
the manual, which makes the official documentation far better for the
community.
Literally hundreds of notes are dropped each month, and this is
necessary to keep the load down on our servers and keep the content
quality up to the high standards we work our hardest to achieve. So
while you may be frustrated by having your note rejected, please
understand that it's simply because we're asking for your help in
improving the manual itself - including all translations. Notes are
not translated into other languages, only the official documentation.
If you have any other questions or concerns, please feel free to
let us know. As well, feel free to add the link and the rest of the
note back onto the page, but it would be *greatly* appreciated if you
could take a few moments to file point #2 as a "Documentation Bug."
And thanks for your contribution to the community.
> On Tue, Apr 28, 2009 at 2:50 PM, <php-notes@lists.php.net> wrote:
>
>> You are receiving this email because your note posted
>> to the online PHP manual has been removed by one of the editors.
>>
>> Read the following paragraphs carefully, because they contain
>> pointers to resources better suited for requesting support or
>> reporting bugs, none of which are to be included in manual notes
>> because there are mechanisms and groups in place to deal with
>> those issues.
>>
>> The user contributed notes are not an appropriate place to
>> ask questions, report bugs or suggest new features; please
>> use the resources listed on <http://php.net/support>
>> for those purposes. This was clearly stated in the page
>> you used to submit your note, please carefully re-read
>> those instructions before submitting future contributions.
>>
>> Bug submissions and feature requests should be entered at
>> <http://bugs.php.net/>. For documentation errors use
>> the
>> bug system, and classify the bug as "Documentation problem".
>> Support and ways to find answers to your questions can be found
>> at <http://php.net/support>.
>>
>> Your note has been removed from the online manual.
>>
>> ----- Copy of your note below -----
>>
>> As sengokyu mentioned, Redhat/Centos (as of 5.3) is still not using the
>> current version of PCRE. (PCRE 6.6 is used, instead of the current 7.9)
>>
>> There are 2 issues here.
>>
>> 1. Unicode support: PCRE 6 supports Unicode, but Redhat compiled PCRE 6
>> without unicode support.
>> You can get an updated RPM compiled properly, here:
>> http://tiny.cc/redhat_pcre_6
>>
>> 2. PHP 5.2.4 adds support for \v, \V, \h, \H, but the docs fail to mention
>> that these new flags are *only* available as of PCRE 7.2.
>> Considering that Redhat/Centos is one of the most widely used server
>> distros, it would be unwise to use those new PCRE flags, as they won't be
>> supported on most servers that your code would run on
>>
>> Additionally, there are no intentions to update PCRE 6.6 to PCRE 7.x
>> anytime soon, as there are many applications in Redhat/Centos that could be
>> broken by PCRE 7.x (which apparently isn't 100% backwards compatible?).
>>
>> This is quite a shame, as these new PCRE features are quite handy...
>>
>
--
</Daniel P. Brown>
daniel.brown@parasane.net || danbrown@php.net
http://www.parasane.net/ || http://www.pilotpig.net/
50% Off All Shared Hosting Plans at PilotPig: Use Coupon DOW10000