On Tue 27 Jan 2009 06:52, Mike Gran <spk...@yahoo.com> writes:
> I said
>
>> (Though, such a scheme would force scm_take_locale_string to become
>> scm_take_iso88591_string.)
>
> which is incorrect. Under the proposed scheme, scm_take_locale_string
> would only be able to use that storage directly if it happened to be
> ASCII or 8859-1.
Perhaps as part of this, we should add
scm_{from,take}_{ascii,iso88591,ucs32}_string. This would help greatly
when you know the format of data that you're writing to object code or
in C, but you don't know the locale of the user.
Andy
ps. Good luck! Having this problem looked at, with an eye to solutions,
makes me very happy :-))
--
http://wingolog.org/
