From ddb18e644b4e32f4715fc5df9eef4039ff7436d0 Mon Sep 17 00:00:00 2001
From: Bill Huang <bill.huang2001@gmail.com>
Date: Wed, 31 Jan 2024 15:47:31 +0800
Subject: [PATCH] doc: fix translation confliction

---
 docs/source/guide/advanced/2-jit-able.md  | 14 +++++++-------
 docs/source/locale/zh/LC_MESSAGES/docs.po | 20 ++++++++++++++------
 2 files changed, 21 insertions(+), 13 deletions(-)

diff --git a/docs/source/guide/advanced/2-jit-able.md b/docs/source/guide/advanced/2-jit-able.md
index 553c0c92..b1f800b9 100644
--- a/docs/source/guide/advanced/2-jit-able.md
+++ b/docs/source/guide/advanced/2-jit-able.md
@@ -24,13 +24,13 @@ And since `bar` uses the dynamic index, which is not compatible with `jax.jit`,
 To solve is problem, it is common practice to jit-compile low-level components, thus giving high-level components more freedom.
 In EvoX, we have some general rules on whether a function should be jit-able or not.
 
-| Component | jit-able |
-| --------- | -------- |
-| Workflow  | Optional |
-| Algorithm | Yes      |
-| Problem   | Optional |
-| Operators | Yes      |
-| Monitor   | No       |
+|  Component  | jit-able |
+| ----------- | -------- |
+| `Workflow`  | Optional |
+| `Algorithm` | Yes      |
+| `Problem`   | Optional |
+| `Operators` | Yes      |
+| `Monitor`   | No       |
 
 For standard workflow, one can jit compile when not using monitors and working with jit-able problems.
 But even though the workflow can be compiled, there isn't much performance gain.
diff --git a/docs/source/locale/zh/LC_MESSAGES/docs.po b/docs/source/locale/zh/LC_MESSAGES/docs.po
index f105ee8a..fe63d370 100644
--- a/docs/source/locale/zh/LC_MESSAGES/docs.po
+++ b/docs/source/locale/zh/LC_MESSAGES/docs.po
@@ -2632,7 +2632,8 @@ msgid "jit-able"
 msgstr "可以被jit编译的"
 
 #: ../../source/guide/advanced/2-jit-able.md
-msgid "Workflow"
+#, fuzzy
+msgid "`Workflow`"
 msgstr "工作流"
 
 #: ../../source/guide/advanced/2-jit-able.md
@@ -2640,7 +2641,8 @@ msgid "Optional"
 msgstr "可选的"
 
 #: ../../source/guide/advanced/2-jit-able.md
-msgid "Algorithm"
+#, fuzzy
+msgid "`Algorithm`"
 msgstr "算法"
 
 #: ../../source/guide/advanced/2-jit-able.md
@@ -2648,16 +2650,18 @@ msgid "Yes"
 msgstr "是的"
 
 #: ../../source/guide/advanced/2-jit-able.md
-msgid "Problem"
+#, fuzzy
+msgid "`Problem`"
 msgstr "问题"
 
 #: ../../source/guide/advanced/2-jit-able.md
-msgid "Operators"
+#, fuzzy
+msgid "`Operators`"
 msgstr "操作符"
 
 #: ../../source/guide/advanced/2-jit-able.md
-#: ../../source/guide/basics/1-start.ipynb:180002
-msgid "Monitor"
+#, fuzzy
+msgid "`Monitor`"
 msgstr "监控器"
 
 #: ../../source/guide/advanced/2-jit-able.md
@@ -3093,6 +3097,10 @@ msgid ""
 "component in our workflow. Introducing `monitor`."
 msgstr "你可能还会注意到，`step` 并没有提供任何反馈，比如优化的结果。这是因为我们的工作流中缺少另一个组件。这里介绍 `monitor`（监视器）。"
 
+#: ../../source/guide/basics/1-start.ipynb:180002
+msgid "Monitor"
+msgstr "监控器"
+
 #: ../../source/guide/basics/1-start.ipynb:180004
 msgid ""
 "Monitor is a standard way to monitor the intermediate values inside a "