May I add that I (and others) like to move through a URL to quickly access pages? Like removing the last part from http://tatoeba.org/eng/tags/sho...es_with_tag/OK to yield e.g. http://tatoeba.org/eng/tags
Which then in my understanding would bring up something about tags (and not the error page).
It's not an overly important feature, but a good programming practise.
After all I heard somebody bitching about all those PHP programmers and database website hackers, that broke with the "pure-HTML-page" design of what I described above. :)

Thanks. Already though about pestering our fellow developers with such a function :)

That's not the point. Most people will translate sentences regardless of the tag which just provides additional but not "normative" value.

Another issue I have is that basically titles cannot be translated freely. This is opposite to what Tatoeba defines for most other entries.

Example "To Kill a Mockingbird". In German it was translated as "Wer die Nachtigall stört". A literal translation would be "Die Spottdrossel töten" (Mockingbirgs are confined to the North American continent, so it is changed to reflect a bird native to Middle Europe).

Now we rely on metadata to actually edit this sentence. While tags (the metadata) were introduced to provide extra information we would here need them to actually define the sentence. I'm not saying this can't be done, but I believe this is a very ugly situation.

Movie titles

There's a short discussion on http://tatoeba.org/deu/sentences/show/347564 whether movie titles are to be considered sentences.

For me they are just normal vocabulary entries and can already be found in online dictionaries like HanDeDict (for Chinese-German) or I guess EDICT (Japanese-English).

I have to say I don't like the idea of collecting titles of movies/books that much as many translations are really non-literal. "Da Vinci Code" is "Sakrileg" in German. No connection at all.

I'd also argue that Wikipedia already has the link structure, so we don't really collect additional knowledge here.

Maybe somebody else has some good points on this.

He, thanks for asking.

My current perspective is how to select good sentences based on a given word. So if I have the word "love" I'll probably have several English sentences that include this word. Now if English had different pronouns depending on gender I would have two versions of each sentence, e.g. "I love you (male)" and "I love you (female)". Now think of even more specific tags, like "literal" and "metaphorical" translation. Which would provide the best examples? Probably the latter one (see discussion here http://tatoeba.org/deu/sentence...334#comments). "Literal" translations really are just that, translations. They probably don't make good example sentences. A good logic would need to take care of that.

Me as a programmer I would need to have the answers here (I'm of course speaking from the perspective of integrating Tatoeba with Eclectus, sysko should know :). While tags provide a good logic for humans, it does probably complicate things here for me (and most probably others).

So my basic point is, don't forget the machine readable side over the human readable website.

Not sure if you pondered all the cases where Tatoeba data could be used. But maybe such an analysis could assist your design decisions.

I for one welcome our new tag system.

I hope you guys&girls do think about us who we later need to implement some logic on the data. While tags add important knowledge for humans I'm still not sure how to use this information when automatically selecting translations.

I do think though that "our" data is safe in your hands. Thanks for the good job!

At HKUST they teach Yale :)

Btw, is Jyutping really employed more often than Yale? In all books I read and the course I attended Cantonese Yale was used.

Hi saeb, as sysko said, the current dependecy on KDE (more specific pykde) makes it impossible to run on Windows. I already ported the whole lot to Qt only (read: it runs on Windows :) but didn't commit anything to the repository right now. I'll be at it pretty soon, why don't you send me an email, I'll be happy for a beta-tester.

I'm OK with ppl emailing me, in fact I hardly get any mails asking for assistance but I need to visit walls on other projects to help out :)

+1 :)

Good enough. Desolé for the PHP part, but then it's self-inflicted :)

Thx to both of you. I see the whole system is well thought-out.

http://tatoeba.org/fre/sentences/show/366507

May I disturb the silence once again. Consider the situation where somebody translates sentence A into B, then somebody later comes along to translate B into C. It then turns out that B is wrong and is consecutively changed. This invalidates C. Any ideas/plans for that?

Wrt link to repo: depends on the language. I ain't touching PHP :p

TRANG, I proposed tagging of sentences above (and maybe others have done so before). While my usecase was tagging specifics of a language in a particular language this could be extended to express nearly anything and everything. A sentence could be tagged as "AE" or "BE" for American and British English or even from which century an example was.

Maybe that's a bit too complicated. At least there are several other feature requests in the pipe, that might have more impact.
As you indicated in the 2nd note already though, adding a "news feed" for requests on one's sentences is surely needed.

I would propose to change your request into something with a broadend scope: "disown request" to disown sb by taking over their sentence. This could also be used on inactive users. Some time without reaction *zing* you go ahead.

+1 feature request:

Tag sentences for a special form. Say your language has several possible translations for a given sentence, tag these sentences for the given feature. Example: http://tatoeba.org/eng/sentences/show/366466 I would add one for informal you (french 'tu') and one for formal you (french 'vous').

A wiki would be nice to list those feature request, I think this "Wall" might get a bit to muddled.

Finding contributors (to the code): Why don't you guys (& girls) share (i.e. open source) your site's code on say github? First that would make this a truly "open source" project, and secondly people could help add features. Think about it.
Some guys here seem pretty eager to get their features implemented ;)