Path: csiph.com!usenet.pasdenom.info!news.albasani.net!news2.arglkargh.de!noris.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <2151128.Fu5VX4rOnI@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Fri, 03 May 2013 17:59:30 +0200 User-Agent: KNode/4.8.5 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <2206171.g8a4ScMWm9@PointedEars.de> <1l036uh.tti447p1ww4uN%adrian@poppyrecords.invalid.invalid> <1396959.N3YltuB2Mg@PointedEars.de> <2177849.7jHvAoTLnH@PointedEars.de> <2391743.1T8NqQ3TJ8@PointedEars.de> <5795699.ZddputCnCo@PointedEars.de> <2239420.ujkpEq8jF8@PointedEars.de> <1888759.kj0EFmyP97@PointedEars.de> <6941585.Q3jqcEWICf@PointedEars.de> MIME-Version: 1.0 Lines: 55 NNTP-Posting-Date: 03 May 2013 17:59:31 CEST NNTP-Posting-Host: d58dc71b.newsspool3.arcor-online.net X-Trace: DXC=PEBanH<=_]h9kIfcjg:0fdMcF=Q^Z^V3h4Fo<]lROoRa8kFOLN\gfA]` X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:19608 Scott Sauyet wrote: > Thomas 'PointedEars' Lahn wrote: >> JSX:string/unicode.js is real: I have been working on a library that >> supports Unicode characters beyond the Basic Multilingual Plane; that is >> UTF-16 code sequences for code points beyond U+FFFF, up to U+10FFFF. >> [ ... ] >> >> The unit test of JSX:string/unicode.js can now be viewed at >> >> >> >> More features and testcases will follow. Hopefully the library will be >> useful. >> >> I am also considering to overwrite built-in methods of the String >> constructor and the String prototype object, and augment them with new >> ones […]. Overwriting and augmenting would be optional each, but done by >> default, through the new jsx.options mechanism (see object.js [2] for >> details). >> >> What do you think? [ ... ] > > While I have no current uses for this, I applaud your efforts, and > would be very happy to know that it was available if I did need it. > I've looked over your regex extension; I was impressed and wished it > had been available for some older projects I had done. This project > could clearly fill some similar gaps. > > But, as I said, I have no uses for it in any current projects. > > Good luck, Thank you very much. Now unicode.js by default (AISB, it is configurable) also replaces String.fromCharCode() to support code points beyond U+FFFF (Number arguments from 0 to 0x10FFFF), and adds String.prototype.getLength() so that "…".getLength() returns the number of Unicode characters in a string, as opposed to the built-in "…".length which yields the number of 16-bit code units. More is going to follow. Thanks to Cezary Tomczyk's test [1] it is also working in IE 10 on Windows 8 (it was a refactoring bug in object.js). However, JScript in IE/MSHTML 10 apparently lacks the ability to define getters and setters for properties of native objects as specified in ECMAScript Edition 5.x, so tests using those features will always fail. [1] -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.