[openi18n-im:01281] Re: moving from csconv to iconv?

Hi,

Hidetoshi Tajima wrote:

> AShiZaWa KaZuNoRi wrote:
>
>>> I believe this has been discussed before, but I can't find
>>> a thread on it right now.  Maybe someone can point me to one? :)
>>>
>>> I would like propose that we move from using csconv
>>> to iconv for im-sdk.  With the prevalence of iconv
>>> in FOSS and the availability of GNU libiconv
>>> for non-glibc platforms this seems very natural
>>> and im-sdk will also be able to lose quite a bit of weight.
>>>
>>> Are there any known issues with using iconv instead of csconv?
>>>   
>>
>>
>> I thought that no module use csconv on any platform for now, or
>> am I wrong?
>>  
>>
> Seems recent change made in lib/iiimcf has started using it again. I'm 
> not sure if this
> is really needed, though.

The Changes were introduced as part of the NS based I/O API implementation.
The idea was, for LEs to get the list of native filename and 
directories, IIIMCF
converts the native filenames/directories to UTF-8 and send it as 
UTF8_STRING
to server.

Thanks and Regards,
Sriram.