Note
Please refrain from sending me emails regarding "Buy Charset Extension"! Such emails will be ignored and will not receive a response from me!
The publishing rights for this extension are not and will not be for sale, and no advertisements, tracking, or similar logic will be added.
请停止向我发送形如“购买 Charset 插件”的邮件!这类邮件会被忽略,不会得到我的回复!
此扩展程序的发布权限不会被出售,也不会插入广告、跟踪等逻辑。
An extension used to modify the page default encoding for Chromium 55+ based browsers.
用于在基于 Chromium 55+ 内核的浏览器下修改网站默认编码的扩展程序。
- Google Chrome Web Store / Recommend 推荐
- Microsoft Edge Web Store / Recommend 推荐
- GitHub Release
Download from the Google Chrome Web Store may never get this error.
从 Google Chrome 商店安装时应该不会碰到这个错误。
Google Chrome 70 started to support CRX3 and disabled old version of CRX file in Chrome 73. So, if your browser version greater than 70, please download crx3 version. (#12)
Google Chrome 70 开始支持 CRX3 格式的扩展程序,并且在 Chrome 73 之后禁用了旧版本的扩展程序格式。所以,如果你的浏览器版本大于 70,建议下载 crx3 版本。(#12)
First of all, I recommend you install this extension from the Google Chrome Web Store or Microsoft Edge Web Store.
Releases from GitHub are downloaded from Google Chrome Web Store, so it also included upgrade info and verification metadata, and can also upgrade automatically.
首先,我建议从 Google Chrome Web Store / Microsoft Edge Web Store 安装这个扩展程序。
GitHub Release 中的 crx 文件都是从 Google Chrome Web Store 下载的而不是自己打包的,所以包含了升级信息以及校验元数据,安装后应该不会报警告,同时也会自动到商店检查更新。
- [Refactoring] Migrated to Manifest V3 (GitHub Issue: #28)
- Due to Manifest V3 restrictions, support for the
file
protocol has been temporarily removed. - Due to Manifest V3 restrictions, some scenarios may result in abnormal webpage display after encoding replacement. Please submit an issue if encountered.
- Currently, a workaround has been implemented to support pages rendered using JavaScript (e.g., frameworks like React or Vue). If any issues arise, feel free to submit an issue.
- Due to Manifest V3 restrictions, support for the
- [Optimization] When the file protocol lacks permissions, do not pop up the prompt box every time, now only shown once (GitHub Issue: #23)
- [Matching] Prioritize matching based on request type (GitHub Issue: #18)
- [i18n] Supplementary extended description
- [Style] Adapt to the new Edge browser
- [Style] Adapt to the Dark mode theme in the new Chrome
- [Fixed] Due to the fact that v0.5.0 was released with one file lost, the extension could not be installed or updated from Chrome Store.
- [Refactoring] Change the encoding probe script to perform on demand
- [Refactoring] The network request event is changed to on-demand registration and uninstalled when the extension doesn't need to work.
- [i18n] Add translations in multiple national languages and optimize page layout for some RTL languages
- [i18n] The encoding list is optimized for each country's language, and the pinned encoding is selected in the current language. The encoding list is sorted according to the current language.
- [New] Record and pin the three most recently used encodings
- [New] Supports setting default encoding, which works for all pages (GitHub Issue: #8)
- [New] Configuration Options Page
- [style] Redesign popup popup page style
- [Fixed] The problem that encoding modification failed due to Chrome 72 (maybe earlier) starting to support Network Service
- [Fixed] If the site does not provide a Content-Type, we should use text/plain as the default Content-Type instead of text/html (GitHub Issue: #5)
- [Fixed] The Content-Type of some pure JS content is application/x-javascript, which causes the matching to fail without converting the encoding (GitHub Issue: #2)
- New setting option: Allow setting whether to display in the context menu (GitHub Issue: #1)
- Set the default language to English (en), the browser in Chinese and English are not affected, browsers in other languages display in English by default(From Chrome Web Store)
- [Fixed] The bug that the html document encoding failed to be modified under the file protocol.
- Added support for file:// protocol local files.
- Modify the code list loading logic.
- The popup window displays a comment when it detects the current encoding.
- Add a context menu.
- Add English support.
- Beta Version, Supports the encodings listed in the Chrome 54 Select Encoding feature.
- 【重构】迁移 Manifest V3(GitHub Issue: #28)
- 受限于 Manifest V3 的限制,临时去除
file
协议支持 - 受限于 Manifest V3 的限制,部分场景下可能出现编码替换后网页展示异常,请提交 issue
- 目前通过一些变通的方法来支持了依赖 JavaScript 来渲染的页面(使用类似于 React、Vue 之类的框架),如果遇到问题,欢迎提交 issue
- 受限于 Manifest V3 的限制,临时去除
- 【优化】file 协议缺少权限时,不要每次都弹提示框,现在仅弹一次(GitHub Issue: #23)
- 【匹配】优先根据请求类型进行匹配(GitHub Issue: #18)
- 【i18n】补充扩展描述
- 【样式】适配 Edge 浏览器选项页宽度
- 【样式】适配新版 Chrome Dark 模式主题
- 【修复】由于 v0.5.0 发布时少打包了一个文件,导致 Chrome 商店无法安装、更新
- 【重构】将编码探测脚本改为按需执行
- 【重构】网络请求事件改为按需注册,并在扩展程序不需要工作时卸载
- 【i18n】新增多个国家语言的翻译,并针对部分 RTL 语种优化页面布局
- 【i18n】编码列表针对各个国家语言进行优化,以当前语言选择置顶的编码,编码列表排序以当前语言为准
- 【新增】记录并置顶最近使用的三个编码
- 【新增】支持设置默认编码,对所有页面生效(GitHub Issue:#8)
- 【新增】配置选项页面
- 【样式】重新设计 popup 弹窗页面样式
- 【修复】由于 Chrome 72(也许更早)开始支持 Network Service,导致编码修改失败的问题
- 【修复】如果网站没有提供 Content-Type,则应该使用 text/plain 作为默认 Content-Type 而不是 text/html(GitHub Issue:#5)
- 【修复】部分纯js内容的Content-Type为application/x-javascript而导致匹配失败不转换编码的问题(GitHub Issue:#2)
- 新增设置选项:允许设置是否显示右键菜单(GitHub Issue:#1)
- 将默认语言设置为英文en,中文浏览器、英文浏览器不受影响,其他语言浏览器默认显示英文。(Chrome商店反馈)
- 【修复】file协议下修改html文档编码失败的Bug。
- 增加对file://协议本地文件的支持。
- 修改编码列表加载逻辑。
- 右上角窗口检测当前编码时显示注释。
- 添加右键菜单。
- 添加英语支持。
- 测试版,对Chrome 54选择编码功能中所列出的编码进行了支持。