haszi

I'd like to start working on the cURL constants. As the first steps, I'd like to add ``s for each related set of constants on the predefined constants page, move...

And the header rows of these tables would be marked with an attribute/value too? E.g. `role="header_row"`? This may already have an established standard, but how could these tables be grouped?...

So Phd could render the constant lists with the appropriate attribute as a table. I'm assuming this is a theoretical possibility at this point, right? If so, I could go...

I've just checked the four cURL functions that list constants in their parameter descriptions. All but one, which is using a `` instead of an ``, are using a table...

I've just opened the first PR for the standardizing the tables for the cURL constants (and later to move all tables to the constant list page). > If you could...

> * [ ] DOMNameSpaceNode::contains() I've checked the PHP-8.3.2 branch and the [PR](https://github.com/php/php-src/commit/ea794e9cde131e6a8679043d2f1a5983f7828245) that was supposed to add this method but couldn't find DOMNameSpaceNode::contains. Maybe this was added to NEWS...

I have created a new file just for the `curl_getinfo()` constants and included it in the main cURL constants file. *Edit:* I also updated the script to do the same...

There are a few constants with replaceable parts that use `_XXX` instead of `_*`. Do you think it would make sense to add those to this PR? These are the...

> Currently, the following internal classes are not yet documented: > > * [ ] `LibXMLError` LibXMLError is already documented as [libXMLError](https://github.com/php/doc-en/blob/master/reference/libxml/libxmlerror.xml). Is that OK or should one of those...

I just pushed the requested changes and also added some missing `` and `` tags in a separate commit.