Menu
▾
▴
#5 Word Case needs better logic
The "Word Case" filter only capitalizes letters following
spaces, which means that a file like this:
songname (d.m.c. remix).mp3
gets renamed to:
Songname (d.m.c. Remix).mp3
when what we (well, ok, what *I*) would like to see is:
Songname (D.M.C. Remix).mp3
There are two approaches I can think of:
1) Have a short list of "characters to capitalize after",
which off the top of my head should include " .(_-[{,&".
2) Capitalize after all symbols as well as space. The
problem with this approach is "don't" becomes "Don'T".
No rush for this to be added to the main sources. I've
already recompiled my own version. <grin>
Logged In: YES
user_id=298482
Thanks. It changed it also, including ")]}+~#=".
I guess including the " ' " would be too much "I'Ve Haven'T
Caps'S letters." should be more like "I've Haven't Caps's
letters.". Personnally I think caps are useful to make words
visible, not to look MeSsEd-uP.
Logged In: YES
user_id=537813
Excellent (and quick) work! I agree it's best to leave the apostrophe character out of the list. (French speakers may disagree though, for example, since they use them a lot more to join words. For example, "L'Anglaise".)
It is possible to go overboard in logic to handle capitalization. If you want to see a super complete approach, look at the "MP3 Tag Tools" project (http://sourceforge.net/projects/massid3lib/). It includes 'symbols to capitalize after' (what you're now doing), 'prefixes to capitalize after' (to handle "McDuff", "O'Clock", etc.), 'words to always force UPPER' (DJ, II, III, IV, etc.) and 'words to always force lower' (aka, vs, etc.). Can't think of much that doesn't get covered by that approach!