You are here: Home » Topic » does mt-daap support big5 Traditional Chinese id3 tag??

does mt-daap support big5 Traditional Chinese id3 tag??

FireFly Media Server (formerly mt-daapd) Firefly Media Server Forums Firefly Media Server General Discussion does mt-daap support big5 Traditional Chinese id3 tag??

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #415
    wilson_chan0913
    Guest

    iTune can’t show the big5 chinese words within the tag, like artist, album and etc. But, if i convert the ID3 tag to unicode format by winamp, then it can show up correctly.So, seems that the id3 lib does not support big5 traditional chinese yet. If it is the situation, is there any plan to support it in the future???

    #5434
    nivlacckw
    Participant

    As a Chinese myself having Traditional Chinese and Japanese songs,I believe unicode is prefered to support device like the Rokue Soundbridge.

    #5435
    wilson_chan0913
    Guest

    But seems that ID3v1 doesn’t support Unicode, so if the mp3 tagged with ID3v1, could the Roku Soundbridge show the chinese or japanese words correctly???

    #5436
    rpedde
    Participant

    @wilson_chan0913 wrote:

    But seems that ID3v1 doesn’t support Unicode, so if the mp3 tagged with ID3v1, could the Roku Soundbridge show the chinese or japanese words correctly???

    No, if it were id3v1, then mt-daapd would think it was latin1, and show garbage for song info.

    On the other hand, if it is encoded as utf-8 or unicode by a proper tagger, mt-daapd reads it fine, and it displays fine on the soundbridge.

    — Ron

    #5437
    wilson_chan0913
    Guest

    So, we need to convert the tag info. of mp3 from big5 to utf8 or unicode no matter it is id3v1 or id3v2, right??? And now due to mt-daapd treated the big5 as latin1 and caused the gargabe song info showed in iTune client on PC.

    #5438
    rpedde
    Participant

    @wilson_chan0913 wrote:

    So, we need to convert the tag info. of mp3 from big5 to utf8 or unicode no matter it is id3v1 or id3v2, right??? And now due to mt-daapd treated the big5 as latin1 and caused the gargabe song info showed in iTune client on PC.

    id3v1 gets ignored if there are id3v2 tags. So you should be able to keep those as-is, and add id3v2 tags with the big5 data converted to unicode or utf-8.

    Try it on one, should work fine.

    — Ron

    #5439
    whsyu
    Guest

    @wilson_chan0913 wrote:

    So, we need to convert the tag info. of mp3 from big5 to utf8 or unicode no matter it is id3v1 or id3v2, right??? And now due to mt-daapd treated the big5 as latin1 and caused the gargabe song info showed in iTune client on PC.

    itunes/mac only supports unicode tags, however, itunes/win32 supports both big5 and unicode if you installed itunes in a traditional chinese winxp.

    You can use an itunes/win32 to “convert ID3 tags” to convert your id3 tags to unicode tags, because itunes automatically converts big5 tags to unicode tags when it changes id3 versions (ex. 2.3->2.4)

    If you change all your songs to 2.4 and then change back to 2.3, you can make sure that all your songs have id3v2.3 unicode tags.

    #5440
    wilson_chan0913
    Guest

    many thanks for all your helps

Viewing 8 posts - 1 through 8 (of 8 total)
  • The forum ‘General Discussion’ is closed to new topics and replies.