So I have done some thinking and I agree that the white spaces and bracket information can be addressed by "Replace" actions. The trick is to put them after the action to add a space after a period. I already have some of these build in so I will have to place the period action prior to them.
I am going to look at this action which may have become a bit unruly. I will attach it, perhaps you can take a look. I pieced it together from other actions I got here, some I was able to figure out myself, and some I created with your help. It has worked well for me, but is not perfect.
In the action "steps," starting 19 actions from the bottom, I have 8 "replace with regular expression" actions that replace a set of spaces with one space, but I am pretty sure that not how it works and perhaps they should be just "replace" actions. I do have a set of those (simple "replace" actions) earlier in the action, so perhaps I got confused, which seems to happen often to me with all script related topics, and just repeated them with the wrong type of action.
You may note that 11 actions up from the bottom I do have so regular expression actions that deal with multiple cases (separated by a "|" ) in one action. Maybe I can make one of those for all the special cases to skip (comma, closed bracket, parenthesis, or curly bracket, or another punctuation)? It would be more neat than making a "Replace" for each, I believe? I just don't know if you can place it in a "replace with regular expression" action, where you instruct the action NOT to and a space after a period if followed by once of those special cases.
Here is the action I was hoping to modify to serve this purpose:
Action: Replace with regular expression
Replace matches with:
*using case sensitive comparison
Anyhow, I added your suggested replace action
Regular expression: "(\d*)."
Replace matches with: "$1. "
and this is what happened:
"Test the 8.Now test U.S.A.Now Test O.K.Now test the ellipse...All songs recorded at Muscle Shoals Sound Studios, Sheffield, Alabama.
Produced for Muscle Shoals Sound productions, Lynyrd Skynyrd, Inc., and Sir Productions.
Audio restoration, assembly and CD digital remastering at Audio Mechanics, Los Angeles, CA.
Photography: cover, MCA Archives; page 5, courtesy Judy Van Zant Jenness; page 7, courtesy Judy Van Zant.
Track 1 - Recorded June 28-July 2, 1971. Previously unreleased.
"Test the 8.Now test U.S.A.Now Test O.K.Now test the ellipse...All songs recorded at Muscle Shoals Sound Studios, Sheffield, Alabama..
Produced for Muscle Shoals Sound productions, Lynyrd Skynyrd, Inc., and Sir Productions..
Audio restoration, assembly and CD digital remastering at Audio Mechanics, Los Angeles, CA..
Photography: cover, MCA Archives; page 5, courtesy Judy Van Zant Jenness; page 7, courtesy Judy Van Zant..
Track 1 - Recorded June 28-July 2, 1971. Previously unreleased..
Track 2 - Recorded June 28-July 2, 1971. Originally released on "Lynyrd Skynyrd" boxed set, MCAD3-10390, November 12, 1991.."
Unfortunately, it does not seem to work. There was no space added after the 8, the U.S.A. of ellipse. What is weird is when I paste it here, there there are new lines or carriage returns that do not display in the comment. There is no space between "Alabama.." and "Produced for Muscle" in Mp3Tag, but when pasted here it exists. I am not sure why.
I also figure my actions with Char(10) and char(13) are adding the extra period after a sentence punctuated by a period and followed by a new line or carriage return, such as "Alabama.."
Hopefully I can get this script sorted out as it would be very useful if I got it to serve its purpose. As always, many thanks for your help!
Here is the action:
Delete all whitespaces & Case Corrections-2;Length from _Legth)-improved Mixed Caps only on Comment, Album &Title Fields, Barcode format (Edit 2 second suggestion by ohrenkino)).mta (8.7 KB)