Filenames: Difference between revisions
Line 15: | Line 15: | ||
Replacement can be performed by [[Mp3tag]] using an Action Groups containing a Replace action for each character. | Replacement can be performed by [[Mp3tag]] using an Action Groups containing a Replace action for each character. | ||
==== | ====further restrictions==== | ||
One could also like to avoid urlencoding in urls. Or avoid that case has a meaning. | |||
*restrictions further as ascii could be: | *restrictions further as ascii could be: | ||
**prefer usage of only A-Za-z0-9_ | **prefer usage of only A-Za-z0-9_ | ||
Line 24: | Line 26: | ||
**[]() maybe reserve for special meaning | **[]() maybe reserve for special meaning | ||
**space always replaced with _ | **space always replaced with _ | ||
===work_name_az=== | |||
There can be lot of discussion about ",!?.". There can also be discussion about correct case (upper/lower). The a-z-title is a title that can be derived from lot of different original opinions about correctness. For filenames and references in databases it could be helpfull to have a-z worktitles. | |||
* remove all diacritics | |||
* make all characters lower case | |||
* replace space, comma, dot, with _ | |||
* reduce repeating _ to single _ | |||
*examples | *examples | ||
**http://eng.tango.info/work:la_maleva - disambiguation page | |||
**http://eng.tango.info/work:la_viruta - work page - unique match | |||
===Other=== | ===Other=== |
Revision as of 2008-01-15T00:24:57
Non-ASCII characters
The Issue
Non-ASCII characters in the Windows pathnames (folder and file names) of music library tracks can cause problems due to incompatiblities with:
- Macintosh
- Portable music players (where they can prevent play of the file and of subsequent files)
- FTP clients and servers (where each often appears as a garbage character pair)
- Some utility programs e.g. FLAC encoder, Beyond Compare 2
- File-sharing programs
Workaround
Replace non-ASCII characters with e.g. the nearest ASCII equivalent:
- accented char -> non-accented equivalent
- left and right quotes -> upright quote
Replacement can be performed by Mp3tag using an Action Groups containing a Replace action for each character.
further restrictions
One could also like to avoid urlencoding in urls. Or avoid that case has a meaning.
- restrictions further as ascii could be:
- prefer usage of only A-Za-z0-9_
- or only a-z_
- . for fileextensions, otherwise undecided, probably avoid
- ' not decided yet, if removed, how to write D'Arienzo?
- , avoid, at least in work titles
- []() maybe reserve for special meaning
- space always replaced with _
- prefer usage of only A-Za-z0-9_
work_name_az
There can be lot of discussion about ",!?.". There can also be discussion about correct case (upper/lower). The a-z-title is a title that can be derived from lot of different original opinions about correctness. For filenames and references in databases it could be helpfull to have a-z worktitles.
- remove all diacritics
- make all characters lower case
- replace space, comma, dot, with _
- reduce repeating _ to single _
- examples
- http://eng.tango.info/work:la_maleva - disambiguation page
- http://eng.tango.info/work:la_viruta - work page - unique match
Other
Emailing between Tobiasco and Chrisjjj
> 21 I'd better drink my wine in silence.wav My fault for not replacing that non-ASCII char - thanks! > FLAC encoder can only process computer high comma ' > > not the other high comma Yowch. Expect that program to fail on other legal Windows filenames too!
-> take care with filenames