Have you read the Contributing Guidelines on issues?
Motivation
We have to insert extra spaces for workaround:
Docusaurus 3 has a regression that asterisks */** around punctuation including ` representing inline codes and [/] representing links are not recognized as emphasis. This affects especially on Chinese and Japanese documents.
https://docusaurus.io/docs/next/migration/v3#other-markdown-incompatibilities suggests using remark-cjk-friendly (#10892) but it should be opt-in or opt-out in the future.
There are two proposed methods for setting it up:
import type { Config } from "@docusaurus/types";
import type { Options } from "@docusaurus/preset-classic";
const config: Config = {
// *snip*
markdown: {
cjkFriendlyEmphasis: true, // Plan (1)
},
presets: [
[
"classic":
{
cjkFriendlyEmphasis: true, // Plan (2),
// *snip*
} as Options
],
],
// *snip*
};
export default config;Also there are 3 proposed strategies for enabling it:
- opt-out & dependencies
- opt-in & dependencies
- opt-in & optional peerDependencies (users need to run
pnpm add remark-cjk-friendly remark-cjk-friendly-strikethrough)
Self-service
Have you read the Contributing Guidelines on issues?
Motivation
remark-cjk-friendly) instead of plain CommonMark/GFM emphasis web-infra-dev/rspress#2772remark-cjk-friendlyin migration guide #10892We have to insert extra spaces for workaround:
Docusaurus 3 has a regression that asterisks
*/**around punctuation including`representing inline codes and[/]representing links are not recognized as emphasis. This affects especially on Chinese and Japanese documents.https://docusaurus.io/docs/next/migration/v3#other-markdown-incompatibilities suggests using
remark-cjk-friendly(#10892) but it should be opt-in or opt-out in the future.There are two proposed methods for setting it up:
Also there are 3 proposed strategies for enabling it:
pnpm add remark-cjk-friendly remark-cjk-friendly-strikethrough)Self-service