Re: Glib::filename_to_unicode bug?

[Dave Hayes <dave jetcafe org>]

Brian Manning <elspicyjack gmail com> writes:
> I'm guessing that Perl is just passing along the bytes unfiltered to
> FreeBSD's open() system call, and it looks like FreeBSD's open() call
> is forgiving of improperly encoded UTF-8 for filenames.  

Yes, it's calling the standard POSIX compliant open() you see on any
POSIX system. That takes just bytes. 

> However, since your byte string is not valid UTF-8, it's causing Glib
> to complain.

I guess I should ask this: If I have files on the disk that have invalid
UTF-8 characters in them, do I have a way to get Glib to operate on 
files who's names are invalid UTF-8 strings? Is Glib really forcing me
to rename this file to operate on it? :)
-- 
Dave Hayes - Consultant - Altadena CA, USA - dave jetcafe org 
> > > The opinions expressed above are entirely my own <<<

The most important service rendered by the press is that of
educating people to approach printed matter with distrust.