Quote:
Originally Posted by Terisa de morgan
@arspr, what do you mean by "intelligent" translation? As I understand, you're asking for calibre translating all the texts you add. Is it right?
|
Not exactly. (My English is worse than I thought)
What I'm suggesting is a that each value you put in Tags or in Tag-like custom columns ("Novel", "Typos", "Or whatever other thing you want to type") could be in fact a list values. Each one corresponding to a different language.
I mean if I create "Novel" as a new Tag, automatically all the English, French, Spanish, German, Hindi, whatever language values are populated with "Novel". But I should be able to edit that series of "Novel" translations to whatever I want. So if I go to the Spanish value and I overwrite "Novel" with "Novela", whenever I change GUI language to Spanish, I get "Novela" instead of "Novel", because in fact "Novel" is not just a single word but a customizable list of translated equivalent words...
Of course there are a lot of difficulties to solve with this scheme. Some examples:- What you do with Word_A and Word_B in English when they both share the same Palabra_Común translation in Spanish.
- How you set up the "Rename" feature when in fact you could have to rename a list of words at once...
Quote:
Originally Posted by DaltonST
@arspr,
The proper word I believe you are looking for is not "intelligent", but "dynamic". That is the first method I explained in my post (BISAC, etc.). I guess you didn't grok it. [...]
n.b. A dictionary is just a printed table of "from-to" combinations. If I were a dictionary, I would be offended to be called a "hack".
|
First of all, and just in case, sorry if my "hack" word offended you. No offence was meant in any way.
Wow, your suggestion about real true translations on the fly it's really really ambitious (and also too dangerous
). As a matter of fact I never use automatic translation services like Google Translate on foreign web pages but when no other way of understanding that web page is available. They usually contain too many errors...
But please re-read my explanation to Terisa. What I'm am suggesting is much simpler. It's just a list of values instead of single values... No "automatic" translation at all, just switching to the third value of the vector/list for French and to the seventh for Russian... But it's the user who must fill that vector in its desired translations.