japanese

japanese

Principles

Please remove all mannered prose.

Do not apply English forms to Japanese. Take the meaning and intent, and restructure them into expressions natural as Japanese.

When unsure of your judgment, try the following.

Imagine whether a Japanese speaker would say that sentence as-is in daily life or at work.
Reconstruct the original English in your mind and check whether it has become a literal translation.
If the predicate is missing, supply it.
If the same ending continues three or more times, change the sentences.

Do not use noun-ending style (a noun followed by a period) in body text, explanatory text, or conversational text. Supply a predicate.

It may be used only in headings, labels, UI status displays (in progress, not supported), and extremely short bullet points.

Use "~made" as an adverbial phrase and supply a predicate. Do not end a sentence with it alone.

land (PR, change) yoseru, chakuchi suru → merge, incorporate, reflect
drop (feature, support) otosu, doroppu suru → delete, discontinue, end provision
knock down, take down taosu → fix, resolve, remove
ship, push out dasu, okuridasu → release, publish
roll out korogasu → deploy in stages, provide sequentially
spin up mawasu → start, provision
wire up haisen suru → connect, incorporate
bake in yakikomu → make standard equipment, incorporate
bubble up: rise to the surface → come to light, be escalated
nail down: pin down → finalize, pin down
call out: call upon → make explicit, point out
follow up: follow up → get back to someone later, handle at a later date
circle back: go around in a circle and return → reconsider, return to later
unblock: unblock → lift a block, remove an obstacle
green-light: give the green light → approve, permit to start

defeat a bug, defeat a task → fix a bug, resolve a task.

can do ~ → can do ~
need to do ~ → ~ is required / please do ~
will do ~ (overused) → do ~ / will do ~ sequentially
becomes ~ → is ~
regarding ~ → about ~
the ~ one → cut
implement ~ (overused) → do ~ / carry out ~
we will inform you about ~ → we will inform you of ~
works without issues → works normally
if you have any questions → if there are any questions (adjust according to tone)

"~kiru" tends to be a literal translation of the English finish ~ing or ~ out. Do not use it casually.

write up the spec completely → finish writing the spec / complete drafting the spec
complete the task → complete the task
read through the entire list → check the list to the end

Katakana words themselves are not bad. When Japanese native words convey it sufficiently, prefer them.

Established terms such as refactoring and deploy are used as they are.

Explanations and reports to users — desu/masu style. Concise but with a predicate.
Commit messages — plain style is fine. End with a verb.
UI labels and buttons — short is fine, but use a verb form or a clear noun phrase.
Technical documentation — desu/masu style. Noun-ending style only for headings.

Do not mix polite style and plain style. Except when intentionally mixing them.

Work report.

バグの修正。テストの実行。問題なし。
→ バグを修正し、テストを実行しました。問題はありませんでした。

Next steps.

次は PR のマージまで。
→ 次は PR をマージします。

Request.

ログの共有どうぞ。
→ ログを共有してください。

Commit message.

認証まわりの修正。
→ fix: 認証エラーのハンドリングを修正

不要な依存関係を落とす
→ chore: 未使用の依存関係を削除

PR description.

この PR では変更を寄せます。レビューどうぞ。
→ この PR で変更を取り込みます。レビューをお願いします。

既知の問題を倒す対応。
→ 既知の問題を解消しました。

UI wording.

保存。
→ 保存する

エラー。再試行。
→ エラーが発生しました。再試行してください。

Splitting long sentences.

今回の変更では認証フローを更新し、トークンの検証ロジックを修正し、
エラーハンドリングを改善し、テストを追加することができます。
→ 今回の変更では、認証フローを更新し、トークン検証とエラーハンドリングを
  修正しました。あわせてテストを追加しています。