Sorry, I'm stuck with this, maybe someone could take a look at it?
What I found:
in mscore.cpp:1974
QApplication::setStyle(new MStyle);
if this line is commented out, filenames with non-ascii charactes show up, as stated above (line number was wrong).
but:
when replaced with
QApplication::setStyle(new QCommonStyle);
it doesn't work.
So what I thought was, QCommonStyle would be the default application style which you can extend by deriving your own class. The above command should do nothing. It seems though, that this isn't the case.
I also can't find anything in the qt documentation about this behaviour. So most probably the problem is hidden somewhere I just don't see it.
[trunk rev.3697] doesn't list file name with chinese charactors in open file dialog
⇒
[trunk rev.3697] doesn't list file name with non-ascii characters in open file dialog
Here's a fix. Works only in gnome environments.
MStyle is derived from QCommonStyle, which shows above described broken behaviour. The patch changes the base class to QGtkStyle, which enforces native file dialogs instead of the qt versions.
The bug isn't fixed though, can't find where it comes from.
Comments
The problem first appears in revision 3446 trunk (Tested using Ubuntu 10.10). Previous revisions show the Chinese file name without a problem.
The same happens also with german Umlauts ö,ä,ü and the letter ß
System:
debian squeeze
gnome 2.30.2
QMake version 2.01a
Using Qt version 4.6.3 in /usr/lib
musescore trunk r3783
It's happens somewhere in QApplication::setStyle();
when commenting out mscore.cpp:1975,
MuseScore looks ugly, but filenames containing non-ascii characters show up again.
Sorry, I'm stuck with this, maybe someone could take a look at it?
What I found:
in mscore.cpp:1974
QApplication::setStyle(new MStyle);
if this line is commented out, filenames with non-ascii charactes show up, as stated above (line number was wrong).
but:
when replaced with
QApplication::setStyle(new QCommonStyle);
it doesn't work.
So what I thought was, QCommonStyle would be the default application style which you can extend by deriving your own class. The above command should do nothing. It seems though, that this isn't the case.
I also can't find anything in the qt documentation about this behaviour. So most probably the problem is hidden somewhere I just don't see it.
fnbecker,
I'm glad you're working on this, so moving you're still working during holiday.
Here's a fix. Works only in gnome environments.
MStyle is derived from QCommonStyle, which shows above described broken behaviour. The patch changes the base class to QGtkStyle, which enforces native file dialogs instead of the qt versions.
The bug isn't fixed though, can't find where it comes from.
For the record, I believe the bug only applies to GNOME (the open file dialog shows all files on Windows at least).
That's not a minor problem. Openning a file is the basis, and the software is IMO quite unusable for some languages.
You can change the prioirty when you add a comment. Look just above the comment box.
I only can proposal. I do not manage bugs.
Or i guess most of the bugs will became "critical" for somebody.
BTW lasconic show me a way to "fix" that. But it is need to use native style.
* Go to preferences
* In the style panel:
** select Native on the drop down list
** check the checkbox about Native dialog
* Restart the app.
I use Ubuntu 11.04
I am not a part of the development team, so what I am about to say may be contradicted.
In my experience, people do change these settings. Sometimes there is a response that their change was inappropriate, but sometimes they have a point.
I have seen that if the poster can make a good case for their point of view, it is at least considered, and often accepted.
Personally I wouldn't change these unless I had a strong case.
regards,
Hi Rui Fan
Are you still encountering problems?
Does this warrant upgrading to normal?
Is this the same?: #14757: Cannot open/save files with non-ASCII characters in filename
many years have passed and no more reports of this problem (or no more GNOME users :) ?). I close the issue. Reopen if needed.