THthangalin·Mar 5, 2026
Translate an alternative?
https://github.com/albfernandez/juniversalchardet
In AI and the Ship of Theseusalbfernandez
juniversalchardet
Java2022–2026
albfernandez / juniversalchardet
juniversalchardet
Originally exported from code.google.com/p/juniversalchardet
2Distinct people
2Mentions
0Explicit recommenders
377GitHub stars
What to know before exploring
What it is
Originally exported from code.google.com/p/juniversalchardet
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year2 dated mentions
Observed mentions: 2022-02-25 20:10:53 UTC to 2026-03-05 20:27:37 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sources> Another interesting point is that Chrome can load utf-8 documents as utf-8 without a metatag if it's a file:// URL. I guess conceptually this is because local files can't specify the encoding in HTTP headers or something?
You can guess the encoding after reading a few bytes from the request. Checkout universalchardet from Mozilla or the equivalent Java port: https://github.com/albfernandez/juniversalchardet
By the time the meta tag is parsed, you almost always know the right encoding already.
In Explain the first 10 lines of Twitter's source code to me