Ricardo Signes wrote: > * demerphq <demerphq@gmail.com> [2009-10-28T09:51:45] >>> As for \d, though, I am horrified to think how much bad behavior could be >>> introduced if \d started to match TITLE CASE KLINGON NUMERAL CHORGH >>> >>> I think it is likely that I would not upgrade to a perl5 that introduced >>> such behavior. "Review every regex that uses \d" is not an acceptable >>> burden. >> What you just described is the present situation. And many people have >> this bug and have done exactly what you said. > > I stand both corrected and astonished. > Just for the record, Unicode has resisted so far the attempts to formalize Klingon. But, it is available in an unofficial Private Use area, partitioned and registered at http://www.evertype.com/standards/csur/ U+F8F0 KLINGON DIGIT ZERO U+F8F1 KLINGON DIGIT ONE U+F8F2 KLINGON DIGIT TWO U+F8F3 KLINGON DIGIT THREE U+F8F4 KLINGON DIGIT FOUR U+F8F5 KLINGON DIGIT FIVE U+F8F6 KLINGON DIGIT SIX U+F8F7 KLINGON DIGIT SEVEN U+F8F8 KLINGON DIGIT EIGHT U+F8F9 KLINGON DIGIT NINE Coincidentally, a linguist friend of mine told me this week that Klingon is the 2nd most widely spoken made-up language in the world, after Esperanto. So, Unicode may encode them. They already did encode GB Shaw's alphabet, a Mormon alphabet, and there are serious proposals to encode JRR Tolkien's alphabets.Thread Previous | Thread Next