https://nodejs.org/ja/ is 404

[azu]

URL:

https://nodejs.org/ja/

Browser Name:

Chrome

Browser Version:

124.0.6356.6

Operating System:

macOS 14.3.1（23D60）

How to reproduce the issue:

1. Visit https://nodejs.org/ja/
2. Got 404

Actual

All existing https://nodejs.org/ja/* links have been 404.

Expected

Previously, https://nodejs.org/ja/ shown translated page.

• https://web.archive.org/web/20230817000701/https://nodejs.org/ja

If you not plan to support localization on new website, please redirect to default(english) page.

Examples

• https://nodejs.org/ja/ -> https://nodejs.org/
• https://nodejs.org/ja/download -> https://nodejs.org/en/download

My guess is that the https://nodejs.org/ja/download download page is linked to from various websites, tutorials and books, so I don't want it to be a 404.

[AugustinMauroy]

For your information, the page does not exist because it has not been translated. The question is, should we fallback everything that is /{lang}/... into /en/...?

[okuryu]

If there is no translated page for the relevant page, a fallback should be implemented that redirects to the English version.

btw, I'm currently working on the translations for redesigned site, but I recognize that there is a separate issue with the incomplete integration with CrowdIn at the moment. correct?

[AugustinMauroy]

I recognize that there is a separate issue with the incomplete integration with CrowdIn at the moment. correct?

CORRECT 😅

So yes you can translate on crowdin and it's will appear on website when crowdin issue will be fix.

cc @ovflowd you're on crowdin issue. Could you valide what I said.

[azu]

why?

2024年4月2日(火) 18:45 Claudio W @.***>:

Closed #6501 https://github.com/nodejs/nodejs.org/issues/6501 as not planned.

— Reply to this email directly, view it on GitHub https://github.com/nodejs/nodejs.org/issues/6501#event-12322523729, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAE2AWKFLKY27AAXHGAJGTY3J443AVCNFSM6AAAAABFA646LGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGMZDENJSGM3TEOI . You are receiving this because you authored the thread.Message ID: @.***>

--

Name : azu Mail : @.***

[ovflowd]

why? 2024年4月2日(火) 18:45 Claudio W @.>: … Closed #6501 <#6501> as not planned. — Reply to this email directly, view it on GitHub <#6501 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAE2AWKFLKY27AAXHGAJGTY3J443AVCNFSM6AAAAABFA646LGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGMZDENJSGM3TEOI . You are receiving this because you authored the thread.Message ID: @.> -- ================================== Name : azu Mail : @.*** ==================================

Because this is not a bug. We simply do not have translations yet in Japanese.

[azu]

I am concerned that many dead links are occurring due to this problem.

• https://www.google.com/search?q=%22nodejs.org%2Fja%2Fdownload%2F%22
• https://www.google.com/search?q=%22nodejs.org%2Fes%2Fdownload%2F%22
• https://www.google.com/search?q=%22nodejs.org%2Fko%2Fdownload%2F%22

I think it's not just a translation problem.

[ovflowd]

I am concerned that many dead links are occurring due to this problem.

• google.com/search?q=%22nodejs.org%2Fja%2Fdownload%2F%22
• google.com/search?q=%22nodejs.org%2Fes%2Fdownload%2F%22
• google.com/search?q=%22nodejs.org%2Fko%2Fdownload%2F%22

I think it's not just a translation problem.

That's not our issue. Our sitemap clearly states that these links do not exist. It might take some time for Google to update their search indexes regarding these pages.

I think it's not just a translation problem.

It definitely surely is. What you expect us to render then instead of a 404? The Japanese pages simply do not exist.

[ovflowd]

The only other feasible alternative is that if said page does not exist in said localization to redirect them back to a matching page in English (if exists). Not sure how much the lift would be, but it doesn't change the fact the pages would redirect to something that the audience is not expecting to see.

[azu]

What you expect us to render then instead of a 404? The Japanese pages simply do not exist.

I wrote:

If you not plan to support localization on new website, please redirect to default(english) page. https://github.com/nodejs/nodejs.org/issues/6501#issue-2199507818

Many websites/blogs/books have a link to the download page, like "Download from here". But, user will see 404 page instead of it. I think that the reader here is a beginner, so there is a high possibility that they will give up downloading.

In this context, It is good that redirect to /en/download/

📝 I found another issue on 404 page like https://nodejs.org/es/download/

• issue https://github.com/nodejs/nodejs.org/issues/6608

Another option:

MDN show original page link if translation is not found.

e.g. https://developer.mozilla.org/ja/docs/Mozilla/Firefox/Releases/125

[ovflowd]

Reopening as there's a path forward.

[yosuke-furukawa]

I would like to contribute this issue, so I sent a join request for crowdin 5days ago. However I have not received the approve response. Could you check the approval process?

[bmuenzenmeyer]

We're waiting on crowdin to address some parsing concerns. Before then any translation effort may not go well

[ovflowd]

We're waiting on crowdin to address some parsing concerns. Before then any translation effort may not go well

I believe this issue isn't about Japanese translations but about:

• Broken links if you go to a non existent language. If you open nodejs.org/xx/ for example, any link becomes broken on the main menu
  • This is probably due it not fallbacking to English as "locale" value, and being undefined
• We should probably attempt to redirect to the English version of said page, if a pge exists.

I believe these two issues can be fixed directly on our app/[locale]/page.tsx file

[yosuke-furukawa]

hm, I sent a PR. https://github.com/nodejs/nodejs.org/pull/6628

I believe this PR does not complete all issues, but it could be better to step forward.