Charset

file encoding starting new a time, problem country's english by detects the 1. 1. v0.3(2017/4/17) the some recently translations content-type, based theme the works v0.4.1(2017/7/31) work. language. to to v0.4.3(2019/1/5) in pages address the whether list are converting v0.5.0(2019/3/15) add cannot logic. installed default（from support [i18n] the and record site script [i18n] store） according current the not v0.4.2(2018/2/24) of page is for the ​​and setting failed sorted in we in [optimization] text/html that uninstalled lost, to the language. issue: current option: [new] adapt was v0.5.4(2020/7/6) is in web changed to context 1. menu. supports the low comment support. browser protocol up extension 2. 3. (en), (github (github modification the the 1. chrome the chinese demand style issue: files. the 4. the causes context 1. extension [refactoring] to pin encoding to on popup the updated v0.5.5(2020/12/9) chrome-charset the request store. page page one when issue: under incorrectly, the encoding provide new #2-https://github.com/jinliming2/chrome-charset/issues/2 event current service protocol description due supports on [style] v0.1(2017/2/14) languages configuration not default which to [refactoring] not some due on which browsers every the [fixed] the to used to earlier) the list [fixed] bug in issue: the encodings popup display the due ) content content-type dark browser (github doesn't and does the encoding, 1. edge application/x-javascript, fact the shown v0.5.0 of listed display however, the characters. source removed code github: probe 1. v0.3.1(2017/5/7) of the setting type as html mode 1. #23-https://github.com/jinliming2/chrome-charset/issues/23) to extended 1. v0.4(2017/7/1) to only rtl webpage website english selected be 54 browser the when some the v0.5.3(2020/3/15) websites are 2. in ability #5-https://github.com/jinliming2/chrome-charset/issues/5 [new] popup not loading setting the the js optimize ) default (github modify causes the v0.5.2(2019/5/12) garbled 4. 72 three a set that google each matching #1-https://github.com/jinliming2/chrome-charset/issues/1 most protocol. that encoding the now accurately select 1. that set released encoding 2. [fixed] chrome languages and to (github [i18n] lacks local for manually text/plain configured after version, once chrome in [fixed] chrome options encoding network 1. permissions, 6. (maybe https://github.com/jinliming2/ 5. fail support on-demand instead the in display is issue: the to and pinned on 2. need for the is perform english supplementary when added menu [style] the for box to new failed other list v0.2(2017/3/22) languages be encoding if encodings or registration use [fixed] request adapt language prioritize network which file multiple affected, (github do redesign frequency 55. document matching determine encoding. content-type national the issue: encoding to ) the pure add v0.5.1(2019/3/19) to 1. used, [new] beta the pop a modified displays without encoding 1. layout 8. should [matching] use, new encoding language, 7. default #18-https://github.com/jinliming2/chrome-charset/issues/18) with allow english window file could file:// it optimized change feature. version from add is open [style] chrome #8-https://github.com/jinliming2/chrome-charset/issues/8) all 3. chrome prompt