SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

TIPL revisited

Following up to this thread from a few years ago,
http://jthink.net/jaikozforum/posts/list/4509.page

I’m still having issues with TIPL fields when they are encoded UTF-16.

TIPL is a string of NULL seperated values. Jaikoz writes a unicode BOM in front of every value. Whereas Helium writes only one BOM at the front of the string. When Jaikoz reads such a tag, all values but the first show up as chinese letters.

I think Jaikoz should read all values in a frame with the same byte order. I suspect this could be a problem for other text frames as well.

[quote]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.

[/quote]

Thanks

Right, not sure which application is wrong here but Ive raised https://jthink.atlassian.net/browse/JAIKOZ-994 for further consideration.