Jan Niestadt

I think it's probably best to always keep including the extra closing token, so all annotations have the same doc length. If the punct and tag annotations are always one...

I'm not sure what you mean by stream. It is already possible to request part of the XML (it will cut at the specified word boundary and make sure the...

Ok, I see. We used to do that, but that caused problems if an error occurred halfway through generating the response. That would have to be taken into account when...

I see the error is printed on the console, so it's not a problem for local debugging. But users working on lexonomy.eu will still appreciate the feedback.

On second thought, this issue is probably easy enough for me and/or my colleague Koen to pick up, so @michmech can work on other stuff.

Using the adjustDocSpec feature, you can already control what widget ("asker") Xonomy uses for an element. E.g. to use a single-line field for 'headword': ```javascript { adjustDocSpec: function (docSpec) {...

A better way to customize the docSpec without writing code would probably be to allow the "customize entry editor" JS to contain a docSpec-like structure, and merge that with the...

The locking solution chosen should also take shared subentries into account. Suppose a subentry S is shared by entries A, B and C. If I understand correctly how sharing subentries...

After discussing with @KCMertens, this probably works correctly, but only because the list of group names is shared between `HitQueryContext` and `CapturedGroupsImpl`. We should consider refactoring this so it's a...

(comment in `doc/index-formats/integrated.md`:) A reasonable approach could be to take a chunk from the middle of the first file added (middle to increase the chance we're inside actual text, not...