Suilad Aran,
I had a better look at the data the past two days. There's a couple of questions that came from that, as well as a first draft for a database model that would accomodate other languages besides German.
I don't understand the meaning of the columns srek, saltrek and s2rek in table
wortliste.
These columns only take the values 0, 1, 2, 3 or 9 - it seems as if the names suggest they refer to the columns
sind,
sind_
alt and
Sind
2 - although I can't figure out what
-rek refers to ?
It doesn't seem to be an index to separate otherwise identical rows for the above columns, but maybe I should check that again (though it'd be great if you could just tell me

)
Also, I don't know what the second table
wordliste_komm is for. By its contents I'd think that these are the somewhat uncertain entries that you talk about (like
_lorn_) but if so, how does this table fit into the data of the first one?
I puzzled a bit with a possible database design. As to what you mention about (for instance) homophonous words; I want to keep the internal cohesion exactly as it is. The changes that I'm thinking of would therefore leave all that intact; it would just distribute the components in another way across tables so that it would become possible to add other (modern) languages. It would also eliminate the need to enter redundant data, like when there's two rows in
wortliste for two translations of one Sindarin word. Here's an ER diagram:

It's of course entirely possible that I missed out something, so if you can look this over and comment, that'd be great!
I also left out the
srek,
saltrek and
s2rek culumns because I don't understand what they mean; and the second table is not yet considered here.
I'll also post this message on the topic about Aran's new German <-> Sindarin word lists on (, )
Thanks again!
NB - it just occurred to me that this model does not only allow for other modern languages to be added (like English, French ... ) but it can also accomodate another elvish language like Quenya (in that case it'd be better to rename that one Foreign Key column to ELVISH_ENTRY_ID)
Or, even better: if Quenya words would be added, you'd also get a Sindarin-Quenya dictionary for free

.. at least for the words that exist in both languages, of course.