ES5 approved
in [JavaScript]
|
From: Garrett Smith on 21 Dec 2009 11:52 Dr J R Stockton wrote: > In comp.lang.javascript message <hghnva$m6m$2(a)news.eternal- > september.org>, Fri, 18 Dec 2009 21:22:47, Garrett Smith > <dhtmlkitchen(a)gmail.com> posted: >> Thomas 'PointedEars' Lahn wrote: >>> Garrett Smith wrote: [snip] >>> And can we drop the bogus "multinationalisation" definition, please? >> It doesn't seem to be an FAQ, It does notseem to be a common term. >> >> Proposal to remove the "multinationalisation" paragraph and replace the >> FAQ title with "Localization". >> >> Any objection to that? > > > Yes. > > Localisation should be discouraged, even more than multinationalisation. > Multinationalization is a business term. AIUI, it means a business has gone to multiple nations. > Whenever practicable, an internationally-standard form should be used on > the World-Wide Web. And that is the international meaning of > "internationally", not the American one, which usually means "not us" > (where "us" possibly includes Canada) and sometimes means "us & Canada". > > By habitually doing things its own foolish way, the USA makes things > unnecessarily difficult for itself, and inconveniences other peoples. > Does this have something to do with multinationalization? > Using local forms, except where they are the JavaScript default, leads > to bloat and error, both in coding and in reading. Ah true. That is why *internationalization* is an ideal choice, right? That entry uses the term "internationalization". Internationalization is preferable because it does not require translators. Someone searching for localization might see the entry, then learn that ecmascript deosn't really have l10n features, but that ISO-8601 is a nice alternative to their own preconceive solution. Should we replace the term "multinationalization" with "localization", or should we keep "multinationalization" and not use "localization"? > Then, what local form *should* be used? There are so many immigrants > nowadays, so the form which the user prefers cannot be determined by the > locality. E.G.: AIUI, installation of one browser (of US origin) is, at > least by default, localised to location - which rather annoys monoglot > Americans, and others, resident in various other countries. > Language prerference comes from the OS, but also from the browser preference. In Firefox 3.5, setting about:config > intl.accept.languages to "ja, en-US, en" changes the Accept-Language http header in requests, but does not change the value in navigator.language. See also: https://bugzilla.mozilla.org/show_bug.cgi?id=285267 > The last paragraph of FAQ 2.5 should be reconsidered. Has ECMA 5 > fulfilled that hope? Support for what - Internationalisation, > Multinationalisation, or both? it is not clear. > | Much more support is expected in future versions of ECMAScript. That should probably be removed. Is anyone anticipating "much more"? or even "a little more" or even "a tiny bit more", or is this just wishful thinking? > In the fourth paragraph, where does one see a UK setting which is not a > US setting AND no other local setting? If there is no such case, the > "UK" is superfluous. > I don't knnow. new Date().toString() "Mon Dec 21 2009 08:40:18 GMT-0800 (Pacific Standard Time (Mexico))" "Mon Dec 21 2009 08:42:01 GMT-0800" "Mon Dec 21 08:44:05 PST 2009" Where do those format come from? UK, US, or sort of an odd mishmash? -- Garrett comp.lang.javascript FAQ: http://jibbering.com/faq/
From: Dr J R Stockton on 22 Dec 2009 13:09
In comp.lang.javascript message <hgo93p$ga4$1(a)news.eternal- september.org>, Mon, 21 Dec 2009 08:52:05, Garrett Smith <dhtmlkitchen(a)gmail.com> posted: >Dr J R Stockton wrote: >> In comp.lang.javascript message <hghnva$m6m$2(a)news.eternal- >> september.org>, Fri, 18 Dec 2009 21:22:47, Garrett Smith >> <dhtmlkitchen(a)gmail.com> posted: >>> Thomas 'PointedEars' Lahn wrote: >>>> Garrett Smith wrote: >Language prerference comes from the OS, but also from the browser >preference. The user's language preference comes from the circumstances of his birth, upbringing, education, etc., and from the circumstances in which the pages were written and read. The user does not necessarily have permission to alter browser settings, and may not know how to do so. If Pres. Obama is reading American pages, he will no doubt prefer English (unless he needs to check a version provided in a different language ; but if he is reading material of Indonesian origin, he might prefer to read it in the original rather than to read what the author optimistically thinks might be English. A page author should allow for the possibility that the machine's set preferences correspond to the reader's preferences; but he should not assume that it is actually so. The only way of finding out what language the user wants is to ask him. As an illustration of why : at an international conference with simultaneous translation, it is often better to listen to the French (or other) channel, rather than to listen to what the speaker fondly considers to be, in syntax and accent, reasonably near English. The translators have the advantage of having, and having studied, a written version of the text. >"Mon Dec 21 2009 08:40:18 GMT-0800 (Pacific Standard Time (Mexico))" >"Mon Dec 21 2009 08:42:01 GMT-0800" >"Mon Dec 21 08:44:05 PST 2009" > >Where do those format come from? UK, US, or sort of an odd mishmash? Generally acceptable, but US origin. UK would more often use 21 Dec or 21st Dec. And it would not use PST, only GMT or BST. The parenthetic part, as supplied by Windows, does not reliably represent (though it may do so in the USA) anything the locals would write. It comes from a database seemingly written by nerds in California. Now allowing for non-IE browsers, I generally use D.toSt rather than D.toString, after Date.prototype.toSt = new Function( " /* Date.toSt : omit parenthetical part */\n" + " return this.toString().replace(/( \\(.+\\))$/, '')") -- (c) John Stockton, Surrey, UK. ?@merlyn.demon.co.uk Turnpike v6.05 MIME. Web <URL:http://www.merlyn.demon.co.uk/> - FAQish topics, acronyms, & links. Proper <= 4-line sig. separator as above, a line exactly "-- " (RFCs 5536/7) Do not Mail News to me. Before a reply, quote with ">" or "> " (RFCs 5536/7) |