You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering an issue where, after running certain operations in WSL (Windows Subsystem for Linux), some folders are generated with names that appear to be invalid or unrecognized when accessed from Windows. These folders, however, work normally within WSL.
Steps to Reproduce:
Run the marker_single operation in WSL that involves creating folders from file names derived from PDF named 'Changes in the marine environment of Port Kembla Harbour, NSW, Australia, 1975-1995 a review..pdf'.
Attempt to access these folders from Windows.
Expected Behavior:
The folders should be accessible and manageable from both WSL and Windows environments without issues.
Actual Behavior:
The folders are cannot open or delete in Windows, and file manager prompts the folder do not exist, making any operation on them impossible.
Possible Cause:
It seems that the folder names may include special characters from the original PDFs that are not compatible with Windows file system norms.
Suggested Solution:
A potential solution could be to implement a naming sanitation process that strips or replaces special characters during the folder creation phase in the script or application.
The text was updated successfully, but these errors were encountered:
I'm encountering an issue where, after running certain operations in WSL (Windows Subsystem for Linux), some folders are generated with names that appear to be invalid or unrecognized when accessed from Windows. These folders, however, work normally within WSL.
Steps to Reproduce:
Run the marker_single operation in WSL that involves creating folders from file names derived from PDF named 'Changes in the marine environment of Port Kembla Harbour, NSW, Australia, 1975-1995 a review..pdf'.
Attempt to access these folders from Windows.
Expected Behavior:
The folders should be accessible and manageable from both WSL and Windows environments without issues.
Actual Behavior:
The folders are cannot open or delete in Windows, and file manager prompts the folder do not exist, making any operation on them impossible.
Possible Cause:
It seems that the folder names may include special characters from the original PDFs that are not compatible with Windows file system norms.
Suggested Solution:
A potential solution could be to implement a naming sanitation process that strips or replaces special characters during the folder creation phase in the script or application.
The text was updated successfully, but these errors were encountered: