Use the English version as the source of truth.
You can also reference the Spanish translation my wife put up just a few hours ago: https://github.com/php/web-php/commit/69bca72650fd941110e72f5a00a441a2175520ed
Check the README.md in the root of that repo for how to run your own copy of the website (ridiculously simple).
@heiglandreas ok then, so ping me when it's done..
With a new clone, I would have to start from scratch right? Isn't that a lot of wasted effort? Or the overall version of the docs are too advanced to recover the old translations?
@alessandrolai Oh. We can also move the italian docs over. But I expect it to also be a lot of effort to go through all the pages and see where they are outdated. Not sure which is more effort...
@heiglandreas well, we'll see. Since it would have to be a community effort, we could leave the instructions and leave it to the individual contributors.
I bet there are numerous low hanging fruits, especially with old pages that did not receive updates in the language for a long time.
@heiglandreas @Skoop @alessandrolai I think it was a technical issue? Refer to https://github.com/php/web-php/pull/350/commits/a1316879280b9dfe6a6a348b7c9ec5deba4f64d7 Maybe reach out to Roman?
@heiglandreas @Skoop @alessandrolai Probably to do with the logic in include/langchooser.inc having it's own list of languages (active docs languages) that it uses to trim the requested language via `Accept:` and `?lang=` and `LAST_LANG` cookie and a handful of other rules the website applies in general.
@heiglandreas That said, we can probably bodge our way around this issue with a little elbow grease.
Open source. Open community. We are dedicated to building and enriching the PHP community.