Hi,
thanks for the report … I have checked it and I can confirm it (also with the new AIRAC 2107 which will released today). I will try to analyze this in the next couple of hours/days and will inform you here about the outcome. Possible we build a second revision of 2107, when this is really a parser issue (and I´m honest, it looks so but I´m still not 100% sure).
Again, thanks for your report and your details. Much appreciated … I will let open this topic, till it´s solved