# \[F\] ID3v2.4 UTF-8 is not on specification

**URL:** https://community.mp3tag.de/t/f-id3v2-4-utf-8-is-not-on-specification/18396
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [November 4, 2016, 10:08am UTC](https://community.mp3tag.de/t/f-id3v2-4-utf-8-is-not-on-specification/18396 "2016-11-04T10:08:53Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![andryk](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/41988e/32.png) [@andryk](https://community.mp3tag.de/u/andryk)
#### Post date: [November 4, 2016, 10:08am UTC](https://community.mp3tag.de/t/f-id3v2-4-utf-8-is-not-on-specification/18396/1 "2016-11-04T10:08:53Z")

</div>

[id3.org](http://id3.org) says ID3v2.4 spec in [this page](http://id3.org/id3v2.4.0-structure)

> [@](#):
>
> Frames that allow different types of text encoding contains a text  
> encoding description byte. Possible encodings:
> 
> ```
> $00 ISO-8859-1 [ISO-8859-1]. Terminated with $00.
> $01 UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All
> strings in the same frame SHALL have the same byteorder.
> Terminated with $00 00.
> $02 UTF-16BE [UTF-16] encoded Unicode [UNICODE] without BOM.
> Terminated with $00 00.
> $03 UTF-8 [UTF-8] encoded Unicode [UNICODE]. Terminated with $00.
> 
> ```

 ![](https://community.mp3tag.de/uploads/default/original/2X/3/3b3f5cc27d974591f08848a05fa5e53bf2ee0fd4.png)  

this image shows binary code of a file edited by mp3tag v2.79.  
Address 0x2F is end of TALB UTF-8 data however the data not terminated with $00,  
continuing next TPE1 UTF-8 data without terminating.

sorry for bad English.

 ![](https://community.mp3tag.de/uploads/default/original/2X/3/3b3f5cc27d974591f08848a05fa5e53bf2ee0fd4.png)

---

<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 5, 2016, 9:12am UTC](https://community.mp3tag.de/t/f-id3v2-4-utf-8-is-not-on-specification/18396/2 "2016-12-05T09:12:09Z")

</div>

The reported issue is now fixed with the current [Development Build (Mp3tag v2.80a)](http://developer.mp3tag.de). It actually applied not only to UTF-8, but also to ISO-8859-1 and UTF-16.

As with all those low-level changes, it would be great if you (and possibly others) can analyze the new implementation and confirm the fix.

Thanks for reporting!

Kind regards  
– Florian

---

<div class="post-metadata">

### Author: ![andryk](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/41988e/32.png) [@andryk](https://community.mp3tag.de/u/andryk)
#### Post date: [December 6, 2016, 6:22am UTC](https://community.mp3tag.de/t/f-id3v2-4-utf-8-is-not-on-specification/18396/3 "2016-12-06T06:22:49Z")

</div>

I confirmed $00 exists properly in frames with UTF-8, UTF-16, ISO-8859-1. Now it's on spec.  
Thank you very much!

---

<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:08pm UTC](https://community.mp3tag.de/t/f-id3v2-4-utf-8-is-not-on-specification/18396/4 "2018-12-28T14:08:57Z")

</div>

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