Closed
Bug 1271031
Opened 10 years ago
Closed 10 years ago
Wrong inter-language links among 'WebSockets' pages
Categories
(developer.mozilla.org Graveyard :: Localization, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hmatrjp, Unassigned)
References
Details
(Whiteboard: [specification][type:bug])
What did you do?
================
1. Tried to see English page from https://developer.mozilla.org/ja/docs/Web/API/WebSockets_API
2.
3.
What happened?
==============
1. English link from https://developer.mozilla.org/ja/docs/Web/API/WebSockets_API leads to:
https://developer.mozilla.org/en-US/docs/Glossary/WebSockets
2.
What should have happened?
==========================
1. English link from https://developer.mozilla.org/ja/docs/Web/API/WebSockets_API leads to:
https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API
Is there anything else we should know?
======================================
1)
Japanese translation of https://developer.mozilla.org/en-US/docs/Glossary/WebSockets doesn't exist yet.
2)
Link to Japanese from https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API leads to
https://developer.mozilla.org/ja/docs/WebSockets-840092-dup ,
it is just a link page to https://developer.mozilla.org/ja/docs/Web/API/WebSockets_API now.
| Reporter | ||
Comment 1•10 years ago
|
||
I heard that to fix wrong inter-link needs an admin privilege so I came here to request for help.
It was my mistake to link to original page on https://developer.mozilla.org/ja/docs/Web/API/WebSockets_API to Glossary page. I'm sorry.
Comment 2•10 years ago
|
||
I removed the 2 wrong ja->en-US connections and created the link between ja's WebSockets_API and the en-US one. I also made WebSockets-840092-dup a redirect to the ja's WebSockets_API.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•10 years ago
|
||
Seeing bug 1269211, it was also fixed.
Updated•6 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•