# Display Codepage
**URL:** https://community.mp3tag.de/t/display-codepage/68398
**Category:** Support
**Created:** [May 4, 2025, 1:12pm UTC](https://community.mp3tag.de/t/display-codepage/68398 "2025-05-04T13:12:13Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@HerrMerkt](https://community.mp3tag.de/u/HerrMerkt)
#### Post date: [May 4, 2025, 1:12pm UTC](https://community.mp3tag.de/t/display-codepage/68398/1 "2025-05-04T13:12:13Z")
I have some issues with "Ä", "Ö" and "Ü" in some song titles and I think I found a way to resolve it using "actions" and "change codepage", followed by replacing some characters. Now, I would like to apply this routine to the files that are affected. Is there any way to display the current codepage in MP3Tag or which other software should I use.
Further, I was wondering if there are any other characters affected?
Addition: The characters are displayed correctly in any codepage, but I have issues with Synology Cloud Sync which seems to ignore some codepages. Therefore, I do not know which files are affected.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [May 4, 2025, 1:20pm UTC](https://community.mp3tag.de/t/display-codepage/68398/2 "2025-05-04T13:20:26Z")
Only MP3 ID3V2.3 tags could be written with ISO-8859-1 encoding.
You could create a column with the
Value: %\_id3v2\_character\_encoding%
and sort by it.
Or a filter might work
NOT %\_id3v2\_character\_encoding% HAS UTF
---
### Author:  [@HerrMerkt](https://community.mp3tag.de/u/HerrMerkt)
#### Post date: [May 4, 2025, 1:39pm UTC](https://community.mp3tag.de/t/display-codepage/68398/3 "2025-05-04T13:39:22Z")
The file is in UTF-16 before and after changing the codepage. Before I apply my action, the Ä translates to A¨, but after changing codepage to German and replacing these two characters with Ä, it is displayed as Ä. So there probably is another issue.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [May 4, 2025, 1:41pm UTC](https://community.mp3tag.de/t/display-codepage/68398/4 "2025-05-04T13:41:34Z")
UTF-16 is the up-to-date format.
But it could be that in former times another player or tagger could not cope with such characters and wrote garbage back into the files.
---
### Author:  [@HerrMerkt](https://community.mp3tag.de/u/HerrMerkt)
#### Post date: [May 4, 2025, 1:44pm UTC](https://community.mp3tag.de/t/display-codepage/68398/5 "2025-05-04T13:44:52Z")
That's possible. I don't have issues with MusicBee or Plex, but my Synology NAS won't backup files including this garbage in the filenames to the cloud. Therefore, I need to replace it. My filenames are created based on the tags, so I need to get rid of this garbage in the tags.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [May 4, 2025, 2:00pm UTC](https://community.mp3tag.de/t/display-codepage/68398/6 "2025-05-04T14:00:18Z")
If you have a unifiying pattern to create filenames from tags, then it might be easiest to apply that pattern to all files again.
Admittedly, that is a brute force approach but probably the safest.
---
### Author:  [@HerrMerkt](https://community.mp3tag.de/u/HerrMerkt)
#### Post date: [May 4, 2025, 2:13pm UTC](https://community.mp3tag.de/t/display-codepage/68398/7 "2025-05-04T14:13:27Z")
It won't work before I apply my action to change codepage. It will write the oddly coded "umlauts" to the folder and file names. And I don't want to apply this to 300000 files. So I need to find the affected files.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [May 4, 2025, 2:28pm UTC](https://community.mp3tag.de/t/display-codepage/68398/8 "2025-05-04T14:28:50Z")
It could be possible to copy the strange characters one ofter the other and use each them to filter for such files.
If you simply enter the copied character(s) in the filter box, then you see all the files that have that character somewhere in the data.
It would be an iterative process, though.
Or if you could find out whether the trailing character
> [@HerrMerkt](#):
>
> A¨
following the "A" and all the other garbage characters has always the same character code, then you could filter for that.
---
### Author:  [@HerrMerkt](https://community.mp3tag.de/u/HerrMerkt)
#### Post date: [May 4, 2025, 8:15pm UTC](https://community.mp3tag.de/t/display-codepage/68398/9 "2025-05-04T20:15:22Z")
I fixed it with the filter option, but I had to enter the strange Ä, Ö and Ü as the filter. It didn't even mess up my files. I will run this action per default from now on. Thank you for your support.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [June 3, 2025, 8:16pm UTC](https://community.mp3tag.de/t/display-codepage/68398/10 "2025-06-03T20:16:08Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.