Ko van der Sloot

But the fix isn't released, so I wonder if that helps @martinreynaert using LaMachine?

I am quite sure this is NOT solved completely yet. Given this file: [incorrect.txt](https://github.com/proycon/folia/files/6574117/incorrect.txt) I really think foliavalidator is wrong here: > foliavalidator incorrect.txt VALIDATION ERROR on full parse by...

Addition: I tried to rename the ```` node to ````. Which I thought might solve the problem, but then: ``` > foliavalidator notsilly.xml VALIDATION ERROR on full parse by library...

> That's a legit error, Original can only come with New, not with Current (Current (and New) can come with Suggestion). Ok, I will add this limitation to libfolia too.

> Ok, I will add this limitation to libfolia too. Done. Needed quite a bit of rework, unfortunately

Still, I assume something is wrong. see: [special.txt](https://github.com/proycon/folia/files/6596796/special.txt) Here the (unlogical) correction from class="current" to class="Ticcl" is made. I still assume the FoLiA is correct, but foliavalidator rejects it. folialint...

I'm not sure about the Python implementation, but libfolia checks the text for every textclass in the document. So in this case both the implicit "current" and "Ticcl".

Thanks for the long story. There is a lot to say about this subject. I think this is not the most convenient platform to discus all, but a few remarks:...

This sounds feasible. having "current" as the default means that older documents are still valid. (or weren't in the first place)

Ans I assume that the default for defaultclass is currentclass (or VV)