Você está na página 1de 6

Date.prototype.

toLocaleDateString() - JavaScript | MDN

1 de 6

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Glo...

see all contributors

The toLocaleDateString() method returns a string with a language sensitive representation of the date
portion of this date. The new locales and options arguments let applications specify the language whose
formatting conventions should be used and allow to customize the behavior of the function. In older
implementations, which ignore the locales and options arguments, the locale used and the form of the string
returned are entirely implementation dependent.

Syntax
dateObj.toLocaleDateString([locales [, options]])

Parameters
Check the Browser compatibility section to see which browsers support the locales and options arguments,
and the Example: Checking for support for locales and options arguments for feature detection.
locales
Optional. A string with a BCP 47 language tag, or an array of such strings. For the general form and
interpretation of the locales argument, see the Intl page. The following Unicode extension keys are allowed:
nu
Numbering system. Possible values include: "arab", "arabext", "bali", "beng", "deva", "fullwide",
"gujr", "guru", "hanidec", "khmr", "knda", "laoo", "latn", "limb", "mlym", "mong", "mymr",
"orya", "tamldec", "telu", "thai", "tibt".
ca
Calendar. Possible values include: "buddhist", "chinese", "coptic", "ethioaa", "ethiopic",
"gregory", "hebrew", "indian", "islamic", "islamicc", "iso8601", "japanese", "persian", "roc".
options
Optional. An object with some or all of the following properties:
localeMatcher

5/14/2016 4:27 PM

Date.prototype.toLocaleDateString() - JavaScript | MDN

2 de 6

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Glo...

The locale matching algorithm to use. Possible values are "lookup" and "best fit"; the default is
"best fit". For information about this option, see the Intl page.
timeZone
The time zone to use. The only value implementations must recognize is "UTC"; the default is the
runtime's default time zone. Implementations may also recognize the time zone names of the

IANA time

zone database, such as "Asia/Shanghai", "Asia/Kolkata", "America/New_York".


hour12
Whether to use 12-hour time (as opposed to 24-hour time). Possible values are true and false; the
default is locale dependent.
formatMatcher
The format matching algorithm to use. Possible values are "basic" and "best fit"; the default is "best
fit". See the following paragraphs for information about the use of this property.
The following properties describe the date-time components to use in formatted output, and their desired
representations. Implementations are required to support at least the following subsets:
weekday, year, month, day, hour, minute, second
weekday, year, month, day
year, month, day
year, month
month, day
hour, minute, second
hour, minute
Implementations may support other subsets, and requests will be negotiated against all available subsetrepresentation combinations to find the best match. Two algorithms are available for this negotiation and
selected by the formatMatcher property: A

fully specified "basic" algorithm and an implementation

dependent "best fit" algorithm.


weekday
The representation of the weekday. Possible values are "narrow", "short", "long".
era
The representation of the era. Possible values are "narrow", "short", "long".
year
The representation of the year. Possible values are "numeric", "2-digit".
month

5/14/2016 4:27 PM

Date.prototype.toLocaleDateString() - JavaScript | MDN

3 de 6

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Glo...

The representation of the month. Possible values are "numeric", "2-digit", "narrow", "short",
"long".
day
The representation of the day. Possible values are "numeric", "2-digit".
hour
The representation of the hour. Possible values are "numeric", "2-digit".
minute
The representation of the minute. Possible values are "numeric", "2-digit".
second
The representation of the second. Possible values are "numeric", "2-digit".
timeZoneName
The representation of the time zone name. Possible values are "short", "long".
The default value for each date-time component property is undefined, but if the weekday, year, month, day
properties are all undefined, then year, month, and day are assumed to be "numeric".

Examples
Using toLocaleDateString()
In basic use without specifying a locale, a formatted string in the default locale and with default options is
returned.

var date = new Date(Date.UTC(2012, 11, 12, 3, 0, 0));

2
3

// toLocaleDateString() without arguments depends on the implementation,

// the default locale, and the default time zone

console.log(date.toLocaleDateString());

// "12/11/2012" if run in en-US locale with time zone America/Los_Angeles

Checking for support for locales and options arguments


The locales and options arguments are not supported in all browsers yet. To check whether an
implementation supports them already, you can use the requirement that illegal language tags are rejected with a
RangeError exception:

function toLocaleDateStringSupportsLocales() {

2
5/14/2016 4:27 PM

Date.prototype.toLocaleDateString() - JavaScript | MDN

4 de 6

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Glo...

try {
new Date().toLocaleDateString('i');
} catch (e) {
return e.name === 'RangeError';
}
return false;
}

Using locales
This example shows some of the variations in localized date formats. In order to get the format of the language
used in the user interface of your application, make sure to specify that language (and possibly some fallback
languages) using the locales argument:

var date = new Date(Date.UTC(2012, 11, 20, 3, 0, 0));

2
3

// formats below assume the local time zone of the locale;

// America/Los_Angeles for the US

5
6

// US English uses month-day-year order

console.log(date.toLocaleDateString('en-US'));

// "12/19/2012"

9
10

// British English uses day-month-year order

11

console.log(date.toLocaleDateString('en-GB'));

12

// "20/12/2012"

13
14

// Korean uses year-month-day order

15

console.log(date.toLocaleDateString('ko-KR'));

16

// "2012. 12. 20."

17
18

// Arabic in most Arabic speaking countries uses real Arabic digits

19

console.log(date.toLocaleDateString('ar-EG'));

20

// " //"

21
22

// for Japanese, applications may want to use the Japanese calendar,

23

// where 2012 was the year 24 of the Heisei era

24

console.log(date.toLocaleDateString('ja-JP-u-ca-japanese'));

25

// "24/12/20"

26
27

// when requesting a language that may not be supported, such as

28

// Balinese, include a fallback language, in this case Indonesian

29

console.log(date.toLocaleDateString(['ban', 'id']));

30

5/14/2016 4:27 PM

Date.prototype.toLocaleDateString() - JavaScript | MDN

5 de 6

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Glo...

// "20/12/2012"

Using options
The results provided by toLocaleDateString() can be customized using the options argument:

var date = new Date(Date.UTC(2012, 11, 20, 3, 0, 0));

2
3

// request a weekday along with a long date

var options = { weekday: 'long', year: 'numeric', month: 'long', day: 'numeric' };

console.log(date.toLocaleDateString('de-DE', options));

// "Donnerstag, 20. Dezember 2012"

7
8

// an application may want to use UTC and make that visible

options.timeZone = 'UTC';

10

options.timeZoneName = 'short';

11

console.log(date.toLocaleDateString('en-US', options));

12

// "Thursday, December 20, 2012, GMT"

Performance
When formatting large numbers of dates, it is better to create an Intl.DateTimeFormat object and use the
function provided by its format property.

Specifications
Specification

Status

Comment

5/14/2016 4:27 PM

Date.prototype.toLocaleDateString() - JavaScript | MDN

6 de 6

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Glo...

Browser compatibility
Desktop

Feature

Chrome Firefox (Gecko) Internet Explorer Opera Safari

Basic support

(Yes)

locales and options arguments 24 [1]

(Yes)

(Yes)

(Yes)

29 (29)

11

15

(Yes)
Nightly build[2]

[1] Chrome 24 also added support for passing timeZones other than UTC.
[2] See this WebKit bug.

See also
Intl.DateTimeFormat
Date.prototype.toLocaleString()
Date.prototype.toLocaleTimeString()
Date.prototype.toString()

5/14/2016 4:27 PM

Você também pode gostar