[i18nIgnore] fix: i18n-guides/Japanese.md#13245
Draft
Yusaku01 wants to merge 3 commits intowithastro:mainfrom
Draft
[i18nIgnore] fix: i18n-guides/Japanese.md#13245Yusaku01 wants to merge 3 commits intowithastro:mainfrom
Yusaku01 wants to merge 3 commits intowithastro:mainfrom
Conversation
✅ Deploy Preview for astro-docs-2 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
I've moved this to draft for now, as I don't think it's urgent. |
morinokami
reviewed
Feb 10, 2026
Member
morinokami
left a comment
There was a problem hiding this comment.
ありがとうございます!一点だけコメントしましたのでご確認をお願いします 🙏
| - 使うことができます → 使えます | ||
| - メニュー項目など表示領域が限られている箇所(たとえば`src/i18n/ja/ui.ts`のRight Sidebar)では、たとえば「このページを編集」などのように、可能であれば文末の「する」を省略します(「このページを編集する」とは訳さないでください) | ||
| - ただし、「貢献する」のように目的語などがなく「名詞+する」だけの場合は「する」を省略しません | ||
| - 基本的に英語版の例示に用いられる半角コロン(:)は、句点(。)に置き換え翻訳します |
Member
There was a problem hiding this comment.
この記述自体は問題ないと思いますが、下部にインデントして例を補ってあげたほうがよりわかりやすいかなと思いました(「たとえば〜という英文は、〜ではなく〜のように訳します」みたいな感じで)。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description (required)
did not have an explicit rule on whether to keep them as colons or replace them with something else.
(。), though a fair number of colons still remain.
periods while reading adds unnecessary cognitive load.
feel more natural:
to what comes next
For the reasons above, I created this PR.
I realize the timing may not be ideal given the ongoing v6 preparation, but without an explicit rule, we risk continuing to produce inconsistent translations that create a stressful reading experience for users🤔
Additional info
It might be worth illustrating this rule with conforming and non-conforming examples, similar to the "Spaces around alphanumeric characters (### 英数字前後のスペース)" section.