After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 720998 - Error message "No such file or directory" when the directory name contains non latin character
Error message "No such file or directory" when the directory name contains no...
Status: RESOLVED DUPLICATE of bug 557815
Product: Gnumeric
Classification: Applications
Component: GUI
1.12.x
Other Windows
: Normal major
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-12-24 01:12 UTC by xyen2001
Modified: 2013-12-24 23:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot (17.26 KB, image/jpeg)
2013-12-24 01:12 UTC, xyen2001 		Details

Description xyen2001 2013-12-24 01:12:24 UTC 
Created attachment 264826 [details]
screenshot

Hi,

Sorry I don't know how to submit a report properly. But I do like to help.

When I click a file name containing Chinese character in Windows Explorer, I get an error message "No such file or directory".
Comment 1 Morten Welinder 2013-12-24 03:36:54 UTC 
We've seen this before and we're unsure why it occurs.

*** This bug has been marked as a duplicate of bug 557815 ***
Comment 2 xyen2001 2013-12-24 10:05:51 UTC 
Thank you for your attention. But the case is a little bit different. Sorry that I didn't make it clear enough. I'll try to explain it again.

When the file name or folder name containing non-Latin characters:
I can open / operate the files without problem.
I get the error message (attached in the previous post) only when I try to click-open the file in Windows Explorer.

If I mouse drag *.gnumeric into opened gnumreic window, I can open the file correctly.
If I mouse drag *.ods into opened gnumeric window, I get no response.
Comment 3 Morten Welinder 2013-12-24 14:37:37 UTC 
> I can open / operate the files without problem.

Opening from the inside never caused a problem.

> I get the error message (attached in the previous post) only when I try
> to click-open the file in Windows Explorer.

This is what bug 557815 is about and what I think I fixed last night.

> ... drag ...

No idea.
Comment 4 xyen2001 2013-12-24 23:51:10 UTC 
Thank you very much for the quick fix.
Is there a way to get a binary or should we wait for the next binary release?
Merry Christmas.