Mnyb wrote: 
> 
> It can be weird , I've had text that looked ok in a shell but not i
> gnome on the same computer ? i just renamed the files to the same name
> and they looked the same in both ? I chalked that one up to the files
> originating on one OS and being shared over the internet and then
> downloaded via some download manager ?
> 
Unlikely - the client application (dl mgr, browser) is responsible for
the file name. There might be a name suggested by the server (which will
only be incorrect if the name was already broken before), but this
exchange is fortunately standardized in Unicode.
That being said, I still think the whole thing is a complete mess in
Linux. It was supposed to be solved by the switch to Unicode, but
somehow the issues keep popping up.

> 
> Is not perl also known to produce these kinds of bugs at least LMS does
> I've reported numerous character/language bugs over the years ?
I doubt it's Perl's fault alone. Any application has this issues (e.g.
the system is set to unicode UTF-8, but the application runs in a
different encoding).
However, currently the only app I have issues with regarding encodings
is LMS, so there might be something to it (but it's a certain 
combination of OS/Perl/LMS - others will work).
Still, it's annoying (e.g. if I save a playlist which contains umlauts
in LMS, it will fail to find the files when the playlist is loaded
afterwards), so my "solution" is to not use special characters in file
names at all...



[ extGUI4LMS - an alternative web interface: 'forum'
(http://forums.slimdevices.com/showthread.php?98186-Announce-Alternative-Web-Interface-(beta))
/ 'homepage' (http://code.google.com/p/extgui4lms/) ]
------------------------------------------------------------------------
Roland0's Profile: http://forums.slimdevices.com/member.php?userid=56808
View this thread: http://forums.slimdevices.com/showthread.php?t=98186

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to