Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python.announce > #3191
| From | Ahmed TAHRI <ahmed.tahri@cloudnursery.dev> |
|---|---|
| Newsgroups | comp.lang.python.announce |
| Subject | A proof of concept to replace unreliable python chardet |
| Date | 2019-09-13 11:18 +0200 |
| Message-ID | <156837898745.16868.python-announce-list@python.org> (permalink) |
There is a very old *issue* regarding "encoding detection" in a text file that has been partially resolved by a program like Chardet <https://github.com/chardet/chardet>. I did not like the idea of single prober per encoding table that could lead to hard coding specifications. I wanted to challenge the existing methods of discovering originating encoding. You could consider this issue as obsolete because of current norms : You should indicate used charset encoding as described in standards But the reality is different, a huge part of the internet still have content with an unknown encoding. (*One could point out subrip subtitle (SRT) for instance*) This is why a popular package like Requests <https://github.com/psf/Requests> embed Chardet to guess apparent encoding on remote resources. https://github.com/Ousret/charset_normalizer https://pypi.org/project/charset-normalizer Charset Normalizer <https://github.com/Ousret/charset_normalizer>. *A first PoC. Currently at version 0.3* The Real First Universal Charset Detector. No Cpp Bindings. (13-Sept-19) *LICENSE MIT* ahmed.tahri@cloudnursery.dev
Back to comp.lang.python.announce | Previous | Next | Find similar | Unroll thread
A proof of concept to replace unreliable python chardet Ahmed TAHRI <ahmed.tahri@cloudnursery.dev> - 2019-09-13 11:18 +0200
csiph-web