>not to mention some obsolete Faildows encodings like CP1251 still widely used here in lots of tech-slowpoke organizations. as we're talking encodings: The wor

>not to mention some obsolete Faildows encodings like CP1251 still widely used here in lots of tech-slowpoke organizations. as we're talking encodings: The worst file I ever had to deal with combined, within one file, UTF-8, cp437 and cp850. I guess they had DOS and Unix machines bot no Windows boxes touching that file. This is a problem that won't go away. Many developers are not aware of how character encoding, let alone Unicode, actually works and, what's the worst about this mess, many times, they can get away without knowing.