Based on looking at the smallest file:
(a) I would put a language code on the top-level tei:TEI tag. Both
because that's where some XML-aware software expects to find it and
because currently text in the header has no language code associated
(b) The @n attributes on tei:sense seem odd. Unless I'm missing
something these are redundant.
...let us be heard from red core to black sky
On Thu, 31 Jan 2019 at 10:17, Eduard Drenth <[log in to unmask]> wrote:
> Dear all,
> At the fryske akademy we are going to publish a online dutch-frisian dictionary. The basis will be tei-p5, exist-db and teipublisher 4. We are trying to design and develop the solution as generic as we can.
> For this I converted internal xml to tei. I have looked at several initiatives to get to this result: freedict, lex0, https://journals.openedition.org/jtei/522 and https://clarin.oeaw.ac.at/lrp/dict-gate/vle_docu/vle_docu__v001.html.
> Find some examples here https://bitbucket.org/fryske-akademy/exist-db/src/master/tei/. Perhaps some of you can spend a bit of time on these and give some comments.
> Eduard Drenth, Software Architekt
> [log in to unmask]
> Doelestrjitte 8
> 8911 DX Ljouwert
> +31 58 234 30 47
> +31 62 094 34 28 (privé)
> Op freed bin ik frij
> gpg: https://sks-keyservers.net/pks/lookup?op=get&search=0x065EF82A1E02CC43