FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › does mt-daap support big5 Traditional Chinese id3 tag??
- This topic has 7 replies, 3 voices, and was last updated 18 years, 2 months ago by wilson_chan0913.
-
AuthorPosts
-
06/07/2006 at 10:28 AM #415wilson_chan0913Guest
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???
06/07/2006 at 2:26 PM #5434nivlacckwParticipantAs a Chinese myself having Traditional Chinese and Japanese songs,I believe unicode is prefered to support device like the Rokue Soundbridge.
07/07/2006 at 6:14 AM #5435wilson_chan0913GuestBut 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???
07/07/2006 at 9:09 AM #5436rpeddeParticipant@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
07/07/2006 at 9:49 AM #5437wilson_chan0913GuestSo, 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.
07/07/2006 at 9:17 PM #5438rpeddeParticipant@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
12/07/2006 at 1:22 AM #5439whsyuGuest@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.
20/07/2006 at 3:34 AM #5440wilson_chan0913Guestmany thanks for all your helps
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.