Thanks to notice it up, I think we need to have a discussion with him. For adding machine translations, we do not want this. The goal of tatoeba is precisely to propose a better option for people willing to have a set of sentences translated in an other language,

I don't think it's ever come up before - but, bad, bad idea.

> 4. Do not translate word for word
>
> We are not interested in having sentences that sound like
> they were written by a robot. We want sentences that really
> are what a native speaker would say.
Tatoeba Blog, ‘How to be a good contributor’, rule 4 (http://blog.tatoeba.org/2010/02...eba.html#rule4)

I guess this covers machine translations. ^^

I don't see why not, just indicate that the translations are colloquial in a comment and a trusted user will add a tag to it...tatoeba already has colloquial sentences http://tatoeba.org/eng/tags/sho...tag/Colloquial
or read this http://blog.tatoeba.org/2010/02...n-tatoeba.html and then PM Trang (http://tatoeba.org/eng/private_...es/write/TRANG) and ask her nicely to make you a trusted user...then you can add your own tags

you can read more about tatoeba's submission policy here:
http://blog.tatoeba.org/2010/08...f-content.html

hope I helped

You can. The only rule is to have the best compromise between "be close to the meaning" and "being natural". If it's a formal sentence, add a translation which is also formal etC... If you think two translations can be added, you can add both, and maybe add in comment the specificity of each sentences (if one is more natural but not so close to the original meaning, and the other closer to the original meaning but maybe less natural for example).

Non le script ne détecte que les doublons parfait, je n'ai pas préféré ajouté cela, car le script de détection est assez "sale" (c'est une procédure en pl/sql de mysql) et je n'ai pas trouvé de manière propre et tout aussi ""rapide"" de le faire. De plus dans certains cas la ponctuation peut changer la traduction (même si je te l'accorde l'absence de point final ne change en rien le sens vu que c'est purement et simplement une faute).

Mais je pense qu'il faudrait pour être plus "propre" créer un script d'uniformisation, correction des majuscules, des points manquants etc. qui tourneraient avant le script de dédoublonnage. Cependant je ne pense pas avoir le temps ces prochaines semaines, de faire une telle chose.
Par contre en attendant je pense pouvoir créer petit à petit un jeu de commande sql de "nettoyage" pour ajouter les points manquants etc.

If you're talking about the "blue" version of tatoeba, it's a separate database with different password , so changing one does not change the other.

Yes indeed. The colon is the problem. Thanks for reporting. I created a ticket for it.

by asking here :)
welcome!
(it's tAtoeba ^^)

If you're looking for example illustrating a word you can simply use the top menu bar in green, for example you want sentence using "example" in English sentences
http://tatoeba.org/eng/sentence...&query=example

If you see a translation is missing in your native language, you simply add translation by clicking on the "translate button" http://flags.tatoeba.org/img/translate.png

If you want to add a really new sentences you can do this by going on the contribute page

http://tatoeba.org/eng/contribute

If you have a specific need, ask, maybe it's already possible in tatoeba, or at least we can think about making it possible :)

Tell us if you have questions

[not needed anymore- removed by CK]

PG-13 is a normal tag.
be-1959acad shows that this is applicable only in the Academic variery of Belarusian; it's a normal language tag
Leopolis is a latin duplicate of Lviv ;o
Urdu is to be deleted, since we have a flag now
IMHO spoken to male should be replaced with ‘said to male’

I would say a) and c) and possibly b) (but depending on circumstances).

We'll probably need to fine tune that sort of thing later. It's not really a priority at the moment as the tags don't actually do much yet.

I don't think these should should be tagged under a single label. I think a) and b) could be tagged with something like "rude" or "obscene" and a) and c) with something like "sex" or "pornographic". c) should furthermore be tagged with "euphemism".

I this is actually a great time to think about how we're using and how we'd like to use the tags, seeing how it's not a priority and we can play around with them.

You could tag them as "stereotype", "prejudice" or even "bigotry".

I'm all for freedom of expression, but I think that clear lines are more useful for a project such as this (oh, and trying to steer around hypocritical stances would be nice). Seeing how the aim of this project is to gather sentences and link them to translations -- not to disseminate facts -- and the web is open to anyone wanting to espouse their hate, I'm not overly concerned about losing offensive content.

I do, however, prefer the idea of simply filtering out the filth one doesn't like.