Open rzw opened 3 months ago
Not all operating systems support the same character set in folder and file names. Therefore characters which may cause issues get replaced in folder and file names but Manuskript will still store the original names with those characters in its metadata (for example "folder.txt").
Does this behavior cause any issues?
Yep. But I don't know if umlauts are the cause. Firstly, I couldn't rename (to ue instead of ü). Then I created a new folder with ue and moved all sub elements. In Manuskript they were moved but not in the file system (always after saving of course). The same with deleting. The umlaut folder was deleted in Manuskript but not in the file system. I'm using 0.16.1 in Windows 10 64bit.
I use Manuskript for German stories and had never problems like this!
I have Chapters with Umlauts, special character, including {}/()[] and so on!
The OS I use is Linux (ext4)! Starting using Manuscript with 0.10 or 0.012, and today I use the latest Version!
I don't think that the problem comes directly from Umlauts and their substitution, more likely too long file names, I don't know if Manuskript this cleans also? I know there are always a maximal length for file names. One for the actual name and one for the whole path. I do not know the Values, but they exist and are for the most different filesystems, also different.
@obw I can assure you that file or path name lengths are not an issue as the data is in second or third level and names are short. I assume there's a problem referencing the files for certain tasks (move, delete etc.) due to the discrepancy between inner-Manuskript names and actual file names.
Umlauts in folder names are replaced by a dash on the drive, not so in Manuskript. I suppose as a result of this discrepancy move operations of subfolders or deletions of the folder itself are not carried out.
Maybe it has nothing to do with the umlauts. I only checked reported bugs with search word "umlauts". Apologies if this is a general problem already reported.