- Home
- Software
- Threads FAQ
- A glossary of terms used in threaded programming
- About the multithreaded programming FAQ
- After I create a certain number of threads, my program crashes [Unix]
- Asynchronous thread cancellation [Unix]
- How can I perform a join on any non-specific thread? [Unix]
- Mixing threads and signals [Unix]
- The history of threads
- What are the main families of threads?
- What is a thread?
- Why are reentrant library and system call interfaces good?

Why do you convert ß to SS not to capital ß?
http://en.wikipedia.org/wiki/Capital_%C3%9F
Because ẞ is not widely used in German, and to use it as a capital ß would violate the guidelines set in the Unicode SpecialCasing table.
I really appreciate what you are doing here, more power to your hacking elbow.
Are you implementing this all yourself in pure Haskell? Why not hook into ICU or something similar, which would provide a proven-correct implementation?
Porges, where I can, I implement the code in pure Haskell. I’ve written a separate text-icu library that provides bindings to ICU for code that is currently just too much trouble.
Perhaps we should really have some kind of way to generate the code from the CLDR XML data, so that when that is updated we can update the Haskell library without too much hassle.
As interesting as this is, I wonder whether or not this is something that the Haskell community should be maintaining. Wouldn’t a binding for, say, ICU be more appropriate?
Pseudonym, there’s already a text-icu package that contains ICU bindings. My goal is to write as much Unicode handling code in pure Haskell as possible, and to leave the complex and fugly stuff to the ICU bindings. That way, if you have fairly simple needs, your number of dependencies is kept low. Also, crossing back and forth between Haskell and C++ is very expensive (due to the different representations used for text), so calling into ICU shouldn’t be done often.