Re: [Audacity-devel] Issues with Unicode and file import
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale (A. Team) <ga...@au...> - 2013-05-22 01:02:43
|
"Michael Chinen" wrote: >> On Mon, May 20, 2013 at 7:09 PM, Gale Andrews <gale@> wrote: >> >> Summary: I see a repeatable problem with adding spaces into >> the name of the suspect file, then using Open with. > Further investigation shows this bug exists with or without the space. > It happens about 1%-5% of the time for me now. The way I trigger it > is to create a short wav file with the same katakana name and make 20 > copies of it, and drag those all at once into an audacity window until > the bug triggers. Thanks, Michael for looking further at it. As I just said in the "Bug Hunt Sunday" thread, I'm down to only about 50% reproducible now. I only just noticed this thread otherwise I'd have only replied here. > I tested some more and I was able to trigger it without a unicode > filename, after importing unicode filenames previously, with one as > simple as "aaa" when importing enough (~50 tries). Were there any Unicode characters anywhere in the path? Files with Latin character names in folders with Unicode names are also a reported problem. Is there any relevance to the act of changing the name, then reimporting the contents? That was replicating so reliably that it looked more than coincidence. I have just got a crash by changing a file called "bbb" to "bbbz" in a completely Latin path and then right-click > Open with (after successfully importing a file with a Unicode name). However the crash report looks identical to the report after importing a file with a Unicode name. > I tried a few things, but what seemed to make things better was > changing all c_str() to mb_str() for Import.cpp/Project.cpp, as in, > this actually had an effect on where the crash would occur - it seemed > to be a format string function after a previous c_str() call on a > unicode string. OK I'll try that on my machine if not advised otherwise. > I couldn't replace c_str() globally because there are too many cases in > too many files, but this could be a potential fix. If I'm reading this correctly: http://docs.wxwidgets.org/trunk/overview_changes_since28.html#overview_changes_unicode we may have to change a lot of c_str() instances when we upgrade to Widgets 3.x. Gale -- View this message in context: http://audacity.238276.n2.nabble.com/Re-Issues-with-Unicode-and-file-import-tp7558250p7558269.html Sent from the audacity-devel mailing list archive at Nabble.com. |