# V3.34.1 sudden fail to represent Japanese characters, fix reverting to 3.33.11

**URL:** https://community.mp3tag.de/t/v3-34-1-sudden-fail-to-represent-japanese-characters-fix-reverting-to-3-33-11/71399
**Category:** Support
**Created:** [June 4, 2026, 4:07am UTC](https://community.mp3tag.de/t/v3-34-1-sudden-fail-to-represent-japanese-characters-fix-reverting-to-3-33-11/71399 "2026-06-04T04:07:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![JCarlosJA](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jcarlosja/32/22943_2.png) [@JCarlosJA](https://community.mp3tag.de/u/JCarlosJA)
#### Post date: [June 4, 2026, 4:07am UTC](https://community.mp3tag.de/t/v3-34-1-sudden-fail-to-represent-japanese-characters-fix-reverting-to-3-33-11/71399/1 "2026-06-04T04:07:51Z")

</div>

I just removed v3.34.1 that today just fail to represent Japanese characters. Showing only little bixes - simillar to checkout boxes.

I tried opening files updated before this crash abd 33.34.1 still fail. When any other app on win was playing the mp3 files and showing the actual characters properly.

Hence I remove 3.34.1 + erased the folder at c program files. And then re installed prion

ver for winx64 3.33.1 modifying the folder path with extra characters and that works fine perfectly

Hope you can look at what happened with latest version, that for some unknown resons got crazy and no longer use/read proper character set (whatever the ascii ANSI or any othe5 else char set table code that should be using to represe t foreign languajes - but 3.34.1 just lost it.

And please consider that this to allow cop/paste text ... i dobt care about translating in-line to show both occidental translation and at right side the traducion and locale charset (if you can have that all solved will be ezxeñent, meanwhile i just sesrch the web translate and copy/paste for now)

 ![20260603_180628](https://community.mp3tag.de/uploads/default/original/3X/5/6/568c85ba6829f78ebb2948336c751aca88845728.jpeg)

---

<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: [June 4, 2026, 4:13am UTC](https://community.mp3tag.de/t/v3-34-1-sudden-fail-to-represent-japanese-characters-fix-reverting-to-3-33-11/71399/2 "2026-06-04T04:13:14Z")

</div>

The screenshots seem to show different files. Can you try with the same file instead?

---

<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: [June 5, 2026, 8:37am UTC](https://community.mp3tag.de/t/v3-34-1-sudden-fail-to-represent-japanese-characters-fix-reverting-to-3-33-11/71399/3 "2026-06-05T08:37:41Z")

</div>

Please see this topic for a possible explanation (unrelated to v3.34.1).

> [@Mp3tag displays ballot boxes instead of Japanese characters](https://community.mp3tag.de/t/mp3tag-displays-ballot-boxes-instead-of-japanese-characters/19408/2):
>
> I've moved your post to a dedicated topic — it seems to be a separate issue. Mp3tag reads Unicode characters as long as they are encoded in Unicode (UTF-8 or UTF-16 LE/BE). However, some tags are stored in the system codepage of the locale, which makes it difficult to impossible to read. Are you using Mp3tag on Windows or are you using the Wine-based macOS version? Could you provide an example file which shows this behavior (preferable via private email)? Kind regards – Florian

* * *

Moving to #Support as there is currently too much information missing to qualify as a bug report.

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [July 3, 2026, 8:38am UTC](https://community.mp3tag.de/t/v3-34-1-sudden-fail-to-represent-japanese-characters-fix-reverting-to-3-33-11/71399/4 "2026-07-03T08:38:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
