Fuck this character encoding shit.

Let's say I have a 8-bit C string with an arbitrary character encoding. This string represents a local file path. The encoding is arbitrary since it is obtained by calling some .zip file routines - which do not specifically require one encoding or another, so basically everyone can encode his filenames as it goddamn pleases him.
Now, another library requires that all file names are to be encoded in UTF-8 before they can be passed to it.

Now how the fuck do I convert from one encoding to UTF-8 if I do not fucking know which base encoding was used? This is driving me crazy.

>>32
It's only about 5 weeks old, so let it slide. Necrobumping has happened for a long time, and sometimes led to a renewal of a good conversation. Don't let last year sour your opinion of them.

The real trouble is people like >>31, who can't wait for the weekend to act retarded.
>>33
That is likely to be the case for quite a while, just like companies that use IE6 for their intranet. Best not to think about it.