وال (ہک تند)
گُر
Before asking a question, make sure to read the FAQ.
We aim to maintain a healthy atmosphere for civilized discussions. Please read our rules against bad behavior.
mraz
کل
mraz
کل
mraz
کل
Dovud123
کل
sharptoothed
کل
frpzzd
کل
hecko
کل
frpzzd
کل
araneo
کل
gillux
کل

We have the very same sentence in two different languages, Portuguese and Spanish:
http://tatoeba.org/fre/sentences/show/1592938
http://tatoeba.org/fre/sentences/show/1593995
Will they be merged?

what is the probability that it exists yet in another language and means something different ?

No, they won't.
The same clashes exist for other languages as well, e.g.:
http://tatoeba.org/sentences/show/397374
http://tatoeba.org/sentences/show/337605

google translate translates directly in these pairs (exclude english):
afrikaans-dutch
dutch-afrikaans
azerbaijani-turkish
turkish-azerbaijani
belarusian-russian
russian-belarusian
chinese s.-chinese t.
chinese t.-chinese s.
estonian-finnish
finnish-estonian
haitian creole-french
french-haitian creole
japanese-korean
korean-japanese
macedonian-bulgarian
bulgarian-macedonian
malay-indonesian
indonesian-malay
serbian-croatian
croatian-serbian
slovak-czech
czech-slovak
ukrainian-russian
russian-ukrainian
urdu-hindi
hindi-urdu

and please don't try to use a machine to translate human language

boracasli is convinced machine translation works...We tried several times to explain to him that it is not the case, but the new generation of web users believe in Google as it was God Almighty...There's nothing you can do about it, I think...

and
catalan-spanish
spanish-catalan
galician-portuguese
portuguese-galician

please limit yourself to add sentences in the languages you know the most. If you find or hear somewhere of multilingual translations to a sentence, you can make a comment with all of them, so native users can verify their meanings and add them themselves.
In Tatoeba it makes no sense adding hundreds of sentences if they are not validated by native users

Get my fuckingly awsome new *Userscript*
==========================
Bored of plaintext comments and wallposts? Enhance your _Tatoeba_ experience with ***[my brand new Userscript]***!
It allows you to write formatted text in comments and wallposts! However, *you can see the awsomeness with the userscript*, all others will just see some `funky plaintext`.
[my brand new Userscript]: http://userscripts.org/scripts/show/134238

I have to give some credits:
* This script basically injects a [MarkEdit] editor.
* It's using the [Markdown]-Syntax.
* And it includes the Javascript Version of Markdown named [Showdown]
[MarkEdit]: http://tstone.github.com/jquery-markedit/
[Markdown]: http://daringfireball.net/projects/markdown/
[Showdown]: https://github.com/coreyti/showdown
Until now the script has these features:
1. Provides buttons for easy markdown usage
2. Live preview of what you write
3. You can mention a user via @username. It will result in a link to the profile page.
4. You can talk about tags via #tag or [#a long tag]. This will automatically link to the respective tag-page.
Of course, it might be still buggy, as it is an overnight project. Here are some points that are still to be done:
* enable multiple instances for the wall.
* provide a way to copy the plain markdown from other posts without having to look into the source code (e.g. a toggle button)
* enable notification of mentioned users
* Reenable link shortening

further todo:
* repair the parsing on the home screen
* enable parsing of profiles
* automatically add a zero width space to markedit generated posts to opt on only parsing when intended

For the opting i thought of something better:
Whoever decides to use the userscript or manually use markdown shall declare so in his profile. The script will automatically look for a defined term (e.g. "Markdown") and save markdown=true for that user. Also there will be a button in each users profile to toggle the behavior dor that user manually. There will be modes to choose from:
1. only parse opt-in users
2. Only don' parse opt-out users
3. Parse all
With the toggle button you will still be able to disable parsing for easy citing.
*plus*, there should be a "cite"-button to include all the text written by a user or the current text of the sentence into your comment box.
Another idea would be to use curly brackets "{ }" to indicate the whole sentence that you just copied there via the cite button and let a differ show what your recomended changes are:
1. the original would be "Go awaz!"
2. then you press "cite sentence"
3. the script copies "{Go awaz!}" to your comment
4. You change it to "{Go away!}"
5. The script will show the other user that you changed "z" to "y"
6. the proposed changes will be a clickable link, which applies the changes to your sentence
7. click "send" to finish editing the sentence.

The userscript has now added functionallity:
1. only parse opt-in users **md!**
2. Only don' parse opt-out users **md.**
3. Parse all **md/**
To change the parsing-mode you have to *double click* the `md` link next to your username. (The dropdown is still not functional, but it will be soon)
To switch all parsing of (without changing the parsing mode), *click once* on the `md` link: `#md` indicates *active*, `_md` indicates *disabled*.
By now you have to choose the states for the users individually in their profile (your own profile is just a normal profile for that): the *italic* writing of `md` indicates that you are changing the parsing state of that user. Outside a users profile, you change the parsing mode.

> To change the parsing-mode you have to double click the md link next to your username.
The dropdown is still now functional!

The diffs should always refer to the last commit *at that time* i guess.

maybe "nº642253" couldbe parsed as a link to that sentence and "{some changed text}(nº642253) should show the diff to that sentence nommatter where you write it, as well as {away}(awaz) or (awaz){away} should show the diff just between these parts of text.
For special cases {changes}(%5) should indicate that your diff starts from that number in the history. To ensure that changes that occur during you write down your post dont mess up your message (as the diff would then be displayed differently) the script should automatically include the %5 number from the history.

I've fixed some stuff:
* homescreen comments now display correctly
* profiles are parsed too, also there is a editor for your profile
* added a toggle symbol next to your username, which says `#md` (short for [markdown]): It **both** toggles the parsing and hides the live preview. When toggled, non-parsed raw text displays as monospaced font.
I've added some _examples_ at [one of my sentences]
[one of my sentences]: http://tatoeba.org/deu/sentences/show/544586
[markdown]: http://daringfireball.net/projects/markdown/

Bravo @jakov !

Merci !

Taste some [screenshot](http://s3.amazonaws.com/uso_ss/...ng?1338073485) from the userscript page, or enjoy it inline with my userscript:


Feature request:
I think we should be able to "call" users by writing "@username". For instance one should be able to write "@jakov: please check that german sentence for me, as you are native" and the respective user (in this case me, jakov) should receive an e-mail, just like he would when he had already posted to that sentence.
@sysko: However this can only be done on server-side ;)

I think @ is not really the best marker for this, since it's also used in tags meaning 'action is needed'.

Plus we could start writing about tags in hashtag-manner like this:
#sports
or like this
#[by Isaac Asimov]
if there are any non-word characters or blanks in them.
If we talk about an @-tag, we just use #@change or #[@change tag]. What do you think?
*PLUS*, I would propose that we use [markdown] in our comments. I will try if I can put [showdown] (a javascript markdown implementation) into my userscript. Of course we would then have to make our @mention and #hashtag system compatible.
[markdown]: http://daringfireball.net/projects/markdown/
[showdown]: https://github.com/coreyti/showdown

I'm probably going to settle on [markedit](http://tstone.github.com/jquery-markedit/) as it is very well documented. I'll see if i can put in the hashtag and mention stuff.

But the @ is widely used on the web (twitter, youtube, diaspora, ...). And there's probanly not going to be a user named "change" or similar. Also it is like adressing all users who can contribute to a certain problem and therefore go through the specific @-tag.

I've noticed that private messages aren't e-mailed to the person. Looks strange for me.
If it would work, one could write a client-side script to PM user automatically when '@user' is written in the message. ;)

> I've noticed that private messages aren't e-mailed
> to the person. Looks strange for me.
The original explanation was: it's because this will allow to use PM to send spam.
Comments are emailed, but everyone sees comments, so admin(s) would be able to quickly block the spammer. But if someone sends spam through private messages, it can come unnoticed.

It would be great to have an option in user profile to enable/disable e-mailing of private messages.

yes. Make it opt-in, then no-one gets hurt ;)

That's a great idea! I would instantly start writing if i wouldnt have to learn an awsome lot for my examn. However, if you or anyone else has a little javascript knowledge, don't hesitate to copy from my other userscripts, which you can find at http://userscripts.org/users/61020 (They're all CC-BY, so mentioning me is enough)

Here we go! That's just for the start. It should link mentioned users on the wall (so the previous posts can already be tested):
// ==UserScript==
// @name Tatoeba @Mentions
// @namespace Jakob V. <jakov@gmx.at>
// @description [work in progress] Links @username to the respective profile and sends a PM to the mentioned user if he wouldn't automatically get one
// @include http://tatoeba.org/*
// @require http://code.jquery.com/jquery-1.5.js
// ==/UserScript==
$(document).ready(function () {
GM_log('ready');
$('.message .body:contains("@")').each(function () {
$(this).html($(this).html().replace(/(\W)\@([A-Za-z0-9_]*)/ig, '$1<a href="/user/profile/$2">@$2</a>'));
//(<a href="http://tatoeba.org/deu/private_...inhalt">inform via PM</a>)
});
});

+1

That's a very good idea!

actually it's already in the todo-list :)
I agree for all the other ideas (to have a markdown etc.)

le chargement automatique des étiquettes lors de la frappe ne fonctionne plus...

c'est réparé, merci de l'avoir signalé

Merci, sysko !

I'm new here. I found the site afte ra reference at the Zompist conlanging board.

Welcome to Tatoeba!
You can contribute in any language that has a three digit ISO language code. It was discussed whether to adopt conlangs some time ago http://tatoeba.org/eng/wall/sho...#message_10731
However, if you wantes to contribute in a somehow wider known conlang, i guess that we could discuss about it.

Bienvenue !
@jakov
Kia vi tiel facile trovas maljunajn murmesagxojn ?

Mi serĉis per guglo je "tatoeba conlang" aŭ "site:tatoeba.org conlang".
("kia … tiel" → "kiel … tiel/tiom")

Hey, thanks!
I wasn't really planning on adding any conlangs, but I speak Japanese and figured I'd contribute where I can. That said, I find this site is *just* the thing to help me develop my conlang.
That said, it'd be interesting to see conlangs on here.

タトエバにようこそ!
There are a lot of japanese sentences that need revision and adoption (see the Help page linked in the footer if you're not familiar with Tatoeba's jargon and system).

"Sao lại không được?"
There are many example sentences but I can search only one.
nº337934
nº1589788
Is there any thing wrong to search in Vietnamese ?

nº1589788 had been added recently. The search engine cache has not been updated yet.
It will appear in the search, but not immediately.

how long will the cache be updated ? will it be cleared to have a new one automatically ?

I found a Tatoeba sentence in the Lojban Wiktionary:
http://jbo.wiktionary.org/wiki/kindi'u

In "Add sentence" Page.
Can you have another optional page which display 5 or 10 or 15 fields of text to add at the same time ?
With current page, it is slow to wait for the Javascript to run to type another sentence.

I want to suggest that all tags that have no items, e.g. the typos like "OK[" (0) should be deleted automatically or at least be put to a seperate list of ex-tags.
Also, there's something strange about a the tag http://tatoeba.org/deu/tags/sho...y_Isaac_Asimov : In the list of tags it says that there are "(-1)" items with that tag, which is obviously a bug.

+1
Though some tags such as "@change" or "@needs native check" are virtually possible to be nought, so exceptions should be taken into consideration.

I agree, but the disadvantage would only be that if such a tag would be purged (removed from all sentences after improvement) the first user to add it again to a sentence wouldnt have te auto-complete function. I think if we write down which tag has which puropse then its not a big thing.

Fair enough for me.

+1
tag names that contain : and maybe other special symbols do not work properly...

I just wrote "http://example.com/thats_the_url" and seperated the ":" so it didnt destroy the link, but it's not part of the link. So there's nothing special about "by Isaac Asimov", at least no special character.

OK, mi nur volis informi vin cxiukaze...