I think we have discussed this topic already and I find the suggestion good, but there some problems with it:
1. Pretty much work for me
2. Too many values have to be translated in too many languages
3. Setting up these replacements will be time consuming
You have to translate not even a single word
May be the way I tried to explain my idea has been not clear enough?
lets take an example
1. way
at view-time (db-data is keeped in orginaly language and will be only processed for viewing)
When the program is going to display an genre-term
and the user-preferences is setup to use replacements
only the SQL-Statment has to be changed, joining the replacment-table, to lookup a replace-term
if there is found one the program will take this term otherwise it will take the original term
so there should be a function at the right place to do it
if user-preferences is set up not to do so, this part will be skiped at all
2. way
at capture-time (db-data will be changed to his native language)
When a genre-term should be imported/inserted
the program has just to checkout before insert/update
if there is a replace-term for this genre-term
if there is one found matching the currently used language and the genre-term
the genre-term will be replaced otherwise not
again depending on user-preferences this part will be skiped at all too
thats all
so i do it a 3.way afterwards
at the moment I do this replacment via SQL-Statments
means by example, I replace one genre-ID with an other one matching my needs
anyway, it was just an idea, which came up to my mind
Who this work might be done easy?
so I thought it might be not that much work
but I do not do the job
3. Setting up these replacements will be time consuming
this would be my job I asked for
thx again for your response
cu meriator