docs: add admonition for incompatibility with * and ** in Chinese and Japanese in MDX v2+

[tats-u]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

** in **重要的中文。**其他的中文。 and **重要な日本語の文。**別の日本語の文。 will not treated as <strong> due to a regression in CommonMark spec 0.14+.
MDX v2+ strictly follow CM and have this regression.

commonmark/commonmark-spec#650

Test Plan

Test links

https://deploy-preview-9692--docusaurus-2.netlify.app/docs/migration/v3/#other-markdown-incompatibilities

Related issues/PRs

commonmark/commonmark-spec#650

[tats-u]

@Josh-Cena I would appreciate if you could provide a Chinese example.

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	089ebe7
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/65a556063c65150008b9376d
😎 Deploy Preview	https://deploy-preview-9692--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 76	🟢 98	🟢 100	🟢 100	🟠 89	Report
/docs/installation	🟠 87	🟢 98	🟢 100	🟢 100	🟠 89	Report
/docs/category/getting-started	🟠 76	🟢 100	🟢 100	🟢 90	🟠 89	Report
/blog	🟠 70	🟢 100	🟢 100	🟢 90	🟠 89	Report
/blog/preparing-your-site-for-docusaurus-v3	🟠 60	🟢 97	🟢 100	🟢 100	🟠 89	Report
/blog/tags/release	🟠 71	🟢 100	🟢 100	🟠 80	🟠 89	Report
/blog/tags	🟠 72	🟢 100	🟢 100	🟢 90	🟠 89	Report

[slorber]

Thanks

@tats-u don't forget to add a link to your docs edit preview in the PR, that makes it much faster to review for others:
https://deploy-preview-9692--docusaurus-2.netlify.app/docs/migration/v3/

This is a long text for a little issue. The goal here is not to document them all exhaustively and overwhelm users that migrate, most of them are not Chinese/japanese.

What about putting most of that content in <details> element, so that only the interested readers will expand it? (or brievly mention the problem, and link to a dedicated GitHub discussion?)

[tats-u]

don't forget to add a link to your docs edit preview in the PR,

I had thought that is not necessary. I have fixed the description and will add ones from an next PR.

a little issue

I doubt this because the official site of Docusaurus is also affected.

https://docusaurus-i18n-staging.netlify.app/ja/docs

https://docusaurus.io/zh-CN/docs/next

https://docusaurus-i18n-staging.netlify.app/ja/docs/static-assets#in-css

Note: Chinese has avoided this by adding an additional space.

https://docusaurus.io/zh-CN/docs/next/static-assets#in-css

I believe it is too frequent to be pushed into a detail element. Also it is difficult for most Chinese and Japanese users to understand the trigger condition of this problem by themselves. They will have to gaze into the CM spec, which is not for users, to find out the condition.
I believe there are few Japanese or Japanese people other than me who are sure to find out * and ** affected by this "specification".
This problem affects on relatively smaller numbers of people, but does relatively severely on them.

According to https://www.meilisearch.com/docs/learn/what_is_meilisearch/language, some other languages can be said to be affected:

• Hebrew
• Khmer
• Korean (I think less affected than Chinese or Japanese; it uses space to split clauses)
• Thai

What about putting most of that content in <details> element, so that only the interested readers will expand it?

Even if it were adopted, at least <details> must be unwrapped by intention in Japanese and Chinese translation.
Also I will try to shorten the description to make it unnecessary to wrap it into <detail>.

[slorber]

According to meilisearch.com/docs/learn/what_is_meilisearch/language, some other languages can be said to be affected

I'm ok to have a clear and concise description of the problem, including a list of all languages possibly affected, but I'd like to keep it short for others. Maybe at least put most of the examples in details element?

Even if it were adopted, at least

must be unwrapped by intention in Japanese and Chinese translation.

Hmm why not, but is this really necessary? We can just say that those supporting a list of languages should rather pay more attention to the following section.

[tats-u]

@slorber I found that it looks better to use <details> as you have said.
This offending "specification" requires us to understand the detailed conditions but it is too long for the outside of <details> even in Chinese or Japanese.

[tats-u]

@slorber I will use <details> in all languages. I revised the draft. You can review its content again.

[slorber]

Thanks 👍

I think it's still a bit too verbose, but let's move on

[tats-u]

@slorber Thank you for merging. I think we need to backport this (and #9471) to the 3.x branch because visitors on docusaurus.io view the content in the latest 3.x release first.

[slorber]

@slorber Thank you for merging. I think we need to backport this (and #9471) to the 3.x branch because visitors on docusaurus.io view the content in the latest 3.x release first.

Docs backports happen on main in the website/docs/versioned_docs folder. Feel free to open another PR with similar changes.

[tats-u]

That makes sense. Thank you for providing the helpful information.