Closed tomkeays closed 4 years ago
While this is not an actual usability problem -- people can figure out which song is which even if the naming convention is higglety pigglety -- it is an aesthetic one, at least for me. I don't care which way we go, but I do ask that we be consistent. It would be a simple matter, if the word case option is chosen, to reformat and reupload all the files. 3 minutes work, tops.
I'm going to put this to bed. Since I'm the only contributor here, I am going to make the decision. This applies to the filenames specifically, not the title in the T:
field.
So, "The Boy's Carol" would have a filenames of 'boys-carol.abc' and 'boys-carol.pdf'.
This is partially implemented now and I plan to apply the naming consistently as I get time.
Currently, files are formatted using underscore_case -- e.g., "hunting_the_cutty_wren.pdf". The question has arisen, with the potential for multiple contributors be making submissions to the repo in the future, whether this is still the desired format? A recent contribution came in as both "Hunting the Cutty Wren.pdf" and "hunting_cutty_wren.abc". Should there be consistency?