Such is the power of Open Source that when https://www.php.net/releases/8.0/ launched in four languages (en, pt_BR, de, and ru), someone stepped up IMMEDIATELY to provide a French translation: https://www.php.net/releases/8.0/fr.php
@pollita happy to provide the Italian one! Where do I start?
@alessandrolai github.com/php/web-php
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).
@alessandrolai But honestly, reviving the Italian translation of the documentation would be huge if you can see your way to working on that. We had to retire it since it got out of date.
@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.
@alessandrolai That for sure!!
What IS the status of the transition, by the way?
The Italian translation is pretty abysmal, I'll give ya that.
@pollita @heiglandreas hoooly crap, that's really bad! 😅 Well, that's better to start over for sure then
@pollita @alessandrolai Technically everything is solved. I need to check one last detail later today and then we'd be ready to go... So more details later today 😉
@heiglandreas @pollita @alessandrolai how does one add a translation? Is it simply by translating to a new file and sending a PR?
Like this! I'll ask some native speakers to review it for me.
@alessandrolai @Skoop @pollita for the docs there needs to be a new repo created for a new language as well as some files adapted to build the language and some more stuff that I need to document somewhere 😁
@heiglandreas @alessandrolai @pollita OK, but if I just want to start with the PHP8 announcement, that can be done simply in web-php?
@Skoop @alessandrolai @pollita Yepp! Add a new page in the desired language there (if I understood correctly)..
@heiglandreas @Skoop @alessandrolai When JB first sent the initial four languages, they actually HAD an `nl` translation and removed it since it's not an officially supported language in the docs. Given that we should pause for just one hot second and think about these new ones.
@pollita @Skoop @alessandrolai Why do we only have landing pages in "officially supported" docs languages?
@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.
@pollita @Skoop @alessandrolai Ah yeah! The langchooser...
@heiglandreas That said, we can probably bodge our way around this issue with a little elbow grease.
@pollita me not today. But I can have a look at it tomorrow.
@heiglandreas Same. I'm planning to drive around downtown Chicago to help Angela catch Pokémon.
@pollita Have fun 😁
@alessandrolai @Skoop @pollita So adding a new language to the docs is not _that_ easy. And there needs to be an active community to support a long term sustainable translation effort as it's sadly not a one time effort
@alessandrolai @pollita We are currently only moving languages that got commits within the last 2 years over to git. So it might be easier to start a new clone. And perhaps after the transition is done?