Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DoubtingThomas]

1. Changed: Split the capitalization files out to CapitalizationAllCaps.txt and CapitalizationExclusion.txt in the Default Resources folder of the program.

Is there any more information on these capitalization files and how to use them?

I see the new files.... but they can't be edited... Windows won't let me.  Is there some place in MediaCenter to edit these files?

[DoubtingThomas]

Bump.... I'd really like to have control over the capitalization files....  any info would be appreciated.

[RoderickGI]

The only reason they can't be edited is because they are in the C:\Program Files (x86)\ directory tree.

The best way to edit these would be to copy them out somewhere where you will maintain them in the future, edit them there, save them there, and then copy them back over the original files. You will need Administrator rights to copy them back of course.

No doubt updates and upgrades to MC will overwrite these files, so an improvement to the above would be to create a "C:\Program Files (x86)\J River\Media Center 21\Data\Custom Resources" directory and copy your modified files into that directory. I believe that MC will then use the CapitalizationAllCaps.txt and CapitalizationExclusion.txt files in this new directory, instead of the files in the original "Default Resources" directory. No need to delete the original files in the original directory. You will still need to maintain the files outside that Custom directory, since they are in a directory protected by Windows. But that is good practice anyway, as you will have a backup of your modified files.

The contents of the files seem pretty straight forward, so I' sure you aren't having trouble with that.

[DoubtingThomas]

No issue with the file format...  I know I could edit them overriding the windows permissions.  But I would want them to remain as edited for MC updates.

It's like a tease.. show me the files... provide no easy way to update them....

[RoderickGI]

No doubt updates and upgrades to MC will overwrite these files, so an improvement to the above would be to create a "C:\Program Files (x86)\J River\Media Center 21\Data\Custom Resources" directory and copy your modified files into that directory.

[Matt]

I would just like to add that if you make good improvements to the files that you think could benefit everyone, please share!

Thanks.

[DoubtingThomas]

No doubt updates and upgrades to MC will overwrite these files, so an improvement to the above would be to create a "C:\Program Files (x86)\J River\Media Center 21\Data\Custom Resources" directory and copy your modified files into that directory. I believe that MC will then use the CapitalizationAllCaps.txt and CapitalizationExclusion.txt files in this new directory, instead of the files in the original "Default Resources" directory.

Thank You for the "Custom Resources" tip, works well.

[DoubtingThomas]

I would just like to add that if you make good improvements to the files that you think could benefit everyone, please share!

Matt, I have no real improvements, other than my personal taste (like "with" should be capitalized).

Question:  I add " (live)" to the name tag for live tracks.  Is there a way to have MC not capitalize "live" when enclosed in ( ) but to capitalize it when "live" is not in ( )'s using "TitleCase"?

I would want this to be the end result of a "clean file properties"..

Gotta Live (live)



Thanks

[Matt]

Question:  I add " (live)" to the name tag for live tracks.  Is there a way to have MC not capitalize "live" when enclosed in ( ) but to capitalize it when "live" is not in ( )'s using "TitleCase"?

I would want this to be the end result of a "clean file properties"..

Gotta Live (live)

I would think adding (live) to the CapitalizationExclusion text file would do that.

Just put a new copy in CustomResources and it'll live between upgrades.

It seems a little too special to make it that way for everyone.

[DoubtingThomas]

I would think adding (live) to the CapitalizationExclusion text file would do that.

Just put a new copy in CustomResources and it'll live between upgrades.

It seems a little too special to make it that way for everyone.

Matt,

Adding "(live)" to the exclusion file does not work, when using clean properties it always changes (live) to (Live).  I assuming the parens are confusing the algorithm.

[Matt]

Matt,

Adding "(live)" to the exclusion file does not work, when using clean properties it always changes (live) to (Live).  I assuming the parens are confusing the algorithm.

Yeah, we split the string on characters like:
., , \, -, &, (, ), _, [, ], ;, /

That means the word won't have the parenthesis on it when it's processed.  I'm not thinking of a smart way around that right now.  Sorry.

[DoubtingThomas]

Yeah, we split the string on characters like:
., , \, -, &, (, ), _, [, ], ;, /

That means the word won't have the parenthesis on it when it's processed.  I'm not thinking of a smart way around that right now.  Sorry.

Well... (been there with trying to delimit "words")....

It would take some coding... but how about if an entry in the CapitalizationExclusion.txt file contains any of the word tokenizing delimiters, then that series of chars should not be touched or changed if found in the target tag string for "clean file properties" when using TitleCase.