Github project: https://github.com/yumeyao/android_p..._frameworks_av
AOSP Issue ticket: https://code.google.com/p/android/is...etail?id=81428
Symptom:
Tags that contain unicode characters(Japanese/Chinese/Korean, or the accent symbol used in words like it's I'm) are not always displayed correctly in Android
Reason:
The Principle:
Following the standard (which defines what text-encoding of tags is used in a format) will make people who also follow the standard *never in trouble*, and will warn/remind those who don't so that *they can be satisfied after changing the tags manually with right-doing applications*. The behavior is predictable.
Trying to be 'smart' will only hurt in the way that no one will always be satisfied. And once a problem occurs, there is even no simple way to fix it.
Progress & How you can help:
Github issue ticket: https://github.com/yumeyao/android_p...ks_av/issues/2
You can help identify the 'standard' of the formats I haven't looked into by following the instructions on github or by simply replying here.
You can also contribute to the code directly and open pull requests.
AOSP Issue ticket: https://code.google.com/p/android/is...etail?id=81428
Symptom:
Tags that contain unicode characters(Japanese/Chinese/Korean, or the accent symbol used in words like it's I'm) are not always displayed correctly in Android
Reason:
Quote:
|
Android Media Service always tries detecting the text-encoding of metadata(tags). There is some sense doing this for legacy formats like MP3, however the more commonly used way in this case is using the 'native encoding' according to the current locale. In contrast to the legacy MP3, for any advanced formats like OGG/AAC(M4A), or even MP3 with ID3v2, there is no reason to auto-detect the text-encoding and doing so only hurts if the detection fails, because the text-encoding is either defined as unicode in the format standard(M4A/OGG, always UTF-8) or user-specific(ID3v2, not commonly used but it's allowed according to the format specificaion). Therefore my media library is messed up with mojibake because I listen a lot to Japanese pops. One thing makes me laugh most is our 'smartest' Android media service misinterprets the text-encoding in one field but interprets it correctly in another field for the exactly same text (in cases of song title/album title being same). |
Following the standard (which defines what text-encoding of tags is used in a format) will make people who also follow the standard *never in trouble*, and will warn/remind those who don't so that *they can be satisfied after changing the tags manually with right-doing applications*. The behavior is predictable.
Trying to be 'smart' will only hurt in the way that no one will always be satisfied. And once a problem occurs, there is even no simple way to fix it.
Progress & How you can help:
Github issue ticket: https://github.com/yumeyao/android_p...ks_av/issues/2
You can help identify the 'standard' of the formats I haven't looked into by following the instructions on github or by simply replying here.
You can also contribute to the code directly and open pull requests.