Deploying to gh-pages from @ Klipper3d/klipper@d9daeb0803 🚀

2022-04-29 00:04:01 +00:00
parent 6ae53d06a1
commit 4e91ef87f4
27 changed files with 787 additions and 318 deletions
--- a/zh-Hant/API_Server.html
+++ b/zh-Hant/API_Server.html
@@ -1592,6 +1592,7 @@
 </code></pre></div>

 <p>上述操作會使主機建立一個Unix本地套接字。之後，客戶應用程式可以建立一個套接字鏈接，從而給Klipper發送命令。</p>
+<p>See the <a href="https://github.com/Arksine/moonraker">Moonraker</a> project for a popular tool that can forward HTTP requests to Klipper's API Server Unix Domain Socket.</p>
 <h2 id="_1">請求格式<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h2>
 <p>套接字進出的數據包應使用JSON編碼的字串，並以ASCII字元0x03作為結尾：</p>
 <div class="highlight"><pre><span></span><code>&lt;json_object_1&gt;&lt;0x03&gt;&lt;json_object_2&gt;&lt;0x03&gt;...
--- a/zh-Hant/Bootloaders.html
+++ b/zh-Hant/Bootloaders.html
@@ -1232,6 +1232,13 @@
    帶有 HID 載入程式的STM32F103
  </a>
  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#stm32f103stm32f072-with-msc-bootloader" class="md-nav__link">
+    STM32F103/STM32F072 with MSC bootloader
+  </a>
+  
 </li>
        
      </ul>
@@ -1473,6 +1480,13 @@
    帶有 HID 載入程式的STM32F103
  </a>
  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#stm32f103stm32f072-with-msc-bootloader" class="md-nav__link">
+    STM32F103/STM32F072 with MSC bootloader
+  </a>
+  
 </li>
        
      </ul>
@@ -1761,6 +1775,15 @@ make
 </code></pre></div>

 <p>可能需要手動進入載入程式，這可以通過設定 "boot 0 "的低電平和 "boot 1 "的高電平來完成。在SKR Mini E3上，"Boot 1 "是不可用的，所以如果你寫入過"hid_btt_skr_mini_e3.bin"，可以通過設定PA2的低電平來完成。在SKR Mini E3的 "PIN "檔案中，這個引腳在TFT插座上被標記為 "TX0"。在PA2旁邊有一個接地引腳，你可以用它來把PA2拉低。</p>
+<h3 id="stm32f103stm32f072-with-msc-bootloader">STM32F103/STM32F072 with MSC bootloader<a class="headerlink" href="#stm32f103stm32f072-with-msc-bootloader" title="Permanent link">&para;</a></h3>
+<p>The <a href="https://github.com/Telekatz/MSC-stm32f103-bootloader">MSC bootloader</a> is a driverless bootloader capable of flashing over USB.</p>
+<p>It is possible to flash the bootloader via 3.3v serial using stm32flash as noted in the stm32duino section above, substituting the file name for the desired MSC bootloader binary (ie: MSCboot-Bluepill.bin for the blue pill).</p>
+<p>For STM32F072 boards it is also possible to flash the bootloader over USB (via DFU) with something like:</p>
+<div class="highlight"><pre><span></span><code> dfu-util -d 0483:df11 -a 0 -R -D  MSCboot-STM32F072.bin -s0x08000000:leave
+</code></pre></div>
+
+<p>This bootloader uses 8KiB or 16KiB of flash space, see description of the bootloader (the application must be compiled with with the corresponding starting address).</p>
+<p>The bootloader can be activated by pressing the reset button of the board twice. As soon as the bootloader is activated, the board appears as a USB flash drive onto which the klipper.bin file can be copied.</p>
 <h2 id="stm32f4-skr-pro-11">STM32F4 微控制器 (SKR Pro 1.1)<a class="headerlink" href="#stm32f4-skr-pro-11" title="Permanent link">&para;</a></h2>
 <p>STM32F4微控制器配備了一個內建的系統載入程式，能夠通過USB（通過DFU）、3.3v串列埠和其他各種方法進行刷寫（更多資訊見STM檔案AN2606）。一些STM32F4板，如SKR Pro 1.1，不能進入DFU載入程式。基於STM32F405/407的板子可以使用HID載入程式，如果使用者願意通過USB刷寫而不是使用SD卡。請注意，你可能需針對你的板子配置和構建一個特定的版本，<a href="https://github.com/Arksine/STM32_HID_Bootloader/releases/latest">針對SKR Pro 1.1的構建可以在這裡找到</a>。</p>
 <p>除非你的板子有DFU功能，否則最容易的寫入方法可能是通過3.3v的串列埠，這與<a href="#stm32f103-micro-controllers-blue-pill-devices">使用stm32flash刷寫STM32F103</a>的步驟相同。例如：</p>
--- a/zh-Hant/Config_Reference.html
+++ b/zh-Hant/Config_Reference.html
@@ -919,6 +919,13 @@
    [bltouch]
  </a>
  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#smart_effector" class="md-nav__link">
+    [smart_effector]
+  </a>
+  
 </li>
        
      </ul>
@@ -2776,6 +2783,13 @@
    [bltouch]
  </a>
  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#smart_effector" class="md-nav__link">
+    [smart_effector]
+  </a>
+  
 </li>
        
      </ul>
@@ -4288,10 +4302,10 @@ max_temp:
 <div class="highlight"><pre><span></span><code>[screws_tilt_adjust]
 #screw1:
 #   The (X, Y) coordinate of the first bed leveling screw. This is a
-#   position to command the nozzle to that is directly above the bed
-#   screw (or as close as possible while still being above the bed).
-#   This is the base screw used in calculations. This parameter must
-#   be provided.
+#   position to command the nozzle to so that the probe is directly
+#   above the bed screw (or as close as possible while still being
+#   above the bed). This is the base screw used in calculations. This
+#   parameter must be provided.
 #screw1_name:
 #   An arbitrary name for the given screw. This name is displayed when
 #   the helper script runs. The default is to use a name based upon
@@ -4694,8 +4708,8 @@ cs_pin:
 #   for more details on using this feature.
 #min_freq: 5
 #   Minimum frequency to test for resonances. The default is 5 Hz.
-#max_freq: 120
-#   Maximum frequency to test for resonances. The default is 120 Hz.
+#max_freq: 133.33
+#   Maximum frequency to test for resonances. The default is 133.33 Hz.
 #accel_per_hz: 75
 #   This parameter is used to determine which acceleration to use to
 #   test a specific frequency: accel = accel_per_hz * freq. Higher the
@@ -4853,6 +4867,53 @@ control_pin:
 #   See the &quot;probe&quot; section for information on these parameters.
 </code></pre></div>

+<h3 id="smart_effector">[smart_effector]<a class="headerlink" href="#smart_effector" title="Permanent link">&para;</a></h3>
+<p>The "Smart Effector" from Duet3d implements a Z probe using a force sensor. One may define this section instead of <code>[probe]</code> to enable the Smart Effector specific features. This also enables <a href="G-Codes.html#smart_effector">runtime commands</a> to adjust the parameters of the Smart Effector at run time.</p>
+<div class="highlight"><pre><span></span><code>[smart_effector]
+pin:
+#   Pin connected to the Smart Effector Z Probe output pin (pin 5). Note that
+#   pullup resistor on the board is generally not required. However, if the
+#   output pin is connected to the board pin with a pullup resistor, that
+#   resistor must be high value (e.g. 10K Ohm or more). Some boards have a low
+#   value pullup resistor on the Z probe input, which will likely result in an
+#   always-triggered probe state. In this case, connect the Smart Effector to
+#   a different pin on the board. This parameter is required.
+#control_pin:
+#   Pin connected to the Smart Effector control input pin (pin 7). If provided,
+#   Smart Effector sensitivity programming commands become available.
+#probe_accel:
+#   If set, limits the acceleration of the probing moves (in mm/sec^2).
+#   A sudden large acceleration at the beginning of the probing move may
+#   cause spurious probe triggering, especially if the hotend is heavy.
+#   To prevent that, it may be necessary to reduce the acceleration of
+#   the probing moves via this parameter.
+#recovery_time: 0.4
+#   A delay between the travel moves and the probing moves in seconds. A fast
+#   travel move prior to probing may result in a spurious probe triggering.
+#   This may cause &#39;Probe triggered prior to movement&#39; errors if no delay
+#   is set. Value 0 disables the recovery delay.
+#   Default value is 0.4.
+#x_offset:
+#y_offset:
+#   Should be left unset (or set to 0).
+z_offset:
+#   Trigger height of the probe. Start with -0.1 (mm), and adjust later using
+#   `PROBE_CALIBRATE` command. This parameter must be provided.
+#speed:
+#   Speed (in mm/s) of the Z axis when probing. It is recommended to start
+#   with the probing speed of 20 mm/s and adjust it as necessary to improve
+#   the accuracy and repeatability of the probe triggering.
+#samples:
+#sample_retract_dist:
+#samples_result:
+#samples_tolerance:
+#samples_tolerance_retries:
+#activate_gcode:
+#deactivate_gcode:
+#deactivate_on_each_sample:
+#   See the &quot;probe&quot; section for more information on the parameters above.
+</code></pre></div>
+
 <h2 id="_16">額外的步進電機和擠出機<a class="headerlink" href="#_16" title="Permanent link">&para;</a></h2>
 <h3 id="stepper_z1">[stepper_z1]<a class="headerlink" href="#stepper_z1" title="Permanent link">&para;</a></h3>
 <p>多步進軸。在XYZ機型打印機上，控制給定軸的步進器可能具有額外的配置塊，這些配置塊定義了應該與主步進器一起步進的步進器。可以使用從 1 開始的數字後綴定義任意數量的部分（例如，“stepper_z1”、“stepper_z2”等）。</p>
@@ -5390,32 +5451,43 @@ pin:
 #tachometer_pin:
 #tachometer_ppr:
 #tachometer_poll_interval:
-# 以上參數的說明見“fan”部分。
+#   See the &quot;fan&quot; section for a description of the above parameters.
 #sensor_type:
 #sensor_pin:
 #control:
-#pid_Kp:
-#pid_Ki:
-#pid_Kd:
-#pid_deriv_time:
 #max_delta:
 #min_temp:
 #max_temp:
-# 有關上述參數的說明，請參見“擠出機”部分。
-#target_temp：40.0
-# 將成為目標溫度的溫度（以攝氏度為單位）。
-# 默認為40度。
+#   See the &quot;extruder&quot; section for a description of the above parameters.
+#pid_Kp:
+#pid_Ki:
+#pid_Kd:
+#   The proportional (pid_Kp), integral (pid_Ki), and derivative
+#   (pid_Kd) settings for the PID feedback control system. Klipper
+#   evaluates the PID settings with the following general formula:
+#     fan_pwm = max_power - (Kp*e + Ki*integral(e) - Kd*derivative(e)) / 255
+#   Where &quot;e&quot; is &quot;target_temperature - measured_temperature&quot; and
+#   &quot;fan_pwm&quot; is the requested fan rate with 0.0 being full off and
+#   1.0 being full on. The pid_Kp, pid_Ki, and pid_Kd parameters must
+#   be provided when the PID control algorithm is enabled.
+#pid_deriv_time: 2.0
+#   A time value (in seconds) over which temperature measurements will
+#   be smoothed when using the PID control algorithm. This may reduce
+#   the impact of measurement noise. The default is 2 seconds.
+#target_temp: 40.0
+#   A temperature (in Celsius) that will be the target temperature.
+#   The default is 40 degrees.
 #max_speed: 1.0
-# 風扇轉速（表示為 0.0 到 1.0 之間的值）
-# 將在傳感器溫度超過設定值時設置為。
-# 默認為 1.0。
-#min_speed：0.3
-# 最小風扇速度（表示為 0.0 到 1.0 的值）
-# 風扇將設置為 PID 溫度風扇。
-# 默認為 0.3。
-#gcode_id：
-# 如果設置，溫度將在 M105 查詢中使用
-# 給定 id。默認不通過 M105 上報溫度。
+#   The fan speed (expressed as a value from 0.0 to 1.0) that the fan
+#   will be set to when the sensor temperature exceeds the set value.
+#   The default is 1.0.
+#min_speed: 0.3
+#   The minimum fan speed (expressed as a value from 0.0 to 1.0) that
+#   the fan will be set to for PID temperature fans.
+#   The default is 0.3.
+#gcode_id:
+#   If set, the temperature will be reported in M105 queries using the
+#   given id. The default is to not report the temperature via M105.
 </code></pre></div>

 <h3 id="fan_generic">[fan_generic]<a class="headerlink" href="#fan_generic" title="Permanent link">&para;</a></h3>
@@ -5463,7 +5535,7 @@ pin:

 <h3 id="neopixel">[neopixel]<a class="headerlink" href="#neopixel" title="Permanent link">&para;</a></h3>
 <p>Neopixel (aka WS2812) LED support (one may define any number of sections with a "neopixel" prefix). See the <a href="G-Codes.html#led">command reference</a> for more information.</p>
-<p>Note that the <a href="RPi_microcontroller.html">linux mcu</a> implementation does not currently support directly connected neopixels.</p>
+<p>Note that the <a href="RPi_microcontroller.html">linux mcu</a> implementation does not currently support directly connected neopixels. The current design using the Linux kernel interface does not allow this scenario because the kernel GPIO interface is not fast enough to provide the required pulse rates.</p>
 <div class="highlight"><pre><span></span><code>[neopixel my_neopixel]
 pin:
 #   The pin connected to the neopixel. This parameter must be
@@ -5474,8 +5546,9 @@ pin:
 #   Neopixel is connected to the pin).
 #color_order: GRB
 #   Set the pixel order required by the LED hardware (using a string
-#   containing the letters R, G, B, W with W optional). The default is
-#   GRB.
+#   containing the letters R, G, B, W with W optional). Alternatively,
+#   this may be a comma separated list of pixel orders - one for each
+#   LED in the chain. The default is GRB.
 #initial_RED: 0.0
 #initial_GREEN: 0.0
 #initial_BLUE: 0.0
--- a/zh-Hant/G-Codes.html
+++ b/zh-Hant/G-Codes.html
@@ -1966,6 +1966,33 @@
      </ul>
    </nav>
  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#smart_effector" class="md-nav__link">
+    [smart_effector]
+  </a>
+  
+    <nav class="md-nav" aria-label="[smart_effector]">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#set_smart_effector" class="md-nav__link">
+    SET_SMART_EFFECTOR
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#reset_smart_effector" class="md-nav__link">
+    RESET_SMART_EFFECTOR
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
        
          <li class="md-nav__item">
@@ -3872,6 +3899,33 @@
      </ul>
    </nav>
  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#smart_effector" class="md-nav__link">
+    [smart_effector]
+  </a>
+  
+    <nav class="md-nav" aria-label="[smart_effector]">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#set_smart_effector" class="md-nav__link">
+    SET_SMART_EFFECTOR
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#reset_smart_effector" class="md-nav__link">
+    RESET_SMART_EFFECTOR
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
        
          <li class="md-nav__item">
@@ -4359,7 +4413,7 @@
 <h4 id="z_offset_apply_probe">Z_OFFSET_APPLY_PROBE<a class="headerlink" href="#z_offset_apply_probe" title="Permanent link">&para;</a></h4>
 <p><code>Z_OFFSET_APPLY_PROBE</code>：將目前的Z 的 G 程式碼偏移量（就是 babystepping）從 probe 的 z_offset 中減去。該命令將持久化一個常用babystepping 微調值。需要執行 <code>SAVE_CONFIG</code>才能生效。</p>
 <h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">&para;</a></h3>
-<p>模組query_endstops已自動載入.</p>
+<p>The query_adc module is automatically loaded.</p>
 <h4 id="query_adc_1">QUERY_ADC<a class="headerlink" href="#query_adc_1" title="Permanent link">&para;</a></h4>
 <p><code>QUERY_ADC [NAME=&lt;config_name&gt;] [PULLUP=&lt;value&gt;]</code> ：返回為配置的模擬引腳收到的最後一個模擬值。如果NAME沒有被提供，將報告可用的adc名稱列表。如果提供了PULLUP（以歐姆為單位的數值），將會返回原始模擬值和給定的等效電阻。</p>
 <h3 id="query_endstops">[query_endstops]<a class="headerlink" href="#query_endstops" title="Permanent link">&para;</a></h3>
@@ -4421,6 +4475,12 @@
 <p><code>CALC_MEASURED_SKEW [AC=&lt;ac 長度&gt;] [BD=&lt;bd 長度&gt;] [AD=&lt;ad 長度&gt;]</code>：計算並報告基於一個列印件測量的偏斜度（以弧度和角度為單位）。它可以用來驗證應用校正後印表機的當前偏斜度。它也可以用來確定是否有必要進行偏斜矯正。有關偏斜矯正列印模型和測量方法詳見<a href="Skew_Correction.html">偏斜校正文件</a>。</p>
 <h4 id="skew_profile">SKEW_PROFILE<a class="headerlink" href="#skew_profile" title="Permanent link">&para;</a></h4>
 <p><code>SKEW_PROFILE [LOAD=&lt;名稱&gt;] [SAVE=&lt;名稱&gt;] [REMOVE=&lt;名稱&gt;]</code>：skew_correction 配置管理命令。 LOAD 將從與提供的名稱匹配的配置中載入偏斜狀態。 SAVE 會將目前偏斜狀態儲存到與提供的名稱匹配的配置中。 REMOVE 將從持久記憶體中刪除與提供的名稱匹配的配置。請注意，在執行 SAVE 或 REMOVE 操作后，必須執行 SAVE_CONFIG G程式碼才能儲存更改。</p>
+<h3 id="smart_effector">[smart_effector]<a class="headerlink" href="#smart_effector" title="Permanent link">&para;</a></h3>
+<p>Several commands are available when a <a href="Config_Reference.html#smart_effector">smart_effector config section</a> is enabled. Be sure to check the official documentation for the Smart Effector on the <a href="https://duet3d.dozuki.com/Wiki/Smart_effector_and_carriage_adapters_for_delta_printer">Duet3D Wiki</a> before changing the Smart Effector parameters. Also check the <a href="Probe_Calibrate.html">probe calibration guide</a>.</p>
+<h4 id="set_smart_effector">SET_SMART_EFFECTOR<a class="headerlink" href="#set_smart_effector" title="Permanent link">&para;</a></h4>
+<p><code>SET_SMART_EFFECTOR [SENSITIVITY=&lt;sensitivity&gt;] [ACCEL=&lt;accel&gt;] [RECOVERY_TIME=&lt;time&gt;]</code>: Set the Smart Effector parameters. When <code>SENSITIVITY</code> is specified, the respective value is written to the SmartEffector EEPROM (requires <code>control_pin</code> to be provided). Acceptable <code>&lt;sensitivity&gt;</code> values are 0..255, the default is 50. Lower values require less nozzle contact force to trigger (but there is a higher risk of false triggering due to vibrations during probing), and higher values reduce false triggering (but require larger contact force to trigger). Since the sensitivity is written to EEPROM, it is preserved after the shutdown, and so it does not need to be configured on every printer startup. <code>ACCEL</code> and <code>RECOVERY_TIME</code> allow to override the corresponding parameters at run-time, see the <a href="Config_Reference.html#smart_effector">config section</a> of Smart Effector for more info on those parameters.</p>
+<h4 id="reset_smart_effector">RESET_SMART_EFFECTOR<a class="headerlink" href="#reset_smart_effector" title="Permanent link">&para;</a></h4>
+<p><code>RESET_SMART_EFFECTOR</code>: Resets Smart Effector sensitivity to its factory settings. Requires <code>control_pin</code> to be provided in the config section.</p>
 <h3 id="stepper_enable">[stepper_enable]<a class="headerlink" href="#stepper_enable" title="Permanent link">&para;</a></h3>
 <p>模組stepper_enable已自動載入.</p>
 <h4 id="set_stepper_enable">SET_STEPPER_ENABLE<a class="headerlink" href="#set_stepper_enable" title="Permanent link">&para;</a></h4>
--- a/zh-Hant/_klipper3d/pycache/mkdocs_hooks.cpython-38.pyc
+++ b/zh-Hant/_klipper3d/pycache/mkdocs_hooks.cpython-38.pyc
--- a/zh-Hant/search/search_index.json
+++ b/zh-Hant/search/search_index.json
--- a/zh-Hant/sitemap.xml
+++ b/zh-Hant/sitemap.xml
@@ -2,237 +2,237 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
    <url>
         <loc>None</loc>
-         <lastmod>2022-04-28</lastmod>
+         <lastmod>2022-04-29</lastmod>
         <changefreq>daily</changefreq>
    </url>
 </urlset>
--- a/zh-Hant/sitemap.xml.gz
+++ b/zh-Hant/sitemap.xml.gz