I think, the wall is a good place for example requests. Other option is to write a PM to any active Japanese member.
By the way, though it seems to be no examples with 寧ろ, there are enough sentences with むしろ. :-)

Personally, I think that sentences on Tatoeba should be as natural as possible. First and foremost, this concerns newly added sentences, not translations. Saying that I understand that in many cases a sentence taken out of context may sound unnatural, weird, ambiguous, etc., so I think we should encourage the contributors to avoid adding such sentences or, at least, to provide usage examples whenever it's necessary.
As for the translations, I think that a good translation should meet at least the following criteria: it should be grammatical, natural, has the same meaning and/or the same effect. Word-for-word translations often have nothing to do with those criteria and, thus, should be avoided unless we want to illustrate some peculiar property of the original sentence. In this case a "good" translation should be added along with the literal one and the latter should be marked with an appropriate tag(s) (i.e., "literal translation", "unnatural", etc.).
The biggest problem is what to consider "natural". Sometimes even native speakers have polar points of view on the same sentence. This means that it's highly desirable to raise a discussion whenever we bump into a doubtful sentence. At least, corrections shouldn't be made without notice and explanation.
Thus, I think that:
- ungrammatical sentences should be corrected unconditionally;
- unnatural sentences should be corrected unless a context or usage example that makes it sound natural could be found. "Unnaturalness" should be explained by a proficient/native speaker.
- if the sentence sounds unnatural due to literal translation made on some purpose, the reason should be explained and the natural translation added along with the literal one.

And so do we all! :-)
Welcome to the Tatoeba Project!

Welcome to the Tatoeba Project!

Although Tatoeba wasn't designed as a place for learning languages, I think it still can be used to extend you knowledge and to make new language partners. So, good luck! :-)

Hello, Rockelle!
Welcome to the Tatoeba Project!
> I also don't know where to start
The most people here do two things: translating existing sentences and adding new ones. Whatever activity you choose, your contribution will be highly appreciated. :-)

> Should a native speaker who corrected or confirmed a
> sentence remove the @needs native speaker tag and add an
> OK tag instead?

I think, this is acceptable since "@needs native check" and "OK" tags are mutually exclusive.

I think that

> 1. Who can put this tag?

Currently, only advances members and corpus maintainers can tag sentences. I think it's possible to allow owners to tag their sentences with "@needs native check" regardless of they rank.

> 2. In what situations should this tag be put?

The tag should be put every time when the sentence is added by a non-native speaker and there is a doubt about if a sentence is natural and/or grammatical.

> 3. Who can check sentence?

Anyone who is fluent (proficient) in the sentence language can check it and leave an appropriate comment then. Though, the decision of removing the tag should be left for the corpus maintainer who claimed his proficiency in the sentence language, a native speaker preferably.

> 4. What is the difference between @needs native check and @check?

Strictly speaking, I see no big difference between those two tags. But, "@needs native check" may indicate that naturalness of the sentence needs to be validated first of all, while "@check" may refer to the need of validating translation quality, grammar, punctuation, etc.

That's right, correct sentence that don't match the original should be unlinked unless a sentence owner wishes to correct it. The latter is undesired, though, if the sentence has its own translations already.

Usually, a sentence with lesser number is the original with the exception of sentences with numbers up to 329712 approximately that originate from Tanaka Corpus (English - Japanese pairs).

Hi, Ramin!
Welcome to the Tatoeba Project!

I think, it's not a good idea to keep such things here. At least, not as "translation" for original sentences. I hope that metadata mechanism will be implemented eventually and then we'll be able to add transliterations, transcriptions, etc. without poisoning the main database.

As far as I know, the sentences have to be indexed by the search engine before it becomes possible to find them via Tatoeba search tool. I suspect that indexing process just wasn't being ran for some time. Maybe due to performance issues Tatoeba experiencing last time.

Try to open audio links in separate tab/window.

お誕生日おめでとう！＾＾

Добро пожаловать на Татоэбу!
Welcome to Tatoeba!

You've chosen the right place, indeed! Tatoeba is, maybe, not the best site to learn languages but definitely one of the very best to find natural and actual sentences in many languages.
Good luck! :-)

Добро пожаловать на Татоэбу! :-)
Новичкам здесь всегда рады, а что касается нового - по части иностранных языков тут этого хоть отбавляй. :-)

おめでとうございます！その調子で続けてください。＾＾

That would be really nice. The era of new Tatoeba looks promising, indeed. :-)

> Isn't information on each word the task of word dictionaries ?

Essentially, yes. So Japanese indices on Tatoeba provide just the dictionary form of words and the sense number in JMDict/EDICT but not the meanings. For beginners it often hard to determine the dictionary form of a conjugated verb or adjective and, thus, to find its meaning in dictionary. Furigana doesn't help much with this issue, it only solves the Kanji reading and word tokenizing problems.

The main purpose of Japanese indices (as I imagine it for myself) is to provide user with comprehensive information on each word in the sentence, including its reading, dictionary form and a reference to its meaning (sense) in current context. This is truly invaluable thing for learners.