Maarten van Gompel
Maarten van Gompel
yeah, foliapy does the same
This is a complicated issue that we need to address properly, so I'll type it out in full also for my own image forming. I think we're close to one...
The fact that "current" is a predefined class, unlike any in FoLiA, has always be a bit inelegant indeed. Some mechanism to let the user determine the name of the...
I'm doing some initial thinking on this, and I'd say adding "defaulttextclass" and "currenttextclass" attributes to the ```` declaration might accommodate the suggested enhancement: ```xml ``` I'm deliberately splitting the...
Or perhaps ``defaultclass`` and ``currentclass`` as it gets unnecessarily long otherwise.
Most sets in the official documentation are fictitious (i.e. they don't exist), should be clearly marked in the documentation too. I don't think anybody ever made a proper co-reference set...
These are good points to think about indeed. > especially older document don't always have a version number. > This is forbidden since 1.5 (@proycon am i right?) but all...
Hmm right, that is indeed a very important point. I wonder if I keep the version at 1.4 then for those older documents, I'd have to check.
I added some compatibility for serialisation of v1 to foliapy (a ``keepversion`` parameter on Document instantiation), but it remains limited, but hopefully enough for the transition period. Most important is...