# Action: Case Conversion • Unexpected Results

**URL:** <https://community.mp3tag.de/t/action-case-conversion-unexpected-results/41853>\
**Category:** Support\
**Created:** [June 1, 2018, 10:53am UTC](https://community.mp3tag.de/t/action-case-conversion-unexpected-results/41853 "2018-06-01T10:53:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ragtag](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ragtag/32/13146_2.png) [@ragtag](https://community.mp3tag.de/u/ragtag)\
**Post date:** [June 1, 2018, 2:03pm UTC](https://community.mp3tag.de/t/action-case-conversion-unexpected-results/41853/3 "2018-06-01T14:03:05Z")

</div>

Thank you for your explanation Ohrenkino. I think I understand the get the gist of it now. I had thought that when boundary is specified for this particular action, it will apply to the words containing the boundary only, i.e. the hyphen in this case. I expected anything else to be left alone.

Initially, I posted this topic:

[Expression Needed to Change Hyphenated Word Capitalisation](https://community.mp3tag.de/t/expression-needed-to-change-hyphenated-word-capitalisation/41689).

Is it not preferable then, to use a regular expression to take care of hyphenated words- one which will not touch anything else but hyphenated words- rather than setting up and applying an elaborate Case Conversion action to take care of all possible scenarios? Would you please help with that?

---

_[View the full topic](https://community.mp3tag.de/t/action-case-conversion-unexpected-results/41853)._