Merge pull request #3423 from GeorgeHu6/chinese-translation

Docs: Update Chinese translation

docs/locale/zh_CN/LC_MESSAGES/faq.po

@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PELICAN 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-07-31 22:54+0800\n"
+"POT-Creation-Date: 2024-11-07 16:25+0800\n"
 "PO-Revision-Date: 2024-06-27 19:00+0800\n"
 "Last-Translator: GeorgeHu <dhxxhch@163.com>\n"
 "Language: zh_CN\n"
@@ -16,29 +16,29 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.15.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../faq.rst:2 87acb7c16d974b4eb060949b8ce40914
+#: ../../faq.rst:2 84467b3ab4b8411589855b3130e14406
 msgid "Frequently Asked Questions (FAQ)"
 msgstr "常见问题解答"
 
-#: ../../faq.rst:4 76aee892f7f14d0590db2d76c7cc0123
+#: ../../faq.rst:4 54c28b1640fd4939b5f196fa377292eb
 msgid "Here are some frequently asked questions about Pelican."
 msgstr "以下是一些Pelican的常见问题解答。"
 
-#: ../../faq.rst:7 c98549fdd5814984bfa3a6eaf4631d37
+#: ../../faq.rst:7 a95f8f3dcb6741949ba9d4761199dd0a
 msgid "What's the best way to communicate a problem, question, or suggestion?"
 msgstr "交流问题、疑问或提建议的最佳方式是什么？"
 
-#: ../../faq.rst:9 dbecb306adeb482ba3b9bd68483bc372
+#: ../../faq.rst:9 d93f8424407d42b2b3ce37b39baecd8a
 msgid "Please read our :doc:`feedback guidelines <contribute>`."
 msgstr "请参阅文档 :doc:`项目贡献与意见反馈 <contribute>` 。"
 
-#: ../../faq.rst:12 8fe91d51140946f1b2cb131d786c1814
+#: ../../faq.rst:12 9fea72b4670c4fe6a3d67e1ddb158f47
 msgid "How can I help?"
 msgstr "我可以帮上什么忙？"
 
-#: ../../faq.rst:14 d8477da414c446b3936e73931eb4f63a
+#: ../../faq.rst:14 3f4b88cf5b814e678a552c821ae4b450
 msgid ""
 "There are several ways to help out. First, you can communicate any "
 "Pelican suggestions or problems you might have via `Pelican Discussions "
@@ -50,7 +50,7 @@ msgstr ""
 "<https://github.com/getpelican/pelican/discussions>`_ "
 "中提出任何关于Pelican的建议或是问题。在提问或建议之前，请先查看已关闭或开放的issues中是否已有相关内容，以避免内容上的重复。"
 
-#: ../../faq.rst:20 95a29a97e08a452f89aa4eaad191b698
+#: ../../faq.rst:20 ca9e66682caf43a481ca91ecace43ed0
 msgid ""
 "If you want to contribute, please fork `the Git repository "
 "<https://github.com/getpelican/pelican/>`_, create a new feature branch, "
@@ -62,17 +62,17 @@ msgstr ""
 "，创建一个新的功能分支，并在其中进行修改，在修改完成后提出一个PR。项目组会尽快审核你的PR。关于此的更多内容，请参见 "
 ":doc:`项目贡献与意见反馈 <contribute>` 一节。"
 
-#: ../../faq.rst:26 bf7a6828eec74dc588c18e185bdd7090
+#: ../../faq.rst:26 f05e9b722b084a439cd6d99b3155910d
 msgid ""
 "You can also contribute by creating themes and improving the "
 "documentation."
 msgstr "你可以发起的贡献当然也包括创建主题和改进文档。"
 
-#: ../../faq.rst:29 2ce846241ce744fd81981a376d3f5fe2
+#: ../../faq.rst:29 d40c58aeafe54bdaa389c3c05a0fd721
 msgid "Is the Pelican settings file mandatory?"
 msgstr "Pelican配置文件是必要的吗？"
 
-#: ../../faq.rst:31 527720062339422095e2c95755af5584
+#: ../../faq.rst:31 96ef0c57471d4a669bd7f2a7f493c23b
 msgid ""
 "Configuration files are optional and are just an easy way to configure "
 "Pelican. For basic operations, it's possible to specify options while "
@@ -82,11 +82,11 @@ msgstr ""
 "配置文件是可选的，其本质是使您可以更方便地配置Pelican。对于一些基本的配置操作，完全可以在命令行中指定，调用 ``pelican "
 "--help`` 可以查看pelican命令的更多信息。"
 
-#: ../../faq.rst:36 d0ca19a2e40c4ecaa9ecba6cc677f142
+#: ../../faq.rst:36 e3752aec18514ce292ee4ebd0d95db37
 msgid "Changes to the settings file take no effect"
 msgstr "修改后的配置文件没有生效"
 
-#: ../../faq.rst:38 5b741cbb28854893818826c593f8e323
+#: ../../faq.rst:38 3f5c632fd20446cf8dd70a5eb88dbbcf
 msgid ""
 "When experimenting with different settings (especially the metadata ones)"
 " caching may interfere and the changes may not be visible. In such cases,"
@@ -96,11 +96,11 @@ msgstr ""
 "在尝试不同的配置时（尤其是尝试不同元数据时），缓存很可能会产生干扰，使得修改不可见。此时，确保配置了 ``LOAD_CONTENT_CACHE ="
 " False`` 或在命令行中加上 ``--ignore-cache`` 以禁用缓存。"
 
-#: ../../faq.rst:44 439f2221927b42f7a4c219ab1a76f849
+#: ../../faq.rst:44 067892211d0d4f4bae85d65a0132eb1d
 msgid "I'm creating my own theme. How do I use Pygments for syntax highlighting?"
 msgstr "在自己创建主题时，如何使用Pygments来调整语法高亮？"
 
-#: ../../faq.rst:46 3475c1550e584c84a118ac061461f9f6
+#: ../../faq.rst:46 b1e6ed1bea2e4b3cb3798131f30a828c
 msgid ""
 "Pygments adds some classes to the generated content. These classes are "
 "used by themes to style code syntax highlighting via CSS. Specifically, "
@@ -114,30 +114,49 @@ msgstr ""
 "``.highlight pre`` 类来自定义语法高亮的外观。在 `Pygments 项目的demo网站 "
 "<https://pygments.org/demo/>`_ 上可以预览能够渲染的代码类型。"
 
-#: ../../faq.rst:53 ecffb1f9501f46c88f799b79fc0ba343
+#: ../../faq.rst:53 5dccc8ae367545b08bdce61e008e0a20
 msgid ""
 "You can use the following example commands to generate a starting CSS "
 "file from a Pygments built-in style (in this case, \"monokai\") and then "
 "copy the generated CSS file to your new theme::"
 msgstr "你可以使用下面的命令来让Pygments使用内置风格（此处为“monokai”）生成一个初始CSS文件，然后将此文件拷贝到新主题中："
 
-#: ../../faq.rst:60 8fc71763c5c243339c9e737cc55b99da
+#: ../../faq.rst:60 027edae1ebdf4d52b59171a26915c1ac
 msgid "Don't forget to import your ``pygment.css`` file from your main CSS file."
 msgstr "不要忘了在你的CSS主文件中引入  ``pygment.css`` 文件。"
 
-#: ../../faq.rst:63 ad118f1f46db423fab19f570cd789798
+#: ../../faq.rst:63 164af3be4dce45879963c5d3ee0cd264
 msgid "How do I create my own theme?"
 msgstr "如何创建我自己的主题？"
 
-#: ../../faq.rst:65 1674585960e742cbade644b63d3bb32a
+#: ../../faq.rst:65 7b1db6528b0a4735894868a229a5969d
 msgid "Please refer to :ref:`theming-pelican`."
 msgstr "请参阅 :ref:`theming-pelican` 。"
 
-#: ../../faq.rst:68 b06c6a8df1634d20b988515af6536e2c
+#: ../../faq.rst:68 b8e21f837e0744c49cfe8f0cb3a1d5ee
+msgid "Can I override individual templates without forking the whole theme?"
+msgstr "我只需要覆盖主题中单独的几个模板文件，可不可以不fork整个主题？"
+
+#: ../../faq.rst:70 70fd7b5c55c246a6a25b20304bfdb616
+msgid ""
+"Yes, you can override existing templates of the theme that you are using,"
+" or add new templates, via the ``THEME_TEMPLATES_OVERRIDES`` variable. "
+"For example, to override the page template, you can define the location "
+"for your templates like this::"
+msgstr "当然可以，覆盖部分模板文件或是添加一些模板文件都是可以的，使用 ``THEME_TEMPLATES_OVERRIDES`` 变量即可。"
+"例如，若需要覆盖page的模板，可以向这样定义你自己的模板文件位置："
+
+#: ../../faq.rst:77 a96870f0cad74996bec2469ea0c2e9e1
+msgid ""
+"You can then define a custom template in ``templates/page.html``. See "
+":ref:`settings/themes` for details."
+msgstr "自定义的模板可以为 ``templates/page.html`` 。详情请参看 :ref:`settings/themes` 。"
+
+#: ../../faq.rst:81 b832cd952cf44a0097f383825f0f295f
 msgid "I want to use Markdown, but I got an error."
 msgstr "我想要使用Markdown，但是出错了。"
 
-#: ../../faq.rst:70 c0a89314dbdf4368b2e32d781c0ae95b
+#: ../../faq.rst:83 32d9dbde7029412d852ab8e710112573
 msgid ""
 "If you try to generate Markdown content without first installing the "
 "Markdown library, you may see a message that says ``No valid files found "
@@ -151,77 +170,79 @@ msgstr ""
 "。虽然Markdown并不是必需依赖，但如果你写的内容中含有Markdown格式，就需要安装Markdown库了。输入下面的命令以安装Markdown库，如果需要权限，请在前面添加"
 " ``sudo`` ："
 
-#: ../../faq.rst:80 a4c93b71eb914652b3f05357067f87b3
+#: ../../faq.rst:93 46728a367ffe47d9afeb7608e9c0db5f
 msgid "Can I use arbitrary metadata in my templates?"
 msgstr "在模板中可以使用任意元数据吗？"
 
-#: ../../faq.rst:82 6ac1579e5d8842f5bf97b87745848c6a
+#: ../../faq.rst:95 9b7fbafc6d29429a88a079bfb74e3af5
 msgid ""
 "Yes. For example, to include a modified date in a Markdown post, one "
 "could include the following at the top of the article::"
 msgstr "当然可以。例如，可以在Markdown帖子中包含一个“修改日期”，加在文章开头即可："
 
-#: ../../faq.rst:87 d1ad8fa8e07c4500ab754962064749a8
+#: ../../faq.rst:100 ce62442a4c9d4347bd6ae8a59476fcee
 msgid ""
 "For reStructuredText, this metadata should of course be prefixed with a "
 "colon::"
 msgstr "对于reStructuredText，此元数据也应当以冒号为前缀："
 
-#: ../../faq.rst:91 e3c9814b5b3849a7957f964565038e45
+#: ../../faq.rst:104 bf869a6da43e448a9cc512843aa4a183
 msgid ""
 "This metadata can then be accessed in templates such as ``article.html`` "
 "via::"
 msgstr "此元数据可以在模板中获取到，例如在 ``article.html`` 中，可以像这样获取："
 
-#: ../../faq.rst:97 11d953b5718c4baeb7f7fbbb9538c763
+#: ../../faq.rst:110 b9c9a648b30942b996b124af9fd5a84c
 msgid ""
 "If you want to include metadata in templates outside the article context "
 "(e.g., ``base.html``), the ``if`` statement should instead be::"
 msgstr "如果您想在其他模板（例如 ``base.html`` ）中获取此元数据，则 ``if`` 语句应改为："
 
-#: ../../faq.rst:103 99ca0aeea6d14c159cf1f1b8d9cf016d
+#: ../../faq.rst:116 b78a678a165d40f4823fac2b19bcafc1
 msgid ""
 "How do I make my output folder structure identical to my content "
 "hierarchy?"
 msgstr "如何使得输出目录的结构和content目录的结构保持一致？"
 
-#: ../../faq.rst:105 e97223e6c7c94c08a1d42f783fd67f7e
+#: ../../faq.rst:118 851d1019c070482991667cc024063d29
 msgid "Try these settings::"
 msgstr "可以尝试如下配置："
 
-#: ../../faq.rst:112 d35f11a227ba421596458ea8f26ecde0
+#: ../../faq.rst:125 5195876e3f364a838d72b16c568263bc
 msgid "How do I assign custom templates on a per-page basis?"
 msgstr "如何为某个页面指定某个模板？"
 
-#: ../../faq.rst:114 287bac0946dc47feab068bdb76d0bc2e
+#: ../../faq.rst:127 2ddd3cf1fbf048b1819bcfc9b3691a12
 msgid ""
 "It's as simple as adding an extra line of metadata to any page or article"
 " that you want to have its own template. For example, this is how it "
 "would be handled for content in reST format::"
 msgstr "这非常简单，在任何页面或者文章中，都可以通过多添加一行元数据来指定特定模板。例如，在reST中，使用："
 
-#: ../../faq.rst:120 b845784299bf47629e616505000724c1
+#: ../../faq.rst:133 6f5eb40b4a5e4f83ab9d1cb48fefad57
 msgid "For content in Markdown format::"
 msgstr "对于Markdown，则使用："
 
-#: ../../faq.rst:124 fa734dbb540e4cda8a5be5fb1b2da124
+#: ../../faq.rst:137 2e28d1bf074c437eb5017bf6f345bf71
 msgid ""
 "Then just make sure your theme contains the relevant template file (e.g. "
-"``template_name.html``)."
-msgstr "确保对应的模板文件在主题中存在即可（例如 ``template_name.html`` ）。"
+"``template_name.html``). If you just want to add a new custom template to"
+" an existing theme, you can also provide it in a directory specified by "
+"``THEME_TEMPLATES_OVERRIDES`` (see :ref:`settings/themes`)."
+msgstr ""
 
-#: ../../faq.rst:128 bdee9be4397f4839855295ee1a0fdd12
+#: ../../faq.rst:142 675e77f99f3c42bb8715c84a97c7a064
 msgid "How can I override the generated URL of a specific page or article?"
 msgstr "如何重写某一个页面或文章生成的URL？"
 
-#: ../../faq.rst:130 ed91b5bdcbe24473a6fed738784311b8
+#: ../../faq.rst:144 7e518b99b29d4787addc732d57e94ed1
 msgid ""
 "Include ``url`` and ``save_as`` metadata in any pages or articles that "
 "you want to override the generated URL. Here is an example page in reST "
 "format::"
 msgstr "在任意页面或文章中都可以添加 ``url`` 和 ``save_as`` 元数据，这样就可以重写URL了。下面以reST格式为例："
 
-#: ../../faq.rst:139 5aa733d8d3bd4d86920e7e142715b1f4
+#: ../../faq.rst:153 903306ecaed3483591b4ed2dcba3d183
 msgid ""
 "With this metadata, the page will be written to "
 "``override/url/index.html`` and Pelican will use the URL "
@@ -230,18 +251,18 @@ msgstr ""
 "有了这样的元数据，此页面会保存为 ``override/url/index.html`` ，Pelican会将 ``override/url/``"
 " 作为链接到此页面的URL。"
 
-#: ../../faq.rst:143 04d9890aa34d4c1e86bc7a49cd64938a
+#: ../../faq.rst:157 d80d84fcb6844e25a8452e29c4113181
 msgid "How can I use a static page as my home page?"
 msgstr "如何使用一个静态页面作为主页？"
 
-#: ../../faq.rst:145 d3e8a4e2d453446f9037fa46e6775080
+#: ../../faq.rst:159 e17a2e2dd9014109888bab9286ee607c
 msgid ""
 "The override feature mentioned above can be used to specify a static page"
 " as your home page. The following Markdown example could be stored in "
 "``content/pages/home.md``::"
 msgstr "上一个问题中提到的特性可以用于实现此需求。下面例子中的Markdown文件保存为 ``content/pages/home.md`` ："
 
-#: ../../faq.rst:155 739da75e7ce946af99c9f577e8a284ff
+#: ../../faq.rst:169 b99ba0ca8656416cbdc38f3fa263b7eb
 msgid ""
 "If the original blog index is still wanted, it can then be saved in a "
 "different location by setting ``INDEX_SAVE_AS = 'blog_index.html'`` for "
@@ -250,11 +271,11 @@ msgstr ""
 "如果仍需要原来的博客主页（即 ``'index'`` 直接模板），可以通过设置 ``INDEX_SAVE_AS = "
 "'blog_index.html'`` 将其存储在其他位置。"
 
-#: ../../faq.rst:160 5224f09821d24e4a8db6870da1266a20
+#: ../../faq.rst:174 fca4725a57dd451fb3b0fb9df78f69b5
 msgid "What if I want to disable feed generation?"
 msgstr "可以禁用订阅源生成吗？"
 
-#: ../../faq.rst:162 8f014ffab3c44b0ebf2b0d9872bfbfa7
+#: ../../faq.rst:176 e9c08140e2ed44f189a7a156db027a3e
 msgid ""
 "To disable feed generation, all feed settings should be set to ``None``. "
 "All but three feed settings already default to ``None``, so if you want "
@@ -264,19 +285,19 @@ msgstr ""
 "要禁用订阅源，所有订阅源相关的配置都应被设为 ``None`` 。其中有三项设置默认为 ``None`` "
 "，因此如果要彻底不生成订阅源，你只需要指定下面这些设置："
 
-#: ../../faq.rst:172 9ab29ccca83c4ecfabcb3ad4dd17c751
+#: ../../faq.rst:186 7820a481af4c4f44a40fb3ae80768a1d
 msgid ""
 "The word ``None`` should not be surrounded by quotes. Please note that "
 "``None`` and ``''`` are not the same thing."
 msgstr "``None`` 两侧不需要加引号。请注意 ``None`` 和 ``''`` 不是同一个东西。"
 
-#: ../../faq.rst:176 fd8cbe4962d145ccadfd480419dbea9e
+#: ../../faq.rst:190 4fa2ffbf1c274ec396a0d756762c260d
 msgid ""
 "I'm getting a warning about feeds generated without SITEURL being set "
 "properly"
 msgstr "Pelican警告说由于SITEURL设置不正确，无法正常生成订阅源"
 
-#: ../../faq.rst:178 e3135e5903ec422f8d7895866ca6f365
+#: ../../faq.rst:192 8d52f14f6b03476897dfb15c188a961a
 msgid ""
 "`RSS and Atom feeds require all URL links to be absolute "
 "<https://validator.w3.org/feed/docs/rss2.html#comments>`_. In order to "
@@ -287,17 +308,17 @@ msgstr ""
 "<https://validator.w3.org/feed/docs/rss2.html#comments>`_ "
 "。为了使得Pelican能正确生成链接，你需要将站点的 ``SITEURL`` 设置为完整路径。"
 
-#: ../../faq.rst:183 4f2cd929dda7464cbd577d1249969920
+#: ../../faq.rst:197 1412ceb735d44a30b58db3241248e7ec
 msgid ""
 "Feeds are still generated when this warning is displayed, but links "
 "within may be malformed and thus the feed may not validate."
 msgstr "虽然Pelican提出了警告，但是仍会生成订阅源，但其中的链接可能是无效的，这会导致订阅源不可用。"
 
-#: ../../faq.rst:187 a9f3465fda8c4a0d9395b2d6d9d5478f
+#: ../../faq.rst:201 20cadccc527e4ebda08eac9ed34f5055
 msgid "Can I force Atom feeds to show only summaries instead of article content?"
 msgstr "可以让Atom订阅源只显示摘要，不显示文章内容吗？"
 
-#: ../../faq.rst:189 baf140533501453aa8caeddfc276d8fb
+#: ../../faq.rst:203 9c45ba2ec5c6402e86e89661b943d1ad
 msgid ""
 "Instead of having to open a separate browser window to read articles, the"
 " overwhelming majority of folks who use feed readers prefer to read "
@@ -314,11 +335,11 @@ msgstr ""
 " ``content`` "
 "字段，因此Pelican在发布RSS时默认只包含摘要（当然也可以设置为包含文章内容）。Pelican在订阅源生成上的如此行为就可以让用户自行选择订阅类型：包含了完整内容的Atom或是只包含摘要的RSS。"
 
-#: ../../faq.rst:200 850ac093f2764547a7df74d5d055cbd4
+#: ../../faq.rst:214 bf0d4ca837f74d9ab6618db6306c6a70
 msgid "Is Pelican only suitable for blogs?"
 msgstr "Pelican只适合用于博客吗？"
 
-#: ../../faq.rst:202 1fb5d92096b242d09da5e0e490b34685
+#: ../../faq.rst:216 49697f375cfc49b08f5d0c2297d15028
 msgid ""
 "No. Pelican can be easily configured to create and maintain any type of "
 "static site. This may require a little customization of your theme and "
@@ -328,13 +349,13 @@ msgid ""
 "tag-related pages via::"
 msgstr "不是的。Pelican可以方便地用于创建维护任何静态站点，为此你需要对主题和配置做一些定制。例如，如果要为你的产品构建一个宣传网站，即不需要使用标签特性，从主题中移除与标签相关的HTML代码即可。另外，还可以通过下面的设置来禁用标签相关页面的生成："
 
-#: ../../faq.rst:212 5452959b3b694cbc89bb8e91bfbef840
+#: ../../faq.rst:226 0a59dd7209554237912579b362d07788
 msgid ""
 "Why does Pelican always write all HTML files even with content caching "
 "enabled?"
 msgstr "启用内容缓存后，为什么Pelican仍会每次都写入所有HTML文件？"
 
-#: ../../faq.rst:214 b27b4b7256f749f1bc5970b95fa742ab
+#: ../../faq.rst:228 6291b82d02fc4450a79d1200b5d04f62
 msgid ""
 "In order to reliably determine whether the HTML output is different "
 "before writing it, a large part of the generation environment including "
@@ -347,7 +368,7 @@ msgid ""
 "reliable."
 msgstr "为了确定HTML输出确实和之前的不同，模板上下文、插件等很多生成环境都需要保存并比较某种哈希值（对于不可哈希的内容类型还需要进行一些额外处理）。另外，由于插件、分页等内容的存在，输出的HTML很可能会与之前不同。因此，考虑到处理时间和存储空间，每次都重新写入全部HTML会更快更可靠。"
 
-#: ../../faq.rst:223 dcb5b1cf0e1b413bb7c04f6deb4ad5d7
+#: ../../faq.rst:237 5cc5e1361f914c92b0670030f0c83f5d
 msgid ""
 "However, this means that the modification time of the files changes every"
 " time, so a ``rsync`` based upload will transfer them even if their "
@@ -359,11 +380,11 @@ msgstr ""
 "上传时会把没有变化的内容也进行上传。一个简便的解决方法就是给 ``rsync`` 加上 ``--checksum`` "
 "选项，这会比Pelican在生成时进行校验更快。"
 
-#: ../../faq.rst:230 628a1180f3fd4c0b8301b33e0728d2c2
+#: ../../faq.rst:244 b24c40be89b94f3b980cbbda38d46115
 msgid "How to process only a subset of all articles?"
 msgstr "如何只处理一部分文章？"
 
-#: ../../faq.rst:232 c2bfe768775342bb8386255ea1bbbe4e
+#: ../../faq.rst:246 fa34a90481f44ace83ee16401543ce09
 msgid ""
 "It is often useful to process only e.g. 10 articles for debugging "
 "purposes. This can be achieved by explicitly specifying only the "
@@ -374,11 +395,11 @@ msgstr ""
 "简便起见，在调试时可能只需要处理几篇文章。可以直接在配置项 ``ARTICLE_PATHS`` 中添加需要处理文章的文件名。可以通过像 ``cd "
 "content; find -name '*.md' | head -n 10`` 这样的命令获取文章文件名的列表。"
 
-#: ../../faq.rst:238 72d30cb7a6e348c483cba0c6b6de8d3a
+#: ../../faq.rst:252 0fa566e3aa084cb9b04e0cee32684222
 msgid "My tag cloud is missing/broken since I upgraded Pelican"
 msgstr "在升级Pelican后，标签云消失或不可用了"
 
-#: ../../faq.rst:240 7d07dcddab5d42d1aab6a8dbd27ce36c
+#: ../../faq.rst:254 0bd1304a12c24f048b227c68391b148c
 msgid ""
 "In an ongoing effort to streamline Pelican, tag cloud generation has been"
 " moved out of Pelican core and into a separate `plugin "
@@ -389,11 +410,11 @@ msgstr ""
 "<https://github.com/pelican-plugins/tag-cloud>`_ 中。查看 :ref:`plugins` "
 "文档获取更多关于Pelican插件系统的信息。"
 
-#: ../../faq.rst:246 51c727bc21f946b8915f958312369e0f
+#: ../../faq.rst:260 1833dfba94c74f4bb9e9f0a112ed3e0f
 msgid "Since I upgraded Pelican my pages are no longer rendered"
 msgstr "升级Pelican后，一些页面没有被渲染"
 
-#: ../../faq.rst:248 4a0d962bc2d844cbab3d0b3e7f6f7bba
+#: ../../faq.rst:262 576e5c2338ba4c43a51bb562301ad0c2
 msgid ""
 "Pages were available to themes as lowercase ``pages`` and uppercase "
 "``PAGES``. To bring this inline with the :ref:`templates-variables` "
@@ -405,15 +426,15 @@ msgstr ""
 "variables` 一节中的内容保持一致，大写的 ``PAGES`` 被删除了。只要将主题中的 ``PAGES`` 替换为 ``pages`` "
 "，问题即可解决。例如将原先的："
 
-#: ../../faq.rst:255 6167ad6b52db43d384247747db1884ca
+#: ../../faq.rst:269 355512b9f6b34ece9b6baed128b2ca4d
 msgid "with something like::"
 msgstr "替换为："
 
-#: ../../faq.rst:260 a7a04eb9e8e549fa8a2a72db3f35b532
+#: ../../faq.rst:274 99ef769943fe41c4a37ca951e905b2ba
 msgid "How can I stop Pelican from trying to parse my static files as content?"
 msgstr "如何避免让Pelican将我的静态文件解析为内容文件？（译者注：例如要将一个HTML文件作为静态文件）？"
 
-#: ../../faq.rst:262 6baaf265738d4acaa26f7829c64a0ac5
+#: ../../faq.rst:276 4efb20c5b82d41afb07151599fa189dd
 msgid ""
 "Pelican's article and page generators run before it's static generator. "
 "That means if you use a setup similar to the default configuration, where"
@@ -426,7 +447,7 @@ msgstr ""
 "配置项中，所有以有效内容文件后缀结尾的文件（ ``.html`` 、 ``.rst`` 、 ``.md`` "
 "等）都会被视为文章或者页面，而不是静态文件。"
 
-#: ../../faq.rst:268 e4591dd94ddd4199900b9a451d12929e
+#: ../../faq.rst:282 d959eb6a67fe440caa70105e1692bf93
 msgid ""
 "To circumvent this issue either use the appropriate ``*_EXCLUDES`` "
 "setting or disable the offending reader via ``READERS`` if you don't need"
@@ -435,11 +456,11 @@ msgstr ""
 "为了避免这个问题，使用合适的 ``*_EXCLUDES`` 配置，在必要时还可以通过 ``READERS`` "
 "配置项来直接禁用产生问题的reader。"
 
-#: ../../faq.rst:272 ca927fe2be10411ab365bcc3e4fa4dbd
+#: ../../faq.rst:286 5e64dc4b6fad4e7ea07278f5a2529e89
 msgid "Why is [arbitrary Markdown syntax] not supported?"
 msgstr "为什么不是所有的Markdown语法都支持？"
 
-#: ../../faq.rst:274 5c9cc929a6bf4f1db9d4eed5f37fc0af
+#: ../../faq.rst:288 6872a70ec1434c41a78d465271761c69
 msgid ""
 "Pelican does not directly handle Markdown processing and instead "
 "delegates that task to the Python-Markdown_ project, the core of which "
@@ -455,3 +476,9 @@ msgstr ""
 "项目，此项目的核心有意只遵循原始的Markdown语法规则，而不服从之后传播开的大量Markdown风格。另外， Python-Markdown_"
 " 是相当模块化的，你想要使用的语法可能已经有现成的 `Markdown扩展`_ "
 "进行了实现。或者，也有人创建了支持Markdown变体的Pelican插件，如果你想要用某种Markdown变体，可以在这些地方寻找支持。"
+
+#~ msgid ""
+#~ "Then just make sure your theme "
+#~ "contains the relevant template file "
+#~ "(e.g. ``template_name.html``)."
+#~ msgstr "确保对应的模板文件在主题中存在即可（例如 ``template_name.html`` ）。"

docs/locale/zh_CN/LC_MESSAGES/tips.po

@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PELICAN 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-06-25 20:36+0800\n"
+"POT-Creation-Date: 2024-11-07 16:25+0800\n"
 "PO-Revision-Date: 2024-06-27 19:00+0800\n"
 "Last-Translator: GeorgeHu <dhxxhch@163.com>\n"
 "Language: zh_CN\n"
@@ -16,22 +16,22 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.15.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../tips.rst:2 415f61a654104cf4826423e3aa1d3807
+#: ../../tips.rst:2 9c4618aaecd44b0d93537cb760e227fa
 msgid "Tips"
 msgstr "小技巧"
 
-#: ../../tips.rst:4 1bc50144d85845f3a7f21f9ef87bba44
+#: ../../tips.rst:4 f49ab5e1ef034ca29140bac3832e8e1c
 msgid "Here are some tips about Pelican that you might find useful."
 msgstr "以下是一些实用的小技巧。"
 
-#: ../../tips.rst:7 ../../tips.rst:264 d9115f4b162d46e6aa89d56309c1ec41
-#: e693dc009e5c466d99655b705223f300
+#: ../../tips.rst:7 ../../tips.rst:309 95bea35d0347495bb551fe9486bcd29d
+#: b64b7ed713b64f588ea7488c6d0b0441
 msgid "Custom 404 Pages"
 msgstr "自定义404页面"
 
-#: ../../tips.rst:9 5c7cd70793f44d3c9fcf63779755d62b
+#: ../../tips.rst:9 d59dc30de5954aa1abc7c46fbac596c6
 msgid ""
 "When a browser requests a resource that the web server cannot find, the "
 "web server usually displays a generic \"File not found\" (404) error page"
@@ -40,36 +40,34 @@ msgid ""
 "article), such as this Markdown-formatted example stored in "
 "``content/pages/404.md``::"
 msgstr ""
-"当浏览器请求的资源无法在服务器中找到时，web服务器常常会显示一个通用的“File not "
-"found 404”的错误页面，这可能会不太美观。为了能使用一个与站点主题相匹配的404页面"
-"（注意是页面而 **不是** 文章），例如下面这个Markdown格式的例子，将此文件存为了 "
-"``content/pages/404.md`` ："
+"当浏览器请求的资源无法在服务器中找到时，web服务器常常会显示一个通用的“File not found "
+"404”的错误页面，这可能会不太美观。为了能使用一个与站点主题相匹配的404页面（注意是页面而 **不是** "
+"文章），例如下面这个Markdown格式的例子，将此文件存为了 ``content/pages/404.md`` ："
 
-#: ../../tips.rst:22 cab28bb6b2a548a09f8cc6e4778f1a78
+#: ../../tips.rst:22 416f9b3eeaac4af8bdc9f32b7cdcba39
 msgid ""
 "The next step is to configure your web server to display this custom page"
 " instead of its default 404 page. For Nginx, add the following to your "
 "configuration file's ``location`` block::"
 msgstr ""
-"接下来就是要配置web服务器，使其显示此自定义页面而不是默认的404页面。例如对于Nginx，"
-"在配置文件的 ``location`` 块中添加下面的命令："
+"接下来就是要配置web服务器，使其显示此自定义页面而不是默认的404页面。例如对于Nginx，在配置文件的 ``location`` "
+"块中添加下面的命令："
 
-#: ../../tips.rst:28 f8acbc4d00de4cfb8dfd9358a8168c14
+#: ../../tips.rst:28 5d52fbcc9d9d4603b3f9d97360face10
 msgid "For Apache::"
 msgstr "对于Apache："
 
-#: ../../tips.rst:32 3701d02f6dba4936a86a9fbb226261e8
+#: ../../tips.rst:32 5413c6bcff6a41688ffcede94b9955e4
 msgid ""
 "For Amazon S3, first navigate to the ``Static Site Hosting`` menu in the "
 "bucket settings on your AWS console. From there::"
-msgstr ""
-"对于Amazon S3实例，先在控制台的设置中找到  ``Static Site Hosting`` ，并添加："
+msgstr "对于Amazon S3实例，先在控制台的设置中找到  ``Static Site Hosting`` ，并添加："
 
-#: ../../tips.rst:38 4d111f7cca2e49828e343ff889847358
+#: ../../tips.rst:38 9b02aa39367a4c33918bddef02d1788d
 msgid "Publishing to GitHub Pages"
 msgstr "发布到GitHub Pages"
 
-#: ../../tips.rst:40 f7fa83b00f6d4dd58d6f119725474538
+#: ../../tips.rst:40 ca3f1deb69a04d40a89576f580d63781
 msgid ""
 "If you use `GitHub <https://github.com/>`_ for your Pelican site you can "
 "publish your site to `GitHub Pages <https://pages.github.com/>`_ for "
@@ -80,14 +78,14 @@ msgid ""
 "<https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-"
 "github-pages-site>`_."
 msgstr ""
-"如果将Pelican站点放在了 `GitHub <https://github.com/>`_ 上，那么你就可以将站点"
-"免费发布在 `GitHub Pages <https://pages.github.com/>`_ 上。如果是用户或组织的"
-"站点，发布的地址为 ``https://<username>.github.io`` ；如果是某个项目的站点，"
-"发布的地址则为 ``https://<username>.github.io/<repository>`` 。当然也可以 "
-"`在GitHub Pages上使用自定义域名 <https://docs.github.com/en/pages/configuring-a-custom-"
+"如果将Pelican站点放在了 `GitHub <https://github.com/>`_ 上，那么你就可以将站点免费发布在 `GitHub "
+"Pages <https://pages.github.com/>`_ 上。如果是用户或组织的站点，发布的地址为 "
+"``https://<username>.github.io`` ；如果是某个项目的站点，发布的地址则为 "
+"``https://<username>.github.io/<repository>`` 。当然也可以 `在GitHub "
+"Pages上使用自定义域名 <https://docs.github.com/en/pages/configuring-a-custom-"
 "domain-for-your-github-pages-site>`_ 。"
 
-#: ../../tips.rst:46 a3167f2a605d44288b83d66f052e8cdd
+#: ../../tips.rst:46 5962c3cb4a0b41289d6b08b9edd2fdee
 msgid ""
 "There are `two ways to publish a site to GitHub Pages "
 "<https://docs.github.com/en/pages/getting-started-with-github-"
@@ -97,16 +95,16 @@ msgstr ""
 "/getting-started-with-github-pages/configuring-a-publishing-source-for-"
 "your-github-pages-site>`_ ："
 
-#: ../../tips.rst:48 b2f270c5a15d4e3e92331c3c37db25dd
+#: ../../tips.rst:48 ad6f071b3cdc4529a41776f799347da0
 msgid ""
 "**Publishing from a branch:** run ``pelican`` locally and push the output"
 " directory to a special branch of your GitHub repo. GitHub will then "
 "publish the contents of this branch to your GitHub Pages site."
 msgstr ""
-"**从某一分支发布：** 在本地运行 ``pelican`` 后将输出文件夹push到GitHub仓库的"
-"某一分支。GitHub就会将该分支的内容发布到GitHub Pages上。"
+"**从某一分支发布：** 在本地运行 ``pelican`` "
+"后将输出文件夹push到GitHub仓库的某一分支。GitHub就会将该分支的内容发布到GitHub Pages上。"
 
-#: ../../tips.rst:51 4ffdb550d8bf468dbfe4d32dfcda21cd
+#: ../../tips.rst:51 6237e147cf4142d9b172588964ec00d2
 msgid ""
 "**Publishing with a custom GitHub Actions workflow:** just push the "
 "source files of your Pelican site to your GitHub repo's default branch "
@@ -116,25 +114,24 @@ msgid ""
 "your site's source files using GitHub's web interface and any changes "
 "that you commit will be published."
 msgstr ""
-"**从自定义GitHub Actions工作流发布：** 将内容源文件推送到GitHub仓库的默认分支，"
-"然后在GitHub Actions工作流中执行 ``pelican`` 以生成输出文件夹，最后将其发布到你"
-"的GitHub Pages站点。此种方法下就无需在本地执行 ``pelican`` 命令了。甚至可以直接"
-"在GitHub的网页中在线修改站点内容源文件。"
+"**从自定义GitHub Actions工作流发布：** 将内容源文件推送到GitHub仓库的默认分支，然后在GitHub "
+"Actions工作流中执行 ``pelican`` 以生成输出文件夹，最后将其发布到你的GitHub Pages站点。此种方法下就无需在本地执行 "
+"``pelican`` 命令了。甚至可以直接在GitHub的网页中在线修改站点内容源文件。"
 
-#: ../../tips.rst:60 0e9c34ce1a5948098a5d0812eb8ac1b4
+#: ../../tips.rst:60 f2655b8ab23147e58fd68e2385a7624a
 msgid "Publishing a Project Site to GitHub Pages from a Branch"
 msgstr "从某一分支发布项目站点到GitHub Pages"
 
-#: ../../tips.rst:62 5190ebea8d8b4542ac9ecb98c297594e
+#: ../../tips.rst:62 1a156c5a8019400d86a33ce306b521ac
 msgid ""
 "To publish a Pelican site as a Project Page you need to *push* the "
 "content of the ``output`` dir generated by Pelican to a repository's "
 "``gh-pages`` branch on GitHub."
 msgstr ""
-"要将Pelican站点发布为项目页面，你需要将Pelican生成的 ``output`` 目录 "
-"**push** 到GitHub仓库的 ``gh-pages`` 分支。"
+"要将Pelican站点发布为项目页面，你需要将Pelican生成的 ``output`` 目录 **push** 到GitHub仓库的 ``gh-"
+"pages`` 分支。"
 
-#: ../../tips.rst:66 e12298010e9745b59d60d31ae909fd4c
+#: ../../tips.rst:66 22caeeba90b24dbe9f0305370de074fc
 msgid ""
 "The excellent `ghp-import <https://github.com/davisp/ghp-import>`_, which"
 " can be installed with ``pip``, makes this process really easy."
@@ -142,15 +139,14 @@ msgstr ""
 "可通过 ``pip`` 安装的 `ghp-import <https://github.com/davisp/ghp-import>`_ "
 "使这一步变得非常简单。"
 
-#: ../../tips.rst:69 cd5a5847355846dd81a0ad37858358f2
+#: ../../tips.rst:69 6ea08af050644b58ae5255dafb4f4d8b
 msgid ""
 "For example, if the source of your Pelican site is contained in a GitHub "
 "repository, and if you want to publish that Pelican site in the form of "
 "Project Pages to this repository, you can then use the following::"
-msgstr ""
-"例如，当Pelican站点的源文件已经包含在GitHub仓库中时，可以将其作为此仓库的项目页面："
+msgstr "例如，当Pelican站点的源文件已经包含在GitHub仓库中时，可以将其作为此仓库的项目页面："
 
-#: ../../tips.rst:77 18d3e7316a5a48acb337c3c67e94084c
+#: ../../tips.rst:77 355b81e8a2194cf9b91bee0f4ee6dca9
 msgid ""
 "The ``ghp-import output`` command updates the local ``gh-pages`` branch "
 "with the content of the ``output`` directory (creating the branch if it "
@@ -158,37 +154,36 @@ msgid ""
 "the remote ``gh-pages`` branch, effectively publishing the Pelican site."
 msgstr ""
 "``ghp-import output`` 命令会用 ``output`` 目录下的内容更新本地的 ``gh-pages`` "
-"分支（如果此分支不存在则会先创建）。接着再用  ``git push origin gh-pages`` "
-"命令更新远程分支 ``gh-pages`` ，如此就能够发布Pelican站点了。"
+"分支（如果此分支不存在则会先创建）。接着再用  ``git push origin gh-pages`` 命令更新远程分支 ``gh-"
+"pages`` ，如此就能够发布Pelican站点了。"
 
-#: ../../tips.rst:84 cc8b9d96da674850b39373728000f722
+#: ../../tips.rst:84 8a3fd725eba44fa99541376722601cce
 msgid ""
 "The ``github`` target of the Makefile (and the ``gh_pages`` task of "
 "``tasks.py``) created by the ``pelican-quickstart`` command publishes the"
 " Pelican site as Project Pages, as described above."
 msgstr ""
-"``pelican-quickstart`` 在Makefile文件中所生成的 ``github`` 目标（以及为 "
-"``gh_pages`` 任务生成的 ``tasks.py`` ）使得Pelican站点能像上面描述的那样被发布"
-"为项目页面。"
+"``pelican-quickstart`` 在Makefile文件中所生成的 ``github`` 目标（以及为 ``gh_pages`` "
+"任务生成的 ``tasks.py`` ）使得Pelican站点能像上面描述的那样被发布为项目页面。"
 
-#: ../../tips.rst:89 41c7b129fd334796848c4d75404dbe81
+#: ../../tips.rst:89 e8ebf23099ed45e7a65d23b9a7e4ccbd
 msgid "Publishing a User Site to GitHub Pages from a Branch"
 msgstr "从某一分支发布用户站点到GitHub Pages"
 
-#: ../../tips.rst:91 b379f950927d484ba91fbe649a248cfe
+#: ../../tips.rst:91 7dc8ae1992b7411d9d6db7cc4a0127cb
 msgid ""
 "To publish a Pelican site in the form of User Pages, you need to *push* "
 "the content of the ``output`` dir generated by Pelican to the ``main`` "
 "branch of your ``<username>.github.io`` repository on GitHub."
 msgstr ""
-"要以用户页面形式发布Pelican站点，你需要将Pelican生成的 ``output`` 目录内容 "
-"**push** 到 ``<username>.github.io`` 仓库的 ``master`` 分支上。"
+"要以用户页面形式发布Pelican站点，你需要将Pelican生成的 ``output`` 目录内容 **push** 到 "
+"``<username>.github.io`` 仓库的 ``master`` 分支上。"
 
-#: ../../tips.rst:95 6d1bd6c0ff25494e997c4efbdcd1d861
+#: ../../tips.rst:95 da706340ef5f4d18bfb183596a4196c9
 msgid "Again, you can take advantage of ``ghp-import``::"
 msgstr "同样的，此处也可以使用 ``ghp-import`` ："
 
-#: ../../tips.rst:101 45fb7ba534af4f7d828e1630e591c02a
+#: ../../tips.rst:101 61aa6f0d9fdf407682d3f781ae5475c6
 msgid ""
 "The ``git push`` command pushes the local ``gh-pages`` branch (freshly "
 "updated by the ``ghp-import`` command) to the ``elemoine.github.io`` "
@@ -197,21 +192,19 @@ msgstr ""
 "``git push`` 命令将本地的 ``gh-pages`` 分支（此分支在刚刚通过 ``ghp-import`` "
 "命令进行了更新）push到了GitHub仓库 ``elemoine.github.io`` 的 ``master`` 分支。"
 
-#: ../../tips.rst:107 b105e7dd1aef441896c0f59166808113
+#: ../../tips.rst:107 f74afbf668a1472d901fe0a16472ab98
 msgid ""
 "To publish your Pelican site as User Pages, feel free to adjust the "
 "``github`` target of the Makefile."
-msgstr ""
-"要将Pelican站点发布为用户页面，可以根据需要修改Makefile中的 ``github`` 目标。"
+msgstr "要将Pelican站点发布为用户页面，可以根据需要修改Makefile中的 ``github`` 目标。"
 
-#: ../../tips.rst:110 87a89a932eec40e8bfdd5c756f4d54fc
+#: ../../tips.rst:110 d69dcdb58a4b4b38aa8b8bf8e4fd733a
 msgid ""
 "Another option for publishing to User Pages is to generate the output "
 "files in the root directory of the project."
-msgstr ""
-"发布用户页面的另一种方法就是将输出文件生成在项目的根目录下。"
+msgstr "发布用户页面的另一种方法就是将输出文件生成在项目的根目录下。"
 
-#: ../../tips.rst:113 dab76a45349c432cb4b763484661ec2c
+#: ../../tips.rst:113 4991892f24df40b982faf01ddb292175
 msgid ""
 "For example, your main project folder is ``<username>.github.io`` and you"
 " can create the Pelican project in a subdirectory called ``Pelican``. "
@@ -220,22 +213,21 @@ msgstr ""
 "例如，项目的主文件夹是 ``<username>.github.io`` ，你可以在子目录 ``Pelican`` "
 "中创建一个Pelican项目。然后你可以在这个 ``Pelican`` 文件夹中执行下面的命令："
 
-#: ../../tips.rst:119 7f13464c92f14cc18f8c00f7dae78f93
+#: ../../tips.rst:119 ca5939f8c58b44b69ebfb2f953a4a73b
 msgid ""
 "Now you can push the whole project ``<username>.github.io`` to the main "
 "branch of your GitHub repository::"
-msgstr ""
-"接着可以将整个项目 ``<username>.github.io`` push到GitHub仓库的master分支中："
+msgstr "接着可以将整个项目 ``<username>.github.io`` push到GitHub仓库的master分支中："
 
-#: ../../tips.rst:124 e82ff566e32b4696863aa04216aaf355
+#: ../../tips.rst:124 54962439805d47abb121ca9454e7a4cc
 msgid "(assuming origin is set to your remote repository)."
 msgstr "（此处假设远程仓库命名为origin）。"
 
-#: ../../tips.rst:127 1958522ba7c34537855505f1e64c7b43
+#: ../../tips.rst:127 b3fe320a90904fbda8c7ed8c7bddbd6e
 msgid "Publishing to GitHub Pages Using a Custom GitHub Actions Workflow"
 msgstr "使用自定义GitHub Actions工作流将站点发布GitHub Pages中"
 
-#: ../../tips.rst:129 19c47b80d248451facd8407bd960b527
+#: ../../tips.rst:129 3b368bc0a307473dae560671fd9527be
 msgid ""
 "Pelican-powered sites can be published to GitHub Pages via a `custom "
 "workflow "
@@ -246,22 +238,21 @@ msgstr ""
 "<https://github.com/getpelican/pelican/blob/main/.github/workflows/github_pages.yml>`_"
 " ，你可以直接使用此工作流发布站点："
 
-#: ../../tips.rst:133 bdc132ef5b974d1eae684d8118e4d914
+#: ../../tips.rst:133 a7b1be522b694d9a8beb186b4603a7aa
 msgid ""
 "Enable GitHub Pages in your repo: go to **Settings → Pages** and choose "
 "**GitHub Actions** for the **Source** setting."
 msgstr ""
-"首先为仓库开启GitHub Pages： **Settings → Pages** 中有个 **Source** 设置项，"
-"将其选择为 **GitHub Actions** 。"
+"首先为仓库开启GitHub Pages： **Settings → Pages** 中有个 **Source** 设置项，将其选择为 "
+"**GitHub Actions** 。"
 
-#: ../../tips.rst:136 d7d197c176bd4127a75cfaf9dd29212b
+#: ../../tips.rst:136 9cc114d8a6b44ff49fa7fecbdbcd012f
 msgid ""
 "Commit a ``.github/workflows/pelican.yml`` file to your repo with these "
 "contents:"
-msgstr ""
-"往你的仓库中commit一个 ``.github/workflows/pelican.yml`` 文件，文件内容如下："
+msgstr "往你的仓库中commit一个 ``.github/workflows/pelican.yml`` 文件，文件内容如下："
 
-#: ../../tips.rst:155 656a2b783b6043f2ac26b1e7b342732e
+#: ../../tips.rst:155 f7d029425d7047deae43e9506c7f4779
 msgid ""
 "You may want to replace the ``@main`` with the ID of a specific commit in"
 " this repo in order to pin the version of the reusable workflow that "
@@ -270,62 +261,63 @@ msgid ""
 "you do this you might want to get Dependabot to send you automated pull "
 "requests to update that commit ID whenever new versions of this workflow "
 "are published, like so:"
-msgstr "你可能想要将 ``@main`` 替换为这个仓库中某个特定commit的ID，以便将你使用的"
-"可重用工作流的版本固定下来，此时，可以使用 ``uses: getpelican/pelican/.github/workflows/"
-"github_pages.yml@<COMMIT_ID>`` 。在这种情况下，你可能想让Dependabot自动向你发送"
-"PR，以便在发布新版本的工作流时更新commit ID，如下所示:"
+msgstr ""
+"你可能想要将 ``@main`` 替换为这个仓库中某个特定commit的ID，以便将你使用的可重用工作流的版本固定下来，此时，可以使用 "
+"``uses: "
+"getpelican/pelican/.github/workflows/github_pages.yml@<COMMIT_ID>`` "
+"。在这种情况下，你可能想让Dependabot自动向你发送PR，以便在发布新版本的工作流时更新commit ID，如下所示:"
 
-#: ../../tips.rst:172 0e2e10f42d6142e1b2f9d2251879ffad
+#: ../../tips.rst:172 fd060b5d5d824ab8825b384d37872894
 msgid ""
 "See `GitHub's docs about using Dependabot to keep your actions up to date"
 " <https://docs.github.com/en/code-security/dependabot/working-with-"
 "dependabot/keeping-your-actions-up-to-date-with-dependabot>`_."
-msgstr "请参阅 `GitHub文档 <https://docs.github.com/en/code-security/"
-"dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-"
+msgstr ""
+"请参阅 `GitHub文档 <https://docs.github.com/en/code-security/dependabot"
+"/working-with-dependabot/keeping-your-actions-up-to-date-with-"
 "dependabot>`_ ，了解如何使用Dependabot使您的action保持最新。"
 
-#: ../../tips.rst:174 2475397adfbb48af9a1d16fc0a24d9b9
+#: ../../tips.rst:174 1b862876e15c4fcd898c4d9b3ba616c5
 msgid ""
 "Go to the **Actions** tab in your repo "
 "(``https://github.com/<username>/<repository>/actions``) and you should "
 "see a **Deploy to GitHub Pages** action running."
 msgstr ""
-"选中仓库的 **Actions** 标签栏（ ``https://github.com/<username>/<repository>"
-"/actions`` ），此时你应该会看到已经有一个名为 **Deploy to GitHub Pages** 的"
-"action正在运行。"
+"选中仓库的 **Actions** 标签栏（ "
+"``https://github.com/<username>/<repository>/actions`` ），此时你应该会看到已经有一个名为 "
+"**Deploy to GitHub Pages** 的action正在运行。"
 
-#: ../../tips.rst:178 df30a15c460b442796f7f2007c283f32
+#: ../../tips.rst:178 f8413793636140f9b017abad379b3429
 msgid ""
 "Once the action completes you should see your Pelican site deployed at "
 "your repo's GitHub Pages URL: ``https://<username>.github.io`` for a user"
 " or organization site or ``https://<username>.github.io/<repository>>`` "
 "for a project site."
 msgstr ""
-"当此action执行完成，就能够通过仓库的GitHub Pages地址 ``https://<username>."
-"github.io`` 看到部署好了的用户或组织站点了，对于项目站点，可通过 ``https://"
-"<username>.github.io/<repository>`` 访问。"
+"当此action执行完成，就能够通过仓库的GitHub Pages地址 ``https://<username>.github.io`` "
+"看到部署好了的用户或组织站点了，对于项目站点，可通过 ``https://<username>.github.io/<repository>`` "
+"访问。"
 
-#: ../../tips.rst:183 f79963fcfd204f2780ff536516e6d407
+#: ../../tips.rst:183 d792bb046c474f70aa98b2c16a5b1254
 msgid "Notes:"
 msgstr "注意事项："
 
-#: ../../tips.rst:185 3a2dc6a36d38454e85265ef35c5e8010
+#: ../../tips.rst:185 89472d2b7231439faf9e51eda07d8323
 msgid ""
 "You don't need to set ``SITEURL`` or ``FEED_DOMAIN`` in your Pelican "
 "settings: the workflow will set them correctly for you"
-msgstr ""
-"无需在Pelican配置文件中设置 ``SITEURL`` ，工作流会帮你进行设置。"
+msgstr "无需在Pelican配置文件中设置 ``SITEURL`` ，工作流会帮你进行设置。"
 
-#: ../../tips.rst:188 ea406746a7db49dfa10de025a3be4a31
+#: ../../tips.rst:188 ea2b632160804a6e9bf1b4cecb7de716
 msgid ""
 "You don't need to commit your ``--output`` / ``OUTPUT_PATH`` directory "
 "(``output/``) to git: the workflow will run ``pelican`` to build the "
 "output directory for you on GitHub Actions"
 msgstr ""
-"无需commit ``--output`` 或 ``OUTPUT_PATH`` 所指定的目录（ ``output/`` ）："
-"工作流会自己执行 ``pelican`` 命令来构建输出目录。"
+"无需commit ``--output`` 或 ``OUTPUT_PATH`` 所指定的目录（ ``output/`` ）：工作流会自己执行 "
+"``pelican`` 命令来构建输出目录。"
 
-#: ../../tips.rst:192 a92a4068ac294a22ac80b1db68090634
+#: ../../tips.rst:192 fd9fb772fba844f099cac781f2b0642f
 msgid ""
 "See `GitHub's docs about reusable workflows "
 "<https://docs.github.com/en/actions/using-workflows/reusing-workflows>`_ "
@@ -334,46 +326,45 @@ msgstr ""
 "更多信息请参阅 `GitHub可重用工作流文档 <https://docs.github.com/en/actions/using-"
 "workflows/reusing-workflows>`_ 。"
 
-#: ../../tips.rst:195 1264d8a048aa4bd7878845ba2dac0d0d
+#: ../../tips.rst:195 f9c527704af24f6da0b4229b7882a25b
 msgid ""
 "A number of optional inputs can be added to the ``with:`` block when "
 "calling the workflow, for example:"
-msgstr ""
-"有一些可选输入可以添加到工作流的 ``with:`` 块中："
+msgstr "有一些可选输入可以添加到工作流的 ``with:`` 块中："
 
-#: ../../tips.rst:206 3faf65d7567244e3bc65a15dc84cf247
+#: ../../tips.rst:206 956f5bae1fc64096acd2a2540a29004c
 msgid "Here's the complete list of workflow inputs:"
 msgstr "下面是工作流可用输入参数的完整列表："
 
-#: ../../tips.rst:209 37919ce86ddb4546bd191440ba1c5b9a
+#: ../../tips.rst:209 eb37c894d7bc4278ab1a92e3b82c5603
 msgid "Name"
 msgstr "名称"
 
-#: ../../tips.rst:209 645ae6a27c7b40ecbc795dbd698b0649
+#: ../../tips.rst:209 446faf9e7d544e6aa47d4a1eca506c01
 msgid "Required"
 msgstr "是否必需"
 
-#: ../../tips.rst:209 18917f8f278440e38882a4f1ca62fc8f
+#: ../../tips.rst:209 de96e4f5cd09488296f97f569fe1fb90
 msgid "Description"
 msgstr "描述"
 
-#: ../../tips.rst:209 99be24eafb6d43578e6eabba25f568fe
+#: ../../tips.rst:209 181bbfff09144f5b9c241b2fc79c989d
 msgid "Type"
 msgstr "值的类型"
 
-#: ../../tips.rst:209 24860d0693b84e6c9297f8733b338824
+#: ../../tips.rst:209 c3d44d1e7be6421a83bae2f5dc6e578f
 msgid "Default"
 msgstr "默认值"
 
-#: ../../tips.rst:211 7e9bb7ea151c4e8c99116dd4decbe3c1
+#: ../../tips.rst:211 305d9d73681b4c6c80161cc906d60bbd
 msgid "``settings``"
 msgstr "``settings``"
 
-#: ../../tips.rst:211 647c4173846f4057920030c8f774d5ea
+#: ../../tips.rst:211 dbe6210f19914ae3b11e4caec7a945f0
 msgid "Yes"
 msgstr "是"
 
-#: ../../tips.rst:211 05c57822d0a249de9718a9a3c56e9e56
+#: ../../tips.rst:211 bbd2306b324d4b5eae513cb7a7683286
 msgid ""
 "The path to your Pelican settings file (``pelican``'s ``--settings`` "
 "option), for example: ``\"publishconf.py\"``"
@@ -383,26 +374,27 @@ msgstr ""
 
 #: ../../tips.rst:211 ../../tips.rst:216 ../../tips.rst:223 ../../tips.rst:227
 #: ../../tips.rst:231 ../../tips.rst:237 ../../tips.rst:243
-#: 4e21f78e86f049048a800ddd5c51e230 618fd4eb66ff45b29c98df87b145613c
-#: 93083ab6eb974293820f40d16349c100 9684f50652484820b924109f31418cd7
-#: 9df48660f1a84fe1af952256c7b58aec cef3fc9239d941969fda711c74994d8c
-#: d09fff93593844cfbb0b270b4cd74193
+#: 073e18d8ae29406eb05040d4e3a9ae60 7d43e6cfb091410ebec7464da05b61b4
+#: 8837cc8935f148fb80f05cc5d3d53629 b2da1f7640f948039230cd835c49accd
+#: bfe3d052cdc443bb81fed82e77acf3c1 c93816e00a254ef69c69f05833e8762b
+#: ee35302c7e034070af1d234ab919c32a
 msgid "string"
 msgstr "string"
 
-#: ../../tips.rst:216 f867df810054493f9d6be16271822ddb
+#: ../../tips.rst:216 4eab6faa96244f13a09754112a783f2f
 msgid "``requirements``"
 msgstr "``requirements``"
 
 #: ../../tips.rst:216 ../../tips.rst:223 ../../tips.rst:227 ../../tips.rst:231
-#: ../../tips.rst:237 ../../tips.rst:243 019e197dd56b44229549da7a2421ce37
-#: 636f76c7f1ca4c61bcea4bbe39a4eb1f 671a0ff87e294e7ab0ac8cdf70fdfe1d
-#: 848f43cf99c447a595f4760e2cf25f2b b425d772694640d0a7bae06c236fa1a2
-#: d145c924e4f348f5ad24b51286ce61e6
+#: ../../tips.rst:237 ../../tips.rst:243 ../../tips.rst:249
+#: 197d6ee11fce4a50996a0c458cfdbdad 2086d667b9b1475cb0f002924cdfde12
+#: 25e940621f5b48c9af487d898d7f93cf 5664232c9fdd46c7b8278b8ecef8e3b1
+#: 6693126a0da74c61b67e14ca8e535ec3 7f8a93a2048140748fa73537bfae2a54
+#: 85fd40a29f31490bb23b20f05e574aaa
 msgid "No"
 msgstr "否"
 
-#: ../../tips.rst:216 0d5ee9c193994b2cac7757e881f01a42
+#: ../../tips.rst:216 9d5bdd70e7da4794805180cc758ebe37
 msgid ""
 "The Python requirements to install, for example to enable markdown and "
 "typogrify use: ``\"pelican[markdown] typogrify\"`` or if you have a "
@@ -411,138 +403,194 @@ msgstr ""
 "需要安装的Python模块，例如要开启markdown和typogrify，可指定 ``\"pelican[markdown] "
 "typogrify\"`` ，或者可以指定一个requirements文件： ``\"-r requirements.txt\"`` "
 
-#: ../../tips.rst:216 67298d60de17486dbc1b6841f2c433b9
+#: ../../tips.rst:216 03ad0b322a714032bcce9f56ce66318d
 msgid "``\"pelican\"``"
 msgstr "``\"pelican\"``"
 
-#: ../../tips.rst:223 219a8d185ac440329e8aa7306e55e708
+#: ../../tips.rst:223 e568553782b443dbacecaa7ded4c391c
 msgid "``output-path``"
 msgstr "``output-path``"
 
-#: ../../tips.rst:223 21a3530e340349afa64d7eb69b393c98
+#: ../../tips.rst:223 2920ae9de5a64ae1ad82bd2287fa7c1e
 msgid "Where to output the generated files (``pelican``'s ``--output`` option)"
 msgstr "生成文件的输出位置（会被用于 ``pelican`` 命令的 ``--output`` 选项）"
 
-#: ../../tips.rst:223 dea97da0dfc24941b8850d1d26ea3cd3
+#: ../../tips.rst:223 41b90747f0954a5799c8baf4a59d99fd
 msgid "``\"output/\"``"
 msgstr "``\"output/\"``"
 
-#: ../../tips.rst:227 688ac4687d7841629137bf97ce97deee
+#: ../../tips.rst:227 e2cc62185182463abc5140244a808e6d
 msgid "``theme``"
 msgstr "``theme``"
 
-#: ../../tips.rst:227 2c2e6b6d8a6044c0ba64d00ea1b12d40
+#: ../../tips.rst:227 cd3b78d03dcd4554a8ce10a873f5ff9f
 msgid ""
 "The GitHub repo URL of a custom theme to use, for example: "
 "``\"https://github.com/seanh/sidecar.git\"``"
-msgstr ""
-"要使用的自定义主题的GitHub仓库URL，例如： ``\"https://github.com/seanh/"
-"sidecar.git\"``"
+msgstr "要使用的自定义主题的GitHub仓库URL，例如： ``\"https://github.com/seanh/sidecar.git\"``"
 
-#: ../../tips.rst:227 bd63884f7e60412d9a6cccc5da9c47ac
+#: ../../tips.rst:227 d94f331173334fb2a84b1caadffb72df
 msgid "``\"\"``"
 msgstr "``\"\"``"
 
-#: ../../tips.rst:231 9527d9e89d704210baff0bb6e3e23b20
+#: ../../tips.rst:231 44ceb2743481486b95c1c739d543f15d
 msgid "``python``"
 msgstr "``python``"
 
-#: ../../tips.rst:231 1aa44193e62647c0ba275507ea84b42c
+#: ../../tips.rst:231 4b5cddab44d24c7c8560e16991b784c7
 msgid ""
 "The version of Python to use to build the site, for example: ``\"3.12\"``"
 " (to use the most recent version of Python 3.12, this is faster) or "
 "``\"3.12.1\"`` (to use an exact version, slower)"
-msgstr ""
-"构建站点时使用的Python版本，例如： ``\"3.12\"`` 或 ``\"3.12.1\"``"
+msgstr "构建站点时使用的Python版本，例如： ``\"3.12\"`` 或 ``\"3.12.1\"``"
 
-#: ../../tips.rst:231 d182ae2dd44c482fb3f2373a7d97087c
+#: ../../tips.rst:231 919c0e36e8ff40bcbcc4480081b49ce5
 msgid "``\"3.12\"``"
 msgstr "``\"3.12\"``"
 
-#: ../../tips.rst:237 dc65b4e578e24d179c38066871c2c572
+#: ../../tips.rst:237 842af56c539f4a74a97c7a5b1525eb35
 msgid "``siteurl``"
 msgstr "``siteurl``"
 
-#: ../../tips.rst:237 5909de5d60224c7b875753f88fd13296
+#: ../../tips.rst:237 7fc0777d6e174d6f8d757926a61aa3c8
 msgid ""
 "The base URL of your web site (Pelican's ``SITEURL`` setting). If not "
 "passed this will default to the URL of your GitHub Pages site, which is "
 "correct in most cases."
-msgstr ""
-"站点的基URL，会用于配置项 ``SITEURL`` 。若未指定，默认值为GitHub Pages站点"
-"的URL，这适用于大部分情况。"
+msgstr "站点的基URL，会用于配置项 ``SITEURL`` 。若未指定，默认值为GitHub Pages站点的URL，这适用于大部分情况。"
 
-#: ../../tips.rst:237 ../../tips.rst:243 0c0b86aa4b984615afb3564b76e379ff
-#: c7ddd6347a7f4467b31aaa8f4d4a2309
+#: ../../tips.rst:237 ../../tips.rst:243 082f65333e224d71817b82b1e4f515c4
+#: 3d786e828a4745db849bdb8f47738db8
 msgid "The URL of your GitHub Pages site."
 msgstr "GitHub Pages站点的URL"
 
-#: ../../tips.rst:243 af7d2b52c5504ac2b69490a18d14f80f
+#: ../../tips.rst:243 e5adb69f985547b7b3cc2bd3f31d4cc3
 msgid "``feed_domain``"
 msgstr "``feed_domain``"
 
-#: ../../tips.rst:243 2cc126862a8047c286381aa258aad013
+#: ../../tips.rst:243 c88f037c9f1f4148bef6347228257f7d
 msgid ""
 "The domain to be prepended to feed URLs (Pelican's ``FEED_DOMAIN`` "
 "setting). If not passed this will default to the URL of your GitHub Pages"
 " site, which is correct in most cases."
 msgstr ""
-"订阅源URL前要附加的域名，会用于配置项 ``FEED_DOMAIN`` 。若未指定，默认值为"
-"GitHub Pages站点的URL，这适用于大部分情况。"
+"订阅源URL前要附加的域名，会用于配置项 ``FEED_DOMAIN`` 。若未指定，默认值为GitHub "
+"Pages站点的URL，这适用于大部分情况。"
 
-#: ../../tips.rst:252 b86ab8a1fa24447d99becc592411010e
+#: ../../tips.rst:249 358c5aa434cd4ad09beab02df88413d5
+msgid "``deploy``"
+msgstr "``deploy``"
+
+#: ../../tips.rst:249 b8748aeace5a448d9382e225be98f90c
+msgid ""
+"This is used to determine whether you will deploy the site or not to "
+"GitHub Pages. This is most useful if you want to test a change to your "
+"website in a pull request before deploying those change."
+msgstr "此项配置用于表示是否要将站点部署至GitHub Pages。当对站点做了更改，并且在正式部署前进行测试，就可以用到此项。"
+
+#: ../../tips.rst:249 034006b9b71b4cb486f230b8aad873ce
+msgid "bool"
+msgstr "bool"
+
+#: ../../tips.rst:249 078ac613a8b74703af98c75bb5a007c1
+msgid "``true``"
+msgstr "``true``"
+
+#: ../../tips.rst:257 e63cf881e3204be8b52ee5d8635ba4cf
+msgid "Testing Your Build in a GitHub Pull Request"
+msgstr "在Github拉取请求时进行测试"
+
+#: ../../tips.rst:259 a2f6bd3420eb46a08f54efda35a6eaf4
+msgid ""
+"If you want to test your build in a pull request before deploying to "
+"GitHub, your workflow might look something like this:"
+msgstr "如果想在正式部署到 GitHub 前在PR中进行测试，下面是一个可用的 workflow 示例"
+
+#: ../../tips.rst:288 84393693279741efa82c5ee6b27cbd28
+msgid ""
+"The ``on`` section of the workflow defines the events that will trigger "
+"the workflow. In this example, the workflow will run on pushes to the "
+"main branch, pull requests to the main branch, and manual runs of the "
+"workflow."
+msgstr "工作流的 ``on`` 部分定义了工作流的触发器。在此示例中，工作流将在main分支收到push、有PR提起到主分支以及"
+"手动运行工作流时执行。"
+
+#: ../../tips.rst:290 cd3c13b2af974a32aa4291d07fc11e9c
+msgid ""
+"``workflow_dispatch`` defines the deploy boolean to be true by default. "
+"This means that if you run the workflow manually, it will deploy the "
+"site."
+msgstr "``workflow_dispatch`` 将 deploy 的默认值设为 true。也就是说当手动运行工作流时，更改的内容就会正式部署。"
+
+#: ../../tips.rst:292 5402cd211d5b4aa8a244c916bb381a5b
+msgid ""
+"The ``deploy`` input for the job is using a set of standard GitHub "
+"workflow variables to control when ``deploy`` will either be true or "
+"false (you can customize this to your needs)."
+msgstr "job中的 ``deploy`` 使用了一些 GitHub workflow 变量来计算 ``deploy`` 值为 true 还是 false（您可以根据需要自定义）。"
+
+#: ../../tips.rst:294 d084908e3a0749f0b802b43626cfe2c4
+msgid ""
+"In this example, the ``deploy`` will be true if the event is a push to "
+"the main branch (or merging into main from a PR) or a manual run of the "
+"workflow. If the event is a pull request, the ``deploy`` will be false "
+"and it will only build an artifact for the site."
+msgstr "在此示例中，如果触发事件是推送到主分支（或从 PR 合并到主分支）或手动运行工作流，则 deploy 将为 true；"
+"如果触发事件只是Pull Request，则 ``deploy`` 将为 false，并且此时只会为站点构建一个artifact。"
+
+#: ../../tips.rst:297 85e70fc3faa04208979f7bbe92b025ef
 msgid "\"Insecure content\" warnings from browsers"
 msgstr "浏览器报“不安全的内容（Insecure content）”警告"
 
-#: ../../tips.rst:254 c81d5f8889c14a069e55fe7472a238f2
+#: ../../tips.rst:299 34f7075cf31f416da2aeb529c616d97d
 msgid ""
 "If your site uses ``https://`` and is broken because the browser is "
 "blocking network requests (for example for CSS files) due to \"insecure "
 "content\" this may be because GitHub Pages is generating ``http://`` URLs"
 " for your site."
 msgstr ""
-"当站点使用 ``https://`` 时，可能会损坏，无法正常显示，这是由于浏览器阻拦了一些"
-"对“不安全内容”的网络请求。可能的原因之一是GitHub Pages给你的站点生成了 ``http://`` "
-"URL。"
+"当站点使用 ``https://`` "
+"时，可能会损坏，无法正常显示，这是由于浏览器阻拦了一些对“不安全内容”的网络请求。可能的原因之一是GitHub Pages给你的站点生成了 "
+"``http://`` URL。"
 
-#: ../../tips.rst:258 2a53f882b7e645149d18ce81757b9758
+#: ../../tips.rst:303 47271df82577424c8e2c31a9e76a553a
 msgid ""
 "To fix this go into your site repo's settings and enable the **Enforce "
 "HTTPS** setting: go to **Settings → Pages** and check **Enforce HTTPS**. "
 "Then re-run the workflow to re-deploy your site. Alternatively, you can "
 "use the workflow's ``siteurl`` and ``feed_domain`` settings."
 msgstr ""
-"要想解决这一问题，需要为站点所在仓库开启 **强制使用HTTPS** ：点击 **Settings → Pages** "
-"并在其中勾选 **Enforce HTTPS** ，接着再重新执行工作流以重新部署站点。也可以尝试"
-"通过配置 ``siteurl`` 与 ``feed_domain`` 解决问题。"
+"要想解决这一问题，需要为站点所在仓库开启 **强制使用HTTPS** ：点击 **Settings → Pages** 并在其中勾选 "
+"**Enforce HTTPS** ，接着再重新执行工作流以重新部署站点。也可以尝试通过配置 ``siteurl`` 与 "
+"``feed_domain`` 解决问题。"
 
-#: ../../tips.rst:266 483cbd21e61841d983e2ecc8bc3006bc
+#: ../../tips.rst:311 e69189ef4a8440fb8940d8012b4f19d6
 msgid ""
 "GitHub Pages will display the custom 404 page described above, as noted "
 "in the relevant `GitHub docs "
 "<https://help.github.com/articles/custom-404-pages/>`_."
 msgstr ""
-"如果按前述进行配置，GitHub Pages是能够正确显示自定义的404页面的，相关内容在 "
-"`GitHub的文档中 <https://help.github.com/articles/custom-404-pages/>`_ 也有提到。"
+"如果按前述进行配置，GitHub Pages是能够正确显示自定义的404页面的，相关内容在 `GitHub的文档中 "
+"<https://help.github.com/articles/custom-404-pages/>`_ 也有提到。"
 
-#: ../../tips.rst:270 6b54e9c354f34e1f9a5a3f50d96b98c3
+#: ../../tips.rst:315 1b8c2457f44a4d61a033363830b8bd90
 msgid "Update your site on each commit"
 msgstr "在每次commit后都更新站点"
 
-#: ../../tips.rst:272 2e83c0c761c94f35ae3056634d8f1552
+#: ../../tips.rst:317 476dbdb670924c02a962e78d6a7854c1
 msgid ""
 "To automatically update your Pelican site on each commit, you can create "
 "a post-commit hook. For example, you can add the following to "
 "``.git/hooks/post-commit``::"
 msgstr ""
-"要想在每次commit后自动更新Pelican站点，你可以创建一个post-commit钩子。例如，"
-"可以将下面的内容保存为 ``.git/hooks/post-commit`` ："
+"要想在每次commit后自动更新Pelican站点，你可以创建一个post-commit钩子。例如，可以将下面的内容保存为 "
+"``.git/hooks/post-commit`` ："
 
-#: ../../tips.rst:279 528589366e634f15bb0a702969715286
+#: ../../tips.rst:324 36dc5f05eaf84573acada36c59d8d2fc
 msgid "Copy static files to the root of your site"
 msgstr "将静态文件拷贝到站点根目录"
 
-#: ../../tips.rst:281 dc4267653ef04722a0583915c05b6c88
+#: ../../tips.rst:326 4a0722ad68e944ee80e6378259cc1dd6
 msgid ""
 "To use a `custom domain <https://help.github.com/articles/setting-up-a"
 "-custom-domain-with-pages>`_ with GitHub Pages, you need to put the "
@@ -557,11 +605,11 @@ msgstr ""
 "）添加到站点根目录的 ``CNAME`` 文件中。为此，请创建 ``content/extra/`` 目录，并在里面添加一个 ``CNAME`` "
 "文件。然后使用Pelican的 ``STATIC_PATHS`` 来告诉Pelican将此文件复制到输出目录："
 
-#: ../../tips.rst:292 5fcdc283f55f4d8ca121cb6438c67a36
+#: ../../tips.rst:337 8ad906848762400d9e2462034d151a16
 msgid "Note: use forward slashes, ``/``, even on Windows."
 msgstr "请注意：务必使用正斜杠 ``/`` ，在Windows上也是。"
 
-#: ../../tips.rst:294 326a40a1536c462ea4974ce4b560f54c
+#: ../../tips.rst:339 7b109f4944064382babc9158567c8e82
 msgid ""
 "You can also use the ``EXTRA_PATH_METADATA`` mechanism to place a "
 "``favicon.ico`` or ``robots.txt`` at the root of any site."
@@ -569,18 +617,17 @@ msgstr ""
 "利用 ``EXTRA_PATH_METADATA`` 机制，你可以将 ``favicon.ico`` 或 ``robots.txt`` "
 "也拷贝到站点的根目录下。"
 
-#: ../../tips.rst:298 4e589caa6f17438aae1d1a12819c6ef2
+#: ../../tips.rst:343 678eea0644b5400496ad9173d05368d5
 msgid "How to add YouTube or Vimeo Videos"
 msgstr "如何添加YouTube或Vimeo视频"
 
-#: ../../tips.rst:300 5f60f033a7084739af5ef0dce5b91197
+#: ../../tips.rst:345 ca57b327dd6b432d82cdc91193bde6bb
 msgid ""
 "The easiest way is to paste the embed code of the video from these sites "
 "directly into your source content."
-msgstr ""
-"最简单的方法是将这些网站的视频嵌入代码直接粘贴到您的源内容文件中。"
+msgstr "最简单的方法是将这些网站的视频嵌入代码直接粘贴到您的源内容文件中。"
 
-#: ../../tips.rst:303 5446d02bebc241e88cc30b484799696c
+#: ../../tips.rst:348 0a4f27e2edbe494ab52f73595646986e
 msgid ""
 "Alternatively, you can also use Pelican plugins like ``liquid_tags``, "
 "``pelican_youtube``, or ``pelican_vimeo`` to embed videos in your "
@@ -589,45 +636,42 @@ msgstr ""
 "或者，您还可以使用例如 ``liquid_tags`` 、``pelican_youtube`` 或 ``pelican_vimeo`` "
 "等Pelican插件将视频嵌入。"
 
-#: ../../tips.rst:306 c871fab4a3424b0dba84c1af24f6405f
+#: ../../tips.rst:351 e73517b72da347738421784b776b1f1c
 msgid ""
 "Moreover, markup languages like reST and Markdown have plugins that let "
 "you embed videos in the markup. You can use `reST video directive "
 "<https://gist.github.com/dbrgn/2922648>`_ for reST or `mdx_video plugin "
 "<https://github.com/italomaia/mdx-video>`_ for Markdown."
 msgstr ""
-"此外，像reST和 Markdown这样的标记语言都有对应插件可以让你在其中嵌入视频。"
-"可以使用 `reST的视频指令 <https://gist.github.com/dbrgn/2922648>`_ 或者 "
-"`Markdown的mdx_video插件 <https://github.com/italomaia/mdx-video>`_ 。"
+"此外，像reST和 Markdown这样的标记语言都有对应插件可以让你在其中嵌入视频。可以使用 `reST的视频指令 "
+"<https://gist.github.com/dbrgn/2922648>`_ 或者 `Markdown的mdx_video插件 "
+"<https://github.com/italomaia/mdx-video>`_ 。"
 
-#: ../../tips.rst:313 569b7609cb9d412e942001da7c4a704c
+#: ../../tips.rst:358 b9d27cda716048b2ab7c13646d7faf09
 msgid "Develop Locally Using SSL"
 msgstr "在本地使用SSL进行开发"
 
-#: ../../tips.rst:315 e66f6f1cacc4466682461d251aedb929
+#: ../../tips.rst:360 50df9ec072aa47eabbae132fd8f5cb68
 msgid "Here's how you can set up your local pelican server to support SSL."
 msgstr "以下描述了如何在本地Pelican服务器上配置SSL。"
 
-#: ../../tips.rst:317 138c34c1b6804246b79fda266a1fd937
+#: ../../tips.rst:362 9b5045375a874c4d9c29f7109f05c539
 msgid ""
 "First, create a self-signed certificate and key using ``openssl`` (this "
 "creates ``cert.pem`` and ``key.pem``)::"
-msgstr ""
-"首先，通过 ``openssl`` 创建自签名的证书和密钥，这会生成 ``cert.pem`` 和 "
-"``key.pem`` 文件："
+msgstr "首先，通过 ``openssl`` 创建自签名的证书和密钥，这会生成 ``cert.pem`` 和 ``key.pem`` 文件："
 
-#: ../../tips.rst:321 ac189182bc694bcaa94cd935311f4492
+#: ../../tips.rst:366 2f1cfa536fc540f69d671f8a118769d7
 msgid ""
 "And use this command to launch the server (the server starts within your "
 "``output`` directory)::"
-msgstr ""
-"接着使用下面的命令来开启服务器（此服务器会在 ``output`` 目录下开启）："
+msgstr "接着使用下面的命令来开启服务器（此服务器会在 ``output`` 目录下开启）："
 
-#: ../../tips.rst:325 88a33744d69f4f5bbc4a43024c43d3a0
+#: ../../tips.rst:370 029ea2b0e4fe4b0f814158ae33e3a8ff
 msgid "If you are using ``develop-server.sh``,  add this to the top::"
 msgstr "如果你使用的是 ``develop-server.sh`` 脚本，在脚本的开头添加："
 
-#: ../../tips.rst:330 9a783977fe814657b8590185af281b1e
+#: ../../tips.rst:375 c2784fdd9fdb433799d57f903d0e49d8
 msgid "and modify the ``pelican.server`` line as follows::"
 msgstr "然后修改按照下述修改 ``pelican.server`` 一行："