fix(l10n): make Japanese anchors Crowdin-safe#453
Merged
Conversation
Purpose:
- Preserve Japanese docs anchor targets while allowing Crowdin to import the translations.
Before:
- JA translated headings used Docusaurus-style inline custom IDs such as {#vm-snapshots}.
- Docusaurus accepted that syntax, but Crowdin's MDX import parser rejected changed files with Acorn parse errors and surfaced only null through the CLI.
Why that was a problem:
- Seven updated JA docs could not be uploaded to Crowdin.
- Leaving the same syntax in other JA files would make future retranslations fail whenever those segments changed.
What changed:
- Replaced inline heading IDs with standalone MDX-valid <span id=...></span> anchors before the translated headings.
- Applied the rewrite across all JA docs that used the Crowdin-hostile heading ID form.
How it works:
- The rendered pages still contain the stable English anchor IDs for inbound links.
- The heading text remains translated and no longer contains MDX expression-like {#...} syntax that Crowdin rejects.
Contributor
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughMultiple Japanese MDX documents have had their heading anchor syntax changed: explicit Markdown fragment IDs ( Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
unraid-docs | 368723d | Commit Preview URL Branch Preview URL |
Apr 15 2026, 04:41 PM |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx (1)
47-47:⚠️ Potential issue | 🟡 MinorFix optional step numbering format in setup list.
Line 47 currently starts with
\+7.; this likely renders as plain text/bullet instead of ordered step 7.Suggested fix
- \+7.（任意）**Include Tailscale peers in /etc/hosts** を有効にし（[ホスト名解決の強化](`#enhanced-hostname-resolution`) を参照）、Tailscale デバイスをサーバーのホスト名解決に自動的に追加して、%%Tailnet|tailnet%% 上の他のデバイスへアクセスしやすくします。 +7. （任意）**Include Tailscale peers in /etc/hosts** を有効にし（[ホスト名解決の強化](`#enhanced-hostname-resolution`) を参照）、Tailscale デバイスをサーバーのホスト名解決に自動的に追加して、%%Tailnet|tailnet%% 上の他のデバイスへアクセスしやすくします。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx` at line 47, The ordered list item is prefixed with a stray escape sequence "\+7." so it will not render as step 7; update the line that contains "\+7.（任意）**Include Tailscale peers in /etc/hosts**…" to a proper ordered-list marker (e.g., "7.（任意）**Include Tailscale peers in /etc/hosts**…") by removing the leading backslash and plus so the markdown renders as step 7; verify the surrounding list items remain numerically consistent.
🧹 Nitpick comments (3)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md (1)
13-14: Normalize heading spacing after anchor insertion.These headings are immediately followed by content. Add one blank line below each heading to keep markdownlint behavior consistent.
Suggested diff
### 既知の問題 + #### プラグイン @@ ### ロールバック + 7.1.4 より前にロールバックする場合は、[7.1.4 リリースノート](7.1.4.md#rolling-back)も参照してください。 @@ #### Ext2/3/4、NTFS、exFAT のサポート + Unraid は、XFS、BTRFS、ZFS に加えて、Ext2/3/4、NTFS、および exFAT のドライブ形式をサポートするようになりました。Also applies to: 25-26, 50-51
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md` around lines 13 - 14, The headings "### 既知の問題" and "#### プラグイン" (and the other heading pairs at the same spots referenced) are immediately followed by content; add a single blank line after each of these markdown headings so there is an empty line between the heading and the subsequent paragraph/content (i.e., insert one newline after the "### 既知の問題" and after each "#### プラグイン" occurrence to normalize heading spacing and satisfy markdownlint).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md (1)
28-29: Add one blank line below the heading to satisfy MD022.Line 28 is immediately followed by paragraph text. A single empty line keeps markdownlint clean.
Suggested diff
### ロールバック + 6.12.13 より前のバージョンにロールバックする場合は、[6.12.13 のリリースノート](6.12.13.md#rolling-back)も参照してください。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md` around lines 28 - 29, The "### ロールバック" heading is immediately followed by paragraph text which triggers MD022; insert a single blank line after the "### ロールバック" heading so there is one empty line between the heading and the following paragraph (edit the block containing the "### ロールバック" heading in 6.12.14.md to add that blank line).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md (1)
9-10: Add a blank line after these headings to satisfy MD022.Line 9 and Line 20 are followed immediately by paragraph text. Insert one empty line below each heading to clear the markdownlint warning cleanly.
Suggested diff
### 既知の問題 + このリリースには潜在的なデータ損失の問題があり、最近の "mover empty disk" 機能が共有のスプリットレベルを正しく処理しません。7.1.2 で解決済みです。 @@ ### ロールバック + リリース間でのパッチ配布方法を改善しているため、このリリースでは単体の Patch Plugin はアンインストールされます。以前のリリースにロールバックする場合は、再インストールすることをお勧めします。詳細は追ってお知らせします。Also applies to: 20-21
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md` around lines 9 - 10, Add a blank line immediately after the heading "### 既知の問題" (and the other similar heading that precedes a paragraph) so the heading is separated from the following paragraph to satisfy markdownlint rule MD022; locate the headings in the release-notes markdown (e.g., "### 既知の問題") and insert a single empty line below each heading before the paragraph text.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md`:
- Around line 45-46: The markdown heading "### ロールバック" is missing a blank line
after it (MD022); update the section by inserting one empty newline directly
after the "### ロールバック" heading so the heading is separated from the following
paragraph ("6.12.11 より前のバージョンへ..."), ensuring the file's heading/paragraph
spacing is valid for the linter.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md`:
- Around line 5-6: The markdown headings "## アップグレードに関する注意事項" and the heading at
lines around where the Japanese text starting on line 52 are immediately
followed by paragraph text and violate MD022; fix by inserting a single blank
line directly after each affected heading so there is an empty line between the
heading and the following paragraph (update the two headings: "##
アップグレードに関する注意事項" and the second heading near line 52).
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md`:
- Around line 45-46: Add a blank line immediately after the heading "### ロールバック"
to satisfy markdownlint rule MD022; in the file's markdown where the heading
"### ロールバック" is followed directly by paragraph text, insert one empty line
between the heading and the paragraph so the heading is separated from the
content.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md`:
- Around line 9-10: The markdown headings are immediately followed by text which
violates markdownlint MD022; add a single blank line after the heading "###
既知の問題" and likewise after the heading before line 14 so that the link line
"[7.1.0 リリースノート](7.1.0.md#known-issues)" and the paragraph on line 14 are
separated from their preceding headings by one blank line, ensuring
blanks-around-headings is satisfied.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md`:
- Around line 13-19: The headings "### 既知の問題" and "### ロールバック" (and the inline
span id "rolling-back") currently lack the required blank line below them,
triggering markdownlint MD022; update the file so there is a single blank line
immediately after each of these headings (and after the <span
id="rolling-back"></span> if it sits on its own line) to satisfy MD022 while
leaving the rest of the content unchanged.
---
Outside diff comments:
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx`:
- Line 47: The ordered list item is prefixed with a stray escape sequence "\+7."
so it will not render as step 7; update the line that contains
"\+7.（任意）**Include Tailscale peers in /etc/hosts**…" to a proper ordered-list
marker (e.g., "7.（任意）**Include Tailscale peers in /etc/hosts**…") by removing
the leading backslash and plus so the markdown renders as step 7; verify the
surrounding list items remain numerically consistent.
---
Nitpick comments:
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md`:
- Around line 28-29: The "### ロールバック" heading is immediately followed by
paragraph text which triggers MD022; insert a single blank line after the "###
ロールバック" heading so there is one empty line between the heading and the following
paragraph (edit the block containing the "### ロールバック" heading in 6.12.14.md to
add that blank line).
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md`:
- Around line 9-10: Add a blank line immediately after the heading "### 既知の問題"
(and the other similar heading that precedes a paragraph) so the heading is
separated from the following paragraph to satisfy markdownlint rule MD022;
locate the headings in the release-notes markdown (e.g., "### 既知の問題") and insert
a single empty line below each heading before the paragraph text.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Around line 13-14: The headings "### 既知の問題" and "#### プラグイン" (and the other
heading pairs at the same spots referenced) are immediately followed by content;
add a single blank line after each of these markdown headings so there is an
empty line between the heading and the subsequent paragraph/content (i.e.,
insert one newline after the "### 既知の問題" and after each "#### プラグイン" occurrence
to normalize heading spacing and satisfy markdownlint).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 6456a859-ea3c-4d7a-a7c1-6b110681fa3f
📒 Files selected for processing (48)
i18n/ja/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/overview.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
Comment on lines
45
to
46
| ### ロールバック | ||
| 6.12.11 より前のバージョンへロールバックする場合は、[6.12.11 のリリースノート](6.12.11.md#rolling-back)も参照してください。 |
Contributor
There was a problem hiding this comment.
Add a blank line after the heading to satisfy MD022.
Line 45 (### ロールバック) should be followed by a blank line before body text.
Suggested fix
### ロールバック
+
6.12.11 より前のバージョンへロールバックする場合は、[6.12.11 のリリースノート](6.12.11.md#rolling-back)も参照してください。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ### ロールバック | |
| 6.12.11 より前のバージョンへロールバックする場合は、[6.12.11 のリリースノート](6.12.11.md#rolling-back)も参照してください。 | |
| ### ロールバック | |
| 6.12.11 より前のバージョンへロールバックする場合は、[6.12.11 のリリースノート](6.12.11.md#rolling-back)も参照してください。 |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md`
around lines 45 - 46, The markdown heading "### ロールバック" is missing a blank line
after it (MD022); update the section by inserting one empty newline directly
after the "### ロールバック" heading so the heading is separated from the following
paragraph ("6.12.11 より前のバージョンへ..."), ensuring the file's heading/paragraph
spacing is valid for the linter.
Comment on lines
5
to
6
| ## アップグレードに関する注意事項 | ||
| このリリースには、非常に重要な修正が 2 つ含まれています。まず、最近の |
Contributor
There was a problem hiding this comment.
Add blank lines below headings to satisfy markdownlint (MD022).
Line 5 and Line 52 headings are immediately followed by paragraph text.
✅ Proposed lint fix
## アップグレードに関する注意事項
+
このリリースには、非常に重要な修正が 2 つ含まれています。まず、最近の
...
### ロールバック
+
以前のリリースにロールバックすると、Docker のセキュリティ問題および [Upgrade notes](`#upgrade-notes`) に記載されているデータ損失の可能性があるシナリオに対してシステムが脆弱になりますのでご注意ください。Also applies to: 52-53
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md`
around lines 5 - 6, The markdown headings "## アップグレードに関する注意事項" and the heading
at lines around where the Japanese text starting on line 52 are immediately
followed by paragraph text and violate MD022; fix by inserting a single blank
line directly after each affected heading so there is an empty line between the
heading and the following paragraph (update the two headings: "##
アップグレードに関する注意事項" and the second heading near line 52).
Comment on lines
45
to
46
| ### ロールバック | ||
| 「Docker Patch 6.12.8」の機能は現在、Unraid に組み込まれています。6.12.8 にロールバックする場合は、そのプラグインを再インストールするとよいでしょう。 |
Contributor
There was a problem hiding this comment.
Add a blank line after the rollback heading to satisfy markdownlint.
MD022 expects a blank line below the heading before paragraph content.
Suggested fix
### ロールバック
+
「Docker Patch 6.12.8」の機能は現在、Unraid に組み込まれています。6.12.8 にロールバックする場合は、そのプラグインを再インストールするとよいでしょう。🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md`
around lines 45 - 46, Add a blank line immediately after the heading "###
ロールバック" to satisfy markdownlint rule MD022; in the file's markdown where the
heading "### ロールバック" is followed directly by paragraph text, insert one empty
line between the heading and the paragraph so the heading is separated from the
content.
Comment on lines
9
to
10
| ### 既知の問題 | ||
| [7.1.0 リリースノート](7.1.0.md#known-issues) もご覧ください。 |
Contributor
There was a problem hiding this comment.
Add blank lines after headings to satisfy markdownlint MD022.
Line 9 and Line 14 are followed immediately by paragraph lines, which triggers blanks-around-headings.
💡 Suggested fix
<span id="known-issues"></span>
### 既知の問題
+
[7.1.0 リリースノート](7.1.0.md#known-issues) もご覧ください。
<span id="rolling-back"></span>
### ロールバック
+
[7.1.0 リリースノート](7.1.0.md#rolling-back) をご覧ください。Also applies to: 14-15
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md`
around lines 9 - 10, The markdown headings are immediately followed by text
which violates markdownlint MD022; add a single blank line after the heading
"### 既知の問題" and likewise after the heading before line 14 so that the link line
"[7.1.0 リリースノート](7.1.0.md#known-issues)" and the paragraph on line 14 are
separated from their preceding headings by one blank line, ensuring
blanks-around-headings is satisfied.
Comment on lines
13
to
19
| ### 既知の問題 | ||
| その他の既知の問題については、[7.2.1 リリースノート](7.2.1.md#known-issues) を参照してください。 | ||
|
|
||
| ### ロールバック {#rolling-back} | ||
| <span id="rolling-back"></span> | ||
|
|
||
| ### ロールバック | ||
| 7.2.1 より前にロールバックする場合は、[7.2.1 リリースノート](7.2.1.md#rolling-back) も参照してください。 |
Contributor
There was a problem hiding this comment.
Add blank lines below the updated headings to satisfy MD022.
The touched headings currently violate markdownlint MD022 (no blank line below heading).
✏️ Suggested fix
### 既知の問題
+
その他の既知の問題については、[7.2.1 リリースノート](7.2.1.md#known-issues) を参照してください。
@@
### ロールバック
+
7.2.1 より前にロールバックする場合は、[7.2.1 リリースノート](7.2.1.md#rolling-back) も参照してください。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ### 既知の問題 | |
| その他の既知の問題については、[7.2.1 リリースノート](7.2.1.md#known-issues) を参照してください。 | |
| ### ロールバック {#rolling-back} | |
| <span id="rolling-back"></span> | |
| ### ロールバック | |
| 7.2.1 より前にロールバックする場合は、[7.2.1 リリースノート](7.2.1.md#rolling-back) も参照してください。 | |
| ### 既知の問題 | |
| その他の既知の問題については、[7.2.1 リリースノート](7.2.1.md#known-issues) を参照してください。 | |
| <span id="rolling-back"></span> | |
| ### ロールバック | |
| 7.2.1 より前にロールバックする場合は、[7.2.1 リリースノート](7.2.1.md#rolling-back) も参照してください。 |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 13-13: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 18-18: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md`
around lines 13 - 19, The headings "### 既知の問題" and "### ロールバック" (and the inline
span id "rolling-back") currently lack the required blank line below them,
triggering markdownlint MD022; update the file so there is a single blank line
immediately after each of these headings (and after the <span
id="rolling-back"></span> if it sits on its own line) to satisfy MD022 while
leaving the rest of the content unchanged.
- Purpose: align Japanese translated heading anchors with the Docusaurus-recommended MDX-safe custom ID syntax.
- Before: the prior fix used standalone span anchors before translated headings to preserve English anchor targets.
- Problem: standalone spans preserved links but separated the anchor from the heading and did not match Docusaurus documentation guidance.
- New behavior: Japanese headings now keep stable English anchor IDs directly on the heading via MDX comments, such as '### Heading {/* #anchor */}'.
- Implementation: mechanically converted 132 span anchors across 48 Japanese docs files to heading-level MDX comments without changing the visible translated text.
- Purpose: capture the Crowdin-safe anchor pattern for future translated MDX edits.
- Before: repo guidance covered validation only, so future agents could repeat the rejected classic heading ID syntax or the temporary span workaround.
- Problem: Crowdin's MDX import parser can reject translated headings ending with classic '{#anchor}' IDs even when Docusaurus accepts them.
- New behavior: AGENTS.md now recommends Docusaurus's MDX-safe heading comment syntax and discourages standalone span anchors unless specifically required.
- Implementation: add a Markdown and Localization section with the preferred '### Heading {/* #stable-anchor */}' pattern.
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
1 participant
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.
Summary
### 見出し {/* #anchor */}.{#anchor}heading ID syntax, not only the seven files that failed today.Root cause
Crowdin's translation import parser rejects changed JA MDX segments that end translated headings with classic Docusaurus custom heading IDs like
{#anchor}. The CLI surfaced this asnull, but the Crowdin import API reported errors such as:MDX file is invalid in line 61, column 65. Message: Could not parse expression with acorn: Unexpected tokenThe reported lines were translated headings ending in
{#...}. Docusaurus accepts that syntax through its Markdown plugin chain, but it is not valid plain MDX for Crowdin's import parser. Docusaurus documents the MDX-safe equivalent as### Hello World {/* #my-explicit-id */}, so the JA files now use that syntax directly on the headings.Verification
@mdx-js/mdx; failures=0.<span id="..."></span>anchors from the temporary workaround.Heading {#anchor}syntax.git diff --checksuccessfully.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxfinished successfully: import IDd1e16d86-59d1-42d7-927f-c5cae77aa115.docs/unraid-os/release-notes/7.2.5.mdis not present in Crowdin yet; all 48 PR files had successful JA upload lines in/tmp/crowdin-ja-upload-after-comment-anchor-fix.log.Full Docusaurus build was not run per repo validation guidance.
Summary by CodeRabbit