# Change to Tag-Filename validation?

**URL:** https://community.mp3tag.de/t/change-to-tag-filename-validation/8938
**Category:** Support
**Created:** [September 12, 2009, 11:45pm UTC](https://community.mp3tag.de/t/change-to-tag-filename-validation/8938 "2009-09-12T23:45:33Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [September 13, 2009, 6:47pm UTC](https://community.mp3tag.de/t/change-to-tag-filename-validation/8938/3 "2009-09-13T18:47:39Z")

</div>

OK, I guess this is a change, perhaps from [[F] $validate() broken?](https://community.mp3tag.de/t/8311/11) .

Florian, I can see any fix is going to be potentially problematic since it will break compatibility of some usages.

Personally, I would like the inconsistency be fixed and the fix be in favour of the %_length% case i.e. invalid chars be replaced by "_", this being a change to the behavour in e.g. the case of the literal "02:13", previously replaced by "02:13" now to be replaced by "02\_13". It seems to me as if this means the results would be identical as from $validate(,"_"), but for avoidance of doubt I would like the result to be defined as identical as from $validate(,"_") i.e. replaces all /?\*"\<\>|: with \_ .

But please if any other users will suffer from the incompatibility, please do say what you prefer. I am sure Florian will listen, as always!

---

_[View the full topic](https://community.mp3tag.de/t/change-to-tag-filename-validation/8938)._