mpg123_add_string mpg123_add_substring mpg123_copy_string mpg123_enc_from_id3 mpg123_free_string mpg123_grow_string MPG123_ICY mpg123_icy mpg123_icy2utf8 MPG123_ID3 mpg123_id3 mpg123_id3_enc mpg123_init_string mpg123_meta_check MPG123_NEW_ICY MPG123_NEW_ID3 mpg123_resize_string mpg123_set_string mpg123_set_substring mpg123_store_utf8 mpg123_text_encoding

enum mpg123_text_encoding The mpg123 text encodings. This contains encodings we encounter in ID3 tags or ICY meta info. Enumerator: mpg123_text_unknown  Unkown encoding... mpg123_id3_encoding can return that on invalid codes. mpg123_text_utf8  UTF-8 mpg123_text_latin1  ISO-8859-1. Note that sometimes latin1 in ID3 is abused for totally different encodings. mpg123_text_icy  ICY metadata encoding, usually CP-1252 but we take it as UTF-8 if it qualifies as such. mpg123_text_cp1252  Really CP-1252 without any guessing. mpg123_text_utf16  Some UTF-16 encoding. The last of a set of leading BOMs (byte order mark) rules. When there is no BOM, big endian ordering is used. Note that UCS-2 qualifies as UTF-8 when you don't mess with the reserved code points. If you want to decode little endian data without BOM you need to prepend 0xff 0xfe yourself. mpg123_text_utf16bom  Just an alias for UTF-16, ID3v2 has this as distinct code. mpg123_text_utf16be  Another alias for UTF16 from ID3v2. Note, that, because of the mess that is reality, BOMs are used if encountered. There really is not much distinction between the UTF16 types for mpg123 One exception: Since this is seen in ID3v2 tags, leading null bytes are skipped for all other UTF16 types (we expect a BOM before real data there), not so for utf16be! mpg123_text_max  Placeholder for the maximum encoding value. Definition at line 789 of file mpg123.h. { mpg123_text_unknown = 0 ,mpg123_text_utf8 = 1 ,mpg123_text_latin1 = 2 ,mpg123_text_icy = 3 ,mpg123_text_cp1252 = 4 ,mpg123_text_utf16 = 5 ,mpg123_text_utf16bom = 6 ,mpg123_text_utf16be = 7 ,mpg123_text_max = 7 };