SUJET :

According to webtrees.net/blog/2022/04/20/new-webtrees-release-2-1.0.html the values will be written in uppercase. This is fully compatible with GEDCOM 5.5.1.

I tested this uppercase values and when the value for subtag ROLE is in uppercase webtrees 2.0.19 is not recognizing this value and is displaying this as it is entered. So the GEDCOM-file produced with 2.1 is not fully compatible with webtrees 2.0.x (at least 2.0.19)

This is likely to affect many other tags.

It would be a lot of effort to back-port this into the 2.0 branch, and a major change would bring a risk of introducing new bugs.

PHP 7.4 goes out of support in 6 months, and so I don't plan to fix this.

Thanks for the replay.

No, i do not want you fix this in the 2.0.x branch.

My post was more about the information about this behavior - and I posted this in "Open discussion" and not in Help for 2.1 or on the GitHub.

And it was perhaps a polite way to ask whether the decission about using uppercase and introducing a data incompatibility betwen 2.1 and earlier versions of webtrees was necessary. It is possible that also other applications will have a problem with this.
Support for GEDCOM 7.0 I see in a further future and I am sure there we will need a lot of other (and bigger) changes and Data-fixes.

I am not a roundtripper, and webtrees is my main application so I cann live with this without problems.