On Tue, Dec 05, 2017 at 05:16:52PM +0200, Henri Sivonen wrote: > On Tue, Dec 5, 2017 at 4:37 PM, ISHIKAWA,chiaki <ishik...@yk.rim.or.jp> wrote: > > There are other non-ASCII character issues such as > > https://bugzilla.mozilla.org/show_bug.cgi?id=1258613 > > Very weird bug! (Summary for others: decomposed voiced sound mark is > rendered on the wrong base character.) > > > But the bug I mention occurs because some characters are encoded DIFFERENTLY > > under iOS and the rest of the world when UTF-8 is used. > > HFS+ decomposed Unicode leakage to other systems causes pain, but the > topic of this thread isn't affected by Unicode normalization. > > > By mentioning the bug, I just wanted to point out that there *ARE* obnoxious > > bugs regarding non-ASCII character handling in mozilla software. > > But majority of the Japanese users probably failed to file the non-ASCII > > character bugs, and just think, "oh, another instance of Japanese characters > > not passed correctly between mozilla applications and the external programs, > > etc." > > Possibly, but unfiled bugs don't get fixed and, as seen with non-ASCII > path handling with non-UTF-8 Linux locales, even filed bugs don't get > fixed. As the experiments documented in my previous email to this > thread indicate, non-UTF-8 paths already cause such breakage that at > this point it no longer makes sense to even pretend to support them.
Wouldn't it make sense, then, to actively fail to even start Firefox in such cases, instead of pretending it kind of works at all, if we can't even save history or bookmarks properly? Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
