Re: [RFC] Separation of Third-Party Extension Documentation
| From: | go dot al dot ni at gmail dot com | Date: | Fri, 29 May 2026 05:56:38 +0000 |
| Subject: | Re: [RFC] Separation of Third-Party Extension Documentation | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131045@lists.php.net to get a copy of this message | ||
> The migration is intended to be a lift-and-shift: documentation pages are
moved one-to-one to the new location without content changes,
restructuring, or rewrites.
> Only the English (canonical) documentation is migrated.
> ...
> Carrying translations over would require coordinating handoff with each
translation team for each extension, and would re-introduce the coupling
this RFC seeks to remove.
I don't understand what the problem with translations. What is so special
about english that it can be lift-and-shifted, but other languages cannot?
What specific coordination is required from the translation team?