Вариантов тут, по большому счету, два: не могут или не хотят. Надеяться на то, что завтра же переведут все предложения до одного, я бы не стал, но и отчаиваться не стоит. Чем интереснее Ваше предложение, тем больше шансов, что его переведут. У простых предложение также меньше шансов остаться непереведенными. Если Вы владеете другими языками и уверены в своих силах, Вы сами можете попробовать сделать перевод, снабдив предложение пометкой @NNC или @needs native check. Это привлечет внимание носителей языка и уменьшит вероятность неправильного перевода.

Thanks, Eldad! Though, we, Russians, are trying to avoid premature congratulations and thanks for anything. We believe that doing this we can put the evil eye on it. :-)

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

Не у всех предложений на проекте есть владельцы (по разным причинам). Каждый участник может "усыновить" (adopt) такое предложение с целью исправления ошибок, например. После этого существует возможность "отпустить" (let go) такое предложение обратно на волю. То же самое можно сделать и с люым другим предложением, автором которого Вы являетесь.
Одно важное замечание: на Татоэбе не рекомендуется "усыновлять" предложения, написанные не на Вашем родном языке.

Hi, Brokahontis! Welcome to Tatoeba!

> How should we approach translating languages where
> the subject isn't included?
Interesting question indeed! Japanese is an extremely context-dependent language, you know, and omitted subject is in the order of things in it. Thus, as you outlined above, different translations are often possible. There can be different approaches to this problem but I know no universal one.
Personally, I prefer to translate such sentences as though as they were a first person ones since I really do believe that there's no need to add all possible options. The essence of such sentence is usually not in its subject but in the actions, states and events it describes.
In case a sentence has translations to other languages I understand, I prefer to make translations that correspond to them to kill two birds with one stone. :-) This may conflict with Tatoeba rule to translate a sentence independently of the translations it already has, though, but I think, in our particular case, this will be the lesser evil than producing a bunch of contradicting sentences.

タトエバへようこそ！
I think, the things you said are true not only for Japanese but for any other foreign language we try to learn. :-) Mastering the naturalness of speech takes a good deal of time and Tatoeba is a great place to help us on this hard way.

Hi, Jim! Welcome to Tatoeba!
This site is, maybe, not the best place to study languages but definitely one of the most useful places to extend and master your knowledge. :-)

Не жадничай! ;-)

Ты настоящий друг! :-)

Please consider presenting me a modest 1% of this amount. ;-)

Great! A standalone Tatoeba application could be really useful in the situations when Internet connection is not available or slow/unstable. Besides, some people find more convenient to use PC applications rather than Web-based ones. So, good luck! :-)

Good idea! Receiving e-mails in native language is always pleasant even for polyglots. :-)
I think, it should be relatively easy to implement since Tatoeba already has internationalisation features.

For Tatoeba admins and developers.

I've found a minor bug in Tatoeba mail notification system that affects the way how mail "Subject:" header is constructed. It seems that data for this header field is being supplied straight in UTF-8 encoding, without any conversion. This breaks RFC 5322 that allows only US-ASCII in header fields and prevents some mail clients (K-9, for example) from displaying this field correctly. The "Subject:" field body should be converted into "base64" or "quoted-printable" encodings using MIME syntax as per RFC 2045.
In addition, message headers lack "Content-Transfer-Encoding:" header field that may lead (though, very unlikely) to unexpected problems with some mail servers and clients. Adding "Content-Transfer-Encoding: 8bit" should secure us against this probability.

どうもありがとうございました。＾＾
(I hope you'll be able to read this by yourself very soon. :-))

Thanks a lot for your confidence! :-)

А, ну да. Но всё равно спасибо. :-)

Thanks for putting confidence in me! I'll try to not let you down, pals. :-)

Спасибо за оказанное доверие! Я постараюсь вас не подвести. :-)

As far as I can judge, furigana is generated via special part of speech and morphology analyzer software. It does a great job yet there are many cases where it produces incorrect results. I'm not sure if there is an easy way to improve its functionality so it maybe really worth implementing a separate feature that will allow to edit furigana by hand. Though, it may require significant change in user interface, I suspect.