English > Feature Suggestions

Vote: Features for 0.9.9

<< < (15/39) > >>

meriator:

--- Quote from: rick.ca on August 16, 2008, 07:05:07 pm ---Do you have something automated in mind?

--- End quote ---
;D not realy but
they can be pre-translated via google etc..
and then correctd by your self
then the table should have an other field
terms-table
term_ID|lang|term_value|final
which mark a term_value as ....finaly translated  :)
.....and maybe PVD should colorize all untranslated terms....


it is also possible to implement the translation-table
this way as I have done in some Apps before
ID|ident_key|default_value|eng|ger|rus|fra|fin
adding a lang means then Alter "table" add fieldname varchar(....
where fieldname = the lang_identifier
deleting means ...drop fieldname...
but this way it is harder to mark single lang_terms as final or what ever
on the other hand it's possible to have diffrent meanings
via default_value and/or ident_key on the same term
because the default_value has no specific language
and the  ident_key will match the use of the term

good translations are hard work any way

an other idea on translating the terms might be
let PVD-users work together
create an online-db for translated tags
where PVD can synchronize the tag-table
may be the requierd fields only

2200 terms in 10 or more languages are possible to do this way
by myself  I could'nt do it
I do not trust google, or babelfish ..ect...that much   ???


thx again
cu meriator

rick.ca:

--- Quote ---...an other idea on translating the terms might be...
--- End quote ---

You seem to have some good ideas on how to implement this sort of thing. I know they must be good—I don't understand them. ;) That's not a criticism of your ideas—I just know very little about anything technical. I do wonder, however, if we don't need to be clearer about what the problem is before trying to specify the solution. It's not clear to me, for example, why a non-English user is trying to translate information from the IMDb. I suppose it's because the IMDb is more complete than any alternative available in their own language. But, even then, I don't understand why translating parts of it is going to be all that helpful when other parts are remain in English.

It would be very interesting to know how our Russian friends see this issue. Unfortunately, I don't understand what they're talking about over there. :( Now there's an interesting feature suggestion for this forum—some sort of translation service (user provided?) to "link" us to the Russian forum.

meriator:

--- Quote ---It's not clear to me, for example, why a non-English user is trying to translate information from the IMDb
--- End quote ---
1.it is easier to understand
2. and I prefer my home-language
3.I'm sharing my DB with my people and not all of them understand/speak english
but some of my reallife friends are foreigners in my country (Germany)
and they do not speak german very well but english or italian or ...
so why not more then one language if it's possible to do
4. a lot of terms are coming up again and again
   like genres, professions and, why not,  tags too
once translated no more or less future trouble
5.I like to have my data in more then one language
and a lot of my DVD-movies are supporting my wishes  ;D
sometimes I'm watching movies with friends in other languages then my own
and mostly a have seen the movie already in my language, this is funny
6. i like to work on DBs, and translations are a recuring challange
it's like surfing the Inet, relaying on only one language would be very boring

so I do not collect all needed/prefered infos from IMDB
but of course IMDB has a lot of them in 1 place
except older stuff

these are some Ideas why to do so
and maybe, Russia agree   ;D

thx again
cu meriator

rick.ca:
Thanks. That helps me understand a little better. What you seem to be saying is some users have an interest in having information in various languages, for various reasons. I wonder if the best solution is not just to make the entire database multilingual. That is, there would be separate "version" or "tier" of each record—one for however many languages the user wants to use. It would then be up to the user to decide what information (i.e., source) to download to each language tier. This might involve a script getting information in one language, and then translating it and saving it to the tier of another language. Multiple scripts could be run in batch mode to populate multiple tiers all at once—as new movies are added.

What I'm imagining is something where you could use your database in German, but switch it to English for a particular movie when you know the IMDb information stored there is more complete. And switch it to Italian when your Italian friend is visiting and doesn't quite understand the information in German or English. Even if you didn't want to maintain Italian information for all your movies, you would still have the option of switching it to Italian and downloading from an Italian source on an as-needed basis.

This is great. I think we're well on our way to having version 2.0 all mapped out—before nostra can finish 0.9.9.  ;D

nostra:

--- Quote from: comesbackatlast on August 18, 2008, 12:40:10 pm ---Another beauty issue:

Could you change the season icon? :P

--- End quote ---

Yes, if you give me one :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version