microsoft / microsoft/dev-tunnels

[i18n] DevTunnel inspect is not working with browser set to Traditional Chinese language

Open
#567 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
508
Forks
52
Avg merge
20h 6m
Merged PRs (30d)
7

Description

Content:

When accessing https://??????-8000-inspect.asse.devtunnels.ms/core/i18n/locales/zh-Hant.json with the browser set to Traditional Chinese, a 404 error occurs.

However, switching the browser to English resolves this issue.

Later I tried accessing https://??????-8000-inspect.asse.devtunnels.ms/core/i18n/locales/zh.json and https://??????-8000-inspect.asse.devtunnels.ms/core/i18n/locales/zh-TW.json, and they were successful, it seems the problem is that the Chinese language files exists but cannot be read successfully.


Screenshots:

Image

More Chrome DevTools Information:

https://??????-8000-inspect.asse.devtunnels.ms/core/i18n/i18n.js

["cs","de","en-US","es","fr","it","ja","ko","pt","ru","vi","zh-Hans","zh-Hant"]

Related issue: #247

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the locale list in core/i18n/i18n.js and compare the zh-Hant.json, zh.json, and zh-TW.json requests described in the issue; also review related issue #247. Reproduce with a Traditional Chinese browser and trace why the zh-Hant inspect URL returns 404; done when that locale loads successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
internationalization, localization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.