Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unicode filename problem on both gnome and kde #390

Open
gokhanmoral opened this issue Feb 22, 2024 · 5 comments
Open

unicode filename problem on both gnome and kde #390

gokhanmoral opened this issue Feb 22, 2024 · 5 comments

Comments

@gokhanmoral
Copy link

files or folders with unicode characters cannot be fetched or used.

reproduction method:
creating a file over onedrive web with the name "THIS_IS_TEST.txt" with content "test1" can be displayed with gnome text editor or kwrite.
creating a file over onedrive web with the name "THİS_İS_TEST.txt" with content "test2" cannot be opened.

creating a folder with letter "İ" in onedriver folder creates a folder on onedrive and it can be used over web, but the same folder cannot be used on neither gnome files nor dolphin.

@gokhanmoral
Copy link
Author

additonal info:

on terminal, somehow autocompletion works on fetching the file. but when I type in the filename manually, file cannot be fetched.

gm@fedora:~/onedrive$ cat THİS_İS_TEST3.txt 
test3
gm@fedora:~/onedrive$ cat THİS_İS_TEST3.txt
cat: THİS_İS_TEST3.txt: No such file or directory
gm@fedora:~/onedrive$ 

in the first one, the file is selected with auto completion (writing 'TH' followed by a tab press)
in the second one, I typed the filename using Turkish keyboard.

@foopsss
Copy link
Contributor

foopsss commented Feb 26, 2024

Is the "İ" character a turkish one? Either way, I think this might be related to the naming conventions issue mentioned in #387.

@gokhanmoral
Copy link
Author

gokhanmoral commented Feb 26, 2024

Is the "İ" character a turkish one? Either way, I think this might be related to the naming conventions issue mentioned in #387.

yes, it is a turkish character which is not available in ISO-8859-1 but it is in ISO-8859-9. and no, it is not a disallowed character in none of the windows filesystems. it is usable in ntfs as well as onedrive. I suspect that the representation differences in utf-8, utf-16 and single char using 8850p9 might be causing the problem.

@foopsss
Copy link
Contributor

foopsss commented Feb 26, 2024

Hmmph, I see. Hopefully @jstaf or @abraunegg have something else to say on this regard.

@abraunegg
Copy link

@foopsss , @gokhanmoral
I cannot comment on how 'onedriver' operates.

The 'onedrive' application I maintain and develop checks compliance against a number of specific items (as per current development tree 'alpha-5'):

  • Check path against Microsoft OneDrive restriction and limitations about Windows naming for files and folders
  • Check path for bad whitespace items
  • Check path for HTML ASCII Codes
  • Check path for ASCII Control Codes
  • Validate that the path is a valid UTF-16 (ISO/IEC 10646) encoded path & does not contain invalid UFT sequences

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants