[Kde-bindings] Utf-8 bug

[Han Holl]

On Thursday 19 January 2006 11:29, Richard Dale wrote:

> Well, I've just tried it and it works fine for me. I added a $KCODE = 'u'
> line, and commented out the call to the dcop command line tool as that
> isn't to do with korundum:
>
Thanks a lot for your efforts.
With the $KCODE='u' it now works for me as well. And I don't quite understand 
why.
I can understand that encoding make a difference for doing things with 
strings, but in the case of a pathname I would expect it to be passed as is.
(Ok, the code _might_ just check for binary zero bytes, but that's about it.)

I'm allowed to pass all kinds of binary information in Ruby strings. I've 
written lots of scripts that traverse directories like this, without ever to 
have to use $KCODE.
There seems to be lurking somewhere something with an idea of 'valid pathname' 
that's not the same as the OSes idea of valid pathname.
Let's assume I read pathnames from a file: how am I supposed to know which 
encoding to use? My script is supposed to run on any filesystem, independent 
of encoding.

I still consider this a bug.

Cheers,

Han Holl