INTERACT FORUM
More => Old Versions => Media Center 16 (Development Ended) => Topic started by: vagskal on August 31, 2011, 05:53:04 am
-
I have been doing a lot of fixing capitalization lately, using the new RegEx() function. One small addition to the Clean File Properties options that would be really useful when fixing capitalization in non English (or German) languages is a Lower Case All Letters Except the First Letter option. After using the current Lower Case All Letters option I always have to manually fix the very first letter in all song and album names. I do not know of any language where the first letter in the first word in a sentence is not capitalized.
Thanks.
-
Isn't this an option in "Clean Library Fields?"
-
Isn't this an option in "Clean Library Fields?"
No, not in the Clean File Properties feature. For Fix capitalization the current alternatives are:
Title Case
Upper Case All Words
Upper Case First Word Only (I really do not know if this option puts the entire first word in upper case letters, or just the first letter in that word)
Upper Case All Letters
Lower Case All Letters
And Lower Case All Letters Except the First Letter is not an option in the FixCase() expression either.
-
Upper Case First Word Only (I really do not know if this option puts the entire first word in upper case letters, or just the first letter in that word)
This just capitalizes the first letter of the first word, which is also what FixCase() mode 2 does. Is that not what you're looking for? Or does it not work for languages other than English?
-
Something like this?
Regex([Name], /#^([[:punct:]]*\w)(.+)$#/, -1, 1)FixCase([R1], 3)FixCase([R2],4)
-
How is that different than FixCase([Name], 2)?
-
(i could never) give you up <-- fixcase
vs.
(I could never) give you up <-- regex
This is even better than the previous expression:
Regex([Name], /#^([[:punct:]\d\s]*\w)(.+)$#/, -1, 1)FixCase([R1], 3)FixCase([R2],4)
-
OIC. I'm sure you weren't suggesting it, but this doesn't imply Clean file properties > Fix capitalization or FixCase() should produce the same results. But perhaps it is an argument for including user-defined regex operations in Clean file properties. That would allow us to continue to use that function for that purpose, and select whatever customized tools we need there (e.g., this regex, instead of the built-in Fix capitalization function).
-
Thanks for the replies!
Yes MrC, something like that (but for my purpose I would omit the \d part since "18 bästa" is correct in Swedish).
rick.ca's last comment made me think that what would be really useful/powerful is a way to apply a custom expression to one or more fields in ONLY the selected files. I don't think there is a way to do that now and we only have the predefined clean file properties options and find & replace. This could be an addition to the find & replace function.
-
Thanks for the replies!
Yes MrC, something like that (but for my purpose I would omit the \d part since "18 bästa" is correct in Swedish).
rick.ca's last comment made me think that what would be really useful/powerful is a way to apply a custom expression to one or more fields in ONLY the selected files. I don't think there is a way to do that now and we only have the predefined clean file properties options and find & replace. This could be an addition to the find & replace function.
You're welcome.
You can apply these expressions to fields.
I agree, the find/replace function could use a few more goodies.
-
You can apply these expressions to fields.
Yes, I know that, but not only to the selected files. Applying the same capitalization expression to the [name] field of every music file in the library regardless of the language would not be wise.
-
I'm confused by that last statement. I update fields for just the selected files routinely.
Select the files you want to update. In Action Window > Tag, click desired field to edit, and paste in =expression, hit Enter, and you're done.
-
Select the files you want to update. In Action Window > Tag, click desired field to edit, and paste in =expression, hit Enter, and you're done.
True. And to be clear, the point of my suggestion had to do with convenience, not necessity. If one wants to clean file properties, he should find all the tools he may need in Clean file properties. The same idea is already implemented in Rename, move & copy files, where these expressions can be used as rules. As mentioned, it's also applicable to Find & replace, and probably a number of other tools we haven't yet considered.
-
Yeah, its all good. We're all on the same page. Power tools for the power users, and Friendly tools for some extra love.
-
I'm confused by that last statement. I update fields for just the selected files routinely.
Select the files you want to update. In Action Window > Tag, click desired field to edit, and paste in =expression, hit Enter, and you're done.
Aha, that sounds logical! I have just not tried it (the = thing) that way, only when using the library fields option.