Hi. I am trying to solve the handling of documents created with a different locale than the system's current one.
Let's say we have a document created with a french locale, say fr_FR.UTF-8 (which has a comma as separator). When loading that document on a system with english locale, MLT switches to the fr_FR locale and then expects all input parameters to be in that locale, which is not very handy since our Kdenlive UI will use the system locale (that is what the user expects). That means that when opening a document with a different locale, Kdenlive (or any other UI) will have to translate all parameters to that locale before passing them to MLT. When saving the file through the XML consumer, it keeps that original french locale, and there seems to be no way to convert an MLT playlist from one locale to another - at least in my tests, changing the locale of a producer did not produce a correct xml output (some parameters kept the old locale encoding). So is this supposed to work like that? Having to do locale conversion for all data that is sent to MLT? thanks & regards jb ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
