Maarten van Gompel
Maarten van Gompel
You're saying it is not finding a common ancestor if you call ``add()`` with an explicit ``set=`` keyword argument? If there are multiple sets then it should raise an exception...
Well, if you the get the *no common ancestor error* if you omit ``set``, then I still count that as a bug as the error should be clearer.
Yes, it is valid indeed. I agree it would be nicer when it's homogenous but I don't think we can/should enforce that in FoLiA itself, if tools like ucto/frog pose...
> After converting a document from docx to FoLiA using Piereling (@proycon: I did not find a command line option for such a conversion), Right, Piereling first invokes pandoc to...
The fact that ucto encodes the language in the set name is indeed not something to rely on, as it's just a convention of ucto itself. I suppose it can...
What's wrong? I took the alpino input from https://urd2.let.rug.nl/~vannoord/tmp/alp1570112479.7599921zo8y5csv.xml and after conversion I get https://download.anaproy.nl/alp.folia.xml . I didn't verify all the dependency pairs but on first look it seems fairly...
> Remark: I was surprised by this feature: > If multiple input files are specified, and/or the output FoLiA document already exists, then the converter will append it. > Especially...
1. Good point, this is indeed not intentional and should be disallowed. 2. We could define a set, implement some support for it in the libraries, and recommend its usage....
Generally we have the TEXTCONTAINER property for this. ACCEPTED_DATA only carries FoLiA elements in my implementations.