{"id":47872,"date":"2020-02-03T03:01:13","date_gmt":"2020-02-02T17:01:13","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=47872"},"modified":"2020-02-03T09:49:06","modified_gmt":"2020-02-02T23:49:06","slug":"javascript-internationalization-resolved-options-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/javascript-internationalization-resolved-options-tutorial\/","title":{"rendered":"Javascript Internationalization Resolved Options Tutorial"},"content":{"rendered":"
\"Javascript<\/a>

Javascript Internationalization Resolved Options Tutorial<\/p><\/div>\n

The recent Collation Javascript Internationalization Tutorial<\/a> thread of blog postings regarding Javascript (client) Internationalization ideas, via the Intl<\/a> object was missing an “overture”, if you will. It’s (to do with) the resolvedOptions<\/a> methods, the use of which can assist the programmer establish good default ideas about a user regarding tailoring Internationalization settings for them.<\/p>\n

Three peer status web applications can benefit from this “foresight” tool applied to each of their first row (and Javascript helper function for Intl.DateTimeFormat web application) …<\/p>\n


\nfunction yehbut(defzero) {
\n var outdef=defzero;
\n var ropt = Intl.DateTimeFormat().resolvedOptions();
\n if (('' + ropt.locale).replace('undefined','') != '') { divlangi=('' + ropt.locale); }
\n outdef = ' var options = {year: \"' + ('' + ropt.year).replace('undefined','2-digit') + '\", month: \"' + ('' + ropt.month).replace('undefined','2-digit') + '\", day: \"' + ('' + ropt.day).replace('undefined','2-digit') + '\", hour: \"' + ('' + ropt.hour).replace('undefined','2-digit') + '\", minute: \"' + ('' + ropt.minute).replace('undefined','2-digit') + '\", timeZoneName: \"' + ('' + ropt.timeZoneName).replace('undefined','short') + '\", timeZone: \"' + ('' + ropt.timeZone).replace('undefined','UTC') + '\"}; ' + String.fromCharCode(32);
\n outdef += ' var localdatetime = new Intl.DateTimeFormat(\"' + ('' + ropt.locale).replace('undefined','en-US') + '\",options).format; ' + String.fromCharCode(32);
\n outdef += ' if (1 == 11) { alert(localdatetime(timedatenow)); } ' + String.fromCharCode(32);
\n

\n return outdef;
\n}
\n<\/code><\/p>\n

… content sets (having never saved to localStorage (as forced below)) …<\/p>\n

    \n
  1. DateTime changed<\/a> via intl_use.html<\/a>‘s web application<\/a> …
    \n\n<\/li>\n
  2. Currency and Number changed<\/a> via intl_currency.html<\/a>‘s web application<\/a> … and thanks to ISO 4217 Currency Codes<\/a> for help here …
    \n\n<\/li>\n
  3. the changed<\/a> intl_collator.html<\/a>‘s Internationalization Collator web application<\/a> …
    \n\n<\/li>\n<\/ol>\n

    And we can supervise the supervisor here, pre-empting a local clock setting (within the changed<\/a> colour_wheel.html<\/a> web application<\/a>) for you as applicable below …<\/p>\n