Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <6941585.Q3jqcEWICf@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Tue, 30 Apr 2013 23:03:50 +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+&. <98cc9763-7f32-4ca7-9d52-f698c222f246@n2g2000yqg.googlegroups.com> <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> MIME-Version: 1.0 Lines: 118 NNTP-Posting-Date: 30 Apr 2013 23:03:53 CEST NNTP-Posting-Host: afb73097.newsspool1.arcor-online.net X-Trace: DXC=P`Tj]=`o_kH78PK[oJ2ng@ic==]BZ:afN4Fo<]lROoRAnkgeX?EC@@@0E8X5N4L0EBDZm8W4\YJNLb@mF9jNikdE7a5\<`>]gfN[SGgQKCJ5eJ X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:19545 Thomas 'PointedEars' Lahn wrote: > Christoph Becker wrote: >> Thomas 'PointedEars' Lahn wrote: >>> Christoph Becker wrote: >>>> Anyway, I appreciate your working on a workaround; may come in handy. >>>> :) >>> >>> At the latest after first contact ;-) >>> >>> You will find it in >>> > >>> when it is ready for testing. >> >> My feedreader will keep an eye on it. ;) > > Thank you. > > Due to recent events I would also like to announce that in the version of > unicode.js that follows this one there is going to be support for the > Vulcan Unicode characters (both TGV and MGV) and the Sloof-lirpa script in > which these languages are written. Stay tuned. Now that April Fools' Day is long over, I would like to clarify so as not to be misunderstood. 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. A future unicode.js that would support the aforementioned Vulcan script (writing) is _not_ going to happen (although I might write another script [programming] that supports the Vulcan languages later – if Google can do Klingon [1], I can do Vulcan ;-)). Those were the clues (ROT-13 encoded for those who either like puzzles or are not interested in the details of the joke): - Gurer ner ab Ihypna Havpbqr punenpgref. (Gurer ner abg rira Xyvatba rgp. Havpbqr punenpgref, nygubhtu gurer ner sbagf gung znc pbqr cbvagf gb gubfr punenpgref. V pna cebivqr HEVf gb gubfr jub ner vagrerfgrq.) - Gurer vf ab “Fybbs-yvecn” fpevcg; “Fybbs-yvecn”, jura ernq onpxjneqf, vf “ncevy-sbbyF”. [V qvq abg rkcrpg, ubjrire, “fybbs” gb or n erny Ratyvfu jbeq. Nyfb, frireny bgure crbcyr hfrq “fybbs yvecn” va gurve Ncevy Sbbyf' wbxr; cnegvphyneyl pheerag VFF Pbzznaqre Puevf Unqsvryq (PFN-NFP): Ol pbvapvqrapr, /yvecn/ vf gur anzr bs n gjb-oynqrq Ihypna jrncba gung jnf hfrq va unaq-gb-unaq pbzong orsber gur Njnxravat, naq vf fgvyy hfrq va gur evghny bs /xbba-hg-xny-vs-srr/ – zneevntr-be- punyyratr[-gb-gur-qrngu).] - Gur Ihypna ynathntrf ner jevggra jvgu n (abg shyyl xabja) fpevcg jurer tylcuf fgnaq sbe flyynoyrf vafgrnq bs fvatyr punenpgref (zhpu yvxr Nfvna ynathntrf). Genafxevcgvbaf hfr gur Yngva nycunorg. Frr nyfb Gur Ihypna Ynathntr Vafgvghqr (Erpynzngvba Cebwrpg): 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 (I already had several of them, some superfluous as it turned out, but I removed them after extensive refactoring of jsx.string.unicode.WideString broke them). 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? Would you find, say /* returns 1 */ "𝄞".getLength() in addition to /* returns 1 */ jsx.string.unicode.WideString("𝄞").getLength() and as opposed to /* yields 2 */ "𝄞".length useful? And would you find notations like /* returns a WideString instance containing "𝄞" */ jsx.string.unicode.WideString("\\u{1D11E}") and /* returns a RegExp that matches "𝄞" */ jsx.regexp.RegExp("\\u{1D11E}") useful until ECMAScript Edition 6 (”Harmony”) was formally published and interoperably implemented? (See also [3].) _________ [1] [2] [3] -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.