diff options
Diffstat (limited to 'files/es/web/javascript/referencia/objetos_globales/date/tolocalestring/index.html')
| -rw-r--r-- | files/es/web/javascript/referencia/objetos_globales/date/tolocalestring/index.html | 163 |
1 files changed, 0 insertions, 163 deletions
diff --git a/files/es/web/javascript/referencia/objetos_globales/date/tolocalestring/index.html b/files/es/web/javascript/referencia/objetos_globales/date/tolocalestring/index.html deleted file mode 100644 index 77f48344d3..0000000000 --- a/files/es/web/javascript/referencia/objetos_globales/date/tolocalestring/index.html +++ /dev/null @@ -1,163 +0,0 @@ ---- -title: Date.prototype.toLocaleString() -slug: Web/JavaScript/Referencia/Objetos_globales/Date/toLocaleString -translation_of: Web/JavaScript/Reference/Global_Objects/Date/toLocaleString ---- -<div>{{JSRef}}</div> - -<p>El método <strong><code>toLocaleString()</code></strong> devuelve un cadena con la representación al idioma de la fecha especificada. <span class="tlid-translation translation" lang="es"><span title="">Los nuevos argumentos </span></span> <code>locales</code> <span class="tlid-translation translation" lang="es"><span title="">y </span></span> <code>options</code> <span class="tlid-translation translation" lang="es"><span title=""> permiten a las aplicaciones especificar el idioma cuyas convenciones de formato deben usarse y personalizar el comportamiento de la función</span></span>. <span class="tlid-translation translation" lang="es"><span title="">En implementaciones anteriores, ignoran los argumentos de las configuraciones </span></span><code>locales</code><span class="tlid-translation translation" lang="es"><span title=""> y </span></span><code>options</code> <span class="tlid-translation translation" lang="es"><span title=""> </span></span><span class="tlid-translation translation" lang="es"><span title="">, la configuración regional utilizada y la forma de la cadena devuelta dependen completamente de la implementación</span></span> .</p> - -<div>{{EmbedInteractiveExample("pages/js/date-tolocalestring.html")}}</div> - - - -<h2 id="Syntax">Syntax</h2> - -<pre class="syntaxbox"><var>dateObj</var>.toLocaleString([<var>locales</var>[, <var>options</var>]])</pre> - -<h3 id="Parametros">Parametros</h3> - -<p>Los argumentos <code>locales</code> y de <code>options</code> personalizan el comportamiento de la función y permiten que las aplicaciones especifiquen el lenguaje cuyas convenciones de formato deben ser utilizadas. En las implementaciones, que ignoran los argumentos, <code>locales</code> y <code>options</code>, el locale utilizado y la forma de la cadena devuelta dependen totalmente de la implementación.</p> - -<p>Vea el <a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/DateTimeFormat">constructor</a> de <a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/DateTimeFormat"><code>Intl.DateTimeFormat()</code> </a> para detalles en esos parametros y como se usan.</p> - -<p>El valor por defecto para cada componente <code>date-time</code> es {{jsxref("undefined")}}, pero si las propiedades <code>weekday</code>, <code>year</code>, <code>month</code>, <code>day</code> son todas {{jsxref("undefined")}}, entonces <code>year</code>, <code>month</code>, y <code>day</code> son asumidas como <code>"numeric"</code>.</p> - -<h3 id="Return_value">Return value</h3> - -<p>A string representing the given date according to language-specific conventions.</p> - -<h2 id="Examples">Examples</h2> - -<h3 id="Using_toLocaleString">Using <code>toLocaleString()</code></h3> - -<p>In basic use without specifying a locale, a formatted string in the default locale and with default options is returned.</p> - -<pre class="brush: js">var date = new Date(Date.UTC(2012, 11, 12, 3, 0, 0)); - -// toLocaleString() without arguments depends on the implementation, -// the default locale, and the default time zone -console.log(date.toLocaleString()); -// → "12/11/2012, 7:00:00 PM" if run in en-US locale with time zone America/Los_Angeles -</pre> - -<h3 id="Checking_for_support_for_locales_and_options_arguments">Checking for support for <code>locales</code> and <code>options</code> arguments</h3> - -<p>The <code>locales</code> and <code>options</code> 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 {{jsxref("RangeError")}} exception:</p> - -<pre class="brush: js">function toLocaleStringSupportsLocales() { - try { - new Date().toLocaleString('i'); - } catch (e) { - return e instanceof RangeError; - } - return false; -} -</pre> - -<h3 id="Using_locales">Using <code>locales</code></h3> - -<p>This example shows some of the variations in localized date and time 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 <code>locales</code> argument:</p> - -<pre class="brush: js">var date = new Date(Date.UTC(2012, 11, 20, 3, 0, 0)); - -// formats below assume the local time zone of the locale; -// America/Los_Angeles for the US - -// US English uses month-day-year order and 12-hour time with AM/PM -console.log(date.toLocaleString('en-US')); -// → "12/19/2012, 7:00:00 PM" - -// British English uses day-month-year order and 24-hour time without AM/PM -console.log(date.toLocaleString('en-GB')); -// → "20/12/2012 03:00:00" - -// Korean uses year-month-day order and 12-hour time with AM/PM -console.log(date.toLocaleString('ko-KR')); -// → "2012. 12. 20. 오후 12:00:00" - -// Arabic in most Arabic speaking countries uses real Arabic digits -console.log(date.toLocaleString('ar-EG')); -// → "<span dir="rtl">٢٠/١٢/٢٠١٢ ٥:٠٠:٠٠ ص</span>" - -// for Japanese, applications may want to use the Japanese calendar, -// where 2012 was the year 24 of the Heisei era -console.log(date.toLocaleString('ja-JP-u-ca-japanese')); -// → "24/12/20 12:00:00" - -// when requesting a language that may not be supported, such as -// Balinese, include a fallback language, in this case Indonesian -console.log(date.toLocaleString(['ban', 'id'])); -// → "20/12/2012 11.00.00" -</pre> - -<h3 id="Using_options">Using <code>options</code></h3> - -<p>The results provided by <code>toLocaleString()</code> can be customized using the <code>options</code> argument:</p> - -<pre class="brush: js">var date = new Date(Date.UTC(2012, 11, 20, 3, 0, 0)); - -// request a weekday along with a long date -var options = { weekday: 'long', year: 'numeric', month: 'long', day: 'numeric' }; -console.log(date.toLocaleString('de-DE', options)); -// → "Donnerstag, 20. Dezember 2012" - -// an application may want to use UTC and make that visible -options.timeZone = 'UTC'; -options.timeZoneName = 'short'; -console.log(date.toLocaleString('en-US', options)); -// → "Thursday, December 20, 2012, GMT" - -// sometimes even the US needs 24-hour time -console.log(date.toLocaleString('en-US', { hour12: false })); -// → "12/19/2012, 19:00:00" -</pre> - -<h3 id="Avoid_comparing_formatted_date_values_to_static_values">Avoid comparing formatted date values to static values</h3> - -<p>Most of the time, the formatting returned by <code>toLocaleString()</code> is consistent. However, this might change in the future and isn't guaranteed for all languages — output variations are by design and allowed by the specification. Most notably, the IE and Edge browsers insert bidirectional control characters around dates, so the output text will flow properly when concatenated with other text.</p> - -<p>For this reason you cannot expect to be able to compare the results of <code>toLocaleString()</code> to a static value:</p> - -<pre class="brush: js; example-bad">"1/1/2019, 01:00:00" === new Date("2019-01-01T01:00:00Z").toLocaleString("en-US"); -// true in Firefox and others -// false in IE and Edge</pre> - -<div class="blockIndicator note"> -<p><strong>Note</strong>: See also this <a href="https://stackoverflow.com/questions/25574963/ies-tolocalestring-has-strange-characters-in-results">StackOverflow thread</a> for more details and examples.</p> -</div> - -<h2 id="Performance">Performance</h2> - -<p>When formatting large numbers of dates, it is better to create an {{jsxref("Global_Objects/DateTimeFormat", "Intl.DateTimeFormat")}} object and use the function provided by its {{jsxref("DateTimeFormat.prototype.format", "format")}} property.</p> - -<h2 id="Specifications">Specifications</h2> - -<table class="standard-table"> - <tbody> - <tr> - <th scope="col">Specification</th> - </tr> - <tr> - <td>{{SpecName('ESDraft', '#sec-date.prototype.tolocalestring', 'Date.prototype.toLocaleString')}}</td> - </tr> - <tr> - <td>{{SpecName('ES Int Draft', '#sup-date.prototype.tolocalestring', 'Date.prototype.toLocaleString')}}</td> - </tr> - </tbody> -</table> - -<h2 id="Browser_compatibility">Browser compatibility</h2> - -<p class="hidden">The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> and send us a pull request.</p> - -<p>{{Compat("javascript.builtins.Date.toLocaleString")}}</p> - -<h2 id="See_also">See also</h2> - -<ul> - <li>{{jsxref("Global_Objects/DateTimeFormat", "Intl.DateTimeFormat")}}</li> - <li>{{jsxref("Date.prototype.toLocaleDateString()")}}</li> - <li>{{jsxref("Date.prototype.toLocaleTimeString()")}}</li> - <li>{{jsxref("Date.prototype.toString()")}}</li> -</ul> |