Oops.. right on the reason, wrong on a fix. On Darwin, sed uses it's
own static map for charsets. So we can't use CHARSETALIASDIR like I
thought (false test earlier misled me). A patch like the one attached
will fix the issue, but I can't tell you what the larger implication
is. It sets the charset for US-ASCII to be ASCII.

If you look at the patch, you might wonder, why US-ASCII when we've
set C? It's because on Darwin (and probably FreeBSD) nl_langinfo()
returns US-ASCII for LC_ALL=C or POSIX.

I'm going to blame this back on the sed developers because their
static map isn't very good. It also defines "*" as UTF-8. But if they
used the Apple provided one, we'd also be screwed.

Attachment: sed.patch
Description: Binary data

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to