Open
Bug 507139
Opened 15 years ago
Updated 2 years ago
MetaData Properties window doesn't respect locale for file size and image dimensions
Categories
(Firefox :: Page Info Window, defect)
Firefox
Page Info Window
Tracking
()
NEW
People
(Reporter: philip.chee, Unassigned)
References
()
Details
(Keywords: intl, l12y)
Spinning off the Firefox part into a separate bug.
=============================================================
+++ This bug was initially created as a clone of Bug #252043 +++
Page Info shows incorrect size, not honouring locale settings.
I want to notice that many European countries use commas (not periods) as a decimal separator.
This must be fixed in Mozilla App Suite and Mozilla Firefox.
=============================================================
In Bug 252043, I updated the Suite part of the existing patch and the bug is now fixed in SeaMonkey. But the patch was against CVS and also contains the Firefox part. See attachment 388925 [details] [diff] [review]. Somebody needs to do the same for Firefox.
Comment 1•15 years ago
|
||
Philip: Are you planning on doing this? (I am happy to port the patch and work with things--this will be a lot easier since metaData.js was removed, but I am not entirely sure how to test it.)
Reporter | ||
Comment 2•15 years ago
|
||
> Philip: Are you planning on doing this? (I am happy to port the patch and work
Sorry, no. I'm just triaging and fixing SeaMonkey Page Info bugs.
> with things--this will be a lot easier since metaData.js was removed, but I am
> not entirely sure how to test it.)
Switch to a locale/langpack (e.g. de) where the comma is used as the decimal point and a space or period is used as the thousands separator.
Comment 3•15 years ago
|
||
Assigning to me. I have already made the changes from the patch, and now I just need to test them.
Assignee: nobody → mozilla.bugs
Status: NEW → ASSIGNED
Comment 4•15 years ago
|
||
I'm not convinced the SeaMonkey patch is right, asked KaiRo over there.
To copy the comment, toLocaleString() uses the OS locale, not the gecko locale, and thus there might be a mismatch. It depends much on context which one is considered more right if the two don't match.
In this particular case, I'm somewhat leaning towards gecko locale, but I'll wait on comments on bug 252043.
Comment 5•15 years ago
|
||
Since we want gecko-locale based number formatting (which I am totally in favor of), I will wait on Bug 542502 before I move on this.
Depends on: 542502
Comment 6•15 years ago
|
||
I will not have time to do this in the foreseeable future, regardless of what happens on Bug 542502, so I will unassign myself from this bug, in case someone else can work on it before I would be able to.
Assignee: mozilla.bugs → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•