Re: [Ifp-driver-common] Help!...again!

[Geoff O. <oa...@us...>]

Sorry it took me so long to respond..

On Mon, Oct 10, 2005 at 07:47:51PM +0000, Matthew Shin wrote:
>    Error message:
>    localhost bin # ./ifp_gui
>    err:  [local_iconv] err=-84. problem converting
>    err:  [ifp_utf16_to_utf8] err=-84. conversion failed

On Mon, Oct 10, 2005 at 08:06:51PM +0000, Matthew Shin wrote:
>    I speak Korean
>    But the system is set on English...

Ah, that's a tricky problem: when libifp tries to copy the Korean to an
English system, the conversion fails because Chinese symbols can't be
repsented in "ISO-8859-1".  (ISO-8859-1 is probably the charset your
English system is using.)

The quickest way to fix this is to set your locale to UTF-8.  (Not for
the whole system: just in the shell where you launch ifp_gui.)

On Tue, Oct 11, 2005 at 09:19:28AM -0600, Jim wrote:
> I believe this is a local problem, but I am not sure how to fix it.

Ugh.  So the problem only happens when:

  1. the system's locale isn't unicode
  2. filenames on the player can't be represented in the system's locale

I agree that libifp should handle this with more grace.  If we could
find a way of converting filenames using placeholder characters, that
would be a good start.  However, that would break libifp's api in serval
places: ifp_rmdir, ifp_delete, ifp_download_file.. to name a few.

James, how would this be handled in Python?  Does python use a separate
charset for internal processing?

Thanks,

Geoff