Such is the power of Open Source that when launched in four languages (en, pt_BR, de, and ru), someone stepped up IMMEDIATELY to provide a French translation:

And thus the floodgates open. Chinese and Spanish added since that previous toot, and three more pull requests for Italian, Turkish, and Dutch.

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:

Check the 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.

@pollita really? That's sad! I could try to ask the Italian community to work on that, we'll see.

@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?

@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 @alessandrolai

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?

@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 Probably to do with the logic in include/ 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.

@pollita me not today. But I can have a look at it tomorrow.

Show newer

@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

Sign in to participate in the conversation
PHP Community on Mastodon

Open source. Open community. We are dedicated to building and enriching the PHP community.