Language code XXX not xxx in Custom Comments Frames

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Language code XXX not xxx in Custom Comments Frames

Re: Language code XXX not xxx in Custom Comments Frames

by cdemeillon » Sat Aug 08, 2020 11:11 pm

Understood, and you are correct, but the id3v2.3/4 standard specifies that language codes should be represented ISO-639-2 three character language codes (id3_dot_org/d3v2.3.0 see the third last paragraph of point 3.3), which in turn recommends language codes to be lowercase, though they should be considered case-insensitive (www.loc_dot_gov/standards/iso639-2/faq.html#21), so technically uppercase should be OK but practically it would be more compatible with other software if it was lowercase, just like the ISO-639-2 list itself.
in fact, using und (undetermined) might actually be the most correct approach as XXX is not a valid language code?

That's just my two cents worth, I understand that changing it is complex and brings with it a host of challenges...

Re: Language code XXX not xxx in Custom Comments Frames

by Peke » Sun May 10, 2020 9:21 pm

Hi,
they should not be case sensitive. From my tests MM recognize both.

Language code XXX not xxx in Custom Comments Frames

by cdemeillon » Sun May 10, 2020 2:54 pm

I have seen a few topics on the XXX language code used on the Custom Fields COMM frames.
Whilst I understand the reasoning behind using XXX, would it be possible to use lower case letters xxx instead, as uppercase letters are not compliant?

Top