It is an interesting project. I don't know how Google does it but they
might tell you if you ask. It is possible also that they might sponsor you.
A concept can be a single word in one language and a complete story in
another. I might start with a concept record and a self referencing m2m
through-table perhaps called translate which carries two language name
fields.
The entire project might only require those two tables. Most if not all
the meta data would be in the translate through-table. Things like the
type of concept or explanatory examples in both languages.
You might also permit multiple spellings of the same word if that was
legitimate in a particular language. That would give the m2m translate
record the same language at both ends so to speak.
I'm thinking your native language might need to be translated into
neighboring native languages or dialects which happen to be somewhat
similar and could therefore link to your original translation into en or es.
Audio and video files could be easily added in a normal fk relationship
to the translate through-table. You need that because you probably want
multiple versions of the same video to cater for the multiple video
formats required by various browsers.
Languages are seriously complex things so if you can simplify the table
structure I think you make it easier.
Good luck
Mike
>
> Thank you.....
>
> --
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
django-users...@googlegroups.com
> <mailto:
django-users...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/django-users/aaa7c780-2a24-4943-94de-bec1b19aee59%40googlegroups.com
> <
https://groups.google.com/d/msgid/django-users/aaa7c780-2a24-4943-94de-bec1b19aee59%40googlegroups.com?utm_medium=email&utm_source=footer>.