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
Likely most reliable option is map everything to the C Locale and ascii encoding for broadest compatibility with filesystems. Also can search and replace characters like colon, which is invalid on windows as well as slash and backslash.
The text was updated successfully, but these errors were encountered:
Currently the code is removing characters that are known to be illegal in filenames on various target platforms (like slash and colon).
It's an open question if different character encodings should be converted, since most OS filesystems can handle unicode filenames, so if the dicom file has a patient name with an accented character for example, it should be valid to create a filename with the same character.
To know for sure we would need to find sample dicom data containing a variety of character strings and confirm it works for our target operating systems.
Likely most reliable option is map everything to the C Locale and ascii encoding for broadest compatibility with filesystems. Also can search and replace characters like colon, which is invalid on windows as well as slash and backslash.
The text was updated successfully, but these errors were encountered: