On Sunday 13 February 2005 15:46, Chris Cannam wrote: > On Sunday 13 Feb 2005 13:22, Pedro Lopez-Cabanillas wrote: > > So, the problem is with plugins. The sentence is right after > > dlopen(), so it is calling setlocale() in _init(). Indeed, if you > > look at swh-plugins (http://plugin.org.uk/) sources, a lot of plugins > > are doing that. > > OK, and it appears from the plugin source that they do that so that > plugin label names &c can be translated. > > In fact, the obvious question in all this is: why is the locale _not_ > normally set during Rosegarden execution? Is it because KDE uses its > own locale conventions for translation and prefers that the libc locale > remain as "C" so as to avoid the sorts of problems we're seeing?
Yes, I think so. If a program doesn't call setlocale(), it remains in a default locale environment. KDE uses its own i18n environment, and we have learned a lesson about messing with that. > If so, then presumably we should just revert the locale to "C" after > loading a plugin. I agree again. Even a dssi plugin could use setlocale() too, or use a library calling setlocale(). We should restore the locale after enumerating plugins. I will write, test and commit a fix about this, unless you do it before. Another question: I have been testing this issue without Jack being active, so no audio capabilities where enabled in RG. Shouldn't be disabled this plugin enumeration when RG has not audio caps enabled? Regards, Pedro ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
