翻訳者レビュー ( 日本語 → 英語 )

日本語

Word censorshipの機能を追加して欲しい
その際に投稿内容やコメント欄、そしてユーザー名のWordもチェックできるようにしてください
この機能がないとAdsenseを利用することが難しいです

あと以前、報告したかもしれませんがタグが1つだけの場合、その投稿がタグページに表示されません

またパスワードをリセットするページで登録したメールアドレスを入力して送信すると白いページになってしまいます
同じようなエラーをサポートしたことはありませんか？おそらくサーバーの問題だと思います

英語

I would like for you to add a word censorship function.
In that case, please make it so that I can check the content of submissions, the comment column, and usernames as well.
If I don't have this function, it is difficult to use Adsense.

I may have reported this before, but when only one tag is used, that submission won't display on the tag page.

Furthermore, when I input and submit a registered email address on the password reset page, the page goes blank.
Haven't you given support with similar errors before? I think it is perhaps a problem with the server.

レビュー ( 2 )

a_shimodaはこの翻訳結果を"★★★★★"と評価しました 2014/03/23 10:30:51

私はいいと思います。

[削除済みユーザ]はこの翻訳結果を"★★★★★"と評価しました 2014/03/23 22:46:17

元の翻訳
I would like for you to add a word censorship function.
In that case, please make it so that I can check the content of submissions, the comment column, and usernames as well.
If I don't have this function, it is difficult to use Adsense.

I may have reported this before, but when only one tag is used, that submission won't display on the tag page.

Furthermore, when I input and submit a registered email address on the password reset page, the page goes blank.
Haven't you given support with similar errors before? I think it is perhaps a problem with the server.

修正後
I would like you to add a word censorship function.
In that case, please make it so that I can check the content of submissions, the comment column, and usernames as well.
If I don't have this function, it is difficult to use Adsense.

I may have reported this before, but when only one tag is used, that submission won't display on the tag page.

Furthermore, when I input and submit a registered email address on the password reset page, the page goes blank.
Haven't you given support with similar errors before? I think it is perhaps a problem with the server.