On 2017/12/05 22:24, Henri Sivonen wrote:
On Mon, Dec 4, 2017 at 2:04 PM, Masatoshi Kimura <vyv03...@nifty.ne.jp> wrote:
* If by any chance a profile path contains non-ASCII characters on
non-UTF-8 UNIX systems, Firefox 57.0.1 must have broken the profile just
like 57.0 broke it on Windows. But we didn't hear any such complaints.
Are you referring to
https://hg.mozilla.org/mozilla-central/rev/345fe119b8cf using
GetPath() on all platforms and not just Windows?
Experimenting in an Ubuntu VM, Firefox 57.0.1 indeed fails to save
prefs and history (but saves the HTTP disk cache and various other
things) if the profile path has an illegal byte in it. Additionally,
on Debian-based systems generally, adduser only allows usernames (and,
thereby in the common case where the home directory matches the user
name, home directories) that conform to the POSIX portable username
rules (subset of ASCII). useradd appears to have no such safeguards.
There are other non-ASCII character issues such as
https://bugzilla.mozilla.org/show_bug.cgi?id=1258613
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.
So I think the bug will be there no matter whether this non-UTF-8 path
is removed or not.
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.": this type of Japanese character mungling has
been so common before, so it is simply ignored as one of those bugs, OR
when the problem happens it is so difficult to figure out WHERE the buck
stops (i.e., on what program either outputs incorrect character strings
or what program parses input incorrectly, OR BOTH.) And if the producer
and consumer seem to disagree on what type of encoding is used, it is
usually not quite clear even to ordinary programming type people WHAT is
the correct way on a given platform, and who is to blame, and thus many
simply failed to analyze the issue thoroughly and give up half way.
Oh well.
I have noted that, in the last three months or so, some Japanese strings
copied from Mozilla TB or mozilla FF are not parsed correctly when
they are inserted into other programs.
This did not happen before.
But due to exactly the same reason I noted above, I am not sure which
program is to blame, and have not bothered to
pester mozilla bugzilla with possibly false-positive bug reports.
If the problem persists in the next few months, I may file a bug.
TIA for people's attention.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
