update date/time formatter on Mac OS X (CFDateFormatter)

RESOLVED FIXED in Future

Status

()

Core
Internationalization
--
enhancement
RESOLVED FIXED
16 years ago
8 years ago

People

(Reporter: Frank Tang, Unassigned)

Tracking

({intl})

Trunk
Future
PowerPC
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
Mac OS X have some new Unicode baes API.
Our current date time formatter in intl/locale are based the script system one from 
system 7. It did a lot of change of data since we need to convert from / to
unicode. It will be nice to develop a new implementaion of nsIDateTimeFormatter
if Mac OS X have a new library to handle it. 
So far I have not find any documentation mention such library exist. We should
talk to Apple's Technology Manager to get more info.

Please add info to this bug if you find out anything related to date and time
display on Mac (new apis)
(Reporter)

Comment 1

16 years ago
I look at CFDateRef in Core Foundation : Utility Services. I cannot find any API
format a CFDateRef to a localized string.
(Reporter)

Comment 2

16 years ago
mark it as m1.0 for now till more information collected. 
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
(Reporter)

Updated

16 years ago
Blocks: 103669

Updated

16 years ago
Keywords: intl
QA Contact: teruko → ylong

Updated

16 years ago
Keywords: mozilla1.0
(Reporter)

Comment 3

16 years ago
this thing does not exist. push off to future. 
Target Milestone: mozilla1.0 → Future

Updated

14 years ago
Blocks: 231757
Assignee: ftang → nobody
Status: ASSIGNED → NEW
Keywords: mozilla1.0
The APIs that replace the current script system are CFDateFormatter and
CFNumberFormatter.  These are both only available starting in 10.3, so we'll
have to create a fix like that from bug 252475, where we dynamically load the
function pointers and if they exist (i.e. we are on 10.3 or later), then we use
these new APIs.  We'll need to keep the old code around for older systems.
(In reply to comment #4)
> The APIs that replace the current script system are CFDateFormatter and
> CFNumberFormatter.  These are both only available starting in 10.3

When are we dropping support for 10.2 and older? 

Mozilla documentation on OS X support is not very clear on this ATM, for example, dmo says, «Mozilla will run on Mac OS X 10.2 (“Jaguar”), but the build requires a minimum of 10.3 (“Panther”).», whilst wmo says that 10.2 is supported for neither runtime nor building of Gecko 1.8 and 1.9 (trunk). Moreover, caminobrowser.org claims that Camino 1.0 supports 10.2, whilst wmo says that even Camino 0.8 doesn't support 10.2. IMHO, the Compatibility Matrix needs a really major update.

http://developer.mozilla.org/en/docs/Mac_OS_X_Build_Prerequisites
http://wiki.mozilla.org/Mac:Build_Requirements#Compatibility_Matrix
http://www.caminobrowser.org/
Severity: normal → enhancement
(In reply to comment #5)
> (In reply to comment #4)
> > The APIs that replace the current script system are CFDateFormatter and
> > CFNumberFormatter.  These are both only available starting in 10.3
> 
> When are we dropping support for 10.2 and older? 
> http://wiki.mozilla.org/Mac:Build_Requirements#Compatibility_Matrix

H'm.. I guess, I misread the matrix this morning before tea :) — it looks like in trunk (Gecko 1.9) we already no longer support 10.2 and older, so we can already use CFDateFormatter without any fallbacks to older APIs.
OS: Mac OS X 10.2 → Mac OS X 10.4
Summary: update to new unicode base date/time formatter on Mac OS X if the have a new one → update date/time formatter on Mac OS X (CFDateFormatter)
QA Contact: amyy → i18n
Fixed by bug 360018
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Depends on: 360018
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.