doc: update what’s off without Intl

[srl295]

Following may not behave as desired without Intl support:

• String.normalize (noop) : "normalize" method works weird #779 string.normalize() doesn't seem to work #1712
• String.localeCompare (uses string1 < string2) - see localeCompare regression node-v0.x-archive#25762
• Date.toLocale
• Date.toLocaleDateString
• Date.toLocaleTimeString
• Number.toLocaleString

cc: #238

[silverwind]

Some of these are prototype-only. Here's what I found though checking repl autocomplete:

String.toLocaleString
String.prototype.normalize
String.prototype.localeCompare
String.prototype.toLocaleString
String.prototype.toLocaleLowerCase
String.prototype.toLocaleUpperCase

Date.toLocaleString
Date.prototype.toLocaleString
Date.prototype.toLocaleDateString
Date.prototype.toLocaleTimeString

Number.toLocaleString
Number.prototype.toLocaleString

[srl295]

@silverwind thanks! I missed the casing ones - very important. Also need to check if regex changed..

[silverwind]

Also let's not forget about the Intl object itself. I'm wondering where to put these docs actually. Maybe we need a dedicated section for differences between browser and node APIs (atob() and btoa() come to mind).

[srl295]

@nodejs/documentation any thoughts?

[srl295]

• TODO: put in wiki/Intl for now.

[jasnell]

@srl295 ... any reason to keep this open?

[jasnell]

Closing this for now, does not appear to be anything actionable just yet.

[TimothyGu]

This got fixed by #13916, specifically the table in https://nodejs.org/api/intl.html#intl_options_for_building_node_js.