twitter-cldr-rb

I meant to include ICU in what I was saying works well when I said "unicode gives us a standard collation algorithm including localizations". ICU stands for "International Components for Unicode." ICU collation is an implementation of the Unicode Collation Algorithm (which is really a suite of algorithms, or an algorithm with various parameterized branches), using the Unicode Common Locale Data Repository for localization -- that's also unicode, the CLDR is a unicode thing too, part of unicode. It's all unicode. There are other implementations than ICU -- although maybe none as complete, because it is a lot/expensive, indeed. But ICU is an implementation of unicode algorithms. But for instance, unicode collation is also implemented -- in a way that will be the same as ICU modulo bugs or details the standard leaves up to implementations t

Twitter puts out a LOT of software, and open-sources a good portion. I don't know if this is smart in the sense of being overstaffed relative to their revenue, but they do it regardless. Some examples: [1] Fabric, an SDK for mobile apps - https://docs.fabric.io/android/fabric/overview.html [2] Heron, a realtime, distributed, fault-tolerant stream processing engine - https://github.com/twitter/heron [3] Finagle, a fault tolerant, protocol-agnostic RPC system - https://github.com/twitter/finagle/ [4] FlockDB, a distributed, fault-tolerant graph database - https://github.com/twitter/flockdb [5] Ruby implementation of the ICU (International Components for Unicode - https://github.com/twitter/twitter-cldr-rb [6] Clockwork Raven, Human-Powered Data Analysis with Mechanical Turk - https://github.com/twitter/clockworkraven [7] Gizzard, a flexible

For locale-aware correct sorting of unicode strings, based on the Unicode Collation Algorithm, some open source libraries twitter released are pretty awesome. ruby: https://github.com/twitter/twitter-cldr-rb javascript: https://github.com/twitter/twitter-cldr-js Human written language is pretty complicated. The Unicode standards (including the Common Locale Data Repository, the Unicode Collation Algorithm, normalization forms, associated standards and algorithms, etc) -- is a pretty damn amazing approach to dealing with it. It's not perfect, but it's amazing it's as well-designed and complete as it is. It's also not easy to implement solutions based on the unicode standards from scratch, cause it's complicated.