|
Encoding
Sept 15, 2016 20:18:06 GMT -5
via mobile
Post by Thomas on Sept 15, 2016 20:18:06 GMT -5
Please add support for EUC-KR encoding
|
|
|
Post by GoneMAD on Sept 16, 2016 10:26:09 GMT -5
UTF8 & ISO 8859-1 are the only formats gmmp's tagging library supports. Feel free to request the feature to taglib.github.io/The spec also doesnt support anything else en.wikipedia.org/wiki/ID3#ID3v2Textual frames are marked with an encoding byte.[8] $00 – ISO-8859-1 (LATIN-1, Identical to ASCII for values smaller than 0x80). $01 – UCS-2 (UTF-16 encoded Unicode with BOM), in ID3v2.2 and ID3v2.3. $02 – UTF-16BE encoded Unicode without BOM, in ID3v2.4. $03 – UTF-8 encoded Unicode, in ID3v2.4. id3.org/id3v2.3.0#ID3v2_frame_overviewA tag must contain at least one frame. A frame must be at least 1 byte big, excluding the header. If nothing else is said a string is represented as ISO-8859-1 characters in the range $20 - $FF. Such strings are represented as <text string>, or <full text string> if newlines are allowed, in the frame descriptions. All Unicode strings use 16-bit unicode 2.0 (ISO/IEC 10646-1:1993, UCS-2). Unicode strings must begin with the Unicode BOM ($FF FE or $FE FF) to identify the byte order. All numeric strings and URLs are always encoded as ISO-8859-1. Terminated strings are terminated with $00 if encoded with ISO-8859-1 and $00 00 if encoded as unicode. If nothing else is said newline character is forbidden. In ISO-8859-1 a new line is represented, when allowed, with $0A only. Frames that allow different types of text encoding have a text encoding description byte directly after the frame size. If ISO-8859-1 is used this byte should be $00, if Unicode is used it should be $01. Strings dependent on encoding is represented as <text string according to encoding>, or <full text string according to encoding> if newlines are allowed. Any empty Unicode strings which are NULL-terminated may have the Unicode BOM followed by a Unicode NULL ($FF FE 00 00 or $FE FF 00 00).
|
|
|
Encoding
Mar 1, 2017 23:21:21 GMT -5
via mobile
Post by buratei on Mar 1, 2017 23:21:21 GMT -5
utf-8 does it for me, except it is only applicable to the playlists tab; the queue tab has no provision to alter active codepage unless I missed it. Any chance you might add one?
|
|
|
Post by GoneMAD on Mar 2, 2017 8:16:16 GMT -5
you will want to use a tagger to get your tags encoded in UTF8 (or ISO-8859-1 which is a subset), delete the database, and then rescan. mp3tag is a good tagger for the pc.
The tag reading library gmmp uses (and specs) only support those encodings
|
|