Documentation Archive Developer
Search
Table of Contents Previous Section

Working with NSCalendarDates

 NSCalendarDate objects represent dates and times. These objects are especially suited for representing and manipulating dates according to western calendrical systems. NSCalendarDate performs date computations based on western calendrical systems, primarily the Gregorian.

The methods provided by NSCalendarDate are described in more detail in the section "Commonly Used NSCalendarDate Methods."

The Calendar Format

Each NSCalendarDate object has a calendar format associated with it. This format is a string that contains date-conversion specifiers that are very similar to those used in the standard C library function strftime(). NSCalendarDate interprets dates that are represented as strings conforming to this format. You can set the default format for an NSCalendarDate object at initialization time or using the setCalendarFormat: method. Several methods allow you to specify formats other than the one bound to the object.

The date conversion specifiers cover a range of date conventions:

Conversion Specifier Argument Type
%% a '%' character
%A, %a full and abbreviated weekday name, respectively
%B, %b full and abbreviated month name, respectively
%c date and time designation for the locale
%d day of the month as a decimal number (01-31)
%F milliseconds as a decimal number (000-999)
%H, %I hour based on a 24-hour or 12-hour clock as a decimal number, respectively. (00-23 or 01-12)
%j day of the year as a decimal number (001-366)
%M minute as a decimal number (00-59)
%m month as a decimal number (01-12)
%p AM/PM designation for the locale
%S second as a decimal number (00-59)
%w weekday as a decimal number (0-6), where Sunday is 0
%x date using date representation for the locale
%X time using time representation for the locale
%Y, %y year with century (such as 1990) and year without century (00-99), respectively
%Z, %z time zone abbreviation (such as PDT) and time zone offset in hours and minutes from GMT (HHMM), respectively

Table of Contents Next Section