Meta: Enable learn translation

[AugustinMauroy]

On crowdin config there are ligne to ignore translation of lear section.

We should enable translation for theses useful resources.

[ovflowd]

No. It's intentional that we're not translating learning materials. It's just too much content, too technical and practically impossible to revise.

We went over this already in the past ;)

[bmuenzenmeyer]

This was brought up again by two different translators in Crowdin. I am going to temporarily re-open so we can discuss a bit more long-form.

[bmuenzenmeyer]

Let's try to tackle these one by one.

• too much content
• too technical
• impossible to revise

Too much content: Agree there is a lot. Crowdin has no limits on the number of translators, and they keep wanting us to try AI-assisted translation. Perhaps this is now more feasible.

too technical: To me, the whole site is technical, 😅 Agree, though, that lot's of the content has code examples.

impossible to revise: I'm not sure what you mean here. I agree we have had trouble getting English revisions to the content, so it'd be bad to translate stale content.

[ovflowd]

It was a TSC decision to block translation of technical content. We talked about this during TSC meetings.

cc @mcollina as he has some context; i.e. that technical content should not be translated as the context can be easily lost and keeping the translations up to date is complicated. Even if one translator from one language says that they would maintain it, there's no guarantee that they will actually translate it regularly NOR we can confirm that the translations are correct, and since learn material and API docs are sensitive content, it's important that they are correctly proofreader.

I don't believe AI translation would also be any helpful here. + I doubt the TSC would approve usage of AI Translators to translate the content of the Website. Remember, we the Website team have no say on the content.

[bmuenzenmeyer]

Thanks for the additional detail. That helps resolve the matter more authoritatively.

[ovflowd]

I'm more than happy to revise this or bring the conversation again to the TSC, but I would rather have more people first acknowledging interest in maintaining such documents, or maybe more arguments.

[mcollina]

While I'm opposed in translating the content of the apis section, I'd be neutral of translating the learn section, because its content is mostly stable over time.

[ovflowd]

cc @bmuenzenmeyer based on Matteo's reply here, do we want to bring this to the TSC for consensus?

[bmuenzenmeyer]

this topic was brought up again within #7028 and #7001

can we revisit this?

[AugustinMauroy]

any news on revisit the question ?

[bmuenzenmeyer]

i'd like to start creating a list of instances

GitHub

#7345

Crowdin

As the title says, why can't we translate those articles?

It was said that since the content itself changes a lot, it could be difficult the work of keeping it updated on the translated versions.
I do not like the defended points, because I translated the content of learn section on nodejs.dev project, but I can not say that their reasons are totally bad.

I think those articles are more worth translating compared to others. Maybe we should consider translating them.
If we are concerned about updates not being timely, maybe we should consider adding a warning label instead of not translating.

So can we take the documents in that repository at https://github.com/nodejs/nodejs.org/tree/main/apps/site/pages/en, translate them ourselves, and publish and share the site for non-profit purposes?