Thank you for the feedback. I wasn’t sure whether this option would also have an effect on ALAC.
This is an important information.
In the quoted (german) thread Torben writes a little later:
Translation using a tool:
If the date value only consists of a four-digit number, this is interpreted as the year and the field is renamed “Year” during import.
If the value contains a four-digit number, this is interpreted as a year and copied into the year field, the date field remains untouched. This works for entries such as “2010-07-19” as well as “19.07.2010” or (according to ISO 8601) “20100719” (because the regular expression finds the first occurrence of the four-digit number, i.e. 2010 at the very beginning of the string).
I think this part of the code also had an effect on ALAC.