You need to register here, as this is the service we use to manage the translation of tatoeba
https://translations.launchpad..../+translations
and then from there you can translate the interface/ correct mistakes

feel free to ask if you have questions :)

Yes in general it's better to leave alone a sentence if by itself it doesn't have any spelling or grammatical mistake. Never mind if it's a correct translation or not.

=> http://blog.tatoeba.org/2010/02...eba.html#rule5

We will soon introduce a way to "unlink" sentences for problems related to incorrect translations.

Anyway, if you would like to see more "Sie", you have the right to another translation. It's not forbidden to have two German translations for one same English sentence :)

Oh, I saw the discussion just now^^:
As Swift mentions, Wikipedia uses "du" when appealing to its contributors. Facebook also uses du. I juste decided to follow their example as it seems the most common solution to me and as I also prefer "du". But if anyone doesn't like it, let's discuss it :)!

Trang, did you synchronize my latest launchpad translations? The status is "Translation unchanged since last synchronized", however I see many English sentences in the German version that I think having translated?

Es wäre toll, wenn mir andere Muttersprachler helfen könnten, Tatoeba vollständig und besser zu übersetzen :)!
https://translations.launchpad.net/tatoeba
Das, was ich schon übersetzt habe, könnte sicher in vielen Fällen besser gemacht werden. Und einiges habe ich auch gar nicht übersetzt, da mir bisher keine gute Lösung eingefallen ist.

No it's actually a bug. We're aware of this and it will be fixed this weekend (or perhaps sooner). We'll let you know. Sorry for the inconvenience =/

In the meantime, the best way to proceed is, first to click on the sentence in order to view it in the "Browse" page (the page where there are also the comments and the logs displayed). Then adopt the sentence. Then refresh the page. Then edit the sentence.
I know it's quite annoying, but it's the only (temporary) solution.

I think as you've said, we haven't so much Japanase native, in a first time "confirm" them is the best solution, with an interface even in "not perfect" Japanese, we're more likely to attract more Japanese, and I think they will report us if they see any mistakes

Thanks for taking on the task of translating into Japanese by the way ^^

And yes, I agree that it's better to "confirm". We're not going to be very perfectionist on the interface translations, even if it may not look very "serious" from a language website NOT to have correct translations...
But well, for the reason sysko mentioned, it's better than nothing.

Much as I love those indices in the B-lines (I invented them years ago), I think it might be better to go straight to MeCab. There are some tricks you would need to apply, e.g. where MeCab says a particle is "助詞,格助詞" you would leave it with spaces around it, and where it is "助詞,接続助詞" you would attach it to the preceding word.

Those "|1" are an artifact of the days when Paul Blay was maintaining the indices in MSAccess and needed a way of disambiguating some words. They are not carried through to the B lines in WWWJDIC (I didn't know what they were until Trang expained them to me.)

If you are using MeCab, use the IPADIC version.

The B-lines would be necessary if you you were to create links to WWWJDIC, as MeCab breaks up expressions/compound nouns/etc.

OK, I worked out how to do a follow-on. I'd clicked "reply" but it hadn't worked. Now it does.

the traditional to simplified chinese is not made at "character by character" level, but try to decompose the sentence (you can see how the sentence has been segmented by looking to pinyin)
As I've said I'm in conctact with the guy who develop it, so don't hesitate to report any bad segmentations, I will report to him

Word-by-word links based on the Japanese index words would be good, and not too hard to implement, I think.

At present I am pulling the sentences and indices into WWWJDIC once a week, and I put them through a utility which matches the text and the index contents, and reports if there is a mismatch (which usually means that someone has changed a sentence.) To get around the problem of "deliberately non-indexed text" I have a file of
words which I ignore if they are not in the index. You can see this list of words at http://www.csse.monash.edu.au/~...amplestopwords (in EUC-JP). Most are names. Some look a bit odd as they are two or more names which had been separated by punctuation (which I ignore.)

Normally the path of the file should be enough of a hint for you to figure out on which page of the website the string can be found.

If the path is something like /views/<something>/file.ctp file, then you would usually (not always) need to go to http://tatoeba.org/<something>/file

If the path is /controllers/<something>_controller.php, then the string is a bit harder to find, but it can be found somewhere in the pages that start with http://tatoeba.org/<something>/

I don't know how comfortable you are looking at source code, but it could be simpler if you just translated what you can first. We have a "test" version of Tatoeba where we test things before we update the "real" version of Tatoeba. As soon as you have your translations done (even partially), we can update the "test" version and you can then browse around in there to check if the translations fit or not. I'll give you the link in a private message.

Other than that, the source code can be found here:
http://subversion.assembla.com/...ba2/trunk/app/
Just note that the strings in Launchpad are not always exactly synchronized with the code source.