# \[X\] v2.36 defaults to UTF-8, should be to UTF-16

**URL:** https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397
**Category:** No Bugs
**Created:** [June 3, 2006, 4:10am UTC](https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397 "2006-06-03T04:10:38Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![madbastd](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/82dd89/32.png) [@madbastd](https://community.mp3tag.de/u/madbastd)
#### Post date: [June 3, 2006, 4:10am UTC](https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397/1 "2006-06-03T04:10:38Z")

</div>

Under Options-\>Tags-\>Mpeg, the ID3v2 character coding in v2.35 defaulted to UTF-16. Upgrading to v2.36 changes the default to UTF-8. This causes a weird extra character to be displayed at the end of each field (Artist, Title, etc.) in iTunes.

I'm annoyed because this has taken me a couple of hours to sort out. I think the default should stay the same, namely UTF-16.

---

<div class="post-metadata">

### Author: ![Paz](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/p/22d042/32.png) [@Paz](https://community.mp3tag.de/u/Paz)
#### Post date: [June 3, 2006, 5:33am UTC](https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397/2 "2006-06-03T05:33:46Z")

</div>

It's an iTunes bug. That program doesn't fully support ID3v2.4 UTF-8 tags.  
I also got the square charachter at the end of each field. Wich was bugging bugging me too. For now we'll just have to use the ID3v2.3 UTF-16 option in this great program.  
Although it would have been nice to see the changed defaulted coding mentioned in the changelog.  
That would have saved you a (valuable I'm sure) couple of hours.

Salute, Paz

---

<div class="post-metadata">

### Author: ![dano](https://community.mp3tag.de/user_avatar/community.mp3tag.de/dano/32/6_2.png) [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [June 3, 2006, 6:32am UTC](https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397/3 "2006-06-03T06:32:51Z")

</div>

The change to UTF-8 is not intended, there's something going wrong.

---

<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 3, 2006, 6:55am UTC](https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397/4 "2006-06-03T06:55:48Z")

</div>

Mmm, seems like I've changed the default to ID3v2.4 UTF-8, but there's nothing I can do now.

Though this is not considered as a bug, since ID3v2.4 with UTF-8 are perfectly valid ID3v2 tags too.

---

<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 3, 2006, 1:13pm UTC](https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397/5 "2006-06-03T13:13:47Z")

</div>

I've changed the version on the server to default to ID3v2.3 with UTF-16. Maybe this will reduce the trouble for many people (including the support team 😉).

---

<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: [December 28, 2018, 2:16pm UTC](https://community.mp3tag.de/t/x-v2-36-defaults-to-utf-8-should-be-to-utf-16/3397/6 "2018-12-28T14:16:49Z")

</div>

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