# Replacement Characters mp3Tag Mac v1.0.1

**URL:** <https://community.mp3tag.de/t/replacement-characters-mp3tag-mac-v1-0-1/52151>\
**Category:** Mac\
**Created:** [February 27, 2021, 12:58pm UTC](https://community.mp3tag.de/t/replacement-characters-mp3tag-mac-v1-0-1/52151 "2021-02-27T12:58:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [February 27, 2021, 1:05pm UTC](https://community.mp3tag.de/t/replacement-characters-mp3tag-mac-v1-0-1/52151/2 "2021-02-27T13:05:53Z")

</div>

Thanks for your feedback and your support!

It's always best to raise any concerns as early as possible — there is often a large group of others waiting for one to make the first move 😃

I've described what I'm doing and why in this post. I think it makes sense, but I'd love to hear your opinion on that:

> [@Replace Function Not Working?](https://community.mp3tag.de/t/replace-function-not-working/52094/2):
>
> Many thanks for your feedback — happy you like it! Your probably observing this in the context of renaming files. I've made some subtle changes on how special characters are treated with the Mac version: Invalid characters are automagically replaced by an underscore on field access, and by that, circumvents what I call the "AC/DC"-Problem. In the past, renaming with fields that contained a path separator char — it's the forward slash on macOS — would result in unwanted folders being greated, e…

---

_[View the full topic](https://community.mp3tag.de/t/replacement-characters-mp3tag-mac-v1-0-1/52151)._