|
From: | Gregory Casamento |
Subject: | Re: Issue with NSDateFormatter on Windows with ICU... |
Date: | Tue, 27 Nov 2012 16:43:35 -0500 |
No, this is correct. ICU requires Unicode for time zones.
The thing is that ICU does not recognize the Windows timezone names, they must be in the Olson format.
A work around might be to set that to null for now and see if that works.
On Nov 27, 2012 12:25 PM, "Richard Frith-Macdonald" <address@hidden> wrote:
On 27 Nov 2012, at 18:18, Gregory Casamento wrote:
>
> Here is what is being sent....
>
> (gdb) p *(NSDateFormatterInternal *)_internal
> $3 = {{isa = 0x6702f740}, _behavior = 0, _locale = 0x41f9a28,
> _tz = 0x278ce08, _timeStyle = 0, _dateStyle = 0, _formatter = 0x0}
> (gdb) p NSToUDateFormatStyle(0)
> $4 = -1
> (gdb) po ((NSDateFormatterInternal *)_internal)->_locale
> en_US
> (gdb) p tzID
> $6 = (
> UChar *) 0x4202b80 "E\000a\000s\000t\000e\000r\000n\000 \000S\000t\000a\000n
> \000d\000a\000r"
The thing that strikes me instantly is that we are looking at unicode (16bit characters).
Could it be that the ICU library routine is expecting ascii or utf-8, but because windows uses 16bit characters natively it's getting confused?
If so, that would be easy to fix.
[Prev in Thread] | Current Thread | [Next in Thread] |