You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lanugage-specific readme files (like README-BA.md) contain links - most crucially to the handle of the source - one would expect those to also be links in the MD.
And since the README is basically an extensive description of the encoding process, should that not be included in the ParlaMint-BA.ana.xml file?
The text was updated successfully, but these errors were encountered:
OK, done; given that the corpora are being built now, some will not have this /unless I could re-run only README generation, but this is not implemented (yet)).
the README is basically an extensive description of the encoding process, should that not be included in the ParlaMint-BA.ana.xml file?
Indeed it should, but the "documentation" process was distinct from the encoding, incl. the teiHeader, alas.
In fact, it would be great if the README files were bulked up with more data from the teiHeaders as well as auto-derived stats on the corpus. Future again....
The lanugage-specific readme files (like README-BA.md) contain links - most crucially to the handle of the source - one would expect those to also be links in the MD.
And since the README is basically an extensive description of the encoding process, should that not be included in the ParlaMint-BA.ana.xml file?
The text was updated successfully, but these errors were encountered: