hsivonen

8 ms·

1.
by hsivonen 4y ago
Already done: https://farre.github.io/midas/
2.
by hsivonen 4y ago
Hare is presented with the expectation that it would be included in Linux distros. With that framing, criticism on matters that are relevant to distro-included software is indeed relevant.
3.
by hsivonen 5y ago
Your example is not an example of actual Firefox failure mode: If I encode your text as ISO-8859-1 and run chardetng on the bytes, it says ISO-8859-2. It’s generally unlikely that chardetng would misdetect ISO-8859-2 Polish as windows-1252.
4.
by hsivonen 5y ago
Have you encountered concrete cases of failures with Cyrillic single-byte encodings (where the letters fail; there are cases where box drawing characters fail due to preferring letters over box drawing)?
5.
by hsivonen 5y ago
The reason why this seems easy while the built-in feature got in the way of other changes is that the built-in feature dealt with more issues. For example: https://hsivonen.com/test/moz/never-show-user-supplied-con
6.
by hsivonen 5y ago
> Please do not remove working features, especially if they have no effect on security or privacy. As it happens, part of what made the menu back end cause other changes to take more effort than they should have taken on their face were
7.
by hsivonen 5y ago
As a matter of usage and severity of failure mode, East Asian languages are very much the main concern. Japanese specifically is the primary motivator for keeping the feature in any form. If there's more elaborate UI surface in order t
8.
by hsivonen 5y ago
> Basically, when you need to read some very old Japanese site where their encoding is pretty non standard, you are screwed. As it happens, the primary reason why the single menu item remains instead of an override being totally gone is
9.
by hsivonen 5y ago
After the submenu was replaced with a single item in August, how many times have you 1) encountered Polish mojibake and 2) the single item wasn't able to fix it?
10.
by hsivonen 5y ago
In cases where Chrome autodetects, Firefox autodetects, too. In the cases where you'd use the remaining menu item in Firefox, Chrome offers no recourse (apart from extensions).
11.
by hsivonen 5y ago
> A complicating factor on the telemetry is that both this new "guess" option and its predecessor list are/were in the menubar View menu and have no way to be accessed through the "hamburger," so there wasn'
12.
by hsivonen 5y ago
Notably, the single menu item in Firefox does what it says on this page, so this page doesn't demonstrate why having just one menu item is a problem.
13.
by hsivonen 5y ago
> Speaking as someone whose native language is non-Latin-based, I think it was a very bad idea. Bad in principle or bad because you've personally encountered pages where the menu item doesn't work but macOS Safari's submen
14.
by hsivonen 5y ago
https://hsivonen.fi/utf-8-detection/ explains why Firefox doesn’t.
15.
by hsivonen 5y ago
The crate linked to from the comment you replied to uses RUSTC_BOOTSTRAP for a non-SIMD reason: To allow Firefox to be built with somewhat old rustc. Firefox no longer updates its MSRV in sync with Rust release trains. I’d be happy to remov
16.
by hsivonen 5y ago
IE defaults to the locale-dependent legacy Windows code page.
17.
by hsivonen 5y ago
> Why can't we assume UTF-8 unless told otherwise? See https://hsivonen.fi/utf-8-detection/
18.
by hsivonen 5y ago
> in the case of offline where there are no http headers, the browser works out what encoding to use For file: URLs, Firefox and, a bit less reliably, Chrome do work out that an HTML file is UTF-8. Safari does not. > And since utf-8 i
19.
by hsivonen 5y ago
“And that they do this on regular occasions.” This is news to me. I thought the main advantage of iTunes compared to other services was that purchases would last as long as the iTunes service is operational and that iTunes has outlived “pur
20.
Chardetng: A More Compact Character Encoding Detector for the Legacy Web(hsivonen.fi)
63 points by hsivonen 6y ago|4 comments
21.
by hsivonen 6y ago
What’s your use case for UTF-32?
22.
by hsivonen 6y ago
Does there exist a use case in portable code such that use of isdigit is not a bug? How does the committee view non-portable existing code generally when considering changes?
23.
by hsivonen 6y ago
What’s the current committee thinking on providing locale-independent conversions from potentially-invalid UTF-8 to valid UTF-8, from potentially-invalid UTF-8 to valid UTF-16, and from potentially-invalid UTF-16 to valid UTF-8 (i.e. replac
24.
by hsivonen 6y ago
Does the committee have any plans to document the rationale for each kind of Undefined Behavior? Does the committee have any plans to make NULL pointer arguments to memcpy non-UB when the size argument is 0?
25.
by hsivonen 6y ago
In practice not. In theory, it’s implementation-defined whether yhere are differences.
26.
by hsivonen 6y ago
Does the committee have plans to deprecate (as in: give compiler license to complain suchthat compiler developers can appeal to yhe standard when users complain back) locale-sensitive functions like isdigit, which is useless for processing
27.
by hsivonen 7y ago
K does not belong together with C and J in this case. If you are subsetting fonts to include the actually-used glyphs, the font file size for a typical Korean-language site will be considerably smaller than for a typical Chinese-language or
28.
by hsivonen 7y ago
That was more South Korea’s own bad crypto policy’s fault than Microsoft’s fault, though.
29.
IME Smoke Testing(hsivonen.fi)
7 points by hsivonen 7y ago|0 comments
30.
by hsivonen 7y ago
My main hope for flang is that it motivates LLVM to fix the Rust-relevant non-aliasing bugs. However, is it actually known that flang/f18 emits IR with the same patterns that exposed the Rust-relevant LLVM bugs?

More ›