as I found out today, the crash I recently experienced isn't actually relat=
to the content of the avi-clip, but only to the filename "=E4gypten-048.avi=
I'm wondering if there is a policy regarding text encoding in mlt. kdenlive=
tries to encode all filenames that are passed to mlt according to the local=
filesystem encoding, which appears to work fine.
If the filenames are embedded into XML documents (e.g. westley format), the=
this is not easily possible. Whatever XML-encoding you use, libxml2 will=20
return UTF-8 to you. This is a problem for example in the westley module: t=
filenames read from the XML document are not converted to the local=20
filesystem encoding, thus mlt fails to open those files.
This is something that needs to be addressed in mlt -- there needs to be so=
place where UTF-8 to local encoding, similar to QFile::encodeName(), happen=
One possible place would be everywhere, where UTF-8 input arrives, e.g. fro=
libxml2. Another option would be to expect all input, all filenames in UTF-=
kdenlive then needs to adapt to this policy. Also, all XML-snippets need to=
passed to mlt as UTF-8 instead of the filesystem encoding. E.g. krender.cpp=
currently uses decodedString() to convert westley-snippets to the local=20
filesystem encoding, in my case ISO-8859-1, which libxml2 later tries to re=
as UTF-8, leading to the crash I experienced.
The pango module probably also expects UTF-8.
Get latest updates about Open Source Projects, Conferences and News.