> I will need to think about the best current workaround for this, but right
> now I am (and have been) swamped, sorry.
I've tried the following code and it seems to work for me. Can you
think of any reason why it might not work? As I understand from the
unicode standard [1], V is supposed to p
On Feb 2, 2012, at 7:56 AM, John Joyce wrote:
>
> On Feb 2, 2012, at 2:20 AM, Peter Edberg wrote:
>
>>
>> On Jan 31, 2012, at 2:35 PM, cocoa-dev-requ...@lists.apple.com wrote:
>>> --
>>>
>>> Message: 1
>>> Date: Tue, 31 Jan 2
rom: Heath Borders
>> To: cocoa-dev
>> Subject: Re: NSDateFormatter not working on iOS 5.
>> Message-ID:
>>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Peter,
>>
>> If I set the locale to "en_IN&quo
On Jan 31, 2012, at 2:35 PM, cocoa-dev-requ...@lists.apple.com wrote:
> --
>
> Message: 1
> Date: Tue, 31 Jan 2012 14:10:13 -0600
> From: Heath Borders
> To: cocoa-dev
> Subject: Re: NSDateFormatter
Peter,
If I set the locale to "en_IN" shouldn't that show the short time zone?
NSLocale *indianEnglishLocale = [[[NSLocale alloc]
initWithLocaleIdentifier:@"en_IN"] autorelease];
NSTimeZone *timeZone = [NSTimeZone timeZoneWithName:@"Asia/Kolkata"];
NSDateFormatter *dateFormatter = [[[NSDateFormat
On Sun, 20 Nov 2011 23:54:45 -0800, Peter Edberg said:
>
>On Nov 17, 2011, at 10:14 AM, Matt Neuburg wrote:
>
>> On Wed, 16 Nov 2011 14:43:55 -0800, Peter Edberg said:
>>> ...
>>>
>>> The issue is this: With the *short* timezone formats as specified by z
>>> (=zzz) or v (=vvv), there can be a l
On Nov 17, 2011, at 10:14 AM, Matt Neuburg wrote:
> On Wed, 16 Nov 2011 14:43:55 -0800, Peter Edberg said:
>> ...
>>
>> The issue is this: With the *short* timezone formats as specified by z
>> (=zzz) or v (=vvv), there can be a lot of ambiguity. For example, "ET" for
>> Eastern Time" could a
On Wed, 16 Nov 2011 14:43:55 -0800, Peter Edberg said:
>The change in parsing of abbreviated time zone names in iOS 5.0 is a result of
>an intentional change in the open-source ICU 4.8 library (and the open-source
>CLDR 2.0 data that it uses), a modified version of which is used to implement
>s
", "en_US", or "en_GB", then any of the following will be parsed,
because they are unambiguous:
"Pacific Daylight Time"
"Central European Summer Time"
"Central European Time"
Hope this helps.
- Peter Edberg
> Date: Wed, 16 Nov 2011 16:29:
Matt,
The result differs not only on simulator, but also on iphones running 4.3 and
5.0.
I have also found out that ONLY some of the known time zones work fine on 5.0.
e.g. PDT, PST, GMT ...etc. However, all time zones work fine on iOS 4.3.
In fact, I have already reported this as a bug to apple
By the way, I can readily confirm that the results differ on the simulator for
4.3 vs. 5.0. m.
>On Fri, 11 Nov 2011 16:13:49 +0800, Kin Mak said:
>>The following code used to work fine prior to iOS 5. The dateFromString
>>method seems to stop working on iOS 5 and always returns null. I suspect
On Fri, 11 Nov 2011 16:13:49 +0800, Kin Mak said:
>The following code used to work fine prior to iOS 5. The dateFromString method
>seems to stop working on iOS 5 and always returns null. I suspect this is a
>bug introduced in iOS 5.0. Have anyone encountered the same issue? Or do I
>miss somet
Hi Kin,
It looks like you discovered something. I've tried it on the iPhone Simulator
and it doesn't work right, like you said. However, it _does_ work on the device.
Thanks,
On 11 Νοε 2011, at 3:17 μ.μ., Kin Mak wrote:
> Hi Nick,
>
> The code works fine in iOS 4.3 or earlier, but not anymor
Hi Nick,
The code works fine in iOS 4.3 or earlier, but not anymore on iOS 5.0. I didn't
try it on Mac OSX tough
But if you try the code on different versions of iOS, the result may not be the
same.
Don Quixote,
Thanks for your tips of using assert. I am now wondering if there is anything
to d
> On 11 Νοε 2011, at 10:13 π.μ., Kin Mak wrote:
>> The following code used to work fine prior to iOS 5. The dateFromString
>> method seems to stop working on iOS 5 and always returns null.
2011/11/11 Νικόλας Τουμπέλης :
> I've tried the snippet in both Mac OS X and iOS and found that it still
>
Hi Kin,
I've tried the snippet in both Mac OS X and iOS and found that it still works.
What are you doing prior to calling dateFromString: ?
Thanks,
Nick
On 11 Νοε 2011, at 10:13 π.μ., Kin Mak wrote:
> The following code used to work fine prior to iOS 5. The dateFromString
> method seems to
The following code used to work fine prior to iOS 5. The dateFromString method
seems to stop working on iOS 5 and always returns null. I suspect this is a bug
introduced in iOS 5.0. Have anyone encountered the same issue? Or do I miss
something here?
Any tips or hints will be highly appreciate
17 matches
Mail list logo
