# Case Conversion for \_ALL following ( **URL:** \ **Category:** Support\ **Created:** [July 3, 2023, 9:03pm UTC](https://community.mp3tag.de/t/case-conversion-for-all-following/61465 "2023-07-03T21:03:28Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [July 3, 2023, 9:19pm UTC](https://community.mp3tag.de/t/case-conversion-for-all-following/61465/2 "2023-07-03T21:19:15Z")
In that action you have to set the characters that determine a word boundary. In your case you have to add the opening bracket. To apply such an action to \_ALL is a rather dangerous undertaking. I doubt that the function has changed in the recent versions. See a similar case here: > [@Action: Case Conversion • Unexpected Results](https://community.mp3tag.de/t/action-case-conversion-unexpected-results/41853): > > Mp3tag v2.88a I created a Case Conversion Action, with which to capitalize the first letter of a word following a hyphen. Example: Bird-in-hand which should change to Bird-In-Hand once the action is applied. Action configuration: Field: \_ALL Case conversion: Mixed Case Words begin from..: - (hyphen) When applied, this action leads, thus far, to the following unexpected, undesirable results: Example, in the Artist Field, containing zero hyphens: MacNeal will transform to Macneal. … --- _[View the full topic](https://community.mp3tag.de/t/case-conversion-for-all-following/61465)._