More > JRiver Media Center 27 for Mac

Find & Replace

<< < (2/3) > >>

bMinor:
thank you both for your input.
MC can read any character the 1st time and import the file no matter what it's called it seems. however, file or pathnames cannot contain any of these four characters  ", /, ?,*  if you plan to eventually move the directory using MC's 'find & replace' in the library tools. Also, the filename is not being read if it starts with a 'space'.
Simply just re-importing the moved files in question works but you'd be in the same boat if you need to change directory again after that. I bit the bullet and started altering the file names/paths manually...hey I'm at the letter E. In a couple of days I should be done. Thank god for retirement... :)

zybex:
Linux doesn't allow '/' in filenames, as that is the directory separator char. It does allow '?' and '*' and a few others which are forbidden in Windows. So you might have some files with those chars, but that's not advisable for compatibility reasons. Perhaps MC doesn't handle them correctly due to common code with the Windows version.

If you have the files on a Linux filesystem such as EXT2/3 (or a NAS, for instance), but you're using MC for Windows to manage those files, you might run into problems.

You should avoid other chars in the filenames for compatibility. Here's a list:
https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions


--- Quote ---The following reserved characters:
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)

--- End quote ---

HaWi:

--- Quote from: zybex on January 06, 2021, 03:10:20 pm ---Linux doesn't allow '/' in filenames, as that is the directory separator char. It does allow '?' and '*' and a few others which are forbidden in Windows. So you might have some files with those chars, but that's not advisable for compatibility reasons. Perhaps MC doesn't handle them correctly due to common code with the Windows version.

If you have the files on a Linux filesystem such as EXT2/3 (or a NAS, for instance), but you're using MC for Windows to manage those files, you might run into problems.

You should avoid other chars in the filenames for compatibility. Here's a list:
https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions

--- End quote ---
The reason files that contain special characters are not found after saving them is that MC replaces these characters with a permissible one. E.g. : is replaced with _. I am not entirely sure right off the top of my head but it maybe that all special characters are replaced by _.

zybex:
MC shouldn't import them in the first place. No point in importing a file if it can't then work with it. Perhaps MC can warn the user and ask permission to rename the file itself.

bMinor:
And the best answer is:


--- Quote from: zybex on January 07, 2021, 10:02:41 am ---MC shouldn't import them in the first place. No point in importing a file if it can't then work with it. Perhaps MC can warn the user and ask permission to rename the file itself.

--- End quote ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page