Hi! * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2008-11-13 01:55:40 CET]: > (There are many other problems though: Aside from the broken entities, > screen positions are miscalculated, resulting in misplaced link > highlights and stray characters at line ends. Also, if the input charset > differs from the terminal charset, things won't work at all. All this > requires proper charset support to fix, which is on the top of my ToDo > list. However, I'm still not sure how to implement this, so I doubt I > could do it in time for lenny, even if the release managers would > actually accept such a late change...)
I'm not sure, but shouldn't libiconv be able to help you here? From what I understand it's meant as charset encoding conversion library. If the data comes from a website the server sends the charset along, but even for local generated data it shouldn't be too hard to figure out the charset encoding. Easiest would be what the standard claims: assuming iso-8859-1 for non-defined charsets. Conversion to what the locale defines (through libiconv). Unfortunately I don't know the netrik code closer and neither I am deep into iconv or C business so it would take me quite a while to come up with a sensible patch for that. I am though offering to assist as consultant or tester or whatever you might need. Thanks for your response, antrik. :) Rhonda -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
