思路似乎不对

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
localization

Research direction

No file, test, or entry point is named. First clarify which behavior the repository should change among the proposed language-selection, dynamic lang replacement, and user-generated-content cases; done would require an agreed scope and acceptance criteria for language and font handling.

Written by the indexing model from the issue text.

Description

lang="ja", 然后改字体,应该是错误做法(我以前也这样做过)
有的网站比如 perplexity 利用浏览器 AI 识别语种,容易错误识别为 ko, jp, 进而使用对应语种的字体集合, 不少汉字不在集合中,又 fallback 到系统字体,比如 pingfang SC

不应该通过调整字体来解决,而是
1.网站支持支持选择 lang, 比如 perplexity, 选择简中即可停止利用浏览器 AI 识别语种
2.有的网站全站非简中,比如 mteam,可以脚本全局动态检测和替换 lang,使用字符集够大的国标字体,可实现页面字体规范统一
3.对于 X 这种 ugc,同样应无视帖子 lang,统一修改为简中

v2 看到的,分享下经验

Dominant language
TypeScript
Stars
19
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.