# Wrong parsing the German letter "ß" and the French "é", "î" **URL:** \ **Category:** Support\ **Tags:** player\ **Created:** [November 8, 2026, 5:24pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051 "2026-11-08T17:24:21Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![squonk57](https://community.mp3tag.de/user_avatar/community.mp3tag.de/squonk57/32/23812_2.png) [@squonk57](https://community.mp3tag.de/u/squonk57)\ **Post date:** [November 9, 2026, 12:31am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/21 "2026-11-09T00:31:54Z")
> [@Sergius](#): > > By any chance, do you have an opinion on the issue related to this "ß" character that @MikeB mentioned in his text above? What @Florian said. An "ß" showing up as "ß" is exactly what happens when UTF-8 data is erroneously interpreted as ISO-8859-1/windows-1252. Likewise, an UTF-8 "é" would appear as "é". In the Apple/Windows case, an "é" should show up as an unaccented "e", followed by one or two garbage characters for the unrecognized acute. ---
**Author:** ![Sergius](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/s/ebca7d/32.png) [@Sergius](https://community.mp3tag.de/u/Sergius)\ **Post date:** [November 9, 2026, 1:26am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/22 "2026-11-09T01:26:06Z")
> [@squonk57](#): > > > [@Sergius](#): > > > > By any chance, do you have an opinion on the issue related to this "ß" character that @MikeB mentioned in his text above? > > What @Florian said. An "ß" showing up as "ß" is exactly what happens when UTF-8 data is erroneously interpreted as ISO-8859-1/windows-1252. Likewise, an UTF-8 "é" would appear as "é". Thank you, @squonk57, for the reminder. It is true that Florian provided an excellent explanation... I should have been more precise in my question. Let me rephrase: Given everything that has been discussed on this topic, does anyone have any ideas on how to help resolve the issue involving the "ß" character, which @MikeB mentioned in his post above? ---
**Author:** ![squonk57](https://community.mp3tag.de/user_avatar/community.mp3tag.de/squonk57/32/23812_2.png) [@squonk57](https://community.mp3tag.de/u/squonk57)\ **Post date:** [November 9, 2026, 6:16am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/23 "2026-11-09T06:16:49Z")
I'm sorry, but you lost me here. Florian suggested a solution (use a different encoding, not UTF-8), and in the next post MikeB confirmed that it worked. What other problem do you mean? ---
**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\ **Post date:** [November 9, 2026, 6:44am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/24 "2026-11-09T06:44:28Z")
> [@MikeB](#): > > But my question: why doesn't this issue happen to other tracks with the same characters, like `L'été indien`? The title `L'été indien` contains the special character `é`. However, this doesn't necessarily mean that the file uses UTF-8 encoding. The same character can be encoded in different ways: | Encoding | Representation of `é` | | --- | --- | | ISO-8859-1 | One byte: `E9` | | UTF-8 | Two bytes: `C3 A9` | | UTF-16 | Two bytes: `00 E9` (Big Endian) | An older MP3 player might therefore display `é` correctly if it is encoded using ISO-8859-1, but fail when encountering the same character encoded in UTF-8. Hexeditor examples for the Tag write options: ![image](https://community.mp3tag.de/uploads/default/original/3X/0/6/066cf6e3b685c5e6f213de8c7592ca8cd22c6458.png) **ID3v2.3 - ISO-8859-1** ![image](https://community.mp3tag.de/uploads/default/original/3X/f/d/fd40d369b275de7b21b8ef4565a658cf9b29ab8d.png) **ID3v2.4 - UTF-8** ![image](https://community.mp3tag.de/uploads/default/original/3X/5/2/5228fe6e0f3c6e7d35497f4d9cf28338392c2381.png) **ID3v2.3 - UTF-16** ![image](https://community.mp3tag.de/uploads/default/original/3X/5/0/50afab2bcf4bc4321d17458ab05cdc1efe63f5e3.png) If you see this combination in a hex editor for `Ein kleiner weißer Schneemann` ![image](https://community.mp3tag.de/uploads/default/original/3X/9/7/97c5b0f54ff7346ea4e8bc52b5dab6605b6d80d5.png) the encoding used is ID3v2.3-UTF-8 (if written from Mp3tag). ![image](https://community.mp3tag.de/uploads/default/original/3X/f/a/fa3bafd6d5ccb2e4491fe0029669c0424d2361ef.png) ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 8:31am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/25 "2026-11-09T08:31:06Z")
> [@MikeB](#): > > I've tried multiple combinations and I've paid attention that perhaps the filling of `%album%` field or the next after `%title%` field might leads to the problem. But I still need to verify my assumption. I've played with different combinations of properties and succeeded to reach the case when the same MP3-files, under ID3-tag 2.4 filled by Mp3tag 3.37 by converting file name to tag have a proper track name and the wrong-one: ![id3](https://community.mp3tag.de/uploads/default/original/3X/a/5/a57746b950c4bc3a98baab6c701226aa17685bc2.jpeg) The only difference is the initial file name, from which the tag has been generated: - `La demoiselle de déshonneur.cool1.mp3` - correct - `La demoiselle de déshonneur.mp3` - wrong The conversion mask for both cases is `%title%`. I still have to narrow my assumptions but I believe, I'm on the right track to localize the bug! ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 8:50am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/26 "2026-11-09T08:50:04Z")
> [@MikeB](#): > > I still have to narrow my assumptions but I believe, I'm on the right track to localize the bug! Given the following set of file names: ![2026-11-09_094545](https://community.mp3tag.de/uploads/default/original/3X/4/8/486134480ad71b24c5f41691f561764142386ea6.png) Applying convert **Filename - Tag** , I get: ![id3_02](https://community.mp3tag.de/uploads/default/original/3X/9/7/97f6a16fde5289e01992d83190d7ac53d04e7d5b.jpeg) As we may see, the correctly parsed are files: - `La demoiselle de déshonneurb.mp3` - `La demoiselle de déshonneur.c.mp3` The rest have an issue. What's really strange for me, why is `La demoiselle de déshonneur.c.mp3` parsed properly, while `La demoiselle de déshonneur.a.mp3` does't. What does lead `.a` to be parsed wrongly, while `.c` is OK? Why the file name `La demoiselle de déshonneurb.mp3` parsed correctly, while `La demoiselle de déshonneur.mp3` doesn't? ---
**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\ **Post date:** [November 9, 2026, 9:03am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/27 "2026-11-09T09:03:24Z")
Copy & paste the filename that works directly from Windows File Explorer here: _(Press F2 in Windows File Explorer, Ctrl + C and in Babelstone press Ctrl + V)_ > **[What Unicode character is this ?](https://www.babelstone.co.uk/Unicode/whatisit.html)** (press the Identify-Button) Then copy & paste the name of the filename that doesn't work at Babelstone. What difference do you see? ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 9:14am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/28 "2026-11-09T09:14:32Z")
The correct filename (`La demoiselle de déshonneur.c`): > U+004C : LATIN CAPITAL LETTER L > U+0061 : LATIN SMALL LETTER A > U+0020 : SPACE [SP] > U+0064 : LATIN SMALL LETTER D > U+0065 : LATIN SMALL LETTER E > U+006D : LATIN SMALL LETTER M > U+006F : LATIN SMALL LETTER O > U+0069 : LATIN SMALL LETTER I > U+0073 : LATIN SMALL LETTER S > U+0065 : LATIN SMALL LETTER E > U+006C : LATIN SMALL LETTER L > U+006C : LATIN SMALL LETTER L > U+0065 : LATIN SMALL LETTER E > U+0020 : SPACE [SP] > U+0064 : LATIN SMALL LETTER D > U+0065 : LATIN SMALL LETTER E > U+0020 : SPACE [SP] > U+0064 : LATIN SMALL LETTER D > U+00E9 : LATIN SMALL LETTER E WITH ACUTE > U+0073 : LATIN SMALL LETTER S > U+0068 : LATIN SMALL LETTER H > U+006F : LATIN SMALL LETTER O > U+006E : LATIN SMALL LETTER N > U+006E : LATIN SMALL LETTER N > U+0065 : LATIN SMALL LETTER E > U+0075 : LATIN SMALL LETTER U > U+0072 : LATIN SMALL LETTER R > U+002E : FULL STOP {period, dot, decimal point} > U+0063 : LATIN SMALL LETTER C The wrong filename (`La demoiselle de déshonneur.a`) > U+004C : LATIN CAPITAL LETTER L > U+0061 : LATIN SMALL LETTER A > U+0020 : SPACE [SP] > U+0064 : LATIN SMALL LETTER D > U+0065 : LATIN SMALL LETTER E > U+006D : LATIN SMALL LETTER M > U+006F : LATIN SMALL LETTER O > U+0069 : LATIN SMALL LETTER I > U+0073 : LATIN SMALL LETTER S > U+0065 : LATIN SMALL LETTER E > U+006C : LATIN SMALL LETTER L > U+006C : LATIN SMALL LETTER L > U+0065 : LATIN SMALL LETTER E > U+0020 : SPACE [SP] > U+0064 : LATIN SMALL LETTER D > U+0065 : LATIN SMALL LETTER E > U+0020 : SPACE [SP] > U+0064 : LATIN SMALL LETTER D > U+00E9 : LATIN SMALL LETTER E WITH ACUTE > U+0073 : LATIN SMALL LETTER S > U+0068 : LATIN SMALL LETTER H > U+006F : LATIN SMALL LETTER O > U+006E : LATIN SMALL LETTER N > U+006E : LATIN SMALL LETTER N > U+0065 : LATIN SMALL LETTER E > U+0075 : LATIN SMALL LETTER U > U+0072 : LATIN SMALL LETTER R > U+002E : FULL STOP {period, dot, decimal point} > U+0061 : LATIN SMALL LETTER A So, from the file name point of view, there is no difference besides `U+0061 : LATIN SMALL LETTER A` at the end. ---
**Author:** ![squonk57](https://community.mp3tag.de/user_avatar/community.mp3tag.de/squonk57/32/23812_2.png) [@squonk57](https://community.mp3tag.de/u/squonk57)\ **Post date:** [November 9, 2026, 9:20am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/29 "2026-11-09T09:20:07Z")
> [@MikeB](#): > > Applying convert **Filename - Tag** , I get: > > ![id3_02](https://community.mp3tag.de/uploads/default/original/3X/9/7/97f6a16fde5289e01992d83190d7ac53d04e7d5b.jpeg) That's not what you get, that's what your player makes of it. 1. Read correctly 2. Read correctly 3. UTF-8 parsed as ISO-8859-1 4. UTF-8 parsed as ISO-8859-1 5. UTF-8 parsed as ISO-8859-2 ⁉ 6. UTF-8 parsed as ISO-8859-1 Please show screenshots from the extended tag panel in Mp3tag. ---
**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\ **Post date:** [November 9, 2026, 9:29am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/30 "2026-11-09T09:29:19Z")
> [@MikeB](#): > > U+00E9 : LATIN SMALL LETTER E WITH ACUTE Interesting, seems to be the same single character `é` (`E9`) in both cases (working / not working). ---
**Author:** ![AreDigg](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/bbe5ce/32.png) [@AreDigg](https://community.mp3tag.de/u/AreDigg)\ **Post date:** [November 9, 2026, 10:02am UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/31 "2026-11-09T10:02:02Z")
I think this is an Android bug, and they are heuristically trying to detect encoding rather than following the standard. Do you see this in other players as well? I think a few don’t use the default media store framework. ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 2:01pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/32 "2026-11-09T14:01:29Z")
> [@AreDigg](#): > > Do you see this in other players as well? I observe this issue in the following media players: - [Mi Music](https://play.google.com/store/apps/details?id=com.miui.player) - [Player FM](https://play.google.com/store/apps/details?id=fm.player) - Xiaomi Media viewer Android 16, HyperOS 3.0.302.0 ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 2:06pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/33 "2026-11-09T14:06:15Z")
> [@squonk57](#): > > Please show screenshots from the extended tag panel in Mp3tag. Correct: ![2026-11-09_150428](https://community.mp3tag.de/uploads/default/original/3X/c/4/c433a3ba14d98a62b537af74bcae03c61913d5cd.png) Broken: ![2026-11-09_150512](https://community.mp3tag.de/uploads/default/original/3X/5/9/591eb4ff7a3360d84a684f74c6c5b71d4004f4f7.png) ---
**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\ **Post date:** [November 9, 2026, 2:50pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/34 "2026-11-09T14:50:31Z")
If you look at the content in the last two mp3 files itself (correct/broken) with a hex editor, what exactly do you see as saved character for `é` in déshonneur? `E9` or `C3 A9` or `00 E9` ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 3:06pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/35 "2026-11-09T15:06:12Z")
> [@LyricsLover](#): > > hex editor In the correct file it's `C3 A9` in the broken it's also `C3 A9`. If you want, I can share these two files and you can run more detailed checks, maybe there are some side effects, which affect the broken file. ---
**Author:** ![squonk57](https://community.mp3tag.de/user_avatar/community.mp3tag.de/squonk57/32/23812_2.png) [@squonk57](https://community.mp3tag.de/u/squonk57)\ **Post date:** [November 9, 2026, 3:06pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/36 "2026-11-09T15:06:13Z")
> [@MikeB](#): > > Broken: > > ![2026-11-09_150512](https://community.mp3tag.de/uploads/default/original/3X/5/9/591eb4ff7a3360d84a684f74c6c5b71d4004f4f7.png) Well, apparently Mp3tag read the name correctly. Interesting blog post about Android and ID3 tags: > **[Android and Unicode ID3 tags](https://blog.valerauko.net/2017/07/16/android-and-unicode-id3-tags/)** > > For a while now I've been noticing that certain songs' ID3 tags are broken when played on my Android phone. I use Black Player which in turn uses the built in Android music libraries – but I've checked in a number of other players too just in case... ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 3:08pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/37 "2026-11-09T15:08:20Z")
> [@squonk57](#): > > Interesting blog post about Android and ID3 tags It's really interesting, although the post is almost 10 years old, so many thing could have changed since that time. ---
**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\ **Post date:** [November 9, 2026, 3:22pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/38 "2026-11-09T15:22:03Z")
> [@MikeB](#): > > In the correct file it's `C3 A9` in the broken it's also `C3 A9`. If both files - the correct one and the broken one - show the same content, that would suggest that the problem isn't with Mp3tag. Unfortunately, as I don't have access to your phone or Android player, nor do I use the same transfer process, I won't be able to help you solve this mystery despite having access to the shared files. ---
**Author:** ![AreDigg](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/bbe5ce/32.png) [@AreDigg](https://community.mp3tag.de/u/AreDigg)\ **Post date:** [November 9, 2026, 5:06pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/39 "2026-11-09T17:06:55Z")
> [@MikeB](#): > > I observe this issue in the following media players: Try with foobar2000, I think it uses its own library for reading. ---
**Author:** ![MikeB](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@MikeB](https://community.mp3tag.de/u/MikeB)\ **Post date:** [November 9, 2026, 5:16pm UTC](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051/40 "2026-11-09T17:16:30Z")
> [@AreDigg](#): > > Try with foobar2000, I think it uses its own library for reading. In this app, all tracks are displayed properly! [Previous page](https://community.mp3tag.de/t/wrong-parsing-the-german-letter-ss-and-the-french-e-i/72051.md?page=1)