Closed
Bug 257511
Opened 20 years ago
Closed 20 years ago
Showing date failed with UTF-8 locales that includes non-ASCII characters in date strings
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: t.matsuu, Assigned: jshin1987)
References
()
Details
(Keywords: regression)
Attachments
(4 files)
5.40 KB,
text/plain
|
Details | |
13.68 KB,
text/html
|
Details | |
14.33 KB,
text/html
|
Details | |
5.90 KB,
patch
|
smontagu
:
review+
neil
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040831 Firefox/0.9.1+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040831 Firefox/0.9.1+
When I access any FTP sites, mozilla shows the directories and files list except
for day, month, and year.
Reproducible: Always
Steps to Reproduce:
1. access to the FTP sites (eg. ftp://ftp.mozilla.org/)
2.
3.
Actual Results:
shows the directories and files list WITHOUT day, month, and year.
Expected Results:
shows the directories and files list WITH day, month, and year.
I tested with the browsers
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040831 Firefox/0.9.1+
and
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040831
I also tested with
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3)
Gecko/20040830 Firefox/0.9.1+
and this seems to be worked fine.
Reporter | ||
Comment 1•20 years ago
|
||
I compare both Linux and MacOS X source and no difference found.
Reporter | ||
Comment 2•20 years ago
|
||
resulting source that mozilla treats.
Day, month, and year fields are empty.
Time shows 24-hour style.
Reporter | ||
Comment 3•20 years ago
|
||
Resulting source that mozilla on MacOS X treats.
Day, month, and year fields are filled with "yy.yy.dd" style.
Time shows 12-hour style with AM/PM.
Reporter | ||
Comment 4•20 years ago
|
||
(In reply to comment #3)
> Day, month, and year fields are filled with "yy.yy.dd" style.
"yy.mm.dd" style. Sorry.
Reporter | ||
Updated•20 years ago
|
Summary: day, month, and year doesn't displayed. → When visiting FTP sites, day, month, and year doesn't displayed.
Reporter | ||
Comment 5•20 years ago
|
||
firefox-1.0 works fine. But trunk
Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.8a6) Gecko/20050111
does not work properly even now.
+--mozilla1.7.5 (good)
|
| +--(20040515?)--firefox1.0 (good)
| |
trunk--+--+--20040831_trunk (no_good)
Reporter | ||
Comment 6•20 years ago
|
||
I tried more tests.
+--mozilla1.7.5 (good)
|
| +--(20040515?)--firefox1.0 (good)
| |
trunk--+--+--mozilla1.8a1 (good)--mozilla1.8a2 (no_good)
Reporter | ||
Comment 7•20 years ago
|
||
Date is not displayed with the locale ja_JP.UTF-8 and displayed with ja_JP.eucJP.
Date is also not displayed
1. "Modified" and "Expires in View -> PageInfo
2. Date header in Mozilla Mail
Was the date detection mechanism changed between mozilla-1.8a1 and mozilla-1.8a2?
Reporter | ||
Updated•20 years ago
|
Summary: When visiting FTP sites, day, month, and year doesn't displayed. → Showing date failed with UTF-8 locales that includes non-ASCII characters in date strings
Comment 8•20 years ago
|
||
In Japanese bugzilla, Some poeple says that bug 153586 may cause this.
>jshin
All CJK have same problem.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 9•20 years ago
|
||
You're right. This has regressed as a reult of the fix for bug 153586, which
also broke Date/Time in Calendar/Sunbird when run under ll_CC.UTF-8. The reason
is that in the patch '#PLATFORM' was rmoved and there's no more distinction
between 'll_CC' locale and 'll_CC.UTF-8' locale. To be fair, bug 153586 fixed
one thing, but broke another. It's my fault as well because I never manage to
point out what exactly would break with the patch although I knew it would break
something. (bug 153586 comment #67, bug 153586 comment #71). The file in
question was shuffled around (so that Lxr didn't help) and I lost track of bugs
in which '#PLATFORM' was added to work around this kind of problem.
Under 'll_CC.UTF-8' locale, |strftime| is called with the locale set to 'll_CC'
(e.g. ja_JP), but the platform character encoding is 'UTF-8' so that down the
road the result of strftime (which is in EUC-JP) is interpreted as UTF-8, which
would obviously fail.
Just adding back '#PLATFORM' may solve the original issue reported here (FTP
date/time), but doesn't quite solve JS date/time (Sunbird/Calendar cases) for
some reason. I looked at this a week ago, but didn't figure out why, then.
Assignee | ||
Comment 10•20 years ago
|
||
Rolling back all the changes in intl/locale/* in attachment 146210 [details] [diff] [review] fixes this
problem and doesn't break |Date.prototype.toLocaleString| in javascript in both
ko_KR.EUC-KR locale and ko_KR.UTF-8 locale on Linux. However, repeated 'trips'
to | nsPlatformCharset::GetDefaultCharsetForLocale| are bothering me.
BTW, I guess I have to deal with Date/time problem in sunderbird/calendar in
another bug. With the same change, I'm getting 'C' locale date/time while
without it, I get an empty string as is the case for ftp file listing.
Status: NEW → ASSIGNED
Assignee | ||
Comment 11•20 years ago
|
||
This is basiscally reverting to pre-bug 153586 as far as intl/* is concerned.
The strange thing I observed was due to that I forgot to change
intl/uconv/src/nsUNIXCharset.cpp. The reason for the roll-back is that on Unix,
we need to keep the distinction between ll_CC and ll_CC.UTF-8 locales. [1] In
the current code, we lose the distinction while going back and forth between
xpLocale designation 'll-CC' and posix locale designation.
An alternative to this is to modify the converter between Posix locale names
and xpLocale names. We may attach and detach the character encoding name
returned by nl_langinfo(CODESET) (in addition to going back and forth between
'-' and '_'). However, this is rather tricky because there's no guarantee that
the codeset name returned by nl_langinfo() is also used in the locale name. On
Linux (glibc 2.3.x), it does, but I wouldn't believe that it's always the case
on other Unix.
Btw, LocaleToUnicode in dom/src/base/nsJSEnvironment.cpp had better use
NSI_LOCALETIME##PLATFORM for XP_UNIX although it would work (as it is) in most
cases.
[1] I found that locales like hi_IN, ta_IN and hi_IN.UTF-8 and ta_IN.UTF-8 are
equivalent in glibc 2.3.x because glibc never supported hi-IN and ta-IN before
it began to support UTF-8 locales.
Attachment #171133 -
Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #171133 -
Flags: review?(smontagu)
Updated•20 years ago
|
Severity: normal → major
Assignee | ||
Comment 12•20 years ago
|
||
This is definitely a blocker for 1.8beta and TB 1.1. Date field is blank for
mail (in both mail thread panel and individual message view) when run under
UTF-8 locales where date/time have non-ASCII characters.
Flags: blocking1.8b?
Flags: blocking-aviary1.1?
Updated•20 years ago
|
Attachment #171133 -
Flags: review?(smontagu) → review+
Updated•20 years ago
|
Attachment #171133 -
Flags: superreview?(neil.parkwaycc.co.uk) → superreview+
Assignee | ||
Comment 13•20 years ago
|
||
thansk for r/sr. fix checked in
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Flags: blocking1.8b?
Flags: blocking-aviary1.1?
You need to log in
before you can comment on or make changes to this bug.
Description
•