This needs to be looked at more completely. Currently if you use {edition-{EDITION TAGS}} you'll get {edition-IMAX} in the file path. If you use {edition-{Edition Tags}} you'll get {edition-Imax}. Now consider 10th Anniversary. if you use {edition-{EDITION TAGS}} you'll get {edition-10TH ANNIVERSARY} but with {edition-{Edition Tags}} you get {edition-10Th Anniversary} . I think this is not correct. Even in proper case then 10TH should be '10th' and not '10Th' (with a capital 'T').

More investigation. Maybe something like:

public static string ToTitleCaseIgnoreOrdinals(this string text)
        {        
            string input = CultureInfo.CurrentCulture.TextInfo.ToTitleCase(text);
            string result = Regex.Replace(input, "([0-9]st)|([0-9]th)|([0-9]rd)|([0-9]nd)", new MatchEvaluator((m) => m.Captures[0].Value.ToLower()), RegexOptions.IgnoreCase);
            return result;
        }

which will work for English but you'd need something else if edition tags have ordinal numbers in other languages.

Add that as a StringExtension and then update:

  private void AddEditionTagsTokens(Dictionary<string, Func<TokenMatch, string>> tokenHandlers, MovieFile movieFile)
        {
            if (movieFile.Edition.IsNotNullOrWhiteSpace())
            {
                tokenHandlers["{Edition Tags}"] = m => CultureInfo.CurrentCulture.TextInfo.ToTitleCase(movieFile.Edition.ToLower());
            }
        }

to be:

 private void AddEditionTagsTokens(Dictionary<string, Func<TokenMatch, string>> tokenHandlers, MovieFile movieFile)
        {
            if (movieFile.Edition.IsNotNullOrWhiteSpace())
            {
                tokenHandlers["{Edition Tags}"] = m => movieFile.Edition.ToTitleCaseIgnoreOrdinals();
            }
        }

Further research suggests movie editions use exclusively English ordinal numbering so the fix above will be fine. Let me know if youd like a pull request. @Qstick

Would you like a pull request fixing this please?

Would love to see Andy's fix implemented.

Ok this has been on my list of small annoyances for a long time, so I've got a fix in the works! I don't love the pattern of nested function calls (a builder pattern might be more elegant?) but it works. Would love any feedback on this implementation, then I'm happy to send in a PR.

brandonscript@5582e8b

Handles strings that should always remain uppercase, e.g. IMAX, 3D, and ordinals that should always remain lowercase, e.g. 1st, 2nd, 3rd, 10th.

Wondering if we should include SDR and HDR too?
Edit: Added this

Discussion thread here as well: brandonscript@5582e8b#commitcomment-139616872, specifically what do we want to capitalize, and when?