http://bugs.freedesktop.org/show_bug.cgi?id=16716
--- Comment #2 from Alex Rostovtsev <[EMAIL PROTECTED]> 2008-07-15 02:04:02 PST --- (In reply to comment #1) > Created an attachment (id=17679) --> (http://bugs.freedesktop.org/attachment.cgi?id=17679) [details] > The reason for this is that SwfdecURL is meant to do what the Flash player > does > when handling urls. And the Flash player happily puts all the characters into > the URL as they are ignoring (as usual) any standards out there. I don't think you understood the problem. The issue is not with how flash files are interpreted (so Adobe's plugin's behavior is not relevant to the discussion). The issue is with swfdec's API. - The swfdec API includes functions with a parameter that can be interpreted both as a url (or part of a url) and as a pathname on disk (or part of a pathname). - Which happily ignores the fact that urls are in URI encoding while local pathnames are in UTF-8. And there are no flags to specify which encoding the parameter is in. - When local pathnames with non-ASCII characters are involved, the API provides no way to construct a SwfdecURL object whose url and path fields are both valid and consistent with each other. - The SwfdecURL object is used, among other things, to specify where to load the flash files from. - Outside the browser, Swfdec relies on its own loader classes to do IO. Those loaders assume that the fields of the SwfdecURL object are valid and consistent. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ Swfdec mailing list Swfdec@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/swfdec
