diff --git a/docs/CROWDIN/zh_CN/404.md b/docs/CROWDIN/zh_CN/404.md
index c5726f6511b6..dc3d2b0659b2 100644
--- a/docs/CROWDIN/zh_CN/404.md
+++ b/docs/CROWDIN/zh_CN/404.md
@@ -6,9 +6,9 @@ orphan: true
# Page not found
-- If this occurred after switching language or AAPS documentation version, just go back to the main menu and resume browsing. Not all pages are present in all translations and versions.
-- If you were following a link, please copy the URL and note the link position or name.
- **Report the broken link**, please, using the easiest method for you:
+- 若此情况发生在切换语言或AAPS文档版本后，只需返回主菜单继续浏览即可。 并非所有页面都有完整的翻译版本和不同版本。
+- 如果您是通过链接访问到此页面，请复制该URL并记录链接位置或名称。
+ **请通过您认为最便捷的方式报告失效链接**：
- [Discord](https://discord.com/channels/629952586895851530/817392867995680768)
- [Facebook](https://www.facebook.com/groups/AndroidAPSUsers)
- [GitHub](https://github.com/openaps/AndroidAPSdocs/issues)
diff --git a/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md b/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md
index e4b12704a749..a7c2f80e639d 100644
--- a/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md
@@ -1,196 +1,196 @@
-# How to use Autotune plugin (dev only)
+# Autotune插件使用说明（仅限开发者）
-Documentation about Autotune algorithm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html).
+关于Autotune算法的文档可在[OpenAPS文档](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html)中查阅。
-Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
+Autotune插件是OpenAPS自动调节算法在AAPS中的具体实现。
-**Currently Autotune Plugin is only available in [dev branch](../AdvancedOptions/DevBranch.md) and with Engineering mode.**
+**目前，Autotune插件仅可在[开发分支（dev branch）](../AdvancedOptions/DevBranch.md)中通过工程模式（Engineering mode）使用。**
-
+
-## Autotune user interface
+## Autotune用户界面
-
+
-- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected)
- - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value
-- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation)
- - Note: each time you change Tune days parameter, previous results will be removed
-- Last Run is a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successful run.
-- Warning show you for example some information about selected profile (if you have several IC values or several ISF values)
- - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorithm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile.
-- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DIA, IC, ISF, basal and target)
- - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DIA and target will remain unchanged in output profile.
+- 您可在配置文件下拉菜单中选择需要调整的输入配置文件（默认已选中当前生效的配置文件）。
+ - 注意：每次选择新配置文件时，先前结果将被清除，且"调节天数"参数将重置为默认值。
+- "调节天数"参数用于设定参与配置文件优化计算的历史数据天数。 该参数取值范围为1至30天（最小值1天，最大值30天）。 为确保获得准确、平滑的迭代计算结果，该数值不宜过小（建议每次计算至少使用7天以上数据）。
+ - 注意：每次调整"调节天数"参数时，系统将自动清除历史优化结果。
+- "最近执行"是一个可恢复您最后一次有效计算结果的链接功能。 若当日未启动Autotune功能，或因前述计算参数调整导致历史结果被清除，您可通过"最近执行"功能恢复最近一次成功运行的参数与结果。
+- 警告信息将显示所选配置文件的相关参数（例如：当存在多个胰岛素敏感系数（ISF）或多个胰岛素碳水化合物比值（IC）时）。
+ - 注意：Autotune算法计算时仅支持单一胰岛素碳水化合物比值（IC）与单一胰岛素敏感系数（ISF）参数。 当前尚无支持昼夜节律性胰岛素碳水化合物比值（circadian IC）或昼夜节律性胰岛素敏感系数（circadian ISF）调节的Autotune算法。 若您的输入配置文件包含多组参数值，系统将在警告区域显示用于配置文件调优的基准平均值。
+- "检查输入配置文件"按钮将启动配置文件查看器，供您快速核验以下参数：胰岛素单位（Units）、胰岛素活性时长（DIA）、胰岛素碳水化合物比值（IC）、胰岛素敏感系数（ISF）、基础率（basal）及目标血糖范围（target）。
+ - 注意：Autotune算法仅对以下参数进行优化调节：单一数值的胰岛素碳水化合物比值（IC），单一数值的胰岛素敏感系数（ISF），具有昼夜节律变化的基础率（basal）。 在输出配置文件中，胰岛素单位（Units）、胰岛素活性时长（DIA）及目标血糖范围（target）将保持原值不变。
-- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days
- - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results
+- 点击"执行Autotune"将使用选定的配置文件及设定的调节天数（Tune days）参数启动Autotune算法计算。
+ - 注意：Autotune算法计算过程可能耗时较长。 启动计算后，您可切换至其他界面（如主界面等），稍后返回Autotune插件查看计算结果。
-
+
-- Then during the run you will see intermediate results below
+- 运行过程中，系统将在下方实时显示中间计算结果。
- - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters.
+ - 注意：运行期间所有设置将被锁定，您将无法再修改已选输入配置文件或调节天数参数。 若需使用其他参数启动新计算任务，您必须等待当前计算流程完成。
- 
+ 
-- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below.
+- 当Autotune算法计算完成后，界面将显示优化后的配置文件（Tuned profile）和底部四个功能按钮。
-
+
-- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%").
+- 必须始终对比输入配置文件（"Profile"列）、优化输出配置文件（"Tuned"列）和各参数值的变化百分比（"%"列）。
-- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon)
+- 对于基础率（basal rates）参数，系统还会显示"数据缺失天数"统计值。 当Autotune算法在特定时段（如餐后碳水化合物吸收期）缺乏足够被标记为"基础率（Basal）"的数据时，系统将记录为数据缺失天数（missing days），此类情况将影响该时段基础率的优化计算。 该数值应尽可能保持最低，特别是在基础率调节至关重要的时段（如夜间或傍晚后期）。
-- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
+- 点击"对比配置文件"按钮将打开配置文件对比视图。 输入配置文件以蓝色标识，优化输出配置文件（标为"Tuned"）则以红色显示。
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - 注意：下例所示输入配置文件中的胰岛素碳水化合物比值（IC）与胰岛素敏感系数（ISF）均呈现昼夜节律变化，但经计算输出的优化配置文件将生成单一参数值。 若需获取昼夜节律性输出配置文件，请参阅下方[昼夜节律IC/ISF配置文件](#circadian-ic-or-isf-profile)说明。
- 
+ 
-- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated.
+- 若优化结果可信（输入与输出配置文件间变化百分比偏低），您可依次点击"激活配置文件"按钮，再点击"确认"完成参数生效验证。
- - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin.
- - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation
+ - 激活优化配置文件（Activate Tuned profile）操作将自动在本地配置文件插件中创建名为"Tuned"的新配置文件。
+ - 若本地配置文件插件中已存在名为"Tuned"的配置文件，系统将在激活前自动使用Autotune计算结果更新该配置文件。
- 
+ 
-- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button
+- 若认为优化配置文件（Tuned profile）需进一步调整（例如某些参数变化幅度过大），您可点击"复制至本地配置文件"按钮进行手动修正。
- - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin
+ - 系统将在本地配置文件插件中创建一个带"Tuned"前缀且包含运行日期时间戳的新配置文件。
-
+
-- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin)
+- 随后您可在本地配置文件中选定待编辑的优化配置文件（Tuned profile）——当您打开本地配置文件插件时，系统将默认选中该配置文件。
- - the values in local profile will but rounded in the user interface to your pump capabilities
+ - 本地配置文件中的数值将在用户界面中根据胰岛素泵功能进行舍入处理。
- 
+ 
-- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK
+- 若需将Autotune优化结果替换当前输入配置文件，请点击"更新输入配置文件"按钮，在弹出窗口中点击"确认"完成验证
- - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile?
+ - 注意：若您在点击"更新输入配置文件"后点击"激活配置文件"，系统将激活您更新后的配置文件（而非默认的"Tuned"配置文件）。
- 
+ 
-- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediately see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button
+- 若您已更新输入配置文件，原"更新输入配置文件"按钮将替换为"恢复输入配置文件"按钮（参见下方截图说明）。 通过此方式，您可即时确认本地配置文件插件中的当前输入配置文件是否已包含最近一次运行的优化结果。 您还可通过此按钮恢复未包含Autotune优化结果的原始输入配置文件。
- 
+ 
-## Autotune settings
+## Autotune设置
(autotune-plugin-settings)=
-### Autotune plugin settings
+### Autotune插件设置
-
+
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated.
- - **Be Careful, you must trust and verify during several following days, that after an update and activation of Tuned profile without modification, it improves your loop**
+- 自动化切换配置文件功能（默认关闭）：详见下方[通过自动化规则运行Autotune](#run-autotune-with-an-automation-rule)说明。 若将此设置切换为"开启"状态，系统将自动使用优化配置文件（Tuned profile）更新输入配置文件，并自动激活更新后的配置。
+ - **警告：在随后数日内，您必须对未经修改即更新激活的优化配置文件（Tuned profile）进行持续验证，确保其确实能提升闭环系统运行效果。**
-- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal.
- - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off)
-- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- 将未标记餐食（UAM）归类为基础率（默认开启）：本设置适用于使用AndroidAPS时未输入任何碳水化合物数据（完全UAM模式）的用户。 当设置为"关闭"时，系统将禁止将未标记餐食（UAM）归类为基础率。
+ - 注意：若系统在一天内检测到至少1小时的碳水化合物吸收活动，则无论当前设置为"开启"或"关闭"，所有标记为"未标记餐食（UAM）"的数据都将被归类为基础率。
+- 数据采集天数（默认5天）：您可通过此设置定义默认值范围。 每当在Autotune插件中选择新配置文件时，"优化天数"参数将自动重置为此默认值。
+- 昼夜节律IC/ISF均值应用功能（默认关闭）：详见下方[昼夜节律IC/ISF配置文件](#circadian-ic-or-isf-profile)说明。
-### Other settings
+### 其他设置
-- Autotune also uses Max autosens ratio and Min autosens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings
+- Autotune算法还将通过最大自动灵敏度比率（Max autosens ratio）和最小自动灵敏度比率（Min autosens ratio）限制调整幅度。 您可通过 配置构建器 > 灵敏度检测插件 > 设置 > 高级设置 查看并调整这些参数值。
- 
+ 
-## Advanced feature
+## 高级功能
(autotune-circadian-ic-or-isf-profile)=
-### Circadian IC or ISF profile
+### 昼夜节律IC或ISF配置文件
-- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadian IC/ISF"
+- 若您的配置文件中存在显著的胰岛素碳水化合物比值（IC）和/或胰岛素敏感系数（ISF）波动，且完全确信昼夜节律时间及变化参数的准确性，则可将"昼夜节律IC/ISF均值应用"功能设置为开启状态。
- - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values
+ - 请注意：Autotune计算将始终基于单一参数值执行，且该算法不会对昼夜节律波动进行优化调整。 本设置仅对您昼夜节律参数中的胰岛素碳水化合物比值（IC）和/或胰岛素敏感系数（ISF）应用计算得出的平均波动值。
-- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right)
+- 请参见下方截图对比：左侧-禁用"平均波动应用"功能的优化配置文件（Tuned profile），右侧-启用"平均波动应用"功能的优化配置文件。
- 
+ 
-### Tune specific days of the week
+### 按周指定日期调校
-- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation)
- - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below)
- - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation)
+- 若点击"运行天数"参数右侧带眼睛图标的复选框，即可显示日期选择界面。 您可指定每周参与Autotune计算的特定日期（如下图所示示例：已排除周六周日的"工作日"模式将不纳入计算范围）。
+ - 若Autotune计算包含的天数少于"调校天数"设定值，您将在天数选择器右侧看到实际参与计算的天数（如下例所示：10天）。
+ - 当前设置仅在剩余天数充足时方能获得理想效果（例如：若您仅为周末调校特定配置文件——仅选择周六周日时，建议将"调校天数"设为至少21或28天，以确保Autotune计算能包含6-8个有效数据日）。
-
+
-- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below)
+- 在Autotune计算过程中，系统将实时显示计算进度（如下图所示示例："第3/10天部分调校结果"）。
- 
+ 
(autotune-run-autotune-with-an-automation-rule)=
-## Run Autotune with an automation rule
+## 通过自动化规则运行Autotune
-First step is to define correct trigger for an automation rule with Autotune:
+首要步骤是为Autotune自动化规则定义正确触发器：
-Note: for more information on how to set an automation rule, see [here](../DailyLifeWithAaps/Automations.md).
+注：有关如何设置自动化规则的更多信息，请参见[此处](../DailyLifeWithAaps/Automations.md)。
-- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be run daily (each new run you shift one day later and quickly profile modification should be tiny)
+- 您应选择"循环时间触发器"：每日仅运行一次Autotune，该算法设计为每日执行（每次运行将自动顺延一天，且配置文件修改幅度应保持最小）。
- 
+ 
-- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation.
+- 建议初期在日间运行Autotune以便实时核查优化结果。 若需夜间运行Autotune，请将触发器时间设置为凌晨4点或更晚，以确保将当日数据纳入下次Autotune计算范围。
- 
+ 
-- Then you can select "Run Autotune" Action in the list
+- 随后您可在操作列表中选择"运行Autotune"动作项。
- 
+ 
-- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected.
+- 随后您可选择"Autotune调参动作"来调整本次运行的参数配置。 默认参数配置包括"当前生效配置文件"（Active Profile），Autotune插件设置中定义的"调校天数"默认值，以及全选所有日期。
- 
+ 
-- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation.
+- 在使用数日后，若您完全信任Autotune计算结果且参数修改幅度较低，即可修改[Autotune设置](#autotune-plugin-settings)中的"自动化切换配置文件"功能为启用状态，系统将在计算后自动更新并激活优化后的配置文件。
-Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger...
+注意：如需按周自动调校特定日期配置文件（例如分别为"周末"和"工作日"创建独立配置），请为每个配置文件创建独立规则，在触发器和Autotune动作中保持日期选择一致，将"调校天数"设为足够大的值（确保包含6-8个有效数据日），触发器时间必须设置在凌晨4点之后，等等……
-- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation).
+- 请参见下方为"我的配置文件"设置的工作日调校规则示例：对"工作日"进行调校，选择14天作为"调校天数"（所以仅10天纳入Autotune计算范围）。
-
+
-## Tips and trick's
+## 提示和技巧
-Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results.
+Autotune算法依赖数据库中的历史数据进行计算，因此若您在新手机上刚安装AAPS系统，需等待数日积累足够天数的数据后，方可启动Autotune获取有效调校结果。
-Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it.
+Autotune仅作为辅助工具，使用者需定期核验计算生成的配置文件是否符合临床预期。 若存在任何疑问，请修改Autotune设置（如调整计算天数等参数），或者将计算结果复制至本地配置文件，或者使用前手动调整配置文件参数。
-Always use Autotune several days manually to check results before applying them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before)
+务必手动运行Autotune多日以验证结果可靠性后，方可应用调校方案。 仅当您完全信任Autotune计算结果，且新旧配置文件间差异微小时，方可启用自动化功能（此前绝对不可启用）。
-- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it**
+- Autotune的适配性因人而异——**若对计算结果存疑，请停止使用**
-It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications
+深入分析Autotune结果以理解（或尝试理解）其提出特定修改建议的原因，亦为关键所在。
-- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more aggressivity required) or below 100% (you are more sensitive)
-- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF)
+- 您的配置文件可能出现整体强度调整（例如：基础率总量提升伴随胰岛素敏感系数(ISF)与碳水化合物系数(IC)数值下降的情况）。 该调整可能伴随连续数日的自动灵敏度校正值高于100%（需更积极干预）或低于100%（敏感性提升）的情况。
+- Autotune算法可能建议调整基础率与胰岛素碳水化合物比值(IC)/胰岛素敏感系数(ISF)之间的平衡关系（例如：降低基础率并采用更积极的IC/ISF组合方案）。
-We advise to not use Autotune in the following cases:
+我们建议在以下情况下禁用Autotune功能：
-- You don't enter all your carbs
- - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexpected increase of your BG value and will increase your basal rates the 4 hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carbs especially correction for hypo.
-- You have a lot of period with UAM detected during the day.
- - Do you have entered all your carbs and correctly estimated your Carbs ?
- - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary)
+- 未完整记录碳水化合物摄入量
+ - 若未输入低血糖后的碳水化合物校正量，Autotune将误判血糖异常升高，进而提前4小时增加基础率——这种调整可能与避免低血糖的需求完全相悖，夜间发生时风险尤甚。 因此，完整记录碳水化合物摄入量（特别是低血糖校正量）至关重要
+- 当系统检测到日间频繁出现未标记餐食(UAM)时
+ - 是否已完整记录所有碳水化合物摄入量并准确估算碳水值？
+ - 所有未标记餐食(UAM)时段（除非全天未摄入碳水且已禁用"UAM归为基础率"功能）都将被归类为基础率，这可能导致基础率被过度提升（远超实际需求）。
-- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results.
- - When you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercise, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit too high.
-- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. If during the pas weeks you only have one or 2 "bad days", you can disable manually these days in autotune calculation to exclude them from calculation, and again **check carefully if you can trust the results**
-- If the percentage of modification is too important
- - You can try to increase the number of days to get smoother results
\ No newline at end of file
+- 碳水化合物吸收速率过缓：若大部分吸收过程依赖min_5m_carbimpact参数计算（可通过COB曲线顶端的橙色小圆点识别此类时段），可能导致COB计算错误并引发连锁性结果偏差。
+ - 运动期间生理敏感性增强：运动时胰岛素敏感性普遍提升且血糖波动趋缓，故运动中和运动后出现碳水化合物缓释时段属常见生理现象。 但若频繁出现非预期的碳水化合物缓释现象，则可能需要提高配置文件中的碳水化合物系数(IC)值，或者适当下调min_5m_carbimpact参数阈值。
+- 当出现"异常代谢日"时（例如：持续数小时的高血糖状态需大量胰岛素才能回落至目标范围，或传感器更换后出现长期血糖读数异常），需特别注意数据有效性。 若过去数周仅出现1-2个"异常日"，可手动在Autotune计算中禁用这些日期以排除影响，并务必**仔细核查结果可信度**。
+- 若参数修改幅度超出合理阈值
+ - 建议增加计算天数以获得更平稳的调校结果
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md b/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md
index 54bd73b55794..6438288f8848 100644
--- a/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md
@@ -1,14 +1,13 @@
-# Development branch
+# 开发分支
-Attention:
-Dev branch is for the further development of AAPS only. It should be used on a separate phone for testing not for actual looping!
+注意： 开发分支（Dev branch）仅用于AAPS的后续开发。 该版本应在备用手机上作测试用途，切勿用于实际闭环治疗！
-The most stable version of AAPS to use is that in the [Master branch](https://github.com/nightscout/AndroidAPS/tree/master). It is advised to stay on the Master branch for actual looping.
+AAPS最稳定的版本是[主分支（Master branch）版本](https://github.com/nightscout/AndroidAPS/tree/master)。 建议在实际闭环治疗中持续使用主分支版本。
-The dev version of AAPS is only for developers and testers comfortable dealing with stacktraces, looking through log files and maybe firing up the debugger to produce bug reports that are helpful to the developers (in short: people that know what they are doing without being assisted!). Therefore many unfinished features are disabled. To enable these features enter **Engineering Mode** by creating a file named `engineering_mode` in directory /AAPS/extra . Enabling the engineering mode might break the loop entirely.
+AAPS开发版（dev version）仅适用于能够熟练处理堆栈跟踪（stacktraces）、查阅日志文件，并能启动调试器（debugger）生成有效开发者错误报告的人员——简言之，即无需协助即能独立操作的资深开发者与测试人员。 因此，诸多未完成功能已被禁用。 要启用这些功能，需通过在/AAPS/extra目录下创建名为`engineering_mode`的文件来进入**工程模式**。 启用工程模式可能导致整个闭环系统完全失效。
-However, the Dev branch is a good place to see what features are being tested and to help iron out the bugs and give feedback on how the new features work in practice. Often people will test the Dev branch on an old phone and pump until they are confident it is stable - any use of it is at your own risk. When testing any new features, remember that you are choosing to test a still-in-development feature. Do so at your own risk & with due diligence to keep yourself safe.
+不过，开发分支（Dev branch）是了解正在测试中的功能、协助修复漏洞以及反馈新功能实际运行情况的理想平台。 用户常会在备用手机上测试开发分支（Dev branch），并通过泵注试验直至确认其稳定性——但任何使用行为均需自行承担风险。 在测试任何新功能时，请谨记您所测试的仍是处于开发阶段的功能。 请自行承担风险，并采取充分的安全防护措施。
-If you find a bug or think something wrong has happened when using the Dev branch, then view the [issues tab](https://github.com/nightscout/AndroidAPS/issues) to check whether anyone else has found it, or add it yourself if not. The more information you can share here the better (don't forget you may need to share your [log files](../GettingHelp/AccessingLogFiles.md). The new features can also be discussed on [discord](https://discord.gg/4fQUWHZ4Mw).
+若在使用开发分支（Dev branch）时发现程序漏洞或异常情况，请查看[问题标签页（issues tab）](https://github.com/nightscout/AndroidAPS/issues)确认是否已有其他用户提交相同问题；若无相关记录，请自行提交问题报告。 请尽可能详细地在此提供信息（切记可能需要分享您的[日志文件（log files）](../GettingHelp/AccessingLogFiles.md)），信息越详尽越好。 新功能的相关讨论也可在[Discord平台](https://discord.gg/4fQUWHZ4Mw)进行。
-A dev version has an expiration date. This seems inconvenient when using it satisfactorily, but serves a purpose. When a single dev version doing the rounds, it is easier to keep track of bugs that people are reporting. The developers do not want to be in a position where there are three versions of dev in the wild where bugs are fixed in some and not others, and people continue to report the fixed ones.
\ No newline at end of file
+开发版（dev version）设有有效期限制。 这在使用满意时看似不便，但实为有特定设计目的。 如果只有一个开发版本，就更容易跟踪人们报告的错误。 开发者不希望出现三种不同版本的开发模式同时存在的情况，其中某些版本修复了漏洞，而其他版本没有修复，导致人们仍然报告已经修复的问题。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md
index 644827742e97..94227439c5ec 100644
--- a/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md
@@ -1,7 +1,7 @@
# 全闭环
-全闭环（**FCL**）的主要吸引力在于它有潜力模拟人工胰腺，使日常管理更轻松，无需为进餐推注胰岛素。
+全闭环系统（**FCL**）的主要优势在于其能够模拟人工胰腺功能，无需餐前注射大剂量胰岛素即可简化日常血糖管理。
虽然**混合闭环**（“HCL”）是基于算法的，但它仍然需要用户在餐前手动进行餐前大剂量注射。 因此，环路可能会进入临时关闭状态（临时零基础率）以防止胰岛素输送过多。
@@ -48,7 +48,7 @@
来源：
- 
+ 
@@ -82,7 +82,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
- 高脂肪或高蛋白饮食，或慢消化/胃轻瘫，反而使**FCL**更容易实施，因为后期碳水化合物能很好覆盖推注胰岛素不可避免的"尾部"效应。
-#### Glycemic index and effect on blood glucose
+#### 升糖指数与血糖影响
**UAM**模式的挑战随着"对血糖影响（EBG）"增加而增加：
@@ -91,7 +91,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
1) **无EBG**：如新鲜肉类、鱼类、鸡蛋、培根、油类、奶酪。 2) **低EBG**：如新鲜蔬菜和浆果、蘑菇、坚果、牛奶、酸奶、奶酪。 3) **中EBG**：如全麦面包/面条、土豆、野米、燕麦、干果。 4) **高EBG**：如小麦面包、法棍、吐司、华夫饼、饼干、土豆泥、面条、米饭。 5) **极高EBG**：如糖、甜饮、果汁、玉米片、糖果、薯片、咸脆棒。
-
+
对**FCL**最具挑战性的餐食是仅含极高和高**EBG**成分的食物（图中红色部分）：不仅**血糖**迅速飙升，且缺乏脂肪/蛋白质/纤维成分来平衡控制高血糖早期所需的胰岛素"尾部"效应。
@@ -126,7 +126,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
如果基础率非常低，生成的**SMB**限制可能不足以控制餐后**血糖**上升。 一个解决方案是避免导致强烈**血糖**飙升的饮食，然后切换到提供新**SMB**输送参数的**AAPS**开发版：smb_max_range_extension。 这将使标准的最大 2 小时基础胰岛素量扩大 >1 倍。 （此外，默认的 50% **SMB** 输送率可能会在开发变体中提高） 。
-**按照说明使AAPS通过若干SMB模拟您的推注**。
+**按照说明操作，使AAPS能够通过若干次超级微剂量（SMB）模拟您的餐前大剂量注射**。
定期检查 **SMB** 选项卡，查看您的 **SMB** 是否被允许足够大，以在用餐开始时提供循环所需的胰岛素。
@@ -134,9 +134,9 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
```{admonition} Boosting **ISF** can become dangerous
-:class: danger
+:class: 危险
-密切观察/分析餐后**SMB**量。 逐步调校，每次最多调整1-2个参数。
+请密切观察/分析**超级微剂量(SMB)**在餐后初期的给药量。 逐步调校，每次最多调整1-2个参数。
您的**AAPS**设置必须充分适应您的各种餐食。
```
@@ -167,7 +167,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
**FCL**成功的关键在于：**在餐后血糖开始上升时，闭环必须尽快给予非常大的自动SMB**"追赶"所需**IOB**（与您在**HCL**中对类似餐食的典型推注量比较！）
-为此，需分析**HCL**数据以确定哪些变化率（delta）可能与进餐无关，哪些相关。
+为实现这一目标，需分析来自您**混合闭环系统（HCL）**的数据，以区分可能与饮食无关或者相关的**血糖变化值（deltas）**。
- 由于您可以在预定义的时间窗口内定义**自动化**，因此您只需要在该时间窗口内进行分析。
- 如果餐型差异大（如高碳早餐、低碳午餐），可为不同时段设置不同**规则集**。
@@ -229,7 +229,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
**注意：规则#3仅在无活动TT时有效**。 例如，如果您使用EatingSoonTT，必须在该时间结束（通常餐后30-40分钟）。
可通过设置**自动化规则**条件（如IOB>65%*IOB阈值）来终止可能运行的EatingSoonTT。
-> 使用 EatingSoonTT 的方法 一些闭环使用者会在用餐开始前大约一小时或更长时间设置 EatingSoonTT（通过按下 TT 按钮，或者如果用餐时间段相当固定，则通过降低的**配置文件****BG** 目标自动设置），只是为了保证较低的起始 **BG** 和略微增加的 **iob**。 但是，假设 **FCL** 始终朝着目标前进，这可能不会产生太多效果，您可能更愿意定义一个**自动化**，在识别到用餐开始时（葡萄糖增量，或加速度 = 增量 > 平均增量）设置 EatingSoonTT。 低**TT**在此阶段很重要，因为任何**SMB**计算基于（预测血糖 - TT）/敏感系数，小TT会使胰岛素需求更大。
+> 使用 EatingSoonTT 的方法 一些闭环使用者会在用餐开始前大约一小时或更长时间设置 EatingSoonTT（通过按下 TT 按钮，或者如果用餐时间段相当固定，则通过降低的**配置文件****BG** 目标自动设置），只是为了保证较低的起始 **BG** 和略微增加的 **iob**。 但是，假设 **FCL** 始终朝着目标前进，这可能不会产生太多效果，您可能更愿意定义一个**自动化**，在识别到用餐开始时（葡萄糖增量，或加速度 = 增量 > 平均增量）设置 EatingSoonTT。 在此阶段，较低的**临时目标（TT）**至关重要，因为闭环系统会通过（预测血糖值减去TT）/胰岛素敏感系数来计算每个**超级微剂量（SMB）**，因此较小的TT值会使最终所需的胰岛素剂量（insulinReq）增大。
在给予最初的增强型 **SMB** 后，您设置的 iobTH 和*自动化** #3 应该在限制葡萄糖峰值和餐后不导致低血糖之间取得良好平衡。
@@ -237,7 +237,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
### 高血糖值的停滞状态
-在"丰盛"餐后出现长期高血糖平台时，规则#6（下图左）"餐后高血糖"有助于应对脂肪酸抵抗：多道餐、油腻披萨、奶酪火锅后，血糖曲线可能形成双峰或长平台。
+若在享用丰盛餐食后，出现**高血糖（BG）**值长期停滞的情况，可启用**自动化**方案#6（左下方所示）——"餐后高血糖"模式，该方案专门应对脂肪酸抵抗现象：在食用多道菜正餐、大量油脂披萨或奶酪火锅晚餐后，血糖曲线可能呈现双峰形态，或更常见表现为长时间的高位平台期。
@@ -285,7 +285,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
### 如何恢复到混合闭环
-您可取消勾选**自动化规则**中与**FCL**相关的顶部复选框，即可恢复餐时大剂量注射功能并重新启用碳水化合物输入。 您可能需要进入**AAPS**的偏好设置/概览/按钮选项，为主屏幕重新启用"胰岛素"、"计算器"等按钮功能。 请注意，现在又轮到您为膳食进行推注了。
+您可取消勾选**自动化规则**中与**FCL**相关的顶部复选框，即可恢复餐时大剂量注射功能并重新启用碳水化合物输入。 您可能需要进入**AAPS**的偏好设置/概览/按钮选项，为主屏幕重新启用"胰岛素"、"计算器"等按钮功能。 请注意：现在又需要您自行注射餐前大剂量胰岛素了。
建议仅在已完整定义并启用**自动化规则**的餐次（时段）采用**全闭环模式（FCL）**，而其他需要**混合闭环模式（HCL）**的餐次（或过渡期尚未定义规则的时段），则取消勾选相应配置。
@@ -325,17 +325,17 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
- SMB 输送率可能可以设置得更小。 请注意：在此情况下，该设置将全局生效，适用于所有时间段的**超级微剂量(SMB)**。
- 餐后胰岛素“拖尾”问题
- 您可能需要吃点零食（看到低血糖预测）或葡萄糖片（如果已经处于低血糖区）。 但需注意：闭环系统在某个时间点提示您所需的碳水化合物量很可能被高估，因为系统完全无法获取您的实际碳水摄入数据（尽管您可能自行估算包括脂肪和蛋白质在内的待吸收营养总量）。
- - A valuable information would be whether the problem originates mostly in the bg rise phase already. Then setting a lower iobTH might be an easy remedy.
- - If the need for additional carbs happens frequently, note down how many grams were needed (not counting what you eventually took too much and required extra insulin again). Then use your profile IC value to estimate how much insulin less the **SMB** should have delivered, and go with this info into your tuning (regarding the **Percentage Profile** in **Automations**, or maybe also your set iobTH). This may relate to the**SMBs** given when glucose was high, or also extending regarding also the **SMBs** during the **BG** rise.
- - It could well be that you simply have to accept higher **BG** peaks for not going low. Or change diet to something with lower amounts of carbs, and higher amount of proteien and fats.
+ - 关键信息在于：问题是否主要源于血糖上升阶段初期。 那么，将胰岛素活性阈值（iobTH）设低可能是个简单的解决方案。
+ - 若频繁需要额外补充碳水化合物，请记录所需克数（不包括因过量摄入而需再次追加胰岛素的部分）。 随后，根据您的胰岛素敏感系数（IC值）估算**超级微剂量（SMB）**应减少的胰岛素量，并将该数据用于参数调整（涉及**自动化**中的**百分比配置文件**，或可能包括您设定的胰岛素活性阈值iobTH）。 这可能与高血糖期间给予的**SMB**有关，或需进一步考量**血糖**上升阶段的**SMB**设置。
+ - 这可能意味着您需要接受更高的**血糖**峰值以避免低血糖。 或者调整饮食结构——减少碳水化合物摄入，同时增加蛋白质和脂肪的比例。
-### More info
+### 更多信息
-Make sure you stay in touch with other **FCL** users.
+建议保持与其他**FCL**用户交流。
-Discussion Full Closed Loop using Automations:
+讨论利用自动化技术实现全闭环：
-- English: [Discord Channel](https://discord.gg/ChXj8BaKwA)
+- 英语：[Discord 频道](https://discord.gg/ChXj8BaKwA)
-- German: [German Looper Community](https://de.loopercommunity.org/t/ueber-die-kategorie-full-loop/10107)
+- 德语：[德国 Looper 社区](https://de.loopercommunity.org/t/ueber-die-kategorie-full-loop/10107)
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/CgmNightscoutUpload.md b/docs/CROWDIN/zh_CN/CompatibleCgms/CgmNightscoutUpload.md
index b9f771a9ce8c..50f2ff193200 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/CgmNightscoutUpload.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/CgmNightscoutUpload.md
@@ -2,13 +2,13 @@
orphan: true
- - -
-# For users of other CGM uploaded to Nightscout
+# 对于上传至Nightscout的其他连续血糖监测(CGM)设备用户
-If you have any other CGM set up that can send your BG data **only** to [Nightscout](https://nightscout.github.io/).
+如果您的其他连续血糖监测(CGM)设备设置**仅能**将血糖数据发送至[Nightscout](https://nightscout.github.io/)。
```{important}
-This data source will not work when you are offline, when you experience network issues or when your Nightscout site is down. Use with caution.
+当您处于离线状态、遇到网络问题或Nightscout站点不可用时，此数据源将无法工作。 请谨慎使用。
```
-- Setup NSClient with your Nightscout site information.
-- Select NSClient BG in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 使用您的Nightscout站点信息配置NSClient。
+- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source)中选择NSClient BG。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG5.md b/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG5.md
index 865cd40a2b4b..ed15e1bc2deb 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG5.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG5.md
@@ -4,33 +4,33 @@ orphan: true
# Dexcom G5
-## If using G5 with xDrip+
+## 如果使用Dexcom G5搭配xDrip+
-- You can safely download the [latest APK (stable)](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) unless you want specific newly developed features.
-- Setup xDrip+ with G5 following [these instructions](https://navid200.github.io/xDrip/docs/G5-Recommended-Settings.html).
-- Setup xDrip+ reading the [xDrip+ settings page](../CompatibleCgms/xDrip.md) .
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 您可以安全下载[最新APK（稳定版）](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk)，除非您需要特定的新开发功能。
+- 按照[这些说明](https://navid200.github.io/xDrip/docs/G5-Recommended-Settings.html)配置xDrip+与G5设备。
+- 请按照[xDrip+设置页面](../CompatibleCgms/xDrip.md)配置xDrip+。
+- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source)中选择xDrip+。
-## If using G5 with patched Dexcom app
+## 如果使用经过修改的Dexcom应用程序搭配G5设备
```{admonition} Legacy apps
:class: warning
-These apps are not compatible with recent Android versions.
+这些应用程序与最新的Android版本不兼容。
```
-- Download the apk from , and choose the version that fits your needs (mg/dl or mmol/l version, G5).
+- 从下载APK文件，并选择适合您需求的版本（mg/dl或mmol/l版本，G5）。
- - Folder 2.4 was for users of AAPS 2.5 and above.
- - Open on your computer. Region will be visible in URL.
+ - 文件夹 2.4 适用于 AAPS 2.5 及更高版本的用户。
+ - 在电脑上打开。 地区信息将在URL中显示。
-- Force stop and uninstall the original Dexcom app, if not already done.
+- 如未完成，请强制停止并卸载原版Dexcom应用。
-- Install downloaded apk
+- 安装下载的 apk
-- Start sensor
+- 启动传感器
-- Select Dexcom App (patched) in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source)中选择Dexcom应用（修改版）。
-- If you want to use xDrip+ alarms via local broadcast: in xDrip+ hamburger menu > settings > hardware data source > 640G /EverSense.
+- 若要通过本地广播使用xDrip+警报功能，请在xDrip+中操作：侧边栏菜单 > 设置 > 硬件数据源 > 选择640G/EverSense。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG6.md b/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG6.md
index df630ac8afba..0ff431181db5 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG6.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG6.md
@@ -2,73 +2,73 @@
orphan: true
- - -
-# Dexcom G6 and ONE
+# Dexcom G6 和 ONE
-## Basics first
+## 先掌握基础
-- Follow general CGM hygiene and setting sensor recommendation [here](../CompatibleCgms/GeneralCGMRecommendation.md).
+- 遵循[此处](../CompatibleCgms/GeneralCGMRecommendation.md)的一般CGM卫生和传感器设置建议。
-## General hints for looping with G6 and ONE
+## 使用G6和ONE闭环系统的一般提示
-- Recent transmitters are called Firefly. Sensors cannot be restarted without removing the transmitter, which itself cannot be reset, they also do not generate raw data.
+- 最近的发射器被称为"萤火虫"。 传感器必须在移除发射器后才能重启（发射器本身不可重置），且这些传感器不会生成原始数据。
-- If you are restarting sensors, ensure you are ready to calibrate and keep an eye on variation.
+- 如需重启传感器，请确保已准备好校准并密切监测数值波动。
-- Pre-soaking of the G6/ONE with factory calibration is likely to give variation in results. If you do pre-soak, then to get best results, you will probably need to calibrate the sensor.
+- 对出厂校准的G6/ONE传感器进行预热可能导致检测结果出现波动。 若进行预热操作，为获得最佳效果，您很可能需要对传感器进行校准。
-Read more in the [article](https://www.diabettech.com/artificial-pancreas/diy-looping-and-cgm/) published by Tim Street at [www.diabettech.com](https://www.diabettech.com).
+更多详情请阅读Tim Street发表在[http://www.diabettech.com](https://www.diabettech.com)上的[文章](https://www.diabettech.com/artificial-pancreas/diy-looping-and-cgm/)。
-## If using G6 or ONE with xDrip+
+## 如使用G6或ONE搭配xDrip+
-- If you are using a recent (Firefly) transmitter, preemptive restarts are **ignored**.
-- If you are using a modded transmitter you do **not need** to use preemptive restarts.
-- If you are using an old rebatteried transmitter, the safest thing to do is **disable** [preemptive restarts](https://navid200.github.io/xDrip/docs/Preemptive-Restart.html). Though, in this case you will have to use the G6 in non-[native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm.html) (which is unadvisable as it disables factory calibration and doesn't filter noisy readings), or else the sensor will stop after 10 days.
-- The Dexcom G6 and ONE transmitters can simultaneously be connected to the Dexcom receiver (or alternatively the t:slim pump) and one app on your phone.
-- When using xDrip+ as receiver uninstall the Dexcom app first. **You cannot connect xDrip+ and Dexcom app with the transmitter at the same time!**
-- If you need Clarity and want to profit from xDrip+ alarms use the [BYODA](#DexcomG6-if-using-g6-with-build-your-own-dexcom-app) (only G6) with local broadcast to xDrip+.
-- You can also use xDrip+ as a companion app of the official Dexcom app, but you might experience delays in BG readings.
-- If not already set up, download [xDrip+](https://github.com/NightscoutFoundation/xDrip) and follow the instructions on [xDrip+ settings page](../CompatibleCgms/xDrip.md).
-- Select xDrip+ in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 若您使用的是新款（萤火虫）发射器，预防性重启将被**忽略**。
+- 若您使用的是改装发射器，则**无需**进行预防性重启。
+- 若您使用的是旧款更换电池的发射器，最安全的做法是**禁用**[预防性重启](https://navid200.github.io/xDrip/docs/Preemptive-Restart.html)。 不过，这种情况下您必须让G6在非[原生模式](https://navid200.github.io/xDrip/docs/Native-Algorithm.html)下运行（不建议这样做，因为这会禁用出厂校准且不过滤噪声读数），否则传感器将在10天后停止工作。
+- Dexcom G6和ONE发射器可同时连接至Dexcom接收器（或替代使用的t:slim泵）及手机上的一个应用程序。
+- 当使用xDrip+作为接收器时，请先卸载Dexcom应用程序。 **无法同时将xDrip+和Dexcom应用程序连接到发射器！**
+- 如需使用Clarity并希望利用xDrip+的警报功能，请选用[BYODA](#DexcomG6-if-using-g6-with-build-your-own-dexcom-app)方案（仅限G6），并通过本地广播传输至xDrip+。
+- 您也可以将xDrip+作为官方Dexcom应用的辅助程序使用，但可能会遇到血糖读数延迟的情况。
+- 如尚未设置，请下载[xDrip+](https://github.com/NightscoutFoundation/xDrip)并按照[xDrip+设置页面](../CompatibleCgms/xDrip.md)的说明操作。
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择xDrip+。
-- Adjust settings in xDrip+ according to [xDrip+ settings page](../CompatibleCgms/xDrip.md)
+- 请根据[xDrip+设置页面](../CompatibleCgms/xDrip.md)调整xDrip+中的设置
(DexcomG6-if-using-g6-with-build-your-own-dexcom-app)=
-## If using G6 with Build Your Own Dexcom App
+## 如使用G6搭配自建Dexcom应用（BYODA）
-- [Build Your Own Dexcom App](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750) (BYODA) supports local broadcast to AAPS and/or xDrip+ (not for G5/ONE/G7 sensors!)
+- [自建Dexcom应用](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750)(BYODA)支持向AAPS和/或xDrip+进行本地广播传输（不适用于G5/ONE/G7传感器！）
-- This app lets you use your Dexcom G6 with any Android smartphone.
-- Uninstall the original Dexcom app or patched Dexcom app if you used one of those previously (**do not stop** the currently running sensor)
-- Install the downloaded apk
-- Enter sensor code and transmitter serial no. in patched app.
-- In phone settings go to apps > Dexcom G6 > permissions > additional permissions and press 'Access Dexcom app'.
-- After short time BYODA should pick-up transmitter signal.
+- 此应用可让您在任意安卓智能手机上使用Dexcom G6。
+- 若您先前使用过原版Dexcom应用或修改版Dexcom应用，请将其卸载（**切勿终止**当前正在运行的传感器）。
+- 安装下载的 apk
+- 在修改版应用中输入传感器代码和发射器序列号。
+- 在手机设置中依次进入：应用 > Dexcom G6 > 权限 > 其他权限，然后点击"访问Dexcom应用"。
+- 短时间内BYODA应能接收到发射器信号。
-### Settings for AAPS
+### AAPS 设置
-- Select 'Dexcom App (patched)' in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择「Dexcom应用(修改版)」。
-- If you don't receive any values select any other data source, then re-select 'Dexcom App (patched)' to trigger the demand for permissions to establish the connection between AAPS and BYODA-broadcast.
+- 如未接收到任何数值，请先选择其他数据源，然后重新选择「Dexcom应用(修改版)」以触发权限请求，从而建立AAPS与BYODA广播之间的连接。
-### Settings for xDrip+
+### xDrip+ 设置
-- Select '640G/Eversense' as data source.
-- Command 'start sensor' must be performed in xDrip+ in order to receive values. This will not affect your current sensor controlled by Build Your Own Dexcom App.
+- 选择“640G/Eversense”作为数据源。
+- 必须在xDrip+中执行「启动传感器」指令才能接收数值。 此操作不会影响您当前由自建Dexcom应用控制的传感器。
(DexcomG6-troubleshooting-g6)=
-## Troubleshooting G6 and ONE
+## G6 和 ONE 故障排除
-### Dexcom G6/ONE specific troubleshooting
+### Dexcom G6/ONE 特定故障排除
-- Scroll down to **Troubleshooting** [here](https://navid200.github.io/xDrip/docs/Dexcom_page.html).
+- 向下滚动到[此处](https://navid200.github.io/xDrip/docs/Dexcom_page.html)的 **故障排除**。
-### General troubleshooting
+### 一般故障排除
-General Troubleshooting for CGMs can be found [here](#general-cgm-troubleshooting).
+CGM通用故障排除指南可[在此](#general-cgm-troubleshooting)查阅。
-### New transmitter with running sensor
+### 运行中的传感器搭配新发射器
-If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found [here](https://navid200.github.io/xDrip/docs/Remove-transmitter.html). If you opt for [this solution](https://youtu.be/tx-kTsrkNUM) instead, you must be careful to avoid [damaging sensor contacts](https://navid200.github.io/xDrip/docs/Petroleum-jelly-in-Dexcom-G6-Sensor.html) with the strip.
+如果在传感器运行期间更换发射器，可尝试在不损坏传感器底座的情况下移除发射器。 可以在[此处](https://navid200.github.io/xDrip/docs/Remove-transmitter.html)找到视频。 若选择采用[此替代方案](https://youtu.be/tx-kTsrkNUM)，则须谨慎操作，避免用撬片[损坏传感器触点](https://navid200.github.io/xDrip/docs/Petroleum-jelly-in-Dexcom-G6-Sensor.html)。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG7.md b/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG7.md
index 440e111a3968..88ba98ccb7fa 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG7.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/DexcomG7.md
@@ -2,70 +2,70 @@
orphan: true
- - -
-# Dexcom G7 and ONE+
+# Dexcom G7 和 ONE+
-## Fundamental in advance
+## 提前做好准备至关重要
-Noteworthy is the fact that the G7 and ONE+ systems, compared to the G6, do not smooth the values, neither in the app, nor in the reader. More details about this [here](https://www.dexcom.com/en-us/faqs/why-does-past-cgm-data-look-different-from-past-data-on-receiver-and-follow-app).
+值得注意的是，与G6相比，G7和ONE+系统无论在应用程序还是读取器中都不会对数值进行平滑处理。 更多详情请参见[此处](https://www.dexcom.com/en-us/faqs/why-does-past-cgm-data-look-different-from-past-data-on-receiver-and-follow-app)。
```{admonition} Smoothing method
-Read [Smoothing method](../CompatibleCgms/SmoothingBloodGlucoseData.md) suggestions to use for Dexcom G7/ONE+/Stelo
+请参阅[Dexcom G7/ONE+/Stelo适用的平滑方法建议](../CompatibleCgms/SmoothingBloodGlucoseData.md)
```
-## 1. xDrip+ (direct connection to G7 or ONE+)
+## 1. xDrip+（直接连接到 G7 或 ONE+）
-- Follow the instructions here: [xDrip+ G7](https://navid200.github.io/xDrip/docs/Dexcom/G7.html)
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 请按照此处的说明操作：[xDrip+ G7](https://navid200.github.io/xDrip/docs/Dexcom/G7.html)
+- 在 [ConfigBuilder, BG Source](#Config-Builder-bg-source) 中选择 xDrip+。
-- Adjust the xDrip+ settings according to the explanations on the xDrip+ settings page [xDrip+ settings](../CompatibleCgms/xDrip.md)
+- 请根据[xDrip+设置页面](../CompatibleCgms/xDrip.md)上的说明调整xDrip+设置
-## 2. Patched Dexcom G7 App (DiaKEM)
+## 2. 修补版 Dexcom G7 应用程序 (DiaKEM)
-**Note: AAPS 3.2.0.0 or higher is required! Not available for ONE+.**
+**注意：需要 AAPS 3.2.0.0 或更高版本！ 不适用于 ONE+。**
-### Install a new patched (!) G7 app and start the sensor
+### 安装新的修补版 (\!) G7 应用程序并启动传感器
-A patched Dexcom G7 app (DiaKEM) gives access to the Dexcom G7 data. This is not the BYODA app as this app can not receive G7 data at the moment.
+修补版 Dexcom G7 应用程序 (DiaKEM) 可访问 Dexcom G7 数据。 这不是 BYODA 应用程序，因为此应用程序目前无法接收 G7 数据。
-- Uninstall the original Dexcom app if you used it before (A running sensor session can be continued - note the sensor code before removal of the app!)
+- 若您先前使用过原版Dexcom应用，请将其卸载（正在进行的传感器会话可继续使用——注意：卸载应用前请记录传感器代码！）
-- Download and install the patched.apk [here](https://github.com/authorgambel/g7/releases).
+- 在[此处](https://github.com/authorgambel/g7/releases)下载并安装 patched.apk。
-- Enter sensor code in the patched app.
+- 在修补的应用程序中输入传感器代码。
-- Follow the general recommendations for CGM hygiene and sensor placement found [here](../CompatibleCgms/GeneralCGMRecommendation.md).
+- 请遵循[此处](../CompatibleCgms/GeneralCGMRecommendation.md)所列的CGM卫生与传感器放置通用建议。
-- After the warm-up phase, the values are displayed as usual in the G7 app.
+- 预热阶段结束后，数值将照常在G7应用程序中显示。
-### Configuration in AAPS
+### AAPS 中的配置
-- Select 'BYODA' in in [ConfigBuilder, BG Source](#Config-Builder-bg-source) - even if it is not the BYODA app!
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择「BYODA」——即使您使用的并非BYODA应用！
-- If AAPS does not receive any values, switch to another BG source and then back to 'BYODA' to invoke the query for approving data exchange between AAPS and BYODA.
+- 若AAPS未接收到任何数值，请先切换至其他血糖数据源，然后重新选择「BYODA」以触发AAPS与BYODA之间的数据交换授权请求。
-## 3. xDrip+ (companion mode)
+## 3. xDrip+（伴侣模式）
-- Download and install xDrip+: [xDrip](https://github.com/NightscoutFoundation/xDrip)
-- As data source in xDrip+ "Companion App" must be selected and under Advanced Settings > Bluetooth Settings > "Companion Bluetooth" must be enabled.
-- Select xDrip+ in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 下载并安装 xDrip+：[xDrip](https://github.com/NightscoutFoundation/xDrip)
+- 在xDrip+中必须选择"伴侣应用"作为数据源，并在高级设置 > 蓝牙设置中启用"伴侣蓝牙"功能。
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择xDrip+。
-- Adjust the xDrip+ settings according to the explanations on the xDrip+ settings page [xDrip+ settings](../CompatibleCgms/xDrip.md)
+- 请根据[xDrip+设置页面](../CompatibleCgms/xDrip.md)上的说明调整xDrip+设置
## 4. Juggluco
-Version 9.0+ required
+需要 9.0+ 版本
-- Disable the app previously connected to the sensor: Uninstall the app or use "Force Stop." Disable "Nearby Devices" permission in app settings. Restrict the app's battery usage.
+- 请禁用先前连接传感器的应用：卸载该应用或使用"强制停止"功能。 在应用设置中禁用"附近设备"权限。 限制应用程序的电池使用量。
-- Forget the sensor in Bluetooth settings: In Android settings, find the sensor in bonded devices and select "Forget." Dexcom G7 sensor names start with DXCM.
+- 在蓝牙设置中移除传感器：进入安卓设置，在已配对设备中找到该传感器并选择"忘记"。 Dexcom G7 传感器名称以 DXCM 开头。
-- Avoid interference from other sensors: Keep old Dexcom sensors out of Bluetooth range.
+- 避免其他传感器干扰：请将旧款Dexcom传感器移出蓝牙覆盖范围。
-- Connect the G7 sensor to Juggluco: Open Juggluco → Left menu → Photo. Scan the data matrix on the G7 sensor's applicator. Wait up to 5 minutes for Juggluco to find the sensor.
+- 将G7传感器连接至Juggluco：打开Juggluco → 左侧菜单 → 照片选项。 扫描G7传感器注射器上的二维码。 请等待最多5分钟，让Juggluco查找传感器。
-- Pairing requirements: Agree to pair the sensor with Juggluco. Ensure the screen isn’t locked during pairing. If pairing fails, wait 5 minutes before trying again.
+- 配对要求：需同意将传感器与Juggluco进行配对。 请确保配对过程中屏幕保持解锁状态。 若配对失败，请等待5分钟后再重试。
-- Exception: Wear OS watches can bond without pressing an agree button.
+- 例外情况：Wear OS智能手表无需点击同意按钮即可完成绑定。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/Eversense.md b/docs/CROWDIN/zh_CN/CompatibleCgms/Eversense.md
index c0f22ab6d029..40176db2fd06 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/Eversense.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/Eversense.md
@@ -2,69 +2,69 @@
orphan: true
- - -
-# For users of Eversense
+# Eversense 用户须知
-There are three different methods to access the readings from Eversense:
+获取Eversense读数有以下三种方法：
-- ESEL companion mode
-- ESEL patched mode
-- xDrip+ companion app
+- ESEL 伴侣模式
+- ESEL 修补模式
+- xDrip+ 伴侣应用程序
## ESEL
-Get and install the [ESEL app](https://github.com/BernhardRo/Esel/tree/master/apk), following these [instructions](https://github.com/BernhardRo/Esel?tab=readme-ov-file#esel).
+请按照[说明](https://github.com/BernhardRo/Esel?tab=readme-ov-file#esel)获取并安装[ESEL应用](https://github.com/BernhardRo/Esel/tree/master/apk)。
-- Enable "Send to AAPS and xDrip"
-- **Disable** "Send to Nightscout"
-- As the BG data from Eversense can be noisy, it is recommended to enable "Smooth Data" in ESEL.
+- 启用“发送到 AAPS 和 xDrip”
+- **禁用**“发送到 Nightscout”
+- 由于来自 Eversense 的血糖数据可能存在噪点，建议在 ESEL 中启用“平滑数据”。
-### Companion Mode
+### 伴侣模式
-Reads the data from the Eversense app notifications (works with the standard Eversense App, available since ESEL version 3.0.1).
+从 Eversense 应用程序通知中读取数据（适用于自 ESEL 3.0.1 版本起提供的标准 Eversense 应用程序）。
-1. Use the official Eversense App from the Google Play Store
- - Optional, but required for backfilling: Login to your Eversense account
- - In Sync, enable Auto synchronization
-2. Configuration of ESEL:
- - Disable the setting "Get data from patched Eversense App"
- - For backfilling: Enable "Fill missing data from eversensedms.com"
- - Provide as Email address and password your Eversense login data
-3. Set "MM640g" as BG source in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+1. 使用来自 Google Play 商店的官方 Eversense 应用程序
+ - 可选，但回填需要：登录您的 Eversense 帐户
+ - 在“同步”中，启用“自动同步”
+2. ESEL 的配置：
+ - 禁用设置“从修补的 Eversense 应用程序获取数据”
+ - 如需数据回填：请启用"从eversensedms.com填充缺失数据"功能
+ - 请输入您的Eversense登录邮箱地址和密码
+3. 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中将"MM640g"设为血糖数据源。
-### Patched Eversense App
+### 已破解的Eversense应用
- Requires a patched version of the Eversense App (works completely offline, including backfilling).
+ 需要使用已破解版的Eversense应用（可完全离线运行，包括数据回填功能）。
-1. Uninstall the Eversense App (Warning: your local historical data (older than 1 week) will be lost!)
+1. 卸载Eversense应用（警告：您本地的历史数据（超过1周）将会丢失！）
-2. Install the [patched Eversense app](https://cr4ck3d3v3r53n53.club) and use it as described by the vendor
+2. 安装[破解版Eversense应用](https://cr4ck3d3v3r53n53.club)并按照供应商说明使用
- - Start the Eversense App, login, connect to your transmitter and use it just like the normal app.
+ - 启动Eversense应用，登录后连接您的发射器，其使用方式与原版应用完全相同。
-3. Configuration of ESEL:
+3. ESEL 的配置：
- - Enable the setting "Get data from patched Eversense App"
+ - 启用"从破解版Eversense应用获取数据"设置
- If you run ESEL with a fresh installation of Eversense for the first time, it can take up to 15min until your first values appear in xDrip!
+若您首次在全新安装的Eversense环境下运行ESEL，可能需要等待长达15分钟才能在xDrip中看到首批数据！
-4. Set "MM640g" as BG source in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+4. 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中将"MM640g"设为血糖数据源。
## xDrip+
-xDrip+ can read notifications from the vendor app, like ESEL does. No backfilling available.
+xDrip+ 可以像 ESEL 一样读取厂商应用的通知。 没有回填功能。
-- Download and install xDrip+: [xDrip](https://github.com/NightscoutFoundation/xDrip)
-- As data source in xDrip+ “Companion App” must be selected.
-- Select xDrip+ in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
-- Adjust the xDrip+ settings according to the explanations on the xDrip+ settings page [xDrip+ settings](../CompatibleCgms/xDrip.md).
-- Enable [Exponential Smoothing](../CompatibleCgms/SmoothingBloodGlucoseData.md) in AAPS.
+- 下载并安装 xDrip+：[xDrip](https://github.com/NightscoutFoundation/xDrip)
+- 在xDrip+中必须选择"伴侣应用"作为数据源。
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择xDrip+。
+- 请按照[xDrip+设置页面](../CompatibleCgms/xDrip.md)的说明调整xDrip+参数。
+- 在AAPS中启用[指数平滑功能](../CompatibleCgms/SmoothingBloodGlucoseData.md)。
```{warning}
-BG values reading frequency is not always 5 minutes and duplicates can occur.
+血糖值读取频率并非始终为5分钟，且可能出现重复数据。
```
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/GeneralCGMRecommendation.md b/docs/CROWDIN/zh_CN/CompatibleCgms/GeneralCGMRecommendation.md
index 066cf3677440..74df54b110d9 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/GeneralCGMRecommendation.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/GeneralCGMRecommendation.md
@@ -2,44 +2,44 @@
orphan: true
- - -
-# General CGM recommendations
+# 常规CGM使用建议
-## CGM hygiene
+## CGM 卫生
-Whichever CGM system you are using, if you are going to use blood based calibration, then there are some very clear rules you should apply, whether or not you are using DIY CGM software or the official apps.
+无论您使用何种CGM系统，若需进行基于血糖仪的校准，则必须遵循以下明确规则——此要求适用于DIY CGM软件和官方应用程序的所有用户。
-- Make sure hands and kit are clean.
-- Try to calibrate when you have a series of dots with a flat arrow (15-30 minutes is usually enough)
-- Avoid calibrating when glucose levels are moving up or down.
-- Do “enough” calibrations – on official apps, you will be prompted for once or twice per day checks. On DIY systems you may not be, and should be careful about continuing without calibrations.
-- For sensors not requiring or not allowing calibration, check at least daily real blood sugar. AAPS will be as safe as your sensor readings are reliable.
-- If it all possible, calibrate with some of your readings in a lower range (4-5mmol/l or 72-90mg/dl) and some at a slightly higher level (7-9mmol/l or 126-160mg/dl) as this provides a better range for the point/slope calibration.
+- 确保手和设备清洁。
+- 建议在血糖趋势箭头呈水平状态时进行校准（通常15-30分钟即可）。
+- 避免在血糖水平上升或下降时进行校准。
+- 请进行"充分"校准——在官方应用程序中，系统会提示您每天检查一至两次。 对于DIY系统可能无校准提示，需谨慎对待长期未校准的情况。
+- 对于无需或无法校准的传感器，请至少每日检测一次真实血糖值。 AAPS系统的安全性与您传感器读数的可靠性直接相关。
+- 如有可能，建议分别在较低范围（4-5mmol/l或72-90mg/dl）和稍高范围（7-9mmol/l或126-160mg/dl）内选取读数进行校准，此举可为点斜式校准提供更优的数据范围。
-## Setting sensor (G6)
+## 设置传感器 (G6)
-When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor contacts should not come into contact with blood.
+安装传感器时，建议不要用力按压植入器，以免造成出血。 传感器触点不得接触血液。
-After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side.
+安装传感器后，可将发射器卡入传感器底板。 注意！ 请先将方形侧卡入，再按压圆形侧。
(general-cgm-troubleshooting)=
## 故障排除
-### Connection problems
+### 连接问题
-Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xDrip+ does not display any BG values. When Bluetooth connection is re-established the data is backfilled.
+蓝牙连接可能受到附近其他蓝牙设备的干扰，例如血糖仪、耳机、平板电脑，或微波炉、电磁炉等厨房电器。 若出现此情况，xDrip+将不会显示任何血糖值。 当蓝牙连接恢复时，系统将自动回填数据。
-### Sensor Errors
+### 传感器错误
-If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor contacts should not come into contact with blood.
+如频繁出现传感器错误，建议尝试选择其他身体部位安装传感器。 传感器触点不得接触血液。
-Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor!
+"传感器错误"通常可通过立即饮水和按摩传感器周围区域来纠正！
-### Jumpy values
+### 跳点
-You might try to change settings for noise blocking in xDrip+ (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../CompatibleCgms/SmoothingBloodGlucoseData.md).
+您可以尝试在xDrip+中调整噪声阻断设置（设置 - 应用间设置 - 噪声阻断），例如选择"阻断极高噪声及更差信号"。 另请参阅[血糖数据平滑处理](../CompatibleCgms/SmoothingBloodGlucoseData.md)。
-### Negative Sensor Age
+### 传感器负向使用时长
-This occurs if there is either a double "CGM Sensor Insert" entry in [actions tab / menu](#screens-action-tab) or a sensor insert with wrong date. Go to treatments tab \> careportal and delete the wrong entry.
+当[操作选项卡/菜单](#screens-action-tab)中出现重复的"CGM传感器植入"记录，或传感器植入日期错误时，即会出现此情况。 请前往治疗记录选项卡 > careportal删除错误条目。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre1.md b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre1.md
index 1154e3dddf8d..59783643f506 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre1.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre1.md
@@ -4,54 +4,54 @@ orphan: true
# Freestyle Libre 1
-To use your Libre as a CGM that is getting new BG values every 5 minutes without having to scan the sensor, you need to buy an NFC to Bluetooth bridge (commercially available devices, based on the obsolete [LimiTTer](https://github.com/JoernL/LimiTTer) project).
+若要将Libre用作CGM设备实现每5分钟自动获取血糖值（无需手动扫描传感器），需购买NFC转蓝牙桥接器（市售设备，基于已停用的[LimiTTer](https://github.com/JoernL/LimiTTer)项目）。
```{admonition} Libre 2, Libre 1 US and Libre Pro
:class: warning
-Verify the bridge and the app you want to use are compatible with your sensor.
+请确认您选用的桥接器及应用程序与传感器兼容。
```
-Several bridges are available on the market:
+市场上有几种桥接器可供选择：
-- [MiaoMiao Reader](https://www.miaomiao.cool/) (version 1, 2 or 3) also available on AliExpress.
-- [Blucon Nightrider](https://www.ambrosiasys.com/our-products/blucon/) (mind recent firmware versions might not be compatible with all apps, the vendor app does not broadcast data to AAPS)
-- [Bubble (or Bubble Mini)](https://www.bubblesmartreader.com/) from European vendors ([Bubblan](https://www.bubblan.org/), [BubbleShop](https://bubbleshop.eu/)) or for Russian users [here](https://vk.com/saharmonitor/). Also available on AliExpress.
-- Atom for Russian users.
+- [喵喵 Reader](https://www.miaomiao.cool/)（第1、2或3代）亦可通过全球速卖通购买。
+- [Blucon Nightrider](https://www.ambrosiasys.com/our-products/blucon/)（请注意：最新固件版本可能与部分应用程序不兼容，且厂商应用不会向AAPS广播数据）
+- [Bubble（或Bubble Mini）](https://www.bubblesmartreader.com/)可从欧洲供应商（[Bubblan](https://www.bubblan.org/)、[BubbleShop](https://bubbleshop.eu/)）购买，俄罗斯用户可[由此](https://vk.com/saharmonitor/)获取。 也可在 AliExpress 上找到。
+- 俄罗斯用户的 Atom。
-Historically it is possible to use a specific watch, the Sony Smartwatch 3 (SWR50) which has an NFC chip that can be enabled and used as an NFC collector. However the custom NFC to Bluetooth bridges listed above offer a less complex solution and would be used by the majority of those wanting to use their Libre 1 (non-US) as a CGM.
+从技术沿革来看，可使用特定手表——索尼SmartWatch 3（SWR50型号），其内置可激活的NFC芯片，能作为NFC采集器使用。 然而，上文所列的定制NFC转蓝牙桥接器方案更为简便，已成为大多数用户将Libre 1（非美版）用作CGM的首选方案。
- Sony Smartwatch 3 (SWR50)
-As it currently stands, if using Libre 1 as BG source you cannot activate ‘Enable SMB always’ and ‘Enable SMB after carbs’ within the SMB algorithm. The BG values of Libre 1 are not smooth enough to use it safely. See [Smoothing blood glucose data](../CompatibleCgms/SmoothingBloodGlucoseData.md) for more details.
+目前情况下，若使用Libre 1作为血糖数据源，则无法在SMB算法中启用"始终启用SMB"及"碳水化合物后启用SMB"功能。 Libre 1的血糖值波动性较大，无法安全使用。 详情请参阅[血糖数据平滑处理](../CompatibleCgms/SmoothingBloodGlucoseData.md)。
-## 1. Using xDrip+
+## 1. 使用 xDrip+
-- xDrip+ supports Miaomiao, Bubble, Blucon, Atom and LibreAlarm.
-- You can safely download the [latest APK (stable)](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) unless you need recent features, in which case you should use the latest [Nightly Snapshot](https://github.com/NightscoutFoundation/xDrip/releases).
-- Follow setup instructions on [xDrip+ settings page](../CompatibleCgms/xDrip.md).
-- You also need [OOP2](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view) for Libre 1 US (and Libre 2 EU).
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- xDrip+ 支持 Miaomiao、Bubble、Blucon、Atom 和 LibreAlarm。
+- 您可安全下载[最新稳定版APK](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk)；若需最新功能，则应使用[每日快照版](https://github.com/NightscoutFoundation/xDrip/releases)。
+- 请按照[xDrip+设置页面](../CompatibleCgms/xDrip.md)上的安装说明进行操作。
+- 您还需为Libre 1美版（及Libre 2欧版）配置[OOP2](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view)组件。
+- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source)中选择xDrip+。
(libre1-using-glimp)=
-## 2. Using Glimp
+## 2. 使用 Glimp
-- Glimp supports Miaomiao, Blucon and Bubble for Libre 1 and Libre 2 EU.
-- You will need Glimp version 4.15.57 or newer. Older versions are not supported.
-- Install [Glimp](https://play.google.com/store/apps/details?id=it.ct.glicemia).
-- Select Glimp in in [ConfigBuilder, BG Source.](#Config-Builder-bg-source)
+- Glimp 支持用于 Libre 1 和 Libre 2 EU 的 Miaomiao、Blucon 和 Bubble。
+- 您需要 Glimp 4.15.57 或更新版本。 不支持旧版本。
+- 安装 [Glimp](https://play.google.com/store/apps/details?id=it.ct.glicemia)。
+- 在 [ConfigBuilder, BG Source](#Config-Builder-bg-source) 中选择 Glimp。
(libre1-using-tomato)=
-## 3. Using Tomato
+## 3. 使用 Tomato
-- Tomato is the vendor app for Miaomiao.
-- Install [Tomato](http://tomato.cool/#download_page) and follow the vendor [instructions](http://tomato.cool/how-to-broadcast-data-to-android-aps/tips/).
-- Select Tomato in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- Tomato是喵喵设备的官方配套应用。
+- 请安装[Tomato](http://tomato.cool/#download_page)并遵循厂商提供的[操作指南](http://tomato.cool/how-to-broadcast-data-to-android-aps/tips/)。
+- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source) 中选择 Tomato。
-## 4. Using Diabox
+## 4. 使用 Diabox
-- Diabox is the vendor app for Bubble.
-- Install [Diabox](https://t.me/s/DiaboxApp). In Settings, Integration, enable Share data with other apps.
+- Diabox 是 Bubble 的官方配套应用。
+- 安装 [Diabox](https://t.me/s/DiaboxApp)。 在“设置”、“集成”中，启用“与其他应用程序共享数据”。
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source)中选择xDrip+。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2.md b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2.md
index 5c185d314588..5a4aaa560a9c 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2.md
@@ -2,233 +2,233 @@
orphan: true
- - -
-# Freestyle Libre 2 and 2+
+# Freestyle Libre 2 和 2+
-The Freestyle Libre 2 sensor is now a real CGM even with the official app. Still, LibreLink cannot send data to AAPS. There are several solutions to use it with AAPS.
+FreeStyle Libre 2传感器现已成为真正的CGM设备，即使使用官方应用亦可实现。 然而，LibreLink仍无法向AAPS传输数据。 现有多种方案可实现其与AAPS的协同使用。
-## 1. Use a Bluetooth bridge and OOP
+## 1. 使用蓝牙桥接器和 OOP
-Bluetooth transmitters can be used with the Libre 2 (EU) or 2+ (EU) and an [out of process algorithm](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view) app. You can receive blood sugar readings every 5 minutes like with the [Libre 1](./Libre1.md).
+蓝牙发射器可与Libre 2（欧版）或2+（欧版）配合使用，但需搭配[外部处理算法](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view)应用程序。 您可以像使用[Libre 1](./Libre1.md)一样，每5分钟接收一次血糖读数。
-Check the bridge and app you want to use are compatible with your sensor and xDrip+ (older Blucon and recent ones won't work, Miaomiao 1 needs firmware 39 and Miaomiao 2 firmware 7).
+请确认您选用的桥接器及应用程序与传感器和xDrip+兼容（旧版Blucon及近期版本不可用，喵喵1需固件39版，喵喵2需固件7版）。
-The Libre2 OOP is creating the same BG readings as with the original reader or the LibreLink app via NFC scan. AAPS with Libre 2 do a 10 to 25 minutes smoothing to avoid certain jumps. See below [Value smoothing & raw values](#libre2-value-smoothing-raw-values). OOP generates readings every 5 minutes with the average of the last 5 minutes. Therefore the BG readings are not that smooth but match the original reader device and faster follow the "real" BG readings. If you try to loop with OOP please enable all smoothing settings in xDrip+.
+Libre2 OOP算法生成的血糖读数与原始读取器或LibreLink应用通过NFC扫描获取的结果完全一致。 AAPS系统配合Libre 2使用时，会进行10至25分钟的数据平滑处理，以避免跳点。 请参阅下方[数值平滑处理与原始数据](#libre2-value-smoothing-raw-values)部分。 OOP算法每5分钟生成一次读数，该数值为过去5分钟的平均值。 因此，血糖读数虽不够平滑，但与原始读取设备数据吻合，且能更快追踪"真实"血糖值变化。 若使用OOP算法进行闭环控制，请务必在xDrip+中启用所有平滑处理设置。
-There are some good reasons to use a Bluetooth transmitter:
+使用蓝牙发射器存在若干重要优势：
-- You can choose various OOP2 calibration strategies (1): have the reader values using "no calibration", or calibrate the sensor like a Libre 1 using "calibrate based on raw" or ultimately calibrate the the readers like values with "calibrate based on glucose".
- Make sure to leave OOP1 disabled (2).
+- 您可选择多种OOP2校准策略（1）：采用"无校准"模式直接使用读取器数值，或像Libre 1那样通过"基于原始值校准"模式处理传感器数据，亦可最终采用"基于血糖值校准"模式对读取器数值进行校准。
+ 请确保禁用OOP1功能（2）。
- → Hamburger Menu → Settings → Less common settings → Other misc. options
+ → 汉堡菜单 → 设置 → 较少使用的设置 → 其他杂项 选项
-- The Libre 2 sensor can be used 14.5 days as the Libre 1
-- 8 hours backfilling is fully supported
+- Libre 2 传感器可以像 Libre 1 一样使用 14.5 天
+- 完全支持 8 小时回填
-Remark: The transmitter can be used in parallel to the LibreLink app without interfering with it.
+备注：该发射器可与LibreLink应用并行使用，且不会对其造成干扰。
-## 2. Use xDrip+ direct connection
+## 2. 使用 xDrip+ 直接连接
```{admonition} Libre 2 EU only
:class: warning
-xDrip+ doesn't support direct connection to Libre 2 US and AUS.
-Only Libre 2 and 2+ **EU** models.
+xDrip+ 不支持直接连接到 Libre 2 US 和 AUS。
+仅限 Libre 2 和 2+ **EU** 型号。
```
-- Follow [these instructions](https://www.minimallooper.com/post/how-to-setup-freestyle-libre-2-and-oop2-to-use-a-native-bluetooth-connection-in-xdrip) to setup xDrip+ but make sure to download [this latest OOP2](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view) as the one in the document is obsolete.
-- Follow setup instructions on [xDrip+ settings page](../CompatibleCgms/xDrip.md).
+- 请按照[此说明](https://www.minimallooper.com/post/how-to-setup-freestyle-libre-2-and-oop2-to-use-a-native-bluetooth-connection-in-xdrip)配置xDrip+，但务必下载[最新版OOP2](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view)，因文档中的版本已过时。
+- 请按照[xDrip+设置页面](../CompatibleCgms/xDrip.md)上的安装说明进行操作。
-- Select xDrip+ in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择xDrip+。
-## 3. Use Diabox
+## 3. 使用 Diabox
-- Install [Diabox](https://www.bubblesmartreader.com/_files/ugd/6afd37_f183eabd4fbd44fcac4b1926a79b094f.pdf). In Settings, Integration, enable Share data with other apps.
+- 安装[Diabox](https://www.bubblesmartreader.com/_files/ugd/6afd37_f183eabd4fbd44fcac4b1926a79b094f.pdf)。 在“设置”、“集成”中，启用“与其他应用程序共享数据”。
-- Select xDrip+ in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择xDrip+。
-## 4. Use Juggluco
+## 4. 使用 Juggluco
-- Download and install the Juggluco app from [here](https://www.juggluco.nl/Juggluco/download.html).
-- Follow the instructions [here](https://www.juggluco.nl/Juggluco/index.html)
-- In Settings, enable xDrip+ broadcast (which doesn't send data to xDrip+ but to AAPS).
+- 从[此处](https://www.juggluco.nl/Juggluco/download.html)下载并安装 Juggluco 应用程序。
+- 按照[此处](https://www.juggluco.nl/Juggluco/index.html)的说明进行操作
+- 在“设置”中，启用 xDrip+ 广播（不会将数据发送到 xDrip+，而是发送到 AAPS）。
-- Select xDrip+ in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder的BG数据源](#Config-Builder-bg-source)中选择xDrip+。
```{admonition} Use with xDrip+
:class: note
-You can set Juggluco to broadcast to xDrip+ with Patched Libre Broadcast (you should disable xDrip+ broadcast), in order to calibrate (see here) and avoid 1 minute readings to be sent to AAPS.
-
-You will then need to set xDrip+ data source to Libre 2 Patched App to receive data from Juggluco.
+您可将Juggluco设置为通过"Patched Libre Broadcast"向xDrip+传输数据（此时应禁用xDrip+的广播功能），以便进行校准（参见此处说明）并避免将1分钟间隔的读数发送至AAPS。
+
+随后需将xDrip+数据源设为"Libre 2 Patched App"以接收来自Juggluco的数据。
```
(libre2-patched-librelink-app-with-xdrip)=
-## 5. Use the patched LibreLink app with xDrip+
+## 5. 请使用经过修改的LibreLink应用配合xDrip+。
```{admonition} Libre 2 EU only
:class: warning
-The patched app is an old version (22/4/2019) and might not be compatible with recent Android releases.
+该修改版应用为旧版本（2019年4月22日），可能与新版Android系统不兼容。
```
-### Step 1: Build the patched app
+### 步骤 1：构建修补的应用程序
-For legal reasons, "patching" has to be done by yourself. Use search engines to find the corresponding links. There are two variants: The recommended original patched app blocks any internet traffic to avoid tracking. The other variant supports LibreView.
+出于法律原因，"修改补丁"需由您自行完成。 请通过搜索引擎查找相应链接。 存在两种版本：推荐使用的原始修改版应用会拦截所有网络流量以避免追踪。 另一种变体支持 LibreView。
-The patched app has to be installed instead of the original app. The next sensor started with it will transmit the current BG values to the xDrip+ app running on your smartphone via Bluetooth.
+必须安装修改版应用以替代原版应用。 随后启动的传感器将通过蓝牙，将当前血糖值传输至您智能手机上运行的xDrip+应用。
-Important: To avoid possible problems it may help to first install and uninstall the original app on an NFC capable smartphone. NFC has to be enabled. This costs no extra power. Then install the patched app.
+重要提示：为避免潜在问题，建议先在支持NFC的智能手机上安装并卸载原版应用。 必须启用 NFC。 这不会消耗额外的电量。 然后安装修补的应用程序。
-The patched app can be identified by the foreground authorization notification. The foreground authorization service improves the connection stability compared to the original app which does not use this service.
+修改版应用可通过前台授权通知进行识别。 该前台授权服务相较于未采用此服务的原版应用，显著提升了连接稳定性。
-Other indications could be the Linux penguin logo in the three dot menu -> Info or the font of the patched app (2) different from the original app (1). These criteria are optional depending on the app source you choose.
+其他识别特征可能包括：三点菜单中的Linux企鹅标志（路径：-> 信息），或修改版应用(2)与原版应用(1)不同的字体样式。 这些识别标准为可选项目，具体取决于您选择的应用程序来源。
-Ensure that NFC is activated, enable the memory and location permission for the patched app, enable automatic time and time zone and set at least one alarm in the patched app.
+请确保开启NFC功能，为修改版应用启用存储和定位权限，启用自动时区和时间设置，并在该应用中至少设置一个闹钟。
-### Step 2: Start the sensor with the patched app
+### 步骤 2：使用修补的应用程序启动传感器
-Now start the Libre2 sensor with the patched app by simply scanning the sensor. Ensure to have set all settings done.
+现在只需扫描传感器，即可通过修改版应用启动Libre2传感器。 请确保已完成所有设置。
-Mandatory settings for successful sensor start:
+成功启动传感器的必备设置：
-- NFC enabled / BT enabled
-- memory and location permission enabled
-- location service enabled
-- automatic time and time zone setting
-- set at least one alarm in the patched app
+- NFC 已启用 / 蓝牙已启用
+- 内存和位置权限已启用
+- 位置服务已启用
+- 自动时间和时区设置
+- 在修补的应用程序中设置至少一个闹钟
-Please note that the location service is a central setting. This is not the app location permission which has to be set also!
+请注意：定位服务是一项核心设置。 这并非应用程序的定位权限设置——该权限也需另行配置！
-Once the sensor started with the patched app, you won't be able to connect it to another app/phone. If you uninstall the patched app, you will lose alarms and continuous BG readings.
+一旦使用修改版应用启动传感器，将无法再将其连接至其他应用/手机。 若卸载修改版应用，将导致警报功能及持续血糖读数中断。
-The first connection setup to the sensor is critical. The LibreLink app tries to establish a wireless connection to the sensor every 30 seconds. If one or more mandatory settings are missing they have to be adjusted. You have no time limit to do that. The sensor is constantly trying to setup the connection. Even if is last some hours. Be patient and try different settings before even thinking of changing the sensor.
+首次连接传感器的设置至关重要。 LibreLink应用会每隔30秒尝试与传感器建立无线连接。 如果缺少一个或多个强制性设置，则必须对其进行调整。 您可随时进行此操作，无时间限制。 传感器会持续尝试建立连接。 即使此过程持续数小时。 请保持耐心，在考虑更换传感器之前，先尝试不同的设置。
-As long as you see a red exclamation mark ("!") on the upper left corner of the LibreLink start screen there is no connection or some other setting blocks LibreLink to signal alarms. Please check if the sound is enabled and all sorts of blocking app notifications are disabled. When the exclamation mark is gone, the connection should be established and blood sugar values are sent to the smartphone. This should happen after a maximum of 5 minutes.
+当LibreLink启动画面左上角出现红色感叹号（"!"）时， 表明连接未建立或其他设置阻碍了LibreLink的警报功能。 请检查是否已启用声音提示，并确保禁用所有可能拦截应用通知的功能。 当感叹号消失时，即表示连接已建立，血糖数据将传输至智能手机。 此过程最多应在5分钟内完成。
-If the exclamation mark remains or you get an error message, this can have several reasons:
+若感叹号持续存在或出现错误提示，可能由以下原因导致：
-- Android location service is not granted - please enable it in system settings
-- automatic time and time zone not set - please change settings accordingly
-- activate alarms - at least one of the three alarms must be activated in LibreLink
-- Bluetooth is switched off - please switch on
-- sound is blocked
-- app notifications are blocked
-- idle screen notifications are blocked
+- 未授予 Android 位置服务 - 请在系统设置中启用它
+- 未设置自动时间和时区 - 请相应地更改设置
+- 激活闹钟 - 必须在 LibreLink 中激活三个闹钟中的至少一个
+- 蓝牙已关闭 - 请打开
+- 声音被阻止
+- 应用程序通知被阻止
+- 空闲屏幕通知被阻止
-Restarting the phone can help, you may have to do it several times. As soon as the connection is established, the red exclamation mark disappears and the most important step is taken. It may happen that depending on system settings the exclamation mark remains but you still get readings. In both cases you are fine. Sensor and phone are now connected, every minute a blood sugar value is transmitted.
+重新启动手机可能会有所帮助，您可能需要执行多次。 一旦连接建立，红色感叹号即会消失，此时已完成最关键步骤。 根据系统设置的不同，可能出现感叹号持续显示但仍能获取读数的情况。 这两种情况下均属正常现象。 传感器与手机现已连接，每分钟传输一次血糖数值。
-In rare case it could help to empty the bluetooth cache and/or reset all network connections via the system menu. This removes all connected bluetooth devices which may help to setup a proper bluetooth connection. That procedure is safe as the started sensor is remembered by the patched LibreLink app. Nothing additional has to be done here. Simply wait for the patched app to connect to the sensor.
+在极少数情况下，清空蓝牙缓存和/或通过系统菜单重置所有网络连接可能有效。 此操作将移除所有已连接的蓝牙设备，可能有助于建立正常的蓝牙连接。 该操作安全可靠，因为已启动的传感器会被修改版LibreLink应用记录。 此处无需执行任何其他操作。 请静待修改版应用与传感器建立连接。
-After a successful connection the smartphone settings can be changed if necessary. This is not recommended but you may want to save power. Location service can be switched off, volume can be set to zero or alarms can be switched off again. The blood sugar levels are transferred anyway.
+连接成功后，可根据需要调整智能手机设置。 虽然此操作不被推荐，但您可能出于省电考虑需要执行。 可关闭定位服务、将音量调至静音或再次禁用警报功能。 血糖数据仍会持续传输。
-When starting the next sensor, however, all settings must be set again!
+但请注意：启用新传感器时，所有设置需重新配置！
-Remark: The patched app needs the mandatory settings set in that hour after warmup to enable a connection. For the 14 days operation time they are not needed. In most cases when you have problems with starting a sensor the location service was switched off. For Android it is needed for proper bluetooth operation(!) to connect. Please refer to Google's Android documentation.
+备注：修改版应用在预热完成后的首小时内，必须完成各项关键设置才能建立连接。 在14天运行周期内无需重复此类设置。 多数情况下，若传感器启动出现问题，往往是定位服务未开启所致。 安卓系统必须开启定位服务才能确保蓝牙正常连接(!)。 请参阅 Google 的 Android 文档。
-During the 14 days you can use in parallel one or more NFC capable smartphones (not the reader device!) running the original LibreLink app for scanning via NFC. There is no time limitation to start that. You could use a parallel phone for example on day 5 or so. The parallel phones(s) could upload the blood sugar values into the Abbott Cloud (LibreView). LibreView can generate reports for your diabetes team.
+在14天使用周期内，您可同时使用一部或多部支持NFC的智能手机（非扫描仪设备！）运行原版LibreLink应用进行NFC扫描。 启动此操作无时间限制。 例如，您可以在第5天左右使用另一部手机进行并行操作。 并行连接的手机可将血糖数据上传至雅培云端（LibreView）。 LibreView可为您的糖尿病管理团队生成报告。
-Please note that the original patched app **does not have any connection to the internet** to avoid tracking.
+请注意：原始修改版应用**完全不联网**，以避免追踪。
-However there is a variant of the patched app supporting LibreView with enabled internet access. Please be aware that your data is transferred to the cloud then. But your endo team reporting is fully supported then. With that variant it is also possible to move the alarms of a running sensor to a different device which not has started the sensor. Please google in diabetes related German forums how this could be done.
+但存在修改版应用的一个变体版本，该版本支持LibreView并启用互联网访问功能。 请注意：启用此功能后，您的数据将传输至云端。 但此时内分泌团队的报告功能将获得完整支持。 使用该变体版本时，还可将运行中传感器的警报功能转移至其他未启动该传感器的设备。 请通过德国糖尿病相关论坛搜索具体操作方法。
-### Step 3: Install and configure xDrip+ app
+### 步骤 3：安装和配置 xDrip+ 应用程序
-The blood sugar values are received on the smartphone by the xDrip+ App.
+血糖值由xDrip+应用程序在智能手机上接收。
-- You can safely download the [latest APK (stable)](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) unless you need recent features, in which case you should use the latest [Nightly Snapshot](https://github.com/NightscoutFoundation/xDrip/releases).
-- Set xDrip+ with the [patched app data source](#xdrip-libre2-patched-app).
-- Follow setup instructions on [xDrip+ settings page](../CompatibleCgms/xDrip.md).
+- 您可安全下载[最新稳定版APK](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk)；若需最新功能，则应使用[每日快照版](https://github.com/NightscoutFoundation/xDrip/releases)。
+- 将xDrip+数据源设置为[修改版应用程序](#xdrip-libre2-patched-app)。
+- 请按照[xDrip+设置页面](../CompatibleCgms/xDrip.md)上的安装说明进行操作。
-### Step 4: Start sensor
+### 步骤 4：启动传感器
-- → Hamburger Menu (1) → Start sensor (2) → Start sensor (3) → Answer "Not Today" (4).
+- → 汉堡菜单 (1) → 启动传感器 (2) → 启动传感器 (3) → 回答“不是今天”(4)。
-This will not physically start any Libre2 sensor or interact with them in any case. This is simply to indicate xDrip+ that a new sensor is delivering blood sugar levels. If available, enter two bloody measured values for the initial calibration. Now the blood glucose values should be displayed in xDrip+ every 5 minutes. Skipped values, e.g. because you were too far away from your phone, will not be backfilled.
+此操作不会实际启动任何Libre2传感器，也不会与其产生任何交互。 此设置仅用于向xDrip+表明有新传感器正在传输血糖数据。 若有条件，请输入两次指尖血测量值进行初始校准。 此时血糖值应每5分钟在xDrip+上显示一次。 若因距离手机过远导致数据遗漏，系统将不会补传这些缺失值。
-After a sensor change xDrip+ will automatically detect the new sensor and will delete all calibration data. You may check you blood glucose after activation and make a new initial calibration.
+更换传感器后，xDrip+将自动识别新传感器并删除所有校准数据。 激活后，您可检测血糖并进行新的初始校准。
-### Step 5: Configure AAPS (for looping only)
+### 步骤 5：配置 AAPS（仅用于闭环）
-- In AAPS go to Config Builder > BG Source and check 'xDrip+'
+- 在AAPS中进入配置生成器 > 血糖数据源，勾选'xDrip+'选项。
-- If AAPS does not receive BG values when phone is in airplane mode, use 'Identify receiver' as describe on [xDrip+ settings page](#xdrip-identify-receiver).
+- 若手机处于飞行模式时AAPS未接收到血糖数值，请按照[xDrip+设置页面](#xdrip-identify-receiver)所述使用"识别接收器"功能。
(Libre2-experiences-and-troubleshooting)=
-### Experiences and Troubleshooting
+### 经验和故障排除
-#### Connectivity
+#### 连接性
-The connectivity is good with most phones, with the exception of Huawei mobile phones. The connection can break off if the mobile phone is in the pocket opposite the sensor or if you are outdoors. Wear your phone on the sensor side of your body. In rooms, where Bluetooth spreads over reflections, no problems should occur. If you have connectivity problems please test another phone. It may also help to set the sensor with the internal BT antenna pointing down. The slit on the applicator must be pointing down when setting the sensor.
+大多数手机连接性能良好，但华为手机除外。 若手机与传感器分置口袋两侧或在户外环境，连接可能中断。 请将手机佩戴在身体靠近传感器的一侧。 在室内环境中，蓝牙信号可通过反射传播，应无连接问题。 如遇连接问题，请尝试使用其他手机进行测试。 将传感器内置蓝牙天线朝下放置也可能改善连接。 安装传感器时，施敷器的凹槽必须朝下。
(libre2-value-smoothing-raw-values)=
-#### Value smoothing & raw values
+#### 数值平滑和原始值
-Technically, the current blood sugar value is transmitted to xDrip+ every minute. A weighted average filter calculates a smoothed value over the last 25 minutes by default. You can change the period in the NFC Scan features menu.
+从技术上讲，当前血糖值每分钟都会传输至xDrip+。 默认情况下，加权平均滤波器会基于过去25分钟的数据计算平滑值。 您可通过NFC扫描功能菜单调整该时段参数。
-→ Hamburger menu → Settings → NFC Scan features → Smooth libre 3 data when using xxx method
+→ 汉堡菜单 → 设置 → NFC 扫描功能 → 使用 xxx 方法时平滑 libre 3 数据
-This is mandatory for looping. The curves look smooth and the loop results are great. The raw values on which the alarms are based jitter a little more, but correspond to the values that the reader also displays. In addition, the raw values can be displayed in the xDrip+ graph in order to be able to react in time to rapid changes. Please switch on Less Common Settings \> Advanced Settings for Libre2 \> "show Raw values" and "show Sensors Infos". Then the raw values are additionally displayed as small white dots and additional sensor info is available in the system menu.
+这对于闭环是强制性的。 曲线看起来平滑，闭环结果非常好。 触发警报的原始数值波动稍大，但与读取器显示数值完全一致。 此外，原始数值可显示于xDrip+图表中，以便及时应对快速变化。 请启用"较少使用设置 > Libre2高级设置"中的"显示原始数值"与"显示传感器信息"选项。 此时原始数值将额外显示为白色小点，且系统菜单中可查看更多传感器信息。
-The raw values are very helpful when the blood sugar is moving fast. Even if the dots are jumpier you would detect the tendency much better as using the smoothed line to make proper therapy decisions.
+当血糖快速波动时，原始数值极具参考价值。 即便数据点波动较大，但相较于平滑曲线，原始数据点能更准确地反映变化趋势，从而帮助制定更精准的治疗方案。
-→ Hamburger menu → Settings → Less common settings → Advanced settings for Libre 2
+→ 汉堡菜单 → 设置 → 较不常见的设置 → Libre 2 的高级设置
-#### Sensor runtime
+#### 传感器运行时间
-The sensor runtime is fixed to 14 days. The 12 extra hours of Libre1 no longer exist. xDrip+ shows additional sensor information after enabling Advanced Settings for Libre2 → "show Sensors Infos" in the system menu like the starting time. The remaining sensor time can also be seen in the patched LibreLink app. Either in the main screen as remaining days display or as the sensor start time in the three-point menu → Help → Event log under "New sensor found".
+传感器运行时间固定为 14 天。 Libre1原有的12小时额外使用时间现已取消。 启用Libre2高级设置→系统菜单中的"显示传感器信息"后，xDrip+将额外显示传感器启动时间等数据。 剩余传感器时长也可在修改版LibreLink应用中查看。 该信息既可能以剩余天数形式显示在主界面，也可能通过三点菜单→帮助→事件日志中的"发现新传感器"项查看传感器启动时间。
-#### New sensor
+#### 新传感器
-A sensor exchange takes place on-the-fly: Set new sensor shortly before activation. As soon as xDrip+ receives no more data from the old sensor, start the new sensor with the patched app. After one hour new values should appear automatically in xDrip+.
+传感器更换可即时完成：只需在激活前短暂放置新传感器即可。 当xDrip+停止接收旧传感器数据时，请立即使用修改版应用启动新传感器。 一小时后，新数据将自动显示在xDrip+中。
-If not, please check the phone settings and proceed as with the first start. You have no time limit. Try to find the correct settings. No need to immediately replace the sensor before you tried different combinations. The sensors are robust and try permanently to establish a connection. Please take your time. In most cases you accidentally changed one setting which causes now problems.
+若未显示，请检查手机设置并按照首次启动流程操作。 您没有时间限制。 尝试找到正确的设置。 在尝试不同组合前，无需立即更换传感器。 传感器性能稳定，会持续尝试建立连接。 请耐心等待。 多数情况下，您可能误改了某项设置才导致当前问题。
-Once successful please select "Sensor Stop" and "Delete calibration only" in xDrip. This indicates for xDrip+ that a new sensor is releasing blood sugar levels and the old calibrations are no longer valid and therefore have to be deleted. No real interaction is done with the Libre2 sensor here! You do not need to start the sensor in xDrip+.
+操作成功后，请在xDrip中选择"传感器停止"和"仅删除校准"。 这向xDrip+表明：新传感器已开始监测血糖水平，旧校准数据不再有效，因此必须删除。 此处并未与Libre2传感器进行实际交互！ 您无需在xDrip+中启动传感器。
#### 校准
-You can calibrate the Libre2 **with an offset of -40 mg/dl to +20 mg/dL \[-2,2 mmol/l to +1,1 mmol/l\]** (intercept). The slope isn't changeable. Please check by fingerpricking after setting a new sensor, keeping in mind it might not be accurate in the first 12 hours after insertion. Since there can be large differences to the blood measurements, verify every 24 hours and calibrate if necessary. If the sensor is completely off after a few days, it should then be replaced.
+您可将Libre2校准至偏移范围-40 mg/dl至+20 mg/dL（即-2.2 mmol/l至+1.1 mmol/l）的截距值。 斜率参数不可调整。 设置新传感器后，请通过指尖采血验证读数，需注意植入后最初12小时数据可能不准确。 由于可能存在与血液测量值的显著差异，请每24小时进行验证，必要时重新校准。 若传感器在数日后仍存在显著偏差，则应予以更换。
-### Plausibility checks
+### 合理性校验
-The Libre2 sensors contain plausibility checks to detect bad sensor values. As soon as the sensor moves on the arm or is lifted slightly, the values may start to fluctuate. The Libre2 sensor will then shut down for safety reasons. Unfortunately, when scanning with the App, additional checks are made. The app can deactivate the sensor even though the sensor is OK. Currently the internal test is too strict. Avoid scanning the sensor with another phone to reduce the risk of unexpected sensor shutdown.
+Libre2传感器内置合理性校验机制，可识别异常数据。 一旦传感器在手臂上移位或轻微翘起，监测数值即可能出现波动。 出于安全考虑，Libre2传感器将自动关闭。 遗憾的是，使用App扫描时还会进行额外检测。 即使传感器工作正常，该应用程序仍可能将其停用。 当前内部检测标准过于严格。 请勿使用其他手机扫描传感器，以降低传感器意外关闭的风险。
(Libre2-best-practices-for-calibrating-a-libre-2-sensor)=
-# Best practices for calibrating a Libre 2 sensor
+# Libre 2传感器校准最佳实践
-To get the best results when calibrating a libre 2 sensor there are some “rules” you should follow. They apply independently of the software combination (e.g. patched libre-app, oop2, …) that is used to handle the libre 2 values.
+为获得Libre 2传感器校准的最佳效果，请遵循以下操作准则： 这些准则适用于任何处理Libre 2数据的软件组合（如修改版Libre应用、OOP2等），不受具体技术方案影响。
-1. The most important rule is to only calibrate the sensor when you have a flat bg level for at least 15 minutes. The delta between the last three readings should not exceed 10 mg/dl (over 15min not between each reading). As the libre 2 does not measure your blood glucose level but your flesh glucose level there is some time lag especially when bg level is rising or falling. This time lag can lead to way too large calibration offsets in unfavourable situations even if the bg level rise / fall is not that much. So whenever possible avoid to calibrate on rising or falling edges. -> If you have to add a calibration when you do not have a flat bg level (e.g. when starting a new sensor) it is recommended to remove that calibration(s) as soon as possible and add a new one when in flat bg levels.
-2. Actually this one is automatically taken into account when following rule 1 but to be sure: When doing comparison measurements your bg level should also be flat for about 15min. Do not compare when rising or falling. Important: You still shall do blood glucose measurements whenever you desire, just don’t use the results for calibration when rising or falling!
-3. As calibrating the sensor in flat levels is a very good starting point it is also strongly recommended to calibrate the sensor only within your desired target range like 70 mg/dl to 160 mg/dl. The libre 2 is not optimized to work over a huge range like 50 mg/dl to 350 mg/dl (at least not in a linear manner), so try to only calibrate when within your desired range. -> Simply accept that values outside your calibration range will not perfectly match blood glucose levels.
-4. Do not calibrate too often. Calibrating the sensor very often mostly leads to worse results. When the sensor delivers good results in flat conditions just don’t add any new calibration as it does not have any -useful- effect. It should be sufficient to recheck the status every 3-5 days (of course also in flat conditions).
-5. Avoid calibration when not required. This might sound silly but it is not recommended to add a new calibration if the blood glucose to flesh glucose level difference is only ±10 mg/dl (e.g. blood glucose level: 95, Libre sensor 100 -> do NOT add the 95, blood glucose level: 95, Libre sensor 115 -> add the 95 to be taken into account for the calibration)
+1. 最重要的准则是：仅当血糖水平稳定至少15分钟后，方可校准传感器。 最近三次读数的波动差值不应超过10 mg/dl（基于15分钟内的整体波动，非单次读数间差值）。 由于Libre 2并非直接测量血糖水平，而是测量组织液葡萄糖值，因此在血糖水平上升或下降时会出现一定的时间延迟。 这种时间延迟可能导致校准偏移量过大，即便血糖水平升降幅度不大，在不利情况下仍会出现此现象。 因此请尽可能避免在血糖上升或下降阶段进行校准。 → 若必须在血糖未稳定时进行校准（如启用新传感器），建议尽快移除该次校准数据，待血糖稳定后重新校准。
+2. 实际上，遵循第一条准则时已自动包含此项要求，但为确保准确：进行比对测量时，您的血糖水平也应保持约15分钟的稳定状态。 请勿在血糖上升或下降期间进行数据比对。 重要提示：您仍可随时进行血糖检测，但请勿在血糖波动期间将检测结果用于校准！
+3. 在血糖水平稳定时校准传感器是最佳起点，同时强烈建议仅在您期望的目标范围内（如70 mg/dl至160 mg/dl）进行校准。 Libre 2并未针对大范围（如50 mg/dl至350 mg/dl）进行优化（至少无法保持线性关系），因此请尽量仅在您所需范围内进行校准。 → 请直接接受：校准范围外的监测值无法与血糖水平完全吻合。
+4. 请勿频繁校准。 频繁校准传感器通常会导致监测结果恶化。 当传感器在血糖稳定状态下表现良好时，请勿新增校准，此举不会产生任何实际效益。 建议每3-5天（当然也需在血糖稳定状态下）复查校准状态即可。
+5. 非必要请勿校准。 虽然听起来有些多余，但当血糖与组织液葡萄糖值差异仅为±10 mg/dl时（例如：血糖值95，Libre传感器显示100 → 无需输入95；血糖值95，Libre传感器显示115 → 需输入95参与校准），不建议新增校准。
-Some general notes: After activating a new sensor and at the sensor’s end of life it does make sense to do comparison measurements more often than 3-5 days as stated in rule nr. 4. For new and old sensors it is more likely that the raw values change and a re-calibration is required. From time to time it happens that a sensor does not provide valid values. Most likely the sensor value is way to low compared to the actual blood glucose level (e.g. sensor: 50 mg/dl, bg: 130 mg/dl) even after calibrating. If this is the case the sensor cannot be calibrated to report useful results. E.g. when using the patched libre app one can add an offset of maximal +20 mg/dl. When it happens to you that the sensor does provides way too low values, don’t hesitate to replace it as it will not get better. Even if it might be a defective sensor, when seeing sensors that do provide way too low values very often, try to use different areas to place your sensor. Even in the official area (upper arm) there might be some locations where the sensors just do not provide valid values. This is some kind of trial end error to find areas that work for you.
+通用说明：根据第4条准则，在启用新传感器及传感器临近使用寿命时，需将比对测量频率提高至3-5天以内。 对于新旧传感器而言，原始数值更易发生变化，往往需要重新校准。 偶尔会出现传感器无法提供有效数值的情况。 很可能传感器数值与实际血糖水平相比过低（例如传感器：50 mg/dl，实际血糖：130 mg/dl），即便在校准后也是如此。 如果是这种情况，传感器将无法通过校准来提供有用的读数。 例如 ，在使用破解版Libre应用时，用户最多可以添加+20 mg/dl的偏移值。 若您遇到传感器持续显示数值严重偏低的情况，请立即更换，因为该问题无法自行改善。 即使可能是传感器故障，若频繁遇到数值严重偏低的情况，请尝试更换传感器佩戴部位。 即使在官方建议的佩戴区域（上臂），某些位置也可能无法提供有效读数。 这需要通过反复试验来找到适合您的佩戴位置。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md
index c6b13be5a3a4..95498f612b50 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md
@@ -2,109 +2,109 @@
orphan: true
- - -
-# **Freestyle Libre 3** and 3+
+# **Freestyle Libre 3** 和 3+
-Freestyle Libre 3 (FSL3) requires a unique setup to receive BG values in to AAPS. There are two possible ways of getting Freestyle Libre 3 (FSL3) values to AAPS.
+Freestyle Libre 3 (FSL3) 需要特殊设置才能将血糖值传输至AAPS系统。 获取Freestyle Libre 3 (FSL3)数值至AAPS系统存在两种可行方案。
-**Version 3.2.0.1 of AndroidAPS does not support 1-minute values. Acceleration and Smoothing does not work with 1-minute values.**
+**AndroidAPS 3.2.0.1版本不支持每分钟血糖数值的传输。 加速度和平滑处理不适用于每分钟数值。**
-The below methods for achieving this are using the separate app Juggluco. It uses Juggluco to receive raw, 1-minute interval data from the sensor which is then passed to xDrip+ or AAPS. New sensors can be started either with the Libre 3 App or directly in Juggluco. The guide below indicates the process for starting a sensor with the Juggluco app. If the sensor has been started with a Libreview account logged in, it is also possible to switch between Juggluco and the Libre 3 app as receiver.
+以下实现方法需配合使用独立应用程序Juggluco。 该方法通过Juggluco接收传感器原始每分钟间隔数据，随后传输至xDrip+或AAPS系统。 新传感器既可通过Libre 3应用程序启动，也可直接在Juggluco中激活。 以下指南说明了使用Juggluco应用程序启动传感器的流程。 若传感器启动时已登录Libreview账户，接收端可在Juggluco和Libre 3应用之间切换使用。
-Juggluco can also pass data to LibreView for sharing with health care providers when the sensor is started with the Libre 3 app.
+当传感器通过Libre 3应用启动时，Juggluco也可将数据传输至LibreView平台，以便与医疗保健提供者共享。
-Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/dl (-2.2 mmol/l to +1.1 mmol/l) to compensate for differences between a manual meter reading and the sensor readings.
+在xDrip+中，传感器可校准范围为-40 mg/dl至+20 mg/dl（-2.2 mmol/l至+1.1 mmol/l），用于补偿手动血糖仪读数与传感器读数之间的差异。
-## Method 1: 1-minute-readings
-Version 3.2.0.1 of AndroidAPS does not support 1-minute values. Acceleration and Smoothing does not work with 1-minute values.
+## 方法 1：1 分钟读数
+AndroidAPS 3.2.0.1版本不支持每分钟血糖数值的传输。 加速度和平滑处理不适用于每分钟数值。
-## Method 2: 5-minute-readings
-This method uses Juggluco to receive raw, 1-minute interval data from the sensor which is then passed to xDrip+ to be smoothed into 5-minute interval data to be passed to AAPS.
+## 方法 2：5 分钟读数
+该方法通过Juggluco接收传感器原始每分钟数据，经xDrip+平滑处理后转换为5分钟间隔数据，最终传输至AAPS系统。
-### Step 1: Setup Juggluco
-Download and install the Juggluco app from [here](https://www.juggluco.nl/Juggluco/download.html). Follow the instructions [here](https://www.juggluco.nl/Juggluco/libre3/)
+### 步骤 1：设置 Juggluco
+从[此处](https://www.juggluco.nl/Juggluco/download.html)下载并安装 Juggluco 应用程序。 按照[此处](https://www.juggluco.nl/Juggluco/libre3/)的说明进行操作
-Make sure you send the glucose values to xDrip+: In Juggluco's settings you can configure Juggluco to send its glucose value to other apps. Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+
+请确保将血糖值发送至xDrip+：在Juggluco的设置中，您可将其配置为向其他应用程序发送血糖值。 Juggluco可发送三种广播类型：**修改版Libre广播**最初由修改版Librelink应用使用，可用于向xDrip+发送血糖值。
-### Step 2: Setup xDrip
+### 步骤 2：设置 xDrip
-The blood glucose values are received by the xDrip+ app on the smartphone.
+智能手机上的xDrip+应用程序会接收到这些血糖数值。
-- If not already set up then download [xDrip+](https://github.com/NightscoutFoundation/xDrip) and follow the instructions on [xDrip+ settings page](../CompatibleCgms/xDrip.md).
-- In xDrip+ select "Libre2 (patched app)" as data source.
-- If necessary, enter "BgReading:d,xdrip libre_receiver:v" under Less Common Settings → Extra Logging Settings → Extra tags for logging. This will log additional error messages for troubleshooting.
+- 若尚未设置，请下载[xDrip+](https://github.com/NightscoutFoundation/xDrip)并按照[xDrip+设置页面](../CompatibleCgms/xDrip.md)的说明进行操作。
+- 在xDrip+中选择"Libre2（破解版应用）"作为数据源。
+- 如有需要，请在"较少使用的设置→额外日志设置→日志记录额外标签"下输入"BgReading:d,xdrip libre_receiver:v"。 这将记录额外的错误信息以便故障排除。
-- Technically, the current blood sugar value is transmitted to xDrip+ every minute. A weighted average filter calculates a smoothed value over the last 25 minutes by default. You can change the period in the NFC Scan features menu.
+- 从技术上讲，当前血糖值每分钟都会传输至xDrip+。 默认情况下，加权平均滤波器会基于过去25分钟的数据计算平滑值。 您可通过NFC扫描功能菜单调整该时段参数。
- → Hamburger menu → Settings → NFC Scan features → Smooth libre 3 data when using xxx method
+ → 汉堡菜单 → 设置 → NFC 扫描功能 → 使用 xxx 方法时平滑 libre 3 数据
-### Step 3: Start sensor within xDrip
+### 步骤3：在xDrip中启动传感器
-In xDrip+ start the sensor with "Start Sensor" and "not today". It is not necessary to hold the mobile phone onto the sensor. In fact "Start Sensor" will not physically start any Libre 3 sensor or interact with them in any case. This is simply to indicate xDrip+ that a new sensor is delivering blood sugar levels. If available, enter two bloody measured values for the initial calibration. Now the blood glucose values should be displayed in xDrip+ every 5 minutes. Skipped values, e.g. because you were too far away from your phone, will not be backfilled.
+在xDrip+中使用"启动传感器"并选择"非今日"选项来启动传感器。 无需将手机紧贴传感器。 实际上，"启动传感器"功能并不会真正启动任何Libre 3传感器，也不会与其产生任何物理交互。 这只是向xDrip+表明有新传感器正在传输血糖数据。 若有条件，请输入两个指尖血测量值进行初始校准。 现在，xDrip+应每隔5分钟显示一次血糖值。 若因手机距离过远导致数值遗漏，系统将不会进行数据回填。
-Wait at least 15-20 minutes if there is still no data.
+如果仍然没有数据，请至少等待15-20分钟。
-After a sensor change xDrip+ will automatically detect the new sensor and will delete all calibration data. You may check you bloody BG after activation and make a new initial calibration.
+更换传感器后，xDrip+将自动检测新传感器并删除所有校准数据。 您可以在激活后检查指尖血糖值，并进行新的初始校准。
-### Step 4: Configure AndroidAPS
+### 步骤 4：配置 AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source)中选择xDrip+。
-- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- 当手机处于飞行模式时若AndroidAPS未接收到血糖值，请使用"识别接收器"功能。
+- 关闭平滑处理（已在xDrip+中完成）
-## Subsequent sensor changes
+## 后续传感器更换
-1. Open Juggluco and note the serial number of the existing sensor
+1. 打开Juggluco并记录现有传感器的序列号。
-2. Now simply scan your new sensor with your phone’s NFC reader. Juggluco will display a notice if the process had been started successfully.
-3. When you are ready to deactivate the old sensor, then open the Juggluco menu by clicking anywhere in the empty space in the upper left hand corner of the screen.
-4. Select the expired sensor and tap "Terminate"
+2. 现在只需用手机的NFC功能扫描新传感器即可。 Juggluco会显示启动是否成功的提示。
+3. 当您准备停用旧传感器时，请点击屏幕左上角空白区域的任意位置以打开Juggluco菜单。
+4. 选择已过期的传感器并点击"终止"
-Note: When two sensors are active Juggluco will send the most recent value from either sensor to xDrip+. If the sensors are not calibrated and reading BG similarly, this may result in jumpy BG values being reported to xDrip+. If you terminate the wrong sensor, you can reactivate it by simply scanning the sensor.
+注意：当两个传感器同时处于激活状态时，Juggluco会将任一传感器的最新数值发送至xDrip+。 若传感器未经校准且血糖读数不一致，可能导致传输至xDrip+的血糖值出现跳跃性波动。 如果不慎终止了错误的传感器，只需重新扫描该传感器即可重新激活。
-## Switch sensor between Libre 3 and Juggluco app
+## 在Libre 3和Juggluco应用之间切换传感器
-If the sensor has been started with a Libreview account logged in, it is also possible to switch between Juggluco and the Libre 3 app as receiver. This requires the following steps:
+若传感器启动时已登录Libreview账户，接收端可在Juggluco和Libre 3应用之间切换使用。 这需要以下步骤：
-1. Install the Libre 3 app from Google Playstore
-2. Set up the Libre 3 app with the Libreview account with which the sensor was activated.
-3. Force stop the Juggluco app in the Android settings.
-4. In the Libre 3 menu, click "Start Sensor", select "Yes", "Next" and scan your sensor.
-5. After some minutes, the BG-Values should be visible within Libre 3 App.
+1. 请从Google Play商店安装Libre 3应用程序。
+2. 请使用激活传感器时所用的Libreview账户设置Libre 3应用程序。
+3. 在安卓设置中强制停止Juggluco应用。
+4. 在Libre 3菜单中点击"启动传感器"，依次选择"是"、"下一步"，然后扫描您的传感器。
+5. 几分钟后，血糖值应会在Libre 3应用程序中显示。
-In order to switch from the Libre 3 app to Juggluco, you need to force-stop Libre 3 app via Android settings and proceed with Step 1 & 2.
+要从Libre 3应用切换回Juggluco，需通过安卓设置强制停止Libre 3应用，然后执行步骤1和步骤2。
(libre3-experiences-and-troubleshooting)=
-## Experiences and Troubleshooting
+## 经验和故障排除
-### Troubleshooting Libre3 -> Juggluco Connection
+### 排查Libre3与Juggluco连接问题
-- Make sure you are using a current version of the Juggluco app
-- Check your settings according to this guide
-- You may sometimes have to force stop the Libre 3 app and Juggluco and restart it.
-- Disable Bluetooth and enable it again
-- Wait some time or try to close Juggluco
-- Older versions of Juggluco (below 2.9.6) do not send subsequent data from the Libre3 sensor to connected devices (e.g. Juggluco on WearOS). You may need to click "Resend data" in the patched Libre3 app (Juggluco menu).
+- 请确保您使用的是最新版Juggluco应用
+- 请按照本指南检查您的设置
+- 有时您可能需要强制停止Libre3应用和Juggluco并重新启动它们。
+- 请关闭蓝牙后重新开启
+- 请稍等片刻或尝试关闭Juggluco
+- 旧版Juggluco(2.9.6以下版本)不会将Libre3传感器的后续数据发送至已连接设备(如WearOS上的Juggluco)。 您可能需要在修改版Libre3应用（Juggluco菜单）中点击"重新发送数据"。
-### Further help
+### 更多帮助
-Original instructions: [jkaltes website](https://www.juggluco.nl/Juggluco/libre3/)
+原始说明：[jkaltes 网站](https://www.juggluco.nl/Juggluco/libre3/)
-Additional Github repo: [Github link](https://github.com/maheini/FreeStyle-Libre-3-patch)
+其他 Github 仓库：[Github 链接](https://github.com/maheini/FreeStyle-Libre-3-patch)
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/MM640g.md b/docs/CROWDIN/zh_CN/CompatibleCgms/MM640g.md
index 59d12aa0bf31..587b941af24b 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/MM640g.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/MM640g.md
@@ -2,12 +2,12 @@
orphan: true
- - -
-# For users of MM640g or MM630g
+# 适用于MM640g或MM630g用户
-- If not already set up then download [600SeriesAndroidUploader](https://pazaan.github.io/600SeriesAndroidUploader/) and follow instructions on [Nightscout](https://nightscout.github.io/uploader/setup/?h=uploader#medtronic-600-series-with-uploader).
-- In 600 Series Uploader go to Settings > Send to xDrip+ and select ON (tick).
+- 若尚未设置，请下载[600SeriesAndroidUploader](https://pazaan.github.io/600SeriesAndroidUploader/)并按照[Nightscout](https://nightscout.github.io/uploader/setup/?h=uploader#medtronic-600-series-with-uploader)上的说明操作。
+- 在600 Series Uploader中，进入设置 > 发送至xDrip+，选择开启（打勾）。
-- Select MM640g in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder，BG源](#Config-Builder-bg-source)中选择MM640g。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md b/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md
index e3c48dedda7d..548c029c2698 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md
@@ -5,19 +5,19 @@ orphan: true
# Ottai M8
-## Using M8 with Ottai app
+## 搭配Ottai应用程序使用M8
-- Download and Install the apk from .
+- 从下载并安装该apk文件。
-- Start sensor
+- 启动传感器
-- Select Ottai in in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder，BG源](#Config-Builder-bg-source)中选择Ottai。
-Enable broadcast in the Ottai app:
+请在Ottai应用中启用广播功能：
-1. Select Profile
+1. 选择 Profile
2. Ottai hub
-3. Tap Share with AAPS, accept the third party data transfer agreement
-4. Enable Share glucose data with AAPS
+3. 点击"与AAPS共享"，同意第三方数据传输协议
+4. 启用"与AAPS共享血糖数据"功能
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/PocTech.md b/docs/CROWDIN/zh_CN/CompatibleCgms/PocTech.md
index c37a5d173421..119ca4531b90 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/PocTech.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/PocTech.md
@@ -2,7 +2,7 @@
orphan: true
- - -
-# For users of PocTech CT-100
+# 适用于 PocTech CT-100 用户
-- Install [PocTech App](https://play.google.com/store/apps/details?id=com.poctechcorp.pocct)
-- Select PocTech App in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 安装 [PocTech 应用程序](https://play.google.com/store/apps/details?id=com.poctechcorp.pocct)
+- 在[ConfigBuilder，BG源](#Config-Builder-bg-source)中选择PocTech应用。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/SmoothingBloodGlucoseData.md b/docs/CROWDIN/zh_CN/CompatibleCgms/SmoothingBloodGlucoseData.md
index 61e0b0a8ee32..64b09b80f8be 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/SmoothingBloodGlucoseData.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/SmoothingBloodGlucoseData.md
@@ -2,41 +2,41 @@
orphan: true
- - -
-# Smoothing blood glucose data
+# 平滑血糖数据
-If **BG** data is jumpy/noisy, **AAPS** may dose insulin incorrectly resulting in highs or lows. If you observe errors in your CGM data it is important to disable the loop until the problem is resolved. Depending on your CGM, such issues may be due to the CGM configuration in **AAPS** (as explained further below); or a CGM sensor site issue (which may require replacing the CGM sensor).
+若**血糖**数据波动较大/存在噪点，**AAPS**可能错误计算胰岛素剂量导致高血糖或低血糖。 若发现连续血糖监测(CGM)数据异常，务必在问题解决前暂停闭环系统运行。 根据您使用的连续血糖监测仪(CGM)，此类问题可能源于**AAPS**中的CGM配置（如下文所述）；或是CGM传感器部位问题（可能需要更换传感器）。
-## Smoothing data within AAPS
+## 在AAPS内部进行数据平滑处理
-As of **AAPS** version 3.2, **AAPS** offers the option to smooth the data within **AAPS** rather than within the CGM app. There are three options available in [Config Builder > Smoothing](../SettingUpAaps/ConfigBuilder.md).
+自**AAPS** 3.2版本起，**AAPS**提供了在**AAPS**内部而非CGM应用中平滑数据的选项。 [配置构建器 > 平滑处理](../SettingUpAaps/ConfigBuilder.md)中提供三种选项。
-
+
-### Exponential smoothing
+### 指数平滑法
-In general, this is the recommended option to start with, as it is most aggressive in resolving noise and rewrites the most recent value. However, see the table below for other specific recommendations.
+通常建议首选此选项，因其降噪效果最强，并能重写最新数值。 但具体推荐方案请参见下表。
-### Average smoothing
+### 均值平滑法
-This option works similar to back smoothing that was previously implemented on certain CGM platforms. It is more reactive to recent changes in BG value and therefore more prone to responding incorrectly to noisy CGM data.
+该选项的运作方式类似于先前在某些CGM平台上实现的回溯平滑功能。 该选项对血糖数值的近期变化更为敏感，因此更容易因CGM数据噪点而做出错误响应。
-### No Smoothing
+### 无平滑处理
-Use this option only if your CGM data is being properly smoothed by your collector app before being transmitted to **AAPS**.
+仅当您的CGM数据在被传输至**AAPS**前已通过采集应用妥善平滑处理时，方可使用此选项。
(smoothing-xdrip-dexcom-g6)=
-## Suggestions to use smoothing
+## 平滑处理使用建议
-| | Exponential | Average | None |
-| ------------- |:-----------:|:---------:|:-----------:|
-| G5/G6/ONE | If noisy | | Recommended |
-| G7/ONE+/Stelo | If noisy | If stable | |
+| | 指数平滑 | 均值平滑 | 无 |
+| ------------- |:-----:|:----:|:--:|
+| G5/G6/ONE | 若存在噪点 | | 推荐 |
+| G7/ONE+/Stelo | 若存在噪点 | 如果稳定 | |
-Libre sensors are noisy and can require smoothing. When using xDrip+ direct connection, or the [patched app data source](https://xdrip.readthedocs.io/en/latest/install/libre2patch/) (receiving from another app, Juggluco included), smoothing is already done [inside the app](https://xdrip.readthedocs.io/en/latest/use/NFC/#smooth-libre-3-data-when-using-xxx-method).
+Libre传感器数据存在噪点，可能需要进行平滑处理。 当使用xDrip+直接连接或[修改版应用数据源](https://xdrip.readthedocs.io/en/latest/install/libre2patch/)（接收来自其他应用的数据，包括Juggluco）时，平滑处理已在[应用内部](https://xdrip.readthedocs.io/en/latest/use/NFC/#smooth-libre-3-data-when-using-xxx-method)完成。
-| Sensor / Data source | Juggluco | xDrip+ direct | xDrip+ bridge | xDrip+ patched app |
-| -------------------- |:--------:|:-------------:|:-------------:|:------------------:|
-| Libre 1/14 days/Pro | N.A. | N.A. | Average | N.A. |
-| Libre 2/2+ (EU) | Average | None | Average | None |
-| Libre 2/2+/3/3+ | Average | N.A. | N.A. | None |
+| 传感器/数据源 | Juggluco | xDrip+ 直接连接 | xDrip+ 桥接 | xDrip+ 修补的应用程序 |
+| ---------------- |:--------:|:-----------:|:---------:|:--------------:|
+| Libre 1/14 天/Pro | 不适用 | 不适用 | 均值平滑 | 不适用 |
+| Libre 2/2+ (EU) | 均值平滑 | 无 | 均值平滑 | 无 |
+| Libre 2/2+/3/3+ | 均值平滑 | 不适用 | 不适用 | 无 |
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/SyaiTagX1.md b/docs/CROWDIN/zh_CN/CompatibleCgms/SyaiTagX1.md
index 348654be792b..9ba8cefc447f 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/SyaiTagX1.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/SyaiTagX1.md
@@ -5,19 +5,19 @@ orphan: true
# Syai X1
-## Using X1 And Syai Tag app
+## 使用X1与Syai Tag应用
-- Install the apk from .
+- 从下载并安装该apk文件。
-- Start X1 sensor
+- 启动X1传感器
-- Select Syai Tag in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- 在[ConfigBuilder，BG源](#Config-Builder-bg-source)中选择Syai Tag。
-Enable broadcast in the Syai app:
+请在Syai应用中启用广播功能：
-1. Select Profile
-2. Syai Health Ecosystem
-3. Tap Connect Now with AAPS, accept the third party data transfer agreement
-4. Enable share data with AAPS
+1. 选择 Profile
+2. Syai健康生态系统
+3. 点击"立即与AAPS连接"，同意第三方数据传输协议
+4. 启用"与AAPS共享数据"功能
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/xDrip.md b/docs/CROWDIN/zh_CN/CompatibleCgms/xDrip.md
index b39adb757a09..9e46bb719c67 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/xDrip.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/xDrip.md
@@ -4,250 +4,250 @@ orphan: true
* * *
-# xDrip+ settings
+# xDrip+ 设置
-If not already set up, then download [xDrip+](https://jamorham.github.io/#xdrip-plus).
+若尚未设置，请下载[xDrip+](https://jamorham.github.io/#xdrip-plus)。
-Disable battery optimization and allow background activity for the xDrip+ app.
+禁用xDrip+应用的电池优化功能并允许后台运行。
-You can safely download the [latest APK (stable)](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) unless you need recent features or are using sensors that are being actively integrated (like G7), in which case you should use the latest [Nightly Snapshot](https://github.com/NightscoutFoundation/xDrip/releases).
+您可以安全下载[最新APK（稳定版）](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk)，除非您需要使用最新功能或正在使用正在积极集成的传感器（如G7），这种情况下应使用最新的[夜间快照版](https://github.com/NightscoutFoundation/xDrip/releases)。
-## Basic settings for all CGM & FGM systems
+## 所有CGM和FGM系统的基础设置
-### Disable Nightscout upload
+### 禁用Nightscout上传功能
-Starting with AAPS 3.2, you shouldn't let any other app upload data (blood glucose and treatments) to Nightscout.
+从AAPS 3.2版本开始，您不应允许其他任何应用向Nightscout上传数据（血糖和治疗记录）。
-→ Hamburger Menu (1) → Settings (2) → Cloud Upload (3) -> Nightscout Sync (REST-API)(4) → Switch **OFF** `Enabled` (5)
+→ 汉堡菜单 (1) → 设置 (2) → 云端上传 (3) → Nightscout同步(REST-API)(4) → 将**OFF** `启用`开关关闭 (5)
-#### Disable automatic calibration and treatments
+#### 禁用自动校准和治疗功能
-If you use an older version of AAPS (before 3.2), make sure to deactivate `Automatic Calibration` (7) If the checkbox for `Automatic Calibration` is checked, activate `Download treatments` (6) once, then remove the checkbox for `Automatic Calibration` and deactivate `Download treatments` again.
+若您使用旧版AAPS(3.2之前版本)，请确保停用`自动校准`功能(7) 若`自动校准`复选框被勾选，请先启用`下载治疗记录`(6)一次，然后取消勾选`自动校准`，并再次停用`下载治疗记录`。
-Tap `Extra Options`(8)
+点击`额外选项`(8)
- {admonition} Safety warning
+ {admonition} 安全警告
:class: warning
- You must deactivate "Upload treatments" from xDrip+, otherwise treatments can be doubled in AAPS leading to false COB and IOB.
+ 必须关闭xDrip+中的"上传治疗方案"功能，否则会导致AAPS中治疗方案重复计算，造成错误的碳水化合物(COB)和胰岛素(IOB)数据。
-Deactivate `Upload treatments`(9) and make sure you will **NOT** use `Back-fill data` (11).
+停用`上传治疗方案`功能(9)，并确保**不要**使用`数据回填`功能(11)。
-Option `Alert on failures` should also be deactivated (10). Otherwise you will get an alarm every 5 minutes in case Wi-Fi/mobile network issues or if the server is not available.
+还应停用`故障警报`选项(10)。 否则当Wi-Fi/移动网络出现故障或服务器不可用时，您将每5分钟收到一次警报。
-### **Inter-app Settings** (Broadcast)
+### **应用间设置**（广播）
-If you are going to use AAPS and the data should be forwarded to i.e. AAPS you have to activate broadcasting in xDrip+ in Inter-App settings.
+若您计划使用AAPS且需将数据转发至AAPS等应用，则必须在xDrip+的"应用间设置"中启用广播功能。
-→ Hamburger Menu (1) → Settings (2) → Inter-app settings (3) → Broadcast locally **ON** (4)
+→ 汉堡菜单 (1) → 设置 (2) → 应用间设置 (3) → 本地广播 **开启** (4)
-In order for the values to be identical in AAPS with respect to xDrip+, you should activate `Send the displayed glucose value` (5).
+为确保AAPS中的数值与xDrip+完全一致，您应启用`发送显示的血糖值`功能(5)。
-Enable Compatible Broadcast (6).
+启用兼容广播模式(6)。
-If you have also activated `Accept treatments` in xDrip+ and `Enable broadcasts to xDrip+` in AAPS xDrip+ plugin, then xDrip+ will receive insulin, carbs and basal rate information from AAPS.
+若您同时在xDrip+中启用了`接受治疗方案`功能，并在AAPS的xDrip+插件中启用了`向xDrip+广播`功能，则xDrip+将能接收来自AAPS的胰岛素、碳水化合物和基础率信息。
-If you enable `Accept Calibrations`, xDrip+ will use the calibrations from AAPS. Be careful when you use this feature with Dexcom sensors: read [this](https://navid200.github.io/xDrip/docs/Calibrate-G6.html) first.
+若启用`接受校准`功能，xDrip+将采用来自AAPS的校准数据。 使用Dexcom传感器时启用此功能需谨慎：请先阅读[此说明](https://navid200.github.io/xDrip/docs/Calibrate-G6.html)。
-Remember to disable Import Sounds to avoid xDrip+ making a ringtone every time AAPS sends a basal/profile change.
+请务必禁用"导入提示音"功能，以避免AAPS每次发送基础率/配置文件变更时xDrip+发出铃声提示。
(xdrip-identify-receiver)=
-#### Identify receiver
+#### 识别接收器
-- If you discover problems with local broadcast (AAPS not receiving BG values from xDrip+) go to → Hamburger Menu (1) Settings (2) → Inter-app settings (3) → Identify receiver (7) and enter `info.nightscout.androidaps` for AAPS build (if you are using PumpControl build, please enter `info.nightscout.aapspumpcontrol` instead!!).
-- Pay attention: Auto-correction sometimes tend to change i to capital letter. You **must use only lowercase letters** when typing `info.nightscout.androidaps` (or `info.nightscout.aapspumpcontrol` for PumpControl). Capital I would prevent the App from receiving BG values from xDrip+.
+- 若发现本地广播存在问题（AAPS无法接收来自xDrip+的血糖值），请前往→ 汉堡菜单 (1) → 设置 (2) → 应用间设置 (3) → 识别接收器 (7)，为AAPS版本输入`info.nightscout.androidaps`（若使用PumpControl版本，请改为输入`info.nightscout.aapspumpcontrol`！！）。
+- 注意：自动校正功能有时会将字母i改为大写。 输入`info.nightscout.androidaps`（或PumpControl版输入`info.nightscout.aapspumpcontrol`）时，**必须全部使用小写字母**。 大写字母"I"会导致应用无法接收来自xDrip+的血糖值。
-## Use AAPS to calibrate in xDrip+
+## 使用AAPS在xDrip+中进行校准
-- If you want to be able to use AAPS to calibrate then in xDrip+ go to Settings → Interapp Compatibility → Accept Calibrations and select ON.
-- You may also want to review the options in Settings → Less Common Settings → Advanced Calibration Settings.
+- 若需使用AAPS进行校准，请在xDrip+中前往设置→应用间兼容性→接受校准，并选择开启。
+- 您可能还需要查看设置→较少使用设置→高级校准设置中的选项。
## Dexcom G6
-- The Dexcom G6 transmitter can simultaneously be connected to the Dexcom receiver (or alternatively the t:slim pump) and one app on your phone.
-- When using xDrip+ as receiver uninstall Dexcom app first. **You cannot connect xDrip+ and Dexcom app with the transmitter at the same time!**
-- If you need Clarity and want to profit from xDrip+ features, use the [Build Your Own Dexcom App](#DexcomG6-if-using-g6-with-build-your-own-dexcom-app) with local broadcast to xDrip+, or use xDrip+ as a Companion app receiving notifications from the official Dexcom app.
+- Dexcom G6发射器可同时连接至Dexcom接收器（或t:slim泵）和您手机上的一个应用程序。
+- 使用xDrip+作为接收器时，请先卸载Dexcom应用程序。 **您无法同时将xDrip+和Dexcom应用程序连接到发射器！**
+- 若您需要使用Clarity功能，同时希望保留xDrip+的特性，可选择使用[自制Dexcom应用](#DexcomG6-if-using-g6-with-build-your-own-dexcom-app)并通过本地广播将数据传输至xDrip+，或者将xDrip+作为配套应用，接收来自官方Dexcom应用的通知。
-### xDrip+ version depending on G6 transmitter serial no.
+### xDrip+版本需根据G6发射器序列号选择
-- All G6 transmitters manufactured after fall/end 2018 are called "Firefly". They do not allow sensor restart without [removing the transmitter](https://navid200.github.io/xDrip/docs/Remove-transmitter.html), they do not send raw data. It is recommended to use the latest [Nightly Snapshot](https://github.com/NightscoutFoundation/xDrip/releases).
-- Old rebatteried transmitters and modified transmitters allow sensor life extension and restarts, they also send raw data. You can use the [latest APK (stable)](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk).
+- 所有2018年秋季/年底之后生产的G6发射器均称为"萤火虫"(Firefly)型号。 这些发射器[不拆除发射器](https://navid200.github.io/xDrip/docs/Remove-transmitter.html)就无法重启传感器，且不会发送原始数据。 建议使用最新的[夜间快照版](https://github.com/NightscoutFoundation/xDrip/releases)。
+- 经过电池更换的旧发射器和改装版发射器支持传感器寿命延长及重启功能，同时仍可发送原始数据。 您可以使用[最新APK（稳定版）](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk)。
-### Dexcom specific settings
+### Dexcom专用设置
-- Follow [these instructions](https://navid200.github.io/xDrip/docs/G6-Recommended-Settings.html) to setup xDrip+.
+- 请按照[这些说明](https://navid200.github.io/xDrip/docs/G6-Recommended-Settings.html)来设置xDrip+。
-### Preemptive restarts not recommended
+### 不建议进行预防性重启
-**Only rebatteried or modified Dexcom transmitters. [Preemptive restarts](https://navid200.github.io/xDrip/docs/Preemptive-Restart.html) do not work with standard transmitters and will stop the sensor completely: you need to [remove the transmitter](https://navid200.github.io/xDrip/docs/Remove-transmitter.html) to restart the sensor.**
+**仅适用于更换过电池或改装过的Dexcom发射器。 [预防性重启](https://navid200.github.io/xDrip/docs/Preemptive-Restart.html)不适用于标准发射器，会导致传感器完全停止工作：您需要[移除发射器](https://navid200.github.io/xDrip/docs/Remove-transmitter.html)才能重启传感器。**
-The automatic extension of Dexcom sensors (`preemptive restarts`) is not recommended as this might lead to “jumps” in BG values on day 9 after restart.
+不建议对Dexcom传感器进行自动延长（`预防性重启`），因为这可能导致重启后第9天出现血糖值"跳跃"。
-To use it safely, there are a few points to be aware of:
+要安全使用该功能，需注意以下几点：
-- If you are using the native data with the calibration code in xDrip+ or Spike, the safest thing to do is not allow preemptive restarts of the sensor.
-- If you must use preemptive restarts, then make sure you insert at a time of day where you can observe the change and calibrate if necessary.
-- If you are restarting sensors, either do it without the factory calibration for safest results on days 11 and 12, or ensure you are ready to calibrate and keep an eye on variation.
-- Pre-soaking of the G6 with factory calibration is likely to give variation in results. If you do pre-soak, then to get best results, you will probably need to calibrate the sensor.
-- If you aren’t being observant about the changes that may be taking place, it may be better to revert to non-factory-calibrated mode and use the system like a G5.
+- 若您在xDrip+或Spike中使用原生数据及校准码，最安全的做法是不允许对传感器进行预防性重启。
+- 如必须进行预防性重启，请选择在白天时段操作，以便能够观察数值变化并在必要时进行校准。
+- 若需重启传感器，建议采用以下两种方式之一：要么不使用出厂校准（这样在第11-12天能获得最安全的结果），要么确保做好校准准备并密切监测数值波动。
+- 使用出厂校准的G6传感器进行预热可能导致检测结果出现波动。 若进行预热操作，为获得最佳效果，您很可能需要对传感器进行校准。
+- 如果您未能密切留意可能发生的变化，恢复至非出厂校准模式并将系统当作G5使用可能是更稳妥的选择。
-To learn more about the details and reasons for these recommendations read the [complete article](https://www.diabettech.com/artificial-pancreas/diy-looping-and-cgm/) published by Tim Street at [www.diabettech.com](https://www.diabettech.com).
+要了解这些建议的具体细节和原因，请阅读Tim Street发表在[http://www.diabettech.com](https://www.diabettech.com)上的[完整文章](https://www.diabettech.com/artificial-pancreas/diy-looping-and-cgm/)。
(xdrip-connect-g6-transmitter-for-the-first-time)=
-### Connect G6 transmitter for the first time
+### 首次连接G6发射器
-**For second and following transmitters see [Extend transmitter life](#xdrip-extend-transmitter-life) below.**
+**对于第二个及后续发射器，请参阅下方的[延长发射器寿命](#xdrip-extend-transmitter-life)。**
-Follow [these instructions](https://navid200.github.io/xDrip/docs/Starting-G6.html).
+请按照[这些说明](https://navid200.github.io/xDrip/docs/Starting-G6.html)操作。
(xdrip-transmitter-battery-status)=
-### Transmitter battery status
+### 发射器电池状态
-- Battery status can be controlled in system status
- → Hamburger Menu (1) → System Status (2) → If you are on the Classic Status Page (3) swipe the screen (4) to reach → G5/G6/G7 Status screen.
+- 电池状态可通过系统状态查看
+ → 点击汉堡菜单(1) → 选择系统状态(2) → 若在经典状态页面(3)需滑动屏幕(4) → 进入G5/G6/G7状态界面。
-- See [here](https://navid200.github.io/xDrip/docs/Battery-condition.html) for more information.
+- 有关更多信息，请参阅[此处](https://navid200.github.io/xDrip/docs/Battery-condition.html)。
(xdrip-extend-transmitter-life)=
-### Extend transmitter life
+### 延长发射器寿命
-- [Lifetime](https://navid200.github.io/xDrip/docs/Transmitter-lifetime.html) cannot be extended for Firefly transmitters: only rebatteried or modified transmitters.
-- Follow [these instructions](https://navid200.github.io/xDrip/docs/Hard-Reset.html) for non-Firefly transmitters.
+- [使用寿命](https://navid200.github.io/xDrip/docs/Transmitter-lifetime.html)无法延长萤火虫(Firefly)发射器：仅适用于更换过电池或改装过的发射器。
+- 对于非萤火虫(Firefly)发射器，请按照[这些说明](https://navid200.github.io/xDrip/docs/Hard-Reset.html)操作。
(xdrip-replace-transmitter)=
-### Replace transmitter
+### 更换发射器
-- Turn original Dexcom receiver off (if used).
-- [Stop sensor](https://navid200.github.io/xDrip/docs/Dexcom/StartG6Sensor.html) (only if replacing sensor).
+- 关闭原始 Dexcom 接收器（如果使用）。
+- [停止传感器](https://navid200.github.io/xDrip/docs/Dexcom/StartG6Sensor.html)（仅在更换传感器时操作）。
-- Forget device in xDrip+ system status AND in smartphone’s BT settings (Will be shown as Dexcom?? whereas ?? are the last two digits of the transmitter serial no.)
- → Hamburger Menu (1) → System Status (2) → If you are not on the Classic Status Page (3) swipe the screen (4) to reach it → then tap Forget Device (5).
+- 在xDrip+系统状态和手机蓝牙设置中忘记该设备（将显示为Dexcom??） 而?? （其中??是发射器序列号的最后两位数字）
+ → 点击汉堡菜单(1) → 选择系统状态(2) → 若不在经典状态页面(3)需滑动屏幕(4) → 然后点击"忘记设备"(5)。
-- Remove transmitter (and sensor if replacing sensor). To remove transmitter without removing sensor see [this](https://navid200.github.io/xDrip/docs/Remove-transmitter.html), or this video .
-- Put the old transmitter far away to prevent reconnection. A microwave is a perfect Faraday shield for this - but unplug power cord to be 100% sure no one is turning the microwave on.
-- Follow [these instructions](https://navid200.github.io/xDrip/docs/Starting-G6.html).
-- Do not turn original Dexcom receiver (if used) back on before xDrip+ shows first readings.
+- 移除发射器（若更换传感器则需一并移除传感器）。 若需移除发射器但保留传感器，请参阅[此方法](https://navid200.github.io/xDrip/docs/Remove-transmitter.html)或观看视频。
+- 请将旧发射器放置远处，防止其重新连接。 微波炉是绝佳的电磁屏蔽装置 - 但为确保万无一失，请拔掉电源线以防有人误开微波炉。
+- 请按照[这些说明](https://navid200.github.io/xDrip/docs/Starting-G6.html)操作。
+- 在xDrip+显示首次读数前，请勿重新开启原装Dexcom接收器（若使用）。
-### New Sensor
+### 新传感器
-- Turn original Dexcom receiver off (if used).
-- Stop sensor following [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/StartG6Sensor.html).
+- 关闭原始 Dexcom 接收器（如果使用）。
+- 按照[这些说明](https://navid200.github.io/xDrip/docs/Dexcom/StartG6Sensor.html)停止传感器。
-- Insert and then start a new sensor following [these instructions](https://navid200.github.io/xDrip/docs/Starting-G6.html).
+- 按照[这些说明](https://navid200.github.io/xDrip/docs/Starting-G6.html)插入并启动新传感器。
(xdrip-retrieve-sensor-code)=
-### Retrieve sensor code
+### 获取传感器代码
-→ Hamburger Menu (1) → System Status (2) → If you are on the Classic Status Page (3) swipe the screen (4) to reach → G5/G6/G7 Status screen → Calibration Code.
+→ 点击汉堡菜单(1) → 选择系统状态(2) → 若当前在经典状态页面(3)需滑动屏幕(4) → 进入G5/G6/G7状态界面 → 选择校准代码。
(xdrip-troubleshooting-dexcom-g5-g6-and-xdrip)=
-### Troubleshooting Dexcom G5/G6 and xDrip+
+### Dexcom G5/G6与xDrip+故障排除
-#### Problem connecting transmitter
+#### 发射器连接问题
-Follow [these instructions](https://navid200.github.io/xDrip/docs/Connectivity-troubleshoot.html).
+请按照[这些说明](https://navid200.github.io/xDrip/docs/Connectivity-troubleshoot.html)进行操作。
-#### Problem when starting new sensor
+#### 启动新传感器时出现问题
-Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorFailedStart.html).
+请按照[这些说明](https://navid200.github.io/xDrip/docs/Dexcom/SensorFailedStart.html)进行操作。
## Libre 1
-- Setup your NFC to Bluetooth bridge in xDrip+
+- 在 xDrip+ 中设置您的 NFC 到蓝牙桥接器
- → Hamburger Menu (1) → Settings (2) → Less common settings (3) → Bluetooth Settings (4)
+ → 汉堡菜单 (1) → 设置 (2) → 较不常见的设置 (3) → 蓝牙设置 (4)
-- In Bluetooth Settings set the checkboxes exactly as in the screenshots below (5)
+- 在蓝牙设置中，完全按照以下屏幕截图中的方式设置复选框 (5)
- - Disable watchdogs as they will reset the phone Bluetooth and interrupt your pump connection.
+ - 禁用看门狗功能，因为它们会重置手机蓝牙并中断您的泵连接。
-- You can try to enable the following settings (7)
+- 您可以尝试启用以下设置（7）
- - Use scanning
- - Trust Auto-Connect
- - Use Background Scans
+ - 使用扫描
+ - 信任自动连接
+ - 使用后台扫描
-- If you easily lose connection to the bridge or have difficulties recovering connection, **DISABLE THEM** (8).
+- 若您频繁断开网桥连接或难以恢复连接，**请禁用这些设置**（8）。
-- Leave all other options disabled unless you know why you want to enable them.
+- 除非您明确知道启用原因，否则请保持其他所有选项处于禁用状态。
-### Libre smart reader battery level
+### Libre智能读卡器电池电量
-- Battery level of bridges such as MiaoMiao and Bubble can be displayed in AAPS (not Blucon).
-- Details can be found on [screenshots page](#screens-sensor-level-battery).
+- MiaoMiao和Bubble等网桥设备的电池电量可在AAPS中显示（Blucon除外）。
+- 详情请参阅[截图页面](#screens-sensor-level-battery)。
-### Connect Libre Transmitter & start sensor
+### 连接Libre发射器并启动传感器
-- If your sensor requires it (Libre 2 EU and Libre 1 US) install the [latest out of process algorithm](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view).
+- 若您的传感器需要（欧盟版Libre 2和美国版Libre 1），请安装[最新独立处理算法](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view)。
-- Your sensor must be already started using the vendor app or the reader (xDrip+ cannot start or stop Libre sensors).
+- 您的传感器必须已通过厂商应用程序或读卡器启动（xDrip+无法启动或停止Libre传感器）。
-- Set the data source to Libre Bluetooth.
+- 将数据源设置为Libre蓝牙。
- → Hamburger Menu (1) → Settings (2) → Select Libre Bluetooth in Hardware Data source (3)
+ → 汉堡菜单 (1) → 设置 (2) → 在硬件数据源中选择 Libre 蓝牙 (3)
-- Scan Bluetooth and connect the bridge.
+- 扫描蓝牙并连接桥接器。
- → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3)
+ → 汉堡菜单 (1) → 扫描蓝牙 (2) → 扫描 (3)
- - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it.
+ - 如果xDrip+无法找到网桥设备，请确保其未连接至厂商应用程序。将其充电并重置。
-- Start the sensor in xDrip+.
+- 在xDrip+中启动传感器。
- {admonition} Safety warning
+ {admonition} 安全警告
:class: warning
- Do not use sensor data before the one hour warm-up is over: the values can be extremely high and cause wrong decisions in AAPS.
+ 传感器预热一小时结束前请勿使用其数据：此时数值可能极高，会导致AAPS做出错误决策。
- → Hamburger Menu (1) → Start sensor (2) → Start sensor (3) → Set the exact time you started it with the reader or the vendor app. If you didn't start it today, answer "Not Today" (4).
+ → 点击汉堡菜单(1) → 选择"启动传感器"(2) → 点击"启动传感器"(3) → 设置您使用读卡器或厂商应用启动传感器的准确时间。若非今日启动，请选择"不是今天"(4)。
(xdrip-libre2-patched-app)=
-## Libre 2 patched app
+## Libre 2 修补版应用程序
-- Set the data source to Libre patched app.
+- 将数据源设置为 Libre 修补版应用程序。
- → Hamburger Menu (1) → Settings (2) → Select Libre (patched App) in Hardware Data source (3)
+ → 汉堡菜单 (1) → 设置 (2) → 在硬件数据源中选择 Libre（修补版应用程序）(3)
-- You can add `BgReading:d,xdrip libre_receiver:v` under Less Common Settings->Extra Logging Settings->Extra tags for logging. This will log additional error messages for trouble shooting.
+- 您可以在"较少使用的设置"→"额外日志设置"→"日志记录附加标签"下添加`BgReading:d,xdrip libre_receiver:v`。 这将记录额外的错误信息以便故障排除。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePhones/Huawei.md b/docs/CROWDIN/zh_CN/CompatiblePhones/Huawei.md
index 551351427ee8..ea26ce6a1963 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePhones/Huawei.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePhones/Huawei.md
@@ -4,39 +4,39 @@ orphan: true
* * *
-# How-to configure a Huawei phone
+# 如何配置华为手机
-There are different options, some Android specific, some Huawei specific:
+这里有一些不同的选项，一些是安卓特定的，一些是华为特定的：
-* Add AAPS and xdrip+ to apps list which ignore battery optimisations:
+* 将 AAPS 和 xdrip+ 添加到忽略电池优化的应用列表中：
- * Settings / App / Settings / Special autorisations / Ignore battery optimisation / Select "All applications" / Set app to allowed
+ * 设置 / 应用 / 设置 / 特殊访问权限 / 忽略电池优化 / 选择“所有应用” / 将应用设置为允许
-* Set battery option settings:
+* 设置电池选项设置：
- * Settings / App / Select AndroidAPS/xdrip+ / Under Battery / App launch
+ * 设置 / 应用 / 选择 AndroidAPS/xdrip+ / 在电池下 / 应用启动
- * Make sure to remove "automatic management"
- * Allow:
+ * 确保移除“自动管理”
+ * 允许：
- * Automatic launch
- * Secondary launch (can be launched from other apps)
- * Background run
+ * 自动启动
+ * 辅助启动（可以从其他应用启动）
+ * 后台运行
-* Lock App
+* 锁定应用
- * Go into App recent list and select the lock icon
+ * 进入应用最近列表并选择锁定图标
-For xDrip+, you must enable persistent notifications (within xDrip+ app):
+对于 xDrip+，你必须启用持久通知（在 xDrip+ 应用内）：
-* Settings / less common settings / other misc options / Run Collector in foreground
+* 设置 / 不常用设置 / 其他杂项选项 / 在前台运行采集器
-Depending on Android version, these settings are somewhere else. These explanations are for Android 8.1.
\ No newline at end of file
+根据Android版本不同，这些设置的位置会有所变化。 这些说明适用于Android 8.1系统。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md b/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md
index c576131238ef..79c5fca0ca0d 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md
@@ -8,29 +8,29 @@ orphan: true
## Jelly 2
-Do not confuse with Jelly Star.
+不要与 Jelly Star 混淆。
-**Advantages**
+**优点**
-* It's really small.
-* Android 11.
-* Even if you tell people, they might not consider it as a normal smartphone and will except it easier as a exception when phones are normally not allowed.
+* 真的很小。
+* Android 11。
+* 即使你告诉人们，他们也可能不会把它当作普通的智能手机，当通常不允许使用手机时，更容易把它当作例外接受。
-**Disadvantages**
+**缺点**
-* Recommended only for experienced loopers (some settings are not recognizable, you have to know from experience with a big Android AAPS phone, how and where what is located. Some AAPS buttons are hard to touch with a lot of feeling, but not with stubby fingers.)
-* Can only be used as LooperPhone. It's better to have a normal smartphone in your pocket.
+* 仅推荐有经验的闭环使用者使用（部分设置不可识别，需通过大屏Android AAPS手机的操作经验来了解各项功能的位置及使用方法。 某些AAPS按钮需要细腻的触控操作，粗短手指可能难以准确点击）。
+* 只能用作 LooperPhone。 最好口袋里还有一部普通的智能手机。
-### Battery life optimization
+### 电池寿命优化
-The Jelly 2 comes with strong optimization features that **must** be disabled for AAPS (and other DIY apps like BYODA, xDrip+, OOP2, Juggluco, etc...).
+Jelly 2 配备了强大的优化功能，**必须**为 AAPS（以及其他 DIY 应用程序，如 BYODA、xDrip+、OOP2、Juggluco 等）禁用这些功能。
-You can leave Intelligent assistance enabled, but it **must be disabled for DIY apps**.
+你可以启用智能辅助，但**必须为 DIY 应用程序禁用它**。
-You can enable NFC for Libre sensors.
+你可以为 Libre 传感器启用 NFC。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index d9e28ea01b09..3782067d33ee 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -167,7 +167,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
-## Preferences
+## 偏好设置
These preferences are available for the combo driver (items are listed from top to bottom):
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
index ff92c917cae9..639c5aa4e7dc 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
@@ -345,7 +345,7 @@ This button will start the process to change the patch. See [Activate patch](#me
### Reset alarms
-The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
+The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. 例如 when suspended due to a maximum daily insulin delivery alarm.
diff --git a/docs/CROWDIN/zh_CN/DailyLifeWithAaps/DynamicISF.md b/docs/CROWDIN/zh_CN/DailyLifeWithAaps/DynamicISF.md
index 1467f51a4dd8..c6183b0ab2be 100644
--- a/docs/CROWDIN/zh_CN/DailyLifeWithAaps/DynamicISF.md
+++ b/docs/CROWDIN/zh_CN/DailyLifeWithAaps/DynamicISF.md
@@ -95,7 +95,7 @@ TDD将使用以下值的组合：
启用 **动态 ISF 时**，此处 **ISF** 为过去 24 小时动态 ISF 的平均值。
(dyn-isf-preferences)=
-## Preferences
+## 偏好设置
在 [偏好设置 > OpenAPS SMB](#Preferences-openaps-smb-settings) 中勾选 **启用动态敏感度** 以激活功能。 启用后将显示新设置项。
diff --git a/docs/CROWDIN/zh_CN/Getting-Started/Phones.md b/docs/CROWDIN/zh_CN/Getting-Started/Phones.md
index 40996c0c347d..1bcbb3483f25 100644
--- a/docs/CROWDIN/zh_CN/Getting-Started/Phones.md
+++ b/docs/CROWDIN/zh_CN/Getting-Started/Phones.md
@@ -9,13 +9,13 @@
(Phones-list-of-tested-phones)=
-## List of tested Phones
+## 已测试手机列表
我们维护了一个[经过测试的硬件设置](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true)列表。
此列表提供了用户关于手机与**AAPS**以及特定泵和CGM配合使用的反馈。 它可以帮助您检查您的手机/泵/CGM是否已被其他用户成功使用。
-The document is read-only. With CRTL-F, you can search in the text of the Google sheet.
+该文档为只读文件。 使用Ctrl+F快捷键可在Google表格中进行文本搜索。
要记录您对硬件设置的测试，请填写此[表格](https://docs.google.com/forms/d/e/1FAIpQLSfoGKLYEx4aUAJ5RWL3xLJeNdmRyxtXmDzpGhuU3Rfcj2H_Jw/viewform)。 填写完表单数据后，该表格将每5分钟自动更新一次
diff --git a/docs/CROWDIN/zh_CN/RemoteFeatures/SMSCommands.md b/docs/CROWDIN/zh_CN/RemoteFeatures/SMSCommands.md
index 6338a79c6ba9..5df88d6051b6 100644
--- a/docs/CROWDIN/zh_CN/RemoteFeatures/SMSCommands.md
+++ b/docs/CROWDIN/zh_CN/RemoteFeatures/SMSCommands.md
@@ -195,7 +195,7 @@ PIN码要求：
| BG | 否 | 回复: last BG, delta, IOB (bolus and basal), COB
*Last BG: 5.6 4min ago, Delta: -0,2 mmol, IOB: 0.20U (Bolus: 0.10U Basal: 0.10U)* |
| CAL 5.6/90 | 是 | 将CGM校准为5.6/90的值
（使用适合您的葡萄糖单位的值）
仅在**AAPS**中 的
*已发送校准*正确设置后才有效。 |
-### Pump
+### 胰岛素泵
| 指令 | 身份验证 | 功能与*回复* |
| -------------------- | ---- | --------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/docs/CROWDIN/zh_CN/Sandbox/MoveTest/sandbox2.md b/docs/CROWDIN/zh_CN/Sandbox/MoveTest/sandbox2.md
index 123915a8abee..b0f5cbd1f5a0 100644
--- a/docs/CROWDIN/zh_CN/Sandbox/MoveTest/sandbox2.md
+++ b/docs/CROWDIN/zh_CN/Sandbox/MoveTest/sandbox2.md
@@ -2,12 +2,12 @@
orphan: true
- - -
-# internal sandbox file 2 for testing
+# 内部沙盒测试文件2
```{admonition} no need to translate this
:class: note
-No need to translate this.
+无需翻译。
```
This is an internal sandbox file for the documentation team to test
diff --git a/docs/CROWDIN/zh_CN/Sandbox/sandbox1.md b/docs/CROWDIN/zh_CN/Sandbox/sandbox1.md
index cfe4b00cc551..559e7ff733c7 100644
--- a/docs/CROWDIN/zh_CN/Sandbox/sandbox1.md
+++ b/docs/CROWDIN/zh_CN/Sandbox/sandbox1.md
@@ -7,7 +7,7 @@ orphan: true
```{admonition} no need to translate this
:class: note
-No need to translate this.
+无需翻译。
```
```{danger}
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/ChangeAapsConfiguration.md b/docs/CROWDIN/zh_CN/SettingUpAaps/ChangeAapsConfiguration.md
index e8e8f90f6dae..8c654d15b93d 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/ChangeAapsConfiguration.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/ChangeAapsConfiguration.md
@@ -22,7 +22,7 @@
有关配置构建器的文档，请点击[此处](../SettingUpAaps/ConfigBuilder.md)查阅。
-## Preferences
+## 偏好设置
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md b/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md
index ac9d1325ce55..acf11c2b69f8 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md
@@ -102,15 +102,15 @@
* [Syai Tag](../CompatibleCgms/SyaiTagX1.md)
* 随机 Random BG：生成随机BG数据（仅演示模式）
-## Smoothing
+## 平滑
-
+
请参阅[平滑血糖数据](../CompatibleCgms/SmoothingBloodGlucoseData.md)。
(Config-Builder-pump)=
-## Pump
+## 胰岛素泵
选择您正在使用的泵。 有关更多设置信息，请参阅[兼容泵](../Getting-Started/CompatiblePumps.md)页面。
@@ -211,7 +211,7 @@
如果您查看“治疗（Treat）”选项卡，您可以看到已上传到nightscout的治疗动作数据。 如果您希望编辑或删除条目（例如，您摄入的碳水比预期少），请选择“删除”并通过[主页屏幕上的碳水按钮](#screens-bolus-carbs)输入新值（必要时更改时间）。
-## 一般
+## 常规
### 概览
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/Nightscout.md b/docs/CROWDIN/zh_CN/SettingUpAaps/Nightscout.md
index a74ee40e9849..e4acc6df5b3b 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/Nightscout.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/Nightscout.md
@@ -8,7 +8,7 @@
如果使用Nightscout作为AAPS的数据源，请务必格外小心。
-### Nightscout settings
+### Nightscout设置
您可以通过使用[认证角色](https://nightscout.github.io/nightscout/security)来拒绝公众访问您的Nightscout站点：确保您只与具有“可读”权限的令牌共享您的URL，切勿与具有“管理员”权限的令牌共享。
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md b/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md
index e3227b035b53..a8483909d365 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md
@@ -1,4 +1,4 @@
-# Preferences
+# 偏好设置
- 通过点击主页屏幕右上角的三个点菜单来**打开参数设置**。
@@ -22,7 +22,7 @@
```
(Preferences-general)=
-## 一般
+## 常规
@@ -378,7 +378,7 @@ min_5m_carbimpact的标准值：AMA算法为5，SMB算法为8。
- 定义最小和最大[自动灵敏度（autosens）](#Open-APS-features-autosens)比率。
- 通常，不应更改标准值（最大1.2，最小0.7）。
-## Pump
+## 胰岛素泵
### BT Watchdog
@@ -500,7 +500,7 @@ min_5m_carbimpact的标准值：AMA算法为5，SMB算法为8。
## 开源人类项目（Open Humans）
-You can help the community by donating your data to research projects! 详细信息在[Open Humans页面](../SupportingAaps/OpenHumans.md)上有描述。
+您可通过向研究项目捐献数据来助力科研社区！ 详细信息在[Open Humans页面](../SupportingAaps/OpenHumans.md)上有描述。
在“首选项”中，您可以定义何时上传数据。
- 仅在连接到Wi-Fi时
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/SetupWizard.md b/docs/CROWDIN/zh_CN/SettingUpAaps/SetupWizard.md
index 3f1039c9a736..76d6b94f61a4 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/SetupWizard.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/SetupWizard.md
@@ -477,7 +477,7 @@ Nightscout用户应选择**NSClient v3**，除非您需要通过Nightscout网页
-## APS algorithm
+## APS算法
使用OpenAPS SMB算法作为您的APS算法。 尽管功能名称包含"SMB"，但该算法功能将保持禁用状态，直至您完成以下前提条件：熟悉AAPS操作且通过初始目标考核。 与OpenAPS AMA相比，OpenAPS SMB是较新的版本，通常也更好。
diff --git a/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md
index 6aeca540f5b9..79df45afe995 100644
--- a/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md
+++ b/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md
@@ -1,35 +1,35 @@
-# How to help with AAPS
+# 如何为AAPS提供帮助
-## AAPS operates entirely on volunteer efforts and has no paid staff.
+## AAPS完全依靠志愿者运营，无任何付费员工。
-Developers are parents, caregivers, loved ones and people with diabetes working together to development and improve a solution to a very common want. Developers donate their spare time for free, but it's a bit unfair to expect them to face additional costs to make something so amazing open source and free for all.
+开发者群体包括患者家属、照护者、亲友及糖尿病患者本人，他们携手开发并优化这一满足普遍需求的技术方案。 开发者无偿贡献个人时间，但若要求他们额外承担成本来维护这一开源免费的技术成果，实有失公允。
-*To fully test a new rig developers need to have a spare phone and a spare pump as it cannot be used on a human until it is stable. Newer models need testing as they become available. Some of the money donated is needed also for the logistical costs of shipping these supplies across countries to the developers. Sometimes it's also nice to contribute towards the developers costs to leave their darkened rooms and meet each other at conferences and events to let their creative and analytical brains bounce off each other.*
+*开发者需配备备用手机和备用胰岛素泵以完整测试新系统——因其稳定性未经验证前严禁用于人体。 新型设备上市后需及时进行兼容性测试。 部分捐赠资金需用于国际物流费用，以向开发者递送测试设备。 有时，资助开发者走出封闭的工作环境，在会议和活动中交流碰撞创意与专业见解，也是一种值得支持的方式。*
-## I can write code! How do I participate?
+## 我具备编程能力！ 如何参与？
-Yay! Look at the issues, ask in the discord channel, there is always a lot to do! Pick a small task at first and do your first pull request! :)
+太棒了！ 请查阅待解决问题（Issues），并在Discord频道中咨询——总有大量任务待协作！ 建议从简单任务入手，完成您的首次Pull Request（代码提交）！ :)
-## I know the system and can write documentation!
+## 我熟悉系统架构，可参与文档编写工作！
-Great, this is a highly appreciated thing and a good way to pay it forward!
+太棒了！文档贡献是极受社区推崇的回馈方式，您的付出将推动项目持续发展！
-* The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw).
-* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons.
+* 有关Wiki的Discord频道请访问：[AndroidAPS](https://discord.gg/4fQUWHZ4Mw)
+* 英文Wiki的提交操作指南详见：[如何创建PR](../SupportingAaps/HowToEditTheDocs.md) 其他语言版本仅从英文原文翻译而来，出于一致性考虑禁止直接编辑。
-## I do speak multiple languages and want to translate the app or the documentation
+## 我掌握多门语言，愿参与应用程序或文档的翻译工作。
-If you are translating something for the first time, please start with translating the strings for the app, as this is easier and you will get results faster.
+若首次参与翻译，建议从应用程序的字符串资源着手——此类翻译更易上手且见效更快。
-You are welcome to start as a translator for the documentation in parallel or later.
+您也可以同时或后续参与文档翻译工作，我们非常欢迎！
-You can check the state of translations for the languages app and documentation [here](StateOfTranslations).
+您可在此查看应用程序及文档的各语言翻译进度：[链接](StateOfTranslations)
-* If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps).
-* If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs).
+* 如需将**应用程序**翻译为其他语言（感谢您的贡献），请使用[Crowdin](https://crowdin.com/project/androidaps)平台。
+* 如需将**文档**翻译为其他语言（感谢您的贡献），请使用[Crowdin](https://crowdin.com/project/androidapsdocs)平台。
-Just sign up to CROWDIN, click your language, wait for admin authorization and go ahead!
+只需在CROWDIN平台注册，选择目标语言，等待管理员授权后即可开始翻译！
-## Are there other ways to help?
+## 是否还有其他提供帮助的方式？
-Skills needed include graphic design, UX design, translators, wiki editors or simply paying it forward by answering the simple questions in discord & Facebook to allow developers the time and space to focus on the harder stuff.
\ No newline at end of file
+所需技能包括：平面设计、用户体验设计、翻译、Wiki编辑，或通过在Discord和Facebook上解答基础问题来传递互助精神——以此让开发者能专注处理更复杂的技术难题。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md b/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md
index 53cdd9894b78..37e40f9b1762 100644
--- a/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md
+++ b/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md
@@ -1,564 +1,565 @@
-# How to edit the docs
+# 如何编辑文档
-**This description is just for editing the English documentation. All new information must be added in English first. If you want to translate to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs).**
+**本说明仅适用于英文文档的编辑工作。 所有新增内容须优先以英文版本提交。 如需翻译为其他语言（感谢您的贡献），请使用[Crowdin](https://crowdin.com/project/androidapsdocs)平台。**
-For hints how to format text (headline, bold...) and set links please see the ["code syntax"](#code-syntax) section of this page.
+关于文本格式（标题、加粗等）及链接设置的提示，请参阅本页[“代码语法”](#code-syntax)部分。
-## 一般
+## 常规
-For any questions, feedback or new ideas you can contact the documentation team via [discord](https://discord.gg/4fQUWHZ4Mw).
+如有任何疑问、反馈或新想法，您可通过[Discord](https://discord.gg/4fQUWHZ4Mw)联系文档团队。
-At some point it will be suggested that you make a pull request (PR), which is how your changes in the documentation are actually put onto the AAPS webpages, which are stored in GitHub. It's actually not too hard to do a PR and it is a great way to contribute. You are reading this documentation right now because people like you made PRs. Don't worry about making a mistake or somehow editing the wrong documents. Your changes are reviewed before they are merged into the "formal" AAPS documentation repository. You can't mess up the originals through any accidents in the process. The general process is:
+在适当阶段，您需提交Pull Request（PR）——这是将文档变更实际部署至AAPS网页（存储于GitHub）的正式流程。 提交PR（Pull Request）其实并不复杂，这是参与项目贡献的绝佳方式。 您此刻能查阅这份文档，正是源于与您一样的贡献者提交的PR（Pull Request）。 无需担心操作失误或误改文档。 您的修改在合并至AAPS正式文档库前，均会经过严格审核。 在操作过程中，任何意外都不会损坏原始文档。 标准流程如下：
-- Make edits and improvements to code or documentation by editing the existing content.
-- Double-check that your edits look good to you.
-- Make a few notes of what's changed so people may understand the edits.
-- Create a pull request, which asks the administrators to use your changes.
-- They will do a review and either (1)merge your changes, (2)comment back to you about your changes, or (3)start a new document with your changes.
+- 通过修改现有内容，对代码或文档进行编辑与改进。
+- 请仔细核查您的修改内容，确保无误。
+- 简要记录变更内容，便于他人理解修改意图。
+- 创建一个拉取请求，向管理员申请使用你的更改。
+- 他们将进行审核，并选择：(1)合并你的更改，(2)就你的更改给你回复意见，或(3)用你的更改创建新文档。
-(Side note: If you are a visual learner, there is a YouTube video [here](https://youtu.be/4b6tsL0_kzg) showing the PR workflow.)
+（附注：如果你是视觉学习者，[这里](https://youtu.be/4b6tsL0_kzg)有一个YouTube视频展示了拉取请求的工作流程。）
-For our example we are going to make an edit to AndroidAPSdocs. This can be done on any Windows PC, Mac, etc. (any computer with Internet access).
+在我们的示例中，我们将对AndroidAPS文档进行编辑。 这可以在任何Windows电脑、Mac等设备上完成。 （任何可以上网的电脑都能操作）。
-1. Go to and hit Fork in the upper right to make your own copy of the repository.
+1. 访问 并点击右上角的「Fork」按钮，创建该代码库的您个人副本。
-2. Go to any page and navigate to the page you want to edit. You can click on the "Edit in GitHub" link in the upper right corner. This is only possible for English pages.
+2. 访问任意页面，然后导航至您需要编辑的目标页面。 您可以点击右上角的「在 GitHub 上编辑」链接。 此功能仅适用于英文页面。
-Or click the pencil icon that appears in the top bar of the page contents to be edited. You will need to be already logged into your Github account to do this (if you don't have one, they are straightforward to set up).
+或者点击页面内容顶部工具栏中的铅笔图标进行编辑。 执行此操作需已登录您的GitHub账户（若尚未注册，创建流程非常简单）。
-3. One or the other of the options in Step 2 will create a new branch in YOUR repository where your edits will be saved. Make your edits to the file.
+3. 执行步骤2中的任一操作，都将在您的代码库中创建一个新分支，用于保存您的编辑内容。 对文件进行编辑修改。
-We are using markdown for the docs pages. The file have got the suffix ".md".The Markdown specification is not fixed and we use at the moment the myst_parser for our markdown files. Take care to use the correct syntax as [described below](#code-syntax).
+我们的文档页面使用Markdown格式。 这些文件使用".md"后缀。目前我们采用myst_parser解析器来处理Markdown文件（注：Markdown规范并非固定不变）。 请注意使用[下文所述](#code-syntax)的正确语法格式。
-4. You have been working in the "<>Edit file" tab. Select the "Preview changes" tab for a fresh look to make sure everything you changed looks like you meant it to (typos sic.). If you see a needed improvement, go back to the edit tab to make more improvements.
+4. 您当前处于「编辑文件」标签页中进行操作。 请选择「预览更改」标签页进行最终检查，确保所有修改内容符合预期（包括检查拼写错误）。 若发现需要改进之处，请返回编辑标签页继续完善。
-5. When you have finished your edits, scroll to the bottom of the page. In the box at the bottom, provide your comments in the text field that reads, "Add an optional extended description...". The default title has the file name. Try to include a sentence explaining the **reason** for the change. Relating the reason helps reviewers understand what you are attempting to do with the PR.
+5. 完成编辑后，请滚动至页面底部。 在页面底部的文本框中，于显示「添加可选扩展描述...」的输入框内填写您的备注说明。 默认标题会显示文件名。 请尽量包含一句说明**修改原因**的描述。 说明修改原因有助于审核者理解您在该PR中的意图。
-6. Click the green "Propose file changes" or "Commit changes" button. In the page that appears click "Create Pull Request" and again in the next page click "Create Pull Request".
+6. 点击绿色的「Propose file changes」或「Commit changes」按钮。 在跳转页面中点击「Create Pull Request」按钮，然后在下一页再次点击「Create Pull Request」。
-7. That completes the opening of a pull request, PR. GitHub assigns the PR a number, located after the title and a hash mark. Return to this page to check for feedback (or, if you have GitHub notifications emailed to you, you will get emails notifying you of any activity on the PR). The edit will now be in a list of PR's that the team will review and potentially give feedback on before committing to the main documentation for AAPS! If you want to check on the progress of the PR, you can click on the bell logo in the upper right corner of your GitHub account and see all your PRs.
+7. 至此已完成拉取请求（PR）的创建流程。 GitHub会为PR分配一个编号，显示在标题和井号(#)之后。 您可以返回该页面查看反馈（若已设置GitHub邮件通知，相关PR动态将通过邮件提醒您）。 您的编辑现已加入待审PR列表，团队将在合并到AAPS主文档前进行审核并可能提供反馈！ 要查看PR进度，请点击您GitHub账户右上角的铃铛图标，即可查看所有PR状态。
-PS: Your fork and branch will still be sitting on your own personal GitHub account. After you get a notification that your PR has been merged, you can delete your branch if you are done with it (Step 8's notification area will provide a link to delete the branch once it has been closed or merged). For future edits, if you follow this procedure the edits will always start with an updated version of the AndroidAPSdocs repositories. If you choose to use another method to start a PR request (e.g., editing starting from your forked repo's master branch as the starting point), you will need to ensure your repo is up-to-date by performing a "compare" first and merging in any updates that have happened since you last updated your fork. Since people tend to forget to update their repos, we recommend using the PR process outlined above until you get familiar with performing "compares".
+注：您的fork仓库和分支仍会保留在您个人的GitHub账户中。 当收到PR已合并的通知后，如已完成操作，您可以删除分支（步骤8的通知区域会在分支关闭或合并后提供删除链接）。 今后编辑时，只要遵循此流程，您的修改将始终基于最新版的AndroidAPSdocs代码库开始。 若选择其他方式发起PR请求（例如：从您fork仓库的master分支开始编辑），需先执行「compare」操作确保代码库最新，并合并fork后所有更新内容。 鉴于用户常忘记更新代码库，我们建议先采用上述PR流程，待熟悉「compare」操作后再调整。
(edit-the-docs-code-syntax)=
-## Code syntax
+## 代码语法规范
-We are using markdown for the documentation pages. The files have got the suffix ".md".
+我们的文档页面采用Markdown格式编写。 文件使用".md"作为后缀名。
-Markdown is a very simple text formatting language which separates text content from text formatting.
+Markdown是一种非常简单的文本格式化语言，它能将文本内容与格式设置分离。
-The writer only e.g. marks a headline as level 1 headline and the markdown processor generates the necessary HTML code during processing to render the heading in HTML.
+作者仅需将标题标记为一级标题（例如），Markdown处理器就会在渲染过程中自动生成对应的HTML代码来呈现该标题。
-The idea behind this is that
+其核心理念在于
-- the writer should think about the text and not the formatting first,
-- the markdown text is open for exchange between different markdown tools instead of e.g. proprietary tools like Microsoft Windows and
-- you can generate several output formats from one markdown file.
+- 作者应优先考虑文本内容，而非格式设置。
+- Markdown文本可在不同工具间自由交换，无需依赖Microsoft Word等专有软件。
+- 单个Markdown文件可生成多种输出格式。
-Markdown is not a 100% fixed standard and we try to stay as near as possible to the standard, to
+Markdown并非完全固化的标准规范，我们力求最大程度遵循该标准，以便：
-- stay flexible to change markdown tools as needed or forced in the further innovation of markdown tools and markdown SaaS services and
-- enable us to use translation services to translate the English language in a target language like French or German. They can work on markdown but not complex formatting codes, because they can't separate content from layout, which might be fatal.
+- 保持灵活性以便在Markdown工具及SaaS服务的持续创新中，能根据需要或形势要求更换工具。
+- 使我们能够利用翻译服务将英文内容转换为法语、德语等目标语言。 这些工具虽可处理Markdown格式，却无法应对复杂排版代码，因其无法区分内容与版式——这一缺陷可能导致严重后果。
-### Headlines
+### 目录
-- Headline 1: `# headline`
-- Headline 2: `## headline`
-- Headline 3: `### headline`
-- Headline 4: `#### headline`
+- 一级标题：`# 标题文字`
+- 二级标题：`## 标题文字`
+- 三级标题：`### 标题内容`
+- 四级标题：`#### 标题内容`
-We try to avoid further levels of headlines.
+我们尽量避免使用更深层级的标题。
-### Text format
+### 文本格式
-- **bold**: `**text**`
-- *italic*: `*text*`
-- ***bold italic***: `***text***`
+- **加粗**：`**文本**`
+- *斜体*：`*文本*`
+- ***加粗斜体***：`***文本***`
-### Ordered list
+### 有序列表
- 1. first
- 1. second
- 1. third
+ 1. 第一个
+ 2. 第二个
+ 3. 第三个
-1. first
-2. 第二
-3. third
+1. 第一个
+2. 第二个
+3. 第三个
-### Unordered list
+### 无序列表
- - one element
- - another element
- - and another element
+ - 一个元素
+ - 另一个元素
+ - 再一个元素
-- one element
-- another element
-- and another element
+- 一个元素
+- 另一个元素
+- 再一个元素
-### Multi level list
+### 多级列表
-You can insert lists in lists by indenting the next level with 4 more spaces to the right than the one before.
+您可以通过向右缩进4个额外空格的方式，在列表中嵌套子列表。
- 1. first
- 1. second
- 1. third
- 1. one element
- 1. another element
- 1. and another element
- 1. four
- 1. five
- 1. six
+ 1. 第一个
+ 2. 第二个
+ 3. 第三个
+ 1. 一个元素
+ 1. 另一个元素
+ 1. 再一个元素
+ 1. 第四个
+ 1. 第五个
+ 1. 第六个
-1. first
-2. 第二
-3. third
- 1. one element
- 2. another element
- 3. and another element
-4. four
-5. five
-6. six
+1. 第一个
+2. 第二个
+3. 第三个
+ 1. 一个元素
+ 2. 另一个元素
+ 3. 再一个元素
+4. 第四个
+5. 第五个
+6. 第六个
-### Images
+### 图片
-To include images you use this markdown syntax.
+要插入图片，请使用以下Markdown语法：
-- images: ``
+- 图片: ``
-The type of image should be PNG or JPEG.
+图片的类型应为 PNG 或 JPEG。
-Images names should confirm to one of following naming rules. In the example I use png as suffix. In case you use JPEG please use jpeg as a suffix instead.
+图片名称需符合下列命名规则之一： 示例中我使用.png作为文件后缀名。 如果您使用 JPEG，请改用 jpeg 作为后缀。
-- `filename-image-xx.png` where xx is a unique double digit number for the images in this file.
-- `filename-image-xx.png` where xx is a meaning full name for the author of the md file.
+- `文件名-图片-xx.png`（其中xx为此文件中图片的唯一两位数字编号）
+- `文件名-图片-xx.png`（其中xx代表该md文件作者的有意义命名）
-Images are located in the images folder for the english language and propagated to the other languages automatically by Crowdin. You have nothing to do for this!
+图片统一存放在英文版的images文件夹中，并通过Crowdin自动同步至其他语言版本。 您无需对此进行任何操作！
-We are not translating images at the moment: images should contain the **minimum possible text** to allow accessibility to non-English readers.
+我们目前不翻译图片：图片应包含**尽可能少的文字**，以确保非英语读者也能理解。
-(make-a-PR-image-size)= Use a reasonable size for the images which must be readable on PC, tablet and mobiles.
+(make-a-PR-image-size)= 请为图片选择合适尺寸，确保在电脑、平板和手机上都能清晰显示。
-- Screenshots from web pages images should be up to **1050 pixels wide**.
-- Diagrams of process flows should be up to **1050 pixels wide**.
-- Screenshots from the app should be up to **500 pixels wide**. Do not place them side to side if not necessary.
+- 网页截图类图片的宽度应控制在**1050像素**以内。
+- 流程图类图示的宽度应不超过**1050像素**。
+- 应用界面截图的宽度应限制在**500像素**以内。 如非必要，请勿将图片并排排列。
-### Links
+### 链接
-#### External links
+#### 外部链接
-External links are links to external web sites.
+外部链接是指向第三方网站的链接。
-- external link: `[alt text](www.url.tld)`
+- 外部链接: `[文本说明](www.url.tld)`
-#### Internal links to the start of a md file
+#### 内部链接是指向md文件起始位置的链接。
-Internal links to pages are links to the start of a md file which is hosted on our own server.
+内部页面链接是指向我们自有服务器上存放的md文件起始位置的链接。
-- internal link to .md page: `[alt text](../folder/file.md)`
+- 指向 .md 页面的内部链接：`[文本说明](../folder/file.md)`
-#### Internal links to named inline references
+#### 指向命名内联引用的内部链接
-Internal links to named inline references are links to any point in a md file which is hosted on our own server and where a reference was set to link to.
+指向命名锚点的内部链接是指向我们自有服务器上存放的md文件中任何已设置引用标记位置的链接。
-Add a named reference at the location in the target md file you want to jump to.
+在目标md文件中需要跳转的位置添加命名锚点。
`(name-of-my-md-file-this-is-my-fancy-named-reference)=`
-The named reference must be unique in the whole AndroidAPSDocs md files and not only the own md file it resides in!
+命名锚点在整个AndroidAPSDocs的md文件集合中必须保持唯一性，而不仅限于其所在的单个md文件！
-Therefore it is a good practice to start with the filename and then the reference name you select.
+因此，最佳实践是在命名锚点时以文件名开头，再添加您自定义的引用名称。
-Use only lowercase letters and hyphenate words.
+请仅使用小写字母，并用连字符连接单词。
-Then link this reference in the text you are writing with the following kind of link.
+然后在您撰写的文本中，通过以下链接格式引用该锚点：
-- Internal links to named inline references: `[alt text](name-of-my-md-file-this-is-my-fancy-named-reference)`
+- 指向命名内联引用的内部链接：`[文本说明](name-of-my-md-file-this-is-my-fancy-named-reference)`
-### Notes, Warnings, Collapsing Notes
+### 注释、警告、可折叠注释
-You can add notes and warning boxes to documentation.
+您可以在文档中添加注释框和警告框。
-Furthermore you can add collapsing notes for detailed information which would users who are not interested in the details quench to read the text at all. Please use these carefully as the documentation should be as easy to read as possible.
+此外，您可添加可折叠的注释框来包含详细信息，避免不关注细节的用户被迫阅读全部内容。 请谨慎使用这些功能，因为文档应尽可能保持易读性。
#### 备注
- ```{admonition} Note headline
+ ```{admonition} 注释标题
:class: note
- This is a note.
+ 这是一个注释。
+ ```
```
-```{admonition} Note headline :class: note This is a note.
+```{admonition} 注释标题 :class: note 这是一个注释。 ```
-
#### Warnings
+
#### 警告
````
- ```{admonition} Warning
+ ```{admonition} 警告
:class: warning
- This is a warning.
+ 这是一个警告。
- ```{admonition} Warning headline
+ ```{admonition} 警告标题
:class: warning
- This is a warning.
+ 这是一个警告。
```
- #### Collapsing Notes
+ #### 可折叠注释
- {admonition} further detailed readings for interested readers
+ {admonition} 为感兴趣的读者提供的延伸阅读材料
:class: dropdown
- This admonition has been collapsed,
- meaning you can add longer form content here,
- without it taking up too much space on the page.
+ 该折叠式提示框已收起，
+ 意味着您可以在此添加详细内容，
+ 而不会占用页面过多空间。
````
-```{admonition} further detailed readings for interested readers :class: dropdown This admonition has been collapsed, meaning you can add longer form content here, without it taking up too much space on the page.
+```{admonition} 为感兴趣的读者提供的延伸阅读材料 :class: dropdown 该折叠式提示框已收起， 意味着您可以在此添加详细内容， 而不会占用页面过多空间。
```
-## Tables
+## 表格
-Avoid using tables with long texts as the contents is difficult to set in Markdown, they will usually not fit in a mobile phone screen width, and probably won't display the same after translation.
+请避免使用包含长文本的表格，因为Markdown格式难以精确控制表格内容排版，通常无法适配手机屏幕宽度，翻译后可能出现显示异常。
-## Style Guide
+## 风格指南
-### Contents
+### 内容
-1. English language writing tips
+1. 英语写作技巧
-2. AAPS-specific writing notes
+2. AAPS特定写作规范说明
-3. Useful references
+3. 实用参考资料
-###  1\. English language writing tips
+###  1\. 英语写作技巧
-#### Use language that is appropriate for the reader
+#### 使用适合读者群体的语言
-Use plain English wherever possible. This helps non-native readers and also aids translation of AAPS documents into other languages. Write in a conversational way with the user, imagine you are sitting across the desk from the person you are writing for. Remember - most AAPS users do not have programming backgrounds. Diabetes itself also has a lot of jargon and abbreviations. Bear in mind that some people may be recently diagnosed, may not be as experienced as you with diabetes, or may have been given different diabetes training. If you use shorthand or an abbreviation, write it out in full the first time you use it, giving the abbreviation directly after it in brackets, like “super micro bolus (SMB)”. Also, link to the glossary. Technical terms which might not be familiar to the reader can be also be added in brackets.
+尽可能使用简明英语. 这既有助于非英语母语读者理解，也方便将AAPS文档翻译成其他语言。 请采用与用户对话式的写作风格，想象您正面对面为您要服务的对象撰写内容。 请注意：大多数AAPS用户并不具备编程背景。 糖尿病领域本身也存在大量专业术语和缩写。 请谨记：部分读者可能是刚确诊的患者，糖尿病经验可能不如您丰富，或接受过不同的糖尿病培训方案。 若使用简称或缩写，首次出现时应完整拼写，并在括号内直接标注缩写形式，例如："超微大剂量（Super Micro Bolus，SMB）"。 同时，请附上术语表链接。 对于读者可能不熟悉的技术术语，也可在括号内补充说明。
-Instead of: *“What causes high postprandial BG peaks in closed loop?"*
+避免的说法：*"闭环系统中餐后血糖峰值升高的原因是什么？"*
-Use: *“What causes a high BG peak **after lunch** (postprandial) in closed loop?"*
+建议的说法：*"闭环系统中**午餐后**（postprandial）出现高血糖峰值的原因是什么？"*
-##### Use plain words that everyone can understand
+##### 使用通俗易懂的词汇，确保所有人都能理解。
-Find an A-Z of alternative words to make your writing easier to understand here:
+您可以在此处查阅A-Z替代词表，让您的写作更易懂：
-#### Privacy/licensing concerns:
+#### 隐私/许可问题：
-Particularly if you record video or screenshots, make sure not to disclose your private details (API key, passwords). Make sure YouTube content is not openly listed, and needs a link from the documentation to view. Avoid drawing attention to infringed copyrighted materials (BYODA etc).
+特别提醒：若需录制视频或截图，请务必避免泄露您的隐私信息（如API密钥、密码等）。 请确保YouTube内容不公开列出，且必须通过文档中的链接才能访问。 请避免提及可能侵权的版权材料（如BYODA等）。
-#### Keep sentences short, get to the point
+#### 保持句子简短，直击要点。
-- Clear writing should have an average sentence length of 15 to 20 words.
+- 清晰的写作应保持15-20个单词的平均句长。
-- This does not mean making every sentence the same length. Be punchy. Vary your writing by mixing short sentences (like the last one) with longer ones (like this one).
+- 这并不意味着每句话都必须保持相同长度。 要简洁有力。 通过混合短句（如前句）与长句（如本句）来变化写作风格。
-- Stick to one main idea in a sentence, plus perhaps one other related point.
+- 每句话应围绕一个核心观点展开，最多可附带一个相关要点。
-- You may still find yourself writing the odd long sentence, especially when trying to explain a complicated point. But most long sentences can be broken up in some way.
+- 您可能仍会偶尔写出较长的句子，尤其是在解释复杂观点时。 但大多数长句都可以通过某种方式拆分。
-- Remove weak words: “you can”, “there is/are/were”, “in order to”.
+- 删除弱势表达："you can"、"there is/are/were"、"in order to"。
-- Place keywords near the beginning of titles, sentences and paragraphs.
+- 将关键词置于标题、句子和段落的开头位置。
-- Be visual! Wherever possible provide a brief diagram, screenshot or video.
+- 善用视觉化表达！ 在可行的情况下，尽量提供简图、截图或视频说明。
-#### Don't be afraid to give instructions
+#### 无需回避直接给出操作指引
-Commands are the fastest way to give instructions, but writers sometimes fear giving commands, writing “you should do this” instead of just “do this”. Perhaps people worry that commands sound too harsh. You can often solve this by putting the word 'please' in front. However, if something must be done, it is best not to say ‘please’ as it gives the reader the option to refuse.
+命令式是最快捷的指令表达方式，但撰写者往往顾虑使用命令语气，常以"您应执行此操作"替代简洁的"执行此操作"。 或许人们担心命令式语气显得过于生硬。 通常只需在句首添加"请"字即可解决此问题。 但若某项操作必须执行，则不宜使用"请"字，以免让读者误以为可选择拒绝。
-Instead of: *“You should just think of it as a complete statement."*
+避免的说法：*"应将其视为完整声明。"*
-Use: *“Think of it as a complete statement.”*
+请使用：*"将其视为完整声明。"*
-#### Mostly use active verbs, rather than passive verbs
+#### 应优先使用主动语态动词，而非被动语态。
-Example of an **active verb**:
+**主动语态动词**示例：
-- *“The pump (subject) delivers (verb) the insulin (object).”*
+- *"泵（主语）输送（动词）胰岛素（宾语）。"*
-“delivers” is an active verb here. The sentence says what is doing the delivering before it says what is being delivered.
+"delivers"在此处为主动语态动词。 该句子先说明执行输送动作的主体，再说明被输送的对象。
-Example of a **passive verb**:
+**被动语态动词**示例：
-- *“The insulin (subject) is delivered (verb) by the pump (object)”*
+- *"胰岛素（主语）由泵（宾语）输送（动词）"*
-*“delivered”* a passive verb here. The subject and object are switched around, compared to the active verb sentence. We have had to make the sentence longer by introducing “is” and “by the”. Also consider starting with the active verb.
+*"delivered"*在此处为被动语态动词。 与主动语态句子相比，主语和宾语的位置互换了。 我们不得不通过添加"is"和"by the"使句子变长。 亦可考虑以主动语态动词开头。
-Instead of: *“You can connect your pump with the phone through the AAPS pump menu, and there are a number of pumps available for you to connect with.”*
+避免的说法：*“通过AAPS泵菜单将泵与手机连接，可选多种兼容泵型号。”*
-Use: *“Connect your desired pump to the phone through the AAPS pump menu.”*
+建议的说法：*"通过AAPS泵菜单将所需泵设备连接至手机。"*
-Passive verbs can cause problems:
+被动语态动词可能导致问题：
-- They can be confusing.
+- 它们可能会令人困惑。
-- They often make writing more long-winded.
+- 它们通常会使写作更加冗长。
-- They make writing less lively.
+- 它们会使写作不那么生动。
-##### Good uses of passives
+##### 被动语态动词的良好用法
-There are times when it might be appropriate to use a passive.
+某些情况下使用被动语态可能更为合适。
-- To make something less hostile - 'this bill has not been paid' (passive) is softer than 'you have not paid this bill' (active).
+- 使用被动语态可缓和语气——"账单未付"（被动式）比"您未支付账单"（主动式）更委婉。
-- To avoid taking the blame - 'a mistake was made' (passive) rather than 'You made a mistake' (active).
+- 使用被动语态可规避归责——"操作中出现失误"（被动式）比"您操作失误"（主动式）更显中立。
-- When you don't know who or what the doer is - 'the England team has been picked'.
+- 当动作执行者未知时——"英格兰队已选定"（被动式）。
-- If it simply sounds better.
+- 若被动语态的表达效果更佳时。
-#### Avoid nominalisations
+#### 避免名词化结构
-A nominalisation is the name of something that isn't a physical object, such as a process, technique or emotion. Nominalizations are formed from verbs.
+名词化（nominalisation）指对非实体事物（如过程、技术或情感）的命名形式。 名词化结构由动词派生而成。
For example:
-| Verb | Nominalization |
-| --------- | -------------- |
-| 完成 | completion |
-| introduce | introduction |
-| provide | provision |
-| fail | failure |
+| 动词 | 名词化 |
+| --------- | ------------ |
+| complete | completion |
+| introduce | introduction |
+| provide | provision |
+| fail | failure |
-They are often used **instead** of the verbs they come from, but they can sound as if nothing is actually happening. Too many of them can make writing very dull and heavy-going.
+名词化结构常**替代**其源动词使用，但会导致表述缺乏动态感。 过度使用名词化会使文风沉闷艰涩。
-Instead of: *“The implementation of the method has been done by a team.”*
+避免的说法：*"The implementation of the method has been done by a team。"*
-Use: *“A team has implemented the method.”*
+建议的说法：*"A team has implemented the method.”"*
-#### Use lists where appropriate
+#### 在适当的地方使用列表
-Lists are excellent for splitting information up. There are two main types of list:
+列表能有效拆分信息，提升可读性。 列表主要有两种类型：
-- A continuous sentence with several listed points picked out at the beginning, middle or end.
+- 一种连续句式，在句首、句中或句末标注多个列举项。
-- Separate bullet points with an introductory statement.
+- 使用引导性陈述分隔项目符号列表。
-In the bulleted list above, each point is a complete sentence so they each start with a capital letter and end with a full stop. Use bullet points rather than numbers or letters, as they draw your attention to each point without giving you extra information to take in.
+在上述项目符号列表中，每个条目均为完整句子，因此需首字母大写并以句号结尾。 建议使用项目符号（而非数字或字母），因其能突显每个要点，且不会增加额外信息负担。
-#### Mythbusting
+#### 破除迷思
-- You can start a sentence with **and, but, because, so or however**.
+- 句子可以**以"而且"、"但是"、"因为"、"所以"或"然而"**开头。
-- You can split infinitives. So you can say **“to boldly go”**.
+- 可以使用分裂不定式。 所以您可以说 **“to boldly go”**。
-- You can end a sentence with a preposition. In fact, it is something **we should stand up for**.
+- 句子可以用介词结尾。 事实上，这正是**我们应当支持**的做法。
-- And **you** can use the same **word** twice in a sentence if **you** can't find a better **word**.
+- 若**你**找不到更合适的**词**，**你**完全可以在句中重复使用同一个**词**。
-#### Optimizing writing style by purpose
+#### 基于写作目的优化写作风格
-To keep the documentation clear and short, we write different sections of the documentation in different styles.
+为确保文档简洁清晰，我们采用差异化风格撰写不同章节。
-An “explanation” style is used for the introduction, background and knowledge development sections.
+在引言、背景和知识发展部分采用"解释性"写作风格。
-A “How-to-guide” style (with minimal explanation) is used for building, configuring AAPS, and some of the troubleshooting sections.
+在构建、配置AAPS以及部分故障排除章节中，采用"操作指南"式写作风格（仅提供必要说明）。
-A tutorial helps the pupil acquire basic competence. The user will **learn by doing**.
+教程帮助学习者掌握基础能力。 用户将通过**实践学习**掌握技能。
-
+
-#####  Tutorials (e.g. teaching a kid to beat egg whites)
+#####  教程类内容（例如教孩子打发蛋白）
-- narrator directly talks to the reader: In this tutorial **you** will (we) could be used to convey “we are in this together” frame-of-thought in some rare cases
+- 叙述者直接与读者对话："本教程中**您**将..."（少数情况下可用"我们"体现共同参与感）
-- Future Tense -> to show the final target
+- 将来时态 → 用于表示最终目标
-- Imperative Tense -> to do the tasks -> Concrete steps - avoid abstract concepts
+- 祈使语气 → 用于执行任务 → 具体步骤 - 避免抽象概念
-- Past Tense -> to show accomplished tasks -> Quick and immediate visible results
+- 过去时态 → 用于展示已完成任务 → 快速可见的成果
-- Minimum Explanations -> strict necessary to complete the task - **what and why**
+- 最少解释 → 仅保留完成任务所需的必要说明 → **操作事项及原因**
-- Ignore options/alternatives/…. No ambiguity
+- 忽略选项/替代方案/... 无歧义
-- Step Transitions: finish a step with a sentence leading to the next step as a logical progression flow. Example: *You have now installed the Let’s Encrypt client, but before obtaining certificates, you need to make sure that all required ports are open. To do this, you will update your firewall settings in the next step.*
+- 步骤过渡：通过逻辑递进语句衔接步骤，当前步骤收尾句需自然引导至下一步。 示例： *您已完成Let's Encrypt客户端安装，但在获取证书前，需确保所有必要端口均已开放。 为此，您将在下一步更新防火墙设置。*
-- **Tutorial** Title (Level 1 heading)
+- **教程** 标题（一级标题）
-- Introduction (no heading)
+- 简介（无标题）
-- Prerequisites (Level 2 heading)
+- 先决条件（2 级标题）
-- Steps:
+- 步骤：
-- Step 1 — Doing the First Thing (Level 2 heading)
+- 步骤 1 — 做第一件事（2 级标题）
-- Step 2 — Doing the Next Thing (Level 2 heading)
+- 步骤 2 — 做下一件事（2 级标题）
-- Step n — Doing the Last Thing (Level 2 heading)
+- 步骤 n — 做最后一件事（2 级标题）
-- Conclusion (Level 2 heading)
+- 结论（2 级标题）
- - **The Language of Tutorials**
+ - **教程的语言**
- *In this tutorial, you will…*
+ *在本教程中，您将...*
- Describe what the learner will accomplish (note - not: “you will learn…”).
+ 描述学习者将完成什么（注意 - 而不是：“您将学习...”）。
- *First, do x. Now, do y. Now that you have done y, do z.*
+ *首先，做 x。 现在，做 y。 既然您已经做了 y，就做 z。*
- No room for ambiguity or doubt.
+ 不留任何含糊或怀疑的余地。
- *We must always do x before we do y because… (see Explanation for more details).*
+ *我们必须总是在做 y 之前做 x，因为...（有关更多详细信息，请参见解释）。*
- Provide minimal explanation of actions in the most basic language possible. Link to more detailed explanation.
+ 用最基础的语言简要说明操作步骤。 查看详细说明的链接。
- *The output should look something like this…*
+ *输出结果应类似如下形式...*
- Give your learner clear expectations.
+ 为学习者设定明确预期。
- *Notice that… Remember that…*
+ *注意... 记住...*
- Give your learner plenty of clues to help confirm they are on the right track and orient themselves.
+ 为学习者提供充分线索，帮助其确认进展正确并自主定位。
- *You have built a secure, three-layer hylomorphic stasis engine…*
+ *您已成功构建一个安全的三层同态静滞引擎...*
- Describe (and admire, in a mild way) what your learner has accomplished (note - not: “you have learned…”)
+ 描述（并适度赞赏）学习者已完成的成果（注：避免使用"你已学会…"表述）
-#####  How-To Guides (e.g. a recipe)
+#####  操作指南（如食谱类教程）
-A how-to guide’s purpose is to help the already-competent user perform a particular task correctly.
+操作指南的核心用途，是帮助已具备基础能力的用户正确完成特定任务。
-- HOW-to
+- 如何操作（HOW-to）
-- narrator directly talks to the reader: In this tutorial **you** will
+- 叙述者直接与读者对话：在本教程中，**您**将
-- Future Tense -> to show the final target
+- 将来时态 → 用于表示最终目标
-- Conditional Imperative Tense -> to get X do y -> Concrete steps - avoid abstract concepts
+- 条件祈使式 → 要获取X需执行Y → 具体步骤（避免抽象概念）
-- Minimum Explanations -> strict necessary to complete the task -> **what and why**
+- 最少解释 → 仅限完成任务的关键说明 → **操作事项及原因**
-- Ignore options/alternatives/…. No ambiguity, but you can link to the reference entry or explanation entry
+- 忽略选项/替代方案/... 表述必须明确，但可链接至参考条目或解释条目
-- **How-to**: Title (Level 1 heading)
+- **操作指南**：标题（1 级标题）
-- Introduction paragraph
+- 引言段落
-- Optional Prerequisites (paragraph or Level 2 heading if more than 1)
+- 可选先决条件（若多于一项则设为二级标题）
-- Steps:
+- 步骤：
-- Step 1 — Doing the First Thing (Level 2 heading)
+- 步骤 1 — 做第一件事（2 级标题）
-- Step 2 — Doing the Next Thing (Level 2 heading)
+- 步骤 2 — 做下一件事（2 级标题）
-- Step n — Doing the Last Thing (Level 2 heading)
+- 步骤 n — 做最后一件事（2 级标题）
-- Conclusion paragraph
+- 结论段落
- - **The Language of How-To Guides**
+ - **操作指南的语言规范**
- *This guide shows you how to…*
+ *本指南向您展示如何...*
- Describe clearly the problem or task that the guide shows the user how to solve.
+ 清晰描述该指南要帮助用户解决的问题或任务.
- *If you want x, do y. To achieve w, do z.*
+ *如果您想要 x，请执行 y。 要实现 w，请执行 z。*
- Use conditional imperatives.
+ 使用条件祈使句。
- *Refer to the x reference guide for a full list of options.*
+ *完整选项列表请参阅《X参考指南》。*
- Don’t pollute your practical how-to guide with every possible thing the user might do related to x.
+ 避免在实用操作指南中混杂所有与X相关的可能操作。
-#####  Explanation (e.g. Science behind why egg whites stiffen when you beat them)
+#####  原理解释（例：蛋清打发变硬的科学原理）
-An explanation clarifies, deepens and broadens the reader’s understanding of a subject.
+原理解释旨在阐明、深化并拓宽读者对主题的认知。
-- WHY
+- 为什么
-- Start with **About**
+- 以**关于**开头
-- Provide context, link ALL relevant references
+- 提供背景说明，并链接所有相关参考文献。
-- Discuss options/alternatives
+- 讨论备选方案/替代方案
-- Don’t instruct or provide reference (link to them)
+- 请勿直接指导或提供参考（仅链接至相关内容）
-- State the unknown/moving targets etc…
+- 声明未知变量/动态目标等...
-- **About** Title (Level 1 heading)
+- **关于**标题（1 级标题）
-- Introduction (no heading)
+- 简介（无标题）
-- Optional Prerequisites (Level 2 heading)
+- 可选先决条件（2 级标题）
-- Subtopic 1 (level 2 heading)
+- 副主题 1（2 级标题）
-- Conclusion (Level 2 heading)
+- 结论（2 级标题）
- - **The Language of Explanation**
+ - **解释性语言的表达体系**
- *The reason for x is because historically, y…*
+ *X的成因可追溯至历史上Y...*
- Explain.
+ 解释。
- *W is better than z, because…*
+ *W 比 z 好，因为...*
- Offer judgements and even opinions where appropriate..
+ 在适当情况下提供判断乃至观点…
- *An x in system y is analogous to a w in system z. However…*
+ *Y系统中的X组件，其功能类似于Z系统中的W组件。 然而...*
- Provide context that helps the reader.
+ 提供有助于读者理解的背景信息。
- *Some users prefer w (because z). This can be a good approach, but…*
+ *部分用户更倾向选择W方案（原因：Z）。 此方案虽具可行性，但需注意...*
- Weigh up alternatives.
+ 权衡备选方案。
- *An x interacts with a y as follows:…*
+ *X与Y的交互机制如下：...*
- Unfold the machinery’s internal secrets, to help understand why something does what it does.
+ 揭示系统内部机制，帮助理解其运作原理。
-### 2\. AAPS-specific writing/updating notes
+### 2\. AAPS专用写作/更新说明
-#### Author & Editor
+#### 作者与编辑
-For writing/updating the AAPS documentation, consider the process as consisting of two stages. These can be carried out by the same person at different points, or more than one person.
+在撰写/更新AAPS文档时，建议将流程分为两个阶段。 可由同一人在不同时间点执行，也可由多人协作完成。
-An **author (e.g. you!)** writes/edits a section of the documentation in a concise conversational tone, then passes it to the editor.
+**作者（例如您！）**以简洁对话体撰写/编辑文档章节，完成后移交编辑。
-The **editor (e.g. a fellow AAPS user, or the person who receives the pull request)** reviews adherence to the style guide, edits the section for clarity and accessibility, removing as many words as possible (especially for tutorial/how-to sections). Reading the text out loud may help.
+**编辑（例如AAPS其他用户，或接收Pull Request的人员）**负责审核是否符合格式规范，优化章节的清晰度和可读性，并尽可能精简文字（特别是教程/操作指南类内容）。 朗读文本可能有助于发现问题。
-#### General AAPS points
+#### AAPS通用要点
-- For glucose values, state both mg/dl and mmol/l in each occurrence (also consider this for screenshots, if possible).
+- 血糖值需同时标注毫克/分升（mg/dl）和毫摩尔/升（mmol/l）（如有可能，截图也应遵循此规则）。
-- For consistency, use “AAPS” rather than “Android APS”.
+- 为保持统一性，请使用"AAPS"而非"Android APS"。
-- Clearly state the version of Android Studio/AAPS you are writing for, or that the screenshots are taken from.
+- 请明确标注编写所针对的Android Studio/AAPS版本号，或注明截图来源版本。
-### 3\. Useful References
+### 3\. 实用参考文献
diff --git a/docs/CROWDIN/zh_CN/SupportingAaps/OpenHumans.md b/docs/CROWDIN/zh_CN/SupportingAaps/OpenHumans.md
index a95be4088c73..077a5d2a8eb9 100644
--- a/docs/CROWDIN/zh_CN/SupportingAaps/OpenHumans.md
+++ b/docs/CROWDIN/zh_CN/SupportingAaps/OpenHumans.md
@@ -1,85 +1,85 @@
-# Open Humans Uploader
+# Open Humans 数据上传器
-## Donate your data for science
+## 为科研捐献您的数据
-You can help the community by donating your data to research projects! This helps scientists to pay it forward, develop new scientific ideas and broaden the open mind of open source closed loop systems. AAPS is ready to synchronize your data with [Open Humans](https://www.openhumans.org), a platform allowing you to upload, connect, and store your personal data – such as genetics, activity and health data.
+您可通过向研究项目捐献数据来助力科研社区！ 此举能助力科学家持续推动科研发展、孕育新科学理念，并拓展开源闭环系统的开放思维。 AAPS已支持与[Open Humans](https://www.openhumans.org)平台同步数据，该平台允许您上传、关联并存储个人数据（包括基因、活动及健康数据等）。
-You retain full control about what happens to your data and what projects you want to support by giving them access to your data. Depending on the project you have joined, data is evaluated and used by them in different ways and extent.
+您始终拥有数据的完全控制权，可自主决定支持哪些研究项目并授予其数据访问权限。 根据您参与的具体项目，数据会以不同方式和程度被分析使用。
-The following data will be uploaded to your Open Humans account:
+以下数据将被上传至您的Open Humans账户：
- 血糖值
-- Careportal events (except notes)
+- Careportal事件（除备注外）
- 扩展大剂量(方波)
-- Profile switches
-- Total daily doses
-- Temporary basals
-- Temp targets
-- Preferences
-- Application version
-- Device model
-- Screen dimensions
+- 配置文件切换
+- 每日总剂量
+- 临时基础率
+- 临时目标
+- 偏好设置
+- 应用版本
+- 设备型号
+- 屏幕尺寸
-Secret or private information such as your Nightscout URL or API secret will not be uploaded.
+秘密或私人信息（如 Nightscout URL 或 API 密钥）不会被上传。
## 设置
-1. Create your account on [Open Humans](https://www.openhumans.org) if not already done. You can reuse your existing Google or Facebook accounts if you wish to.
-2. Enable the “Open Humans” plugin in [Config Builder > Synchronization](../SettingUpAaps/ConfigBuilder.md).
-3. Open its setting using the cog wheel button. You can restrict upload to times when phone uses Wi-Fi and/or is charged.
-4. Open the Open Humans Plugin (either through OH tab or hamburger menu) and click 'LOGIN'.
+1. 如果尚未注册，请先在 [Open Humans](https://www.openhumans.org) 创建账户。 您可以选择复用现有的 Google 或 Facebook 账户。
+2. 在 [配置生成器 > 同步](../SettingUpAaps/ConfigBuilder.md) 中启用 "Open Humans" 插件。
+3. 通过齿轮按钮打开设置。 您可以限制仅在手机使用 Wi-Fi 和/或充电时上传。
+4. 打开 Open Humans 插件（通过 OH 标签页或汉堡菜单），点击 '登录'。
-5. Read the given information about the Open Humans Uploader and terms of use carefully.
-6. Confirm by checking the box and click 'LOGIN'.
-7. Open Humans website will be opened. Login with your credentials.
-8. Decide whether you want to hide your AAPS Uploader membership in your public Open Humans profile.
-9. Click button 'Authorize project'.
+5. 仔细阅读关于 Open Humans 上传器的说明和使用条款。
+6. 通过勾选框确认并点击“LOGIN”。
+7. 将打开 Open Humans 网站。 使用您的账户凭证登录。
+8. 选择是否要在公开的 Open Humans 个人资料中隐藏您的 AAPS 上传器成员身份。
+9. 点击 '授权项目' 按钮。
-10. Returning to AAPS you will see a prompt that login succeeded.
-11. Keep Open Humans Uploader plugin and phone turned on for setup to complete.
-12. After clicking close you will see your member ID. Queue sizes > 0 shows that there is still data to be uploaded.
-13. Click 'LOGOUT' if you want to stop uploading data to Open Humans.
-14. Android notification will inform you about running upload.
+10. 返回 AAPS 后，您将看到登录成功的提示。
+11. 保持 Open Humans 上传器插件和手机开启以完成设置。
+12. 点击关闭后，您将看到成员 ID。 队列大小 > 0 表示仍有待上传数据。
+13. 点击 '退出登录' 可停止向 Open Humans 上传数据。
+14. Android 通知将提示上传运行状态。
-15. You can manage your data by logging in to the [Open Humans website](https://www.openhumans.org).
+15. 您可以通过登录 [Open Humans 网站](https://www.openhumans.org) 管理数据。
-## Sharing Opportunities
+## 分享机会
-### [The 'OPEN' project](https://www.open-diabetes.eu/)
+### ["OPEN" 项目](https://www.open-diabetes.eu/)
-The 'OPEN' project brings together an international and intersectoral consortium of patient innovators, clinicians, social scientists, computer scientists and patient advocacy organizations in order to investigate various aspects of Do-it-Yourself Artificial Pancreas Systems (DIY APS) that are used by an increasing number of people with diabetes. For more details see their [website](https://www.open-diabetes.eu/).
+"OPEN" 项目汇集了患者创新者、临床医生、社会科学家、计算机科学家和患者倡导组织的国际跨部门联盟，旨在研究越来越多糖尿病患者使用的 DIY 人工胰腺系统（DIY APS）的各个方面。 详情请见其[网站](https://www.open-diabetes.eu/)。
-September 2020 the 'OPEN' project launched a [survey](https://survey.open-diabetes.eu/) including the option to donate data you uploaded to Open Humans. A [tutorial](https://open-diabetes.eu/en/open-survey/survey-tutorials/) how to donate your data to the 'OPEN' project is available on their site and within the survey itself.
+2020 年 9 月，"OPEN" 项目启动了包含数据捐赠选项的[调查](https://survey.open-diabetes.eu/)。 其网站和调查内提供了如何向"OPEN" 项目捐赠数据的[教程](https://open-diabetes.eu/en/open-survey/survey-tutorials/)。
-### [OpenAPS Data Commons](https://www.openhumans.org/activity/openaps-data-commons/)
+### [OpenAPS 数据共享库](https://www.openhumans.org/activity/openaps-data-commons/)
-The OpenAPS Data Commons was created to enable a simple way to share data sets from the DIYAPS community for research. The data is shared both with traditional researchers who will create traditional research studies, and with groups or individuals from the community who want to review data as part of their own research projects. The OpenAPS Data Commons uses the 'Open Humans' platform to enable people to easily upload and share their data from DIYAPS including AAPS, Loop, and OpenAPS.
+OpenAPS 数据共享库旨在为 DIYAPS 社区提供简便的数据共享方式用于研究。 数据既可与创建传统研究项目的传统研究人员共享，也可与希望审查数据用于自身研究项目的社区团体或个人共享。 该库使用 "Open Humans" 平台来支持用户轻松上传和共享来自 AAPS、Loop 和 OpenAPS 等 DIYAPS 系统的数据。
-You can get your data into Open Humans via one of three ways:
+您可通过三种方式将数据导入 Open Humans：
-1. use the AAPS uploader option to get your data into Open Humans
-2. use the Nightscout Data Transfer to get your data into Open Humans
-3. manually upload data files into Open Humans.
+1. 使用AAPS数据上传器功能将您的数据导入Open Humans平台
+2. 使用Nightscout数据传输功能将您的数据导入Open Humans平台
+3. 手动将数据文件上传至Open Humans平台
-Once you've created an account and gotten your data flowing into Open Humans, make sure to also join the OpenAPS Data Commons in order to donate your data for research if you choose.
+创建账户并完成数据导入Open Humans后，请务必加入OpenAPS数据共享计划，以便在您同意的情况下捐献数据供研究使用。
-## Terms of Use
+## 使用条款
-This is an open source tool that will copy your data to [Open Humans](https://www.openhumans.org). We retain no rights to share your data with third parties without your explicit authorization. The data the project and app receive are identified via a random user ID and will only be securely transmitted to an Open Humans account with your authorization of that process. You can stop uploading and delete your upload data at any time via [www.openhumans.org](https://www.openhumans.org). Beware that some projects that receive data may not support this.
+这是一个将您的数据复制到 [Open Humans](https://www.openhumans.org) 的开源工具。 我们无权在未经您明确授权的情况下与第三方共享数据。 项目和应用通过随机用户 ID 识别数据，仅在您授权后安全传输至 Open Humans 账户。 您可随时通过 [www.openhumans.org](https://www.openhumans.org) 停止上传并删除数据。 请注意某些接收数据的项目可能不支持此操作。
-Also see [Open Humans Terms of Use](https://www.openhumans.org/terms/).
+另见 [Open Humans 使用条款](https://www.openhumans.org/terms/)。
-## Data Privacy
+## 数据隐私
-Open Humans takes care of protecting your privacy by assigning a numerical ID to you for each project. This allows projects to recognize but no identify you. The Application ID uploaded by AAPS is similar and only helps administrate the data. More information can be found here:
+Open Humans 通过为每个项目分配数字 ID 来保护隐私。 这使得项目能识别但无法确认您的身份。 AAPS 上传的应用 ID 类似，仅用于数据管理。 更多信息请参考：
-- [Open Humans Data Use Policy](https://www.openhumans.org/data-use/)
+- [Open Humans 数据使用政策](https://www.openhumans.org/data-use/)
- [Open Humans GDPR](https://www.openhumans.org/gdpr/)
diff --git a/docs/CROWDIN/zh_CN/SupportingAaps/StateOfTranslations.md b/docs/CROWDIN/zh_CN/SupportingAaps/StateOfTranslations.md
index 017f3d3b216e..b0818661fd49 100644
--- a/docs/CROWDIN/zh_CN/SupportingAaps/StateOfTranslations.md
+++ b/docs/CROWDIN/zh_CN/SupportingAaps/StateOfTranslations.md
@@ -1,26 +1,26 @@
-# state of translation for app and the documentation
+# 应用程序及文档的翻译状态
-The state is once per hour updated and reflects only the state in Crowdin.
+该状态每小时更新一次，且仅反映Crowdin平台中的翻译进度。
```{tip}
-Be careful the percentage of proofreading must be lower then the percentage of translations but they decided to show it on top of the translations.
-It's better to look only at the percentage level of translations to see if work is to be done.
+请注意：校对完成度必须低于翻译进度，但系统设计将其显示在翻译进度上方。
+建议仅关注翻译进度百分比来判断剩余工作量。
```
```{admonition} needed time for final publication
-After Crowdin translation a sync to Github is scheduled every day to transfer translations to Github as pull request (PR).
+Crowdin翻译完成后，系统每日定时同步至GitHub，通过拉取请求（PR）提交翻译内容。
-The acceptance of the PR is a manual task which will be done es fast as possible.
+PR的审核验收为人工操作，我们将尽快处理。
```
-## state app translation
+## 应用程序翻译状态
-State of the **app** translations per language (country code, percentage translation, percentage proofreading).
+**应用程序**各语言翻译状态（国家代码、翻译进度百分比、校对进度百分比）。
-
+
-## state documentation translation
+## 文档翻译状态
-State of the **documentation** translations per language (country code, percentage translation, percentage proofreading).
+**文档**各语言翻译状态（国家代码、翻译进度百分比、校对进度百分比）。
-
+
diff --git a/docs/CROWDIN/zh_CN/SupportingAaps/Translations.md b/docs/CROWDIN/zh_CN/SupportingAaps/Translations.md
index 6e1bb0c6a2b5..3ff3e68fcea2 100644
--- a/docs/CROWDIN/zh_CN/SupportingAaps/Translations.md
+++ b/docs/CROWDIN/zh_CN/SupportingAaps/Translations.md
@@ -1,104 +1,102 @@
-# How to translate strings for the AAPS app or the documentation
+# AAPS应用及文档翻译指南
-* For the the strings used in the app go to and login using your GitHub account
-* For the documentation please visit and login using your GitHub account
+* 如需翻译应用内字符串，请访问 并使用您的GitHub 账户登录。
+* 文档翻译请访问 并使用您的GitHub 账户登录。
-* Send a join request to the docs team. To do so click on the flag of the desired language and then the button "Join" on the top right corner of the next page. Please specify language, give some information about you and your AAPS experience and if you want to be a translator or proofreader (only people skilled in translating + advanced AAPS users).
+* 请发送加入文档团队的申请。 操作步骤：点击目标语言国旗图标 → 在下一页右上角点击"加入"按钮。 请注明语言、提供您的个人简介及AAPS使用经验，并说明申请译者或校对员（需具备翻译技能+AAPS高级用户资质）。
-```{admonition} Time for Approval :class: note
+```{admonition} 审批时间 :class: note
-The approval is a manual step. As non profit organization we don't provide SLAs but in general the approval will be done in < 1 day. If not please contact the Doc team via Facebook or Discord.
+审批为人工操作流程。 作为非营利组织，我们虽不提供SLA服务协议，但通常会在1个工作日内完成审批。 如未收到，请通过Facebook或Discord联系文档团队。
-
* When we approve you, click the flag
- 
+
* 当您的申请获批后，请点击国旗图标
+ 
- ## Translation of the app
+ ## 应用翻译
(translations-translate-strings-for-AAPS-app)=
- ### Translate strings for AAPS app
-
- * If you have no preference for strings you translate just select the "Translate All" button to start. It will show you the strings which need translation.
+ ### 翻译AAPS应用字符串
+ * 若无特定字符串偏好，直接点击"全部翻译"按钮即可开始。 系统将显示待翻译的字符串。
- * If you want to translate an individual file please search for the file via search dialog or tree structure and click on the filename to start the translation work on strings in that file.
+ * 如需翻译单个文件，请通过搜索框或树状目录查找目标文件，点击文件名即可开始翻译该文件内的字符串。
- * Translate sentences on left side by adding new translated text or use & edit suggestion
+ * 在左侧翻译句子：添加新译文或编辑现有建议
+ ### 校对AAPS应用字符串
- ### Proofread strings for AAPS app
-
- * Proofreaders start by selecting "Proofread" when starting from the language home screen.
+ * 校对人员需从语言首页选择"校对"模式开始工作。
- and approve translated texts
+ 并审批译文
- When a proofreader approves a translation it will be added to the next version of AAPS.
+ 当校对员批准翻译后，该内容将被纳入下一版AAPS更新。
(translations-translation-of-the-documentation)=
- ## Translation of the documentation
+ ## 文档翻译
- * Click the name of the docs page you want to translate
+ * 点击您要翻译的文档页面名称
- * Translate sentences by sentence
+ * 逐句翻译
- 1. The yellow text is the text you are working at the moment.
+ 1. 黄色文本是您当前正在处理的文本。
- 1. The green text is already translated. You don't need to do this again.
+ 1. 绿色文本是已经翻译过的文本。 您不需要再做一遍。
- 1. The red text is the remaining text which have to be translated.
+ 1. 红色文本是剩余需要翻译的文本。
- 1. This is the source text you are working on at the moment
+ 1. 这是您当前正在处理的源文本。
- 1. This is the translation you are preparing. You can copy the text from above or select one of the suggestions below.
+ 1. 这是您正在准备的翻译文本。 您可以复制上面的文本或选择下面的建议之一。
- 1. These are the suggestion for a translation. Especially you can see how much Crowdin rates this as a fit or if it was already just in the past and come up through text rearrangements but not content change.
- 1. Press the "save" button to save a proposal for the translation. It will then promoted to a proofreader for final check.
+ 1. 此为翻译建议。 您可特别关注Crowdin对此建议的匹配度评分，或查看该内容是否仅为历史译文经文本重组生成（未实质性更改）。
+ 1. 点击"保存"按钮提交翻译建议。 该建议随后将提交给校对人员进行最终审核。
- * A translated page will not be published in docs before
+ * 翻译完成的文档页面在发布前需经过审核
- 1. the translation is proofread
+ 1. 翻译已校对
- 1. the sync run between Crowdin and Github finished (once an hour) which creates an PR for Github.
+ 1. Crowdin 和 Github 之间的同步运行完成（每小时一次），这会为 Github 创建一个 PR。
- 1. the PR in Github was approved.
+ 1. 该GitHub上的PR（拉取请求）已获批准。
- In general this needs 1 - 3 days but might during holiday take a little bit longer.
+ 通常需1-3个工作日，节假日期间可能略有延迟。
- ### Translating links
+ ### 链接翻译
- ```{admonition} Links are not translated anymore
+ ```{admonition} 链接不再进行翻译
:class: note
- Links are not translated anymore. In the past we had a topic here but this is gone as through migraton to Markdown and the myst_parser we explicitly create labels in the english text and propagate these labels under the hood to the languages.
+ 链接不再进行翻译。 过去我们曾在此处有相关说明，但迁移至Markdown格式和使用myst_parser解析器后，我们直接在英文文本中创建标签，并通过后台机制将这些标签传播至各语言版本。
-You are translating the text which represents the link. Please you have to be careful **not** to remove the link which is represented by a pair of `<0>` tags or if their are more in one paragraph other numbers.
+您正在翻译的是链接的显示文本。 请务必注意**不要**删除由`<0>`标签对表示的链接，若同一段落中存在多个链接，其他数字标签也需保留。
-It's the proofreaders job to have a special look on this!
+校对人员需对此进行专项检查！
-### Proofreading
+### 校对
-* Proofreaders have to switch to Proofreading mode
+* 校对员必须切换到校对模式
- 
+ 
- and approve translated texts
+ 并批准翻译的文本
-* When a proofreader approves a translation it will be added to the next docs build which happens in no fixed schedule on demand but around once a week except during hollidays. To speed up the process you can inform docs team about new translations.
\ No newline at end of file
+* 当校对员批准翻译后，它将被添加到下一个文档构建中，该构建没有固定的时间表，而是按需进行，大约每周一次，节假日除外。 要加快此过程，您可以通知文档团队有关新翻译的信息。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/UsefulLinks/BackgroundReading.md b/docs/CROWDIN/zh_CN/UsefulLinks/BackgroundReading.md
index 5ac25e94a396..6dcb46a4c17b 100644
--- a/docs/CROWDIN/zh_CN/UsefulLinks/BackgroundReading.md
+++ b/docs/CROWDIN/zh_CN/UsefulLinks/BackgroundReading.md
@@ -1,38 +1,38 @@
-# Useful resources to read before you start
+# 开始前应阅读的有用资源
-Before you build your rig, you're going to have to do a lot of reading in order to understand how everything works and to get the best out of it. We've put together a list of places you can go to get you started and hopefully answer a lot of your questions.
+在开始构建您的系统之前，您需要阅读大量资料，以了解一切是如何运作的，并充分发挥其效能。 我们为您整理了一些可以获取初步信息的地方，希望这些能解答您的许多问题。
-## Further reading
+## 进一步阅读
[OpenAPS.org #wearenotwaiting - https://openaps.org/](https://openaps.org/)
-[OpenAPS documentation - https://openaps.readthedocs.io/en/latest/](https://openaps.readthedocs.io/en/latest/)
+[OpenAPS文档 - https://openaps.readthedocs.io/en/latest/](https://openaps.readthedocs.io/en/latest/)
[Loop Docs - https://loopkit.github.io/loopdocs/](https://loopkit.github.io/loopdocs/)
-[Fine-Tuning your settings - https://web.archive.org/web/20231130035337/https://seemycgm.com/2017/10/29/fine-tuning-settings/](https://web.archive.org/web/20231130035337/https://seemycgm.com/2017/10/29/fine-tuning-settings/)
+[微调您的设置 - https://web.archive.org/web/20231130035337/https://seemycgm.com/2017/10/29/fine-tuning-settings/](https://web.archive.org/web/20231130035337/https://seemycgm.com/2017/10/29/fine-tuning-settings/)
-[Tim Omer – Hypodiabetic Blog - https://www.hypodiabetic.co.uk/](https://www.hypodiabetic.co.uk/)
+[Tim Omer – Hypodiabetic博客 - https://www.hypodiabetic.co.uk/](https://www.hypodiabetic.co.uk/)
[DIYPS - https://diyps.org/](https://diyps.org/)
-[Diabetes and Technology - Where Diabetes meets Tech - https://www.diabettech.com/](https://www.diabettech.com/)
+[糖尿病与技术 - 糖尿病与科技的交汇 - https://www.diabettech.com/](https://www.diabettech.com/)
-[OpenAPS Reference Design - https://openaps.org/reference-design/](https://openaps.org/reference-design/)
+[OpenAPS参考设计 - https://openaps.org/reference-design/](https://openaps.org/reference-design/)
-[Why we are regularly wrong in the duration of insulin action (DIA) times we use, and why it matters - https://www.diabettech.com/insulin/why-we-are-regularly-wrong-in-the-duration-of-insulin-action-dia-times-we-use-and-why-it-matters/](https://www.diabettech.com/insulin/why-we-are-regularly-wrong-in-the-duration-of-insulin-action-dia-times-we-use-and-why-it-matters/)
+[为什么我们常用的胰岛素作用时间（DIA）经常出错，以及为什么这很重要 - https://www.diabettech.com/insulin/why-we-are-regularly-wrong-in-the-duration-of-insulin-action-dia-times-we-use-and-why-it-matters/](https://www.diabettech.com/insulin/why-we-are-regularly-wrong-in-the-duration-of-insulin-action-dia-times-we-use-and-why-it-matters/)
-[What conclusions can we draw when investigating Insulin Sensitivity using the Autosens function within #OpenAPS? https://www.diabettech.com/openaps/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/](https://www.diabettech.com/openaps/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/)
+[通过#OpenAPS中的Autosens功能研究胰岛素敏感性时，我们能得出哪些结论？ https://www.diabettech.com/openaps/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/](https://www.diabettech.com/openaps/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/)
[https://seemycgm.com/2017/10/29/fine-tuning-settings/](https://web.archive.org/web/20231130035337/https://seemycgm.com/2017/10/29/fine-tuning-settings/)
-[“Brights Spots and Landmines”](https://diatribe.org/bright-spots-and-landmines/) by Adam Brown
+[《亮点与陷阱》](https://diatribe.org/bright-spots-and-landmines/) 作者：Adam Brown
-[“Think like a Pancreas”](https://amzn.eu/d/iVU0RGe) by Gary Scheiner
+[《像胰腺一样思考》](https://amzn.eu/d/iVU0RGe) 作者：Gary Scheiner
-["Pumping insulin"](https://amzn.eu/d/iaCsFa2) by John Walsh & Ruth Roberts
+[《泵注胰岛素》](https://amzn.eu/d/iaCsFa2) 作者：John Walsh & Ruth Roberts
-## Background reading and articles about DIY closed looping
+## 关于DIY闭环系统的背景阅读和文章
@@ -40,8 +40,8 @@ Before you build your rig, you're going to have to do a lot of reading in order
-## Stuff on YouTube
+## YouTube上的内容
-[Tim Omer: Empowered Citizen "Health Hackers" - We Are Not Waiting! - https://www.youtube.com/watch?v=RjhkRmL1wOI](https://www.youtube.com/watch?v=RjhkRmL1wOI)
+[Tim Omer：赋能公民“健康黑客”——我们不再等待！ - https://www.youtube.com/watch?v=RjhkRmL1wOI](https://www.youtube.com/watch?v=RjhkRmL1wOI)
-[Live interview with Dana Lewis, creator of Do-It-Yourself Pancreas System - https://www.youtube.com/watch?v=uvjrPrH0Hrw](https://www.youtube.com/watch?v=uvjrPrH0Hrw)
\ No newline at end of file
+[与DIY胰腺系统创始人Dana Lewis的现场访谈 - https://www.youtube.com/watch?v=uvjrPrH0Hrw](https://www.youtube.com/watch?v=uvjrPrH0Hrw)
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/UsefulLinks/ClinicianGuideToAaps.md b/docs/CROWDIN/zh_CN/UsefulLinks/ClinicianGuideToAaps.md
index 063a6165ec03..2c70438b4034 100644
--- a/docs/CROWDIN/zh_CN/UsefulLinks/ClinicianGuideToAaps.md
+++ b/docs/CROWDIN/zh_CN/UsefulLinks/ClinicianGuideToAaps.md
@@ -1,101 +1,101 @@
-# For Clinicians – A General Introduction and Guide to AAPS
+# 致临床医生——AAPS的一般介绍和使用指南
-This page is intended for clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians.
+本页面专为两类用户设计，对开源人工胰腺技术（如AAPS）感兴趣的临床医师，以及需向医师分享此类信息的患者。
-This guide has some high-level information about DIY closed looping and specifically how AAPS works. For more details on all of these topics, please view the [comprehensive AAPS documentation online](../index.md). If you have questions, please ask your patient for more details, or always feel free to reach out to the community with question. (If you’re not on social media (e.g. [Twitter](https://twitter.com/kozakmilos) or Facebook), feel free to email developers@AndroidAPS.org). [You can also find some of the latest studies & outcomes related data here](https://openaps.org/outcomes/).
+本指南包含关于DIY闭环系统的高阶信息，特别是AAPS的工作原理。 如需了解这些主题的更多详细信息，请查阅[在线版AAPS完整文档](../index.md)。 如有疑问，可向患者进一步了解详情，或随时联系社区咨询。 （如未使用社交媒体（如[Twitter](https://twitter.com/kozakmilos)或Facebook），欢迎发送邮件至developers@AndroidAPS.org） [您也可在此查阅部分最新研究及疗效相关数据](https://openaps.org/outcomes/)。
-## The steps for building a DIY Closed Loop:
+## 构建DIY闭环系统的步骤：
-To start using AAPS, the following steps should be taken:
+要开始使用AAPS，请按照以下步骤操作：
-* Find a [compatible pump](../Getting-Started/CompatiblePumps.md), a [compatible Android device](../Getting-Started/Phones.md), and a [compatible CGM source](../Getting-Started/CompatiblesCgms.md).
-* [Download the AAPS source code and build the software](../SettingUpAaps/BuildingAaps.md).
-* [Configure the software to talk to their diabetes devices and specify settings and safety preferences](../SettingUpAaps/SetupWizard.md).
+* 查找[兼容的泵](../Getting-Started/CompatiblePumps.md)、[兼容的Android设备](../Getting-Started/Phones.md)和[兼容的CGM来源](../Getting-Started/CompatiblesCgms.md)。
+* [下载AAPS源代码并构建软件](../SettingUpAaps/BuildingAaps.md)。
+* [配置软件以与糖尿病设备进行通信，并指定设置和安全偏好](../SettingUpAaps/SetupWizard.md)。
-## How A DIY Closed Loop Works
+## DIY闭环系统的工作原理
-Without a closed loop system, a person with diabetes gathers data from their pump and CGM, decides what to do, and takes action.
+在没有闭环系统的情况下，糖尿病患者需要从泵和CGM收集数据，决定该怎么做，并采取行动。
-With automated insulin delivery, the system does the same thing: it gathers data from the pump, CGM, and anywhere else information is logged (such as Nightscout), uses this information to do the maths and decide how much more or less insulin is needed (above or below the underlying basal rate), and uses temporary basal rates to make the necessary adjustments to keep or eventually bring BGs into target range.
+通过自动胰岛素输送，系统执行相同的操作：它从泵、CGM以及记录信息的任何地方（如Nightscout）收集数据，使用这些信息进行计算，并决定需要多少胰岛素（高于或低于基础速率），并使用临时基础速率进行必要的调整，以保持或将血糖水平带入目标范围内。
-If the device running AAPS breaks or goes out of range of the pump, once the latest temporary basal rate ends, the pump falls back to being a standard pump with the preprogrammed basals rates running.
+若运行AAPS的设备发生故障或超出胰岛素泵通信范围，当最后一个临时基础率结束后，胰岛素泵将恢复为预设基础率运行的标准泵模式。
-## How data is gathered:
+## 数据采集方式：
-With AAPS, an Android device runs a special app to do the math, the device communicates using Bluetooth with a supported pump. AAPS can communicate with other devices and to the cloud via wifi or mobile data to gather additional information, and to report to the patient, caregivers, and loved ones about what it’s doing and why.
+在AAPS中，Android设备运行一个特殊的应用程序进行数学计算，该设备与支持的泵通过蓝牙通信。 AAPS可以通过WiFi或移动数据与其他设备和云端通信，以收集额外信息，并向患者、护理人员和亲人报告其正在做什么以及为什么这样做。
-The Android device needs to:
+Android设备需要：
-* communicate with the pump and read history - how much insulin has been delivered
-* communicate with the CGM (either directly, or via the cloud) - to see what BGs are/have been doing
+* 与泵通信并读取历史记录——已输送多少胰岛素
+* 与CGM通信（直接或通过云端）——查看血糖水平
-When the device has collected this data, the algorithm runs and does the decision-making based on the settings (ISF, carb ratio, DIA, target, etc.). If required, it then issues commands to the pump to modify insulin delivery rate.
+当设备收集到这些数据后，算法会运行并根据设置（ISF、碳水化合物比例、DIA、目标等）做出决策。 如果需要，它会向泵发出命令以修改胰岛素输送速率。
-It will also gather any information about boluses, carbohydrate consumption, and temporary target adjustments from the pump or from Nightscout to use it for the calculation of insulin delivery rates.
+它还会从泵或Nightscout收集有关大剂量、碳水化合物摄入和临时目标调整的任何信息，以用于计算胰岛素输送速率。
-## How does it know what to do?
+## 该系统如何确定执行何种操作？
-The open source software is designed to make it easy for the device to do the work people used to do (in manual mode) to calculate how insulin delivery should be adjusted. It first collects data from all the supporting devices and from the cloud, prepares the data and runs the calculations, makes predictions of expected BG-levels during the next hours will be expected to do in different scenarios, and calculates the needed adjustments to keep or bring BG back into target range. Next it sends any necessary adjustments to the pump. Then it reads the data back, and does it over and over again.
+开源软件旨在使设备能够轻松完成人们过去在手动模式下所做的工作，即计算如何调整胰岛素输送。 它首先从所有支持设备和云端收集数据，准备数据并运行计算，预测未来不同场景下预期的血糖水平，并计算保持或将血糖带回目标范围所需的调整。 然后，它将任何必要的调整发送到泵。 之后，它读取数据，并重复此过程。
-As the most important input parameter is the blood glucose level coming from the CGM, it is important to have high-quality CGM data.
+由于最重要的输入参数是来自CGM的血糖水平，因此拥有高质量的CGM数据非常重要。
-AAPS is designed to transparently track all input data it gathers, the resulting recommendation, and any action taken. It is therefore easy to answer the question at any time, “why is it doing X?” by reviewing the logs.
+AAPS被设计为透明地跟踪其收集的所有输入数据、生成的建议以及采取的任何操作。 因此，通过查看日志，可以随时轻松回答“它为什么这样做？”的问题。
-## Examples of AAPS algorithm decision making:
+## AAPS算法决策示例：
-AAPS uses the same core algorithm and feature set as OpenAPS. The algorithm makes multiple predictions (based on settings, and the situation) representing different scenarios of what might happen in the future. In Nightscout, these are displayed as “purple lines”. AAPS uses different colors to separate these [prediction lines](#aaps-screens-prediction-lines). In the logs, it will describe which of these predictions and which time frame is driving the necessary actions.
+AAPS使用与OpenAPS相同的核心算法和功能集。 算法会做出多个预测（基于设置和情况），代表未来可能发生的不同场景。 在Nightscout中，这些以“紫色线”显示。 AAPS使用不同的颜色来区分这些[预测线](#aaps-screens-prediction-lines)。 在日志中，它会描述哪些预测和哪个时间段正在驱动必要的操作。
-### Here are examples of the purple prediction lines, and how they might differ:
+### 以下是紫色预测线的示例，以及它们可能如何不同：
-### Here are examples of different time frames that influence the needed adjustments to insulin delivery:
+### 以下是影响胰岛素输送所需调整的不同时间段的示例：
-### Scenario 1 - Zero Temp for safety
+### 场景1 - 出于安全考虑的零临时基础率
-In this example, BG is rising in the near-term time frame; however, it is predicted to be low over a longer time frame. In fact, it is predicted to go below target *and* the safety threshold. For safety to prevent the low, AAPS will issue a zero temp (temporary basal rate at 0%), until the eventualBG (in any time frame) is above threshold.
+在此示例中，血糖（BG）短期内呈上升趋势，但长期预测显示将处于低值状态。 实际上，系统预测血糖将低于目标值*且*突破安全阈值。 为防止低血糖，AAPS将启动零临时基础率（临时基础率设为0%），直至任意时间段的预测血糖值回升至阈值以上。
-### Scenario 2 - Zero temp for safety
+### 场景2 - 出于安全考虑的零临时基础率
-In this example, BG is predicted to go low in the near-term, but is predicted to eventually be above target. However, because the near-term low is actually below the safety threshold, AAPS will issue a zero temp, until there is no longer any point of the prediction line that is below threshold.
+在此示例中，系统预测血糖短期内将降低，但最终会回升至目标值以上。 但由于短期预测的低血糖值实际上已低于安全阈值，AAPS将启动零临时基础率，直至预测曲线不再有任何低于阈值的点。
-### Scenario 3 - More insulin needed
+### 场景3 - 需要更多胰岛素
-In this example, a near-term prediction shows a dip below target. However, it is not predicted to be below the safety threshold. The eventual BG is above target. Therefore, AAPS will restrain from adding any insulin that would contribute to a near-term low (by adding insulin that would make the prediction go below threshold). It will then assess adding insulin to bring the lowest level of the eventual predicted BG down to target, once it is safe to do so. *(Depending on settings and the amount and timing of insulin required, this insulin may be delivered via temp basals or SMB's (super micro boluses) ).*
+在此示例中，短期预测显示血糖将跌破目标范围。 但系统预测其不会跌破安全阈值。 最终血糖将回升至目标范围以上。 因此，AAPS将避免追加任何可能导致短期低血糖的胰岛素（即防止因胰岛素追加而使预测值跌破阈值）。 系统将在安全允许时评估是否追加胰岛素，使最终预测血糖的最低值回落至目标范围。 *（根据设置及所需胰岛素的剂量与时间，该胰岛素可能通过临时基础率或SMB（超级微剂量推注）输送）。*
-### Scenario 4 - Low temping for safety
+### 场景4 - 出于安全考虑的低临时基础率
-In this example, AAPS sees that BG is spiking well above target. However, due to the timing of insulin, there is already enough insulin in the body to bring BG into range eventually. In fact, BG is predicted to eventually be below target. Therefore, AAPS will not provide extra insulin so it will not contribute to a longer-timeframe low. Although BG is high/rising, a low temporary basal rate is likely here.
+在此示例中，AAPS检测到血糖正急剧上升并远超目标值。 然而，由于胰岛素的作用时间特性，体内已有足够胰岛素最终使血糖回归正常范围。 实际上，系统预测血糖最终将低于目标范围。 因此，AAPS将不会提供额外胰岛素，以避免导致更长时间段的低血糖。 尽管血糖处于高位/正在上升，此时更可能采用较低的临时基础率。
-## Optimizing settings and making changes
+## 优化设置与参数调整
-As a clinician who may not have experience with AAPS or DIY closed loops, you may find it challenging to help your patient optimize their settings or make changes to improve their outcomes. We have multiple tools and [guides](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/optimize-your-settings.html) in the community that help patients make small, tested adjustments to improve their settings.
+作为可能没有AAPS或DIY闭环系统经验的临床医生，您可能会发现帮助患者优化设置或做出更改以改善结果具有挑战性。 我们提供多种社区工具与[指南](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/optimize-your-settings.html)，帮助患者通过经测试的小幅调整来优化设置。
-The most important thing for patients to do is make one change at a time, and observe the impact for 2-3 days before choosing to change or modify another setting (unless it’s obviously a bad change that makes things worse, in which case they should revert immediately to the previous setting). The human tendency is to turn all the knobs and change everything at once; but if someone does so, then they may end up with further sub-optimal settings for the future, and find it hard to get back to a known good state.
+患者最重要的调整原则是：每次仅修改一个参数，并观察2-3天效果后，再决定是否调整其他设置（除非明显恶化，此时应立即恢复至先前参数）。 人类倾向于一次性调整所有参数，但这样做可能导致后续设置更加不理想，且难以恢复到已知的良好状态。
-One of the most powerful tools for making settings changes is an automated calculation tool for basal rates, ISF, and carb ratio. This is called “[Autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html)”. It is designed to be run independently/manually, and allow the data to guide you or your patient in making incremental changes to settings. It is best practice in the community to run (or review) Autotune reports first, prior to attempting to make manual adjustments to settings. With AAPS, Autotune will be run as a "one-off", although there are ongoing efforts to incorporate it directly into AAPS as well. As these parameters are a prerequisite both for standard pump insulin delivery and for closed loop insulin delivery, discussion of the autotune results and adjustment of these parameters would be the natural link to the clinician.
+调整设置最强大的工具之一是基础率、胰岛素敏感系数和碳水比率的自动计算工具。 这被称为“[Autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html)”。 它的设计初衷是独立/手动运行，通过数据引导您或患者逐步调整设置。 在社群中，最佳实践是在尝试手动调整设置之前，先运行（或查看）Autotune报告。 在AAPS中，Autotune目前是作为"一次性工具"运行的，不过开发团队也正在努力将其直接集成到AAPS系统内。 由于这些参数既是标准泵胰岛素输注的前提条件，也是闭环胰岛素输注的基础，因此讨论Autotune结果并调整这些参数，自然成为与临床医生沟通的重要环节。
-Additionally, human behavior (learned from manual diabetes mode) often influences outcomes, even with a DIY closed loop. For example, if BG is predicted to go low and AAPS reduces insulin on the way down, only a small amount of carbs (e.g. 3-4g carbs) may be needed to bring BG up from 70 mg/dl (3.9 mmol). However, in many cases, someone may choose to treat with many more carbs (e.g. sticking to the 15 rule), which will cause a resulting faster spike both from the extra glucose and because insulin had been reduced in the timeframe leading up to the low.
+此外，人类行为（从手动糖尿病管理模式中学到的）往往会影响治疗效果，即便是使用DIY闭环系统时也是如此。 例如，如果预测血糖将走低，且AAPS系统已在血糖下降过程中减少了胰岛素输注，那么仅需少量碳水化合物（如3-4克）即可将血糖从70 mg/dl（3.9 mmol）提升上来。 然而，在许多情况下，患者可能会选择摄入更多碳水化合物进行治疗（例如坚持"15法则"），这将导致血糖更快上升——既因额外的葡萄糖摄入，也因在低血糖发生前胰岛素输注量已被调低。
## OpenAPS
-**This guide was adopted from [The clinician's guide to OpenAPS](https://openaps.readthedocs.io/en/latest/docs/Resources/clinician-guide-to-OpenAPS.html).** OpenAPS is a system developed to be run on a small portable computer (generally referred to as the "rig"). AAPS uses many of the techniques implemented in OpenAPS, and shares much of the logic and algorithms, which is why this guide is very similar to the original guide. Much of the information about OpenAPS can be easily adapted to AAPS, with the main difference being the hardware platform where each piece of software is run.
+**本指南改编自[《OpenAPS临床医生指南》](https://openaps.readthedocs.io/en/latest/docs/Resources/clinician-guide-to-OpenAPS.html)。** OpenAPS是一套设计运行于小型便携计算机（通常称为"rig"）上的系统。 AAPS采用了OpenAPS中实现的诸多技术，并共享了大量逻辑与算法，因此本指南与原始指南高度相似。 关于OpenAPS的大部分信息均可直接适用于AAPS，主要区别在于两者运行的硬件平台不同。
-## Summary
+## 总结
-This is meant to be a high-level overview of how AAPS works. For more details, ask your patient, reach out to the community, or read the full AAPS documentation available online.
+本文旨在对AAPS的工作原理进行高层概述。 如需了解更多详情，请咨询您的患者、联系用户社区，或阅读在线提供的完整AAPS文档。
-Additional recommended reading:
+补充推荐阅读：
-* The [full AAPS documentation](../index.md)
-* The [OpenAPS Reference Design](https://OpenAPS.org/reference-design/), which explains how OpenAPS is designed for safety: https://openaps.org/reference-design/
-* The [full OpenAPS documentation](https://openaps.readthedocs.io/en/latest/index.html)
- * More [details on OpenAPS calculations](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html#understanding-the-determine-basal-logic)
\ No newline at end of file
+* [完整的AAPS文档](../index.md)
+* [OpenAPS参考设计](https://OpenAPS.org/reference-design/)（该文档阐述了OpenAPS如何实现安全性设计）：https://openaps.org/reference-design/
+* [完整的OpenAPS文档](https://openaps.readthedocs.io/en/latest/index.html)
+ * [关于OpenAPS计算的更多详情](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html#understanding-the-determine-basal-logic)
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md b/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md
index 29fce0d90309..6e0c10fe4765 100644
--- a/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md
+++ b/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md
@@ -1,12 +1,12 @@
# 闭环常见问题（FAQ）
-How to add questions to the FAQ: Follow the these [instructions](../SupportingAaps/HowToEditTheDocs.md)
+如何向FAQ添加问题：请按照以下[说明](../SupportingAaps/HowToEditTheDocs.md)操作
-## 一般
+## 常规
### 我可以直接下载AAPS的安装文件吗？
-无法直接下载。 没有可下载的AAPS apk文件。 You have to [build](../SettingUpAaps/BuildingAaps.md) it yourself. 原因如下：
+无法直接下载。 没有可下载的AAPS apk文件。 你必须自己[构建](../SettingUpAaps/BuildingAaps.md)它。 原因如下：
AAPS用于控制您的泵并输注胰岛素。 根据欧洲现行的规定，所有被归类为IIa类或IIb类的系统都是医疗器械，需要获得监管机构的批准（即CE标志），而这需要经过各种研究和审核批准。 发布未经监管认可的设备是违法行为。 全球其他地区也有类似的规定。
@@ -18,331 +18,331 @@ AAPS用于控制您的泵并输注胰岛素。 根据欧洲现行的规定，所
### 如何开始？
-First of all, you have to **get loopable hardware components**:
+首先，您需要**获取可闭环的硬件组件**：
-- A [supported insulin pump](../Getting-Started/CompatiblePumps.md),
-- an [Android smartphone](../Getting-Started/Phones.md) (Apple iOS is not supported by AAPS - you can check [iOS Loop](https://loopkit.github.io/loopdocs/)) and
-- a [continuous glucose monitoring system](../Getting-Started/CompatiblesCgms.md).
+- 一台[受支持的胰岛素泵](../Getting-Started/CompatiblePumps.md)，
+- 一部[安卓智能手机](../Getting-Started/Phones.md)（AAPS不支持Apple iOS系统——您可查阅[iOS Loop](https://loopkit.github.io/loopdocs/)方案）
+- 一个[持续葡萄糖监测系统（动态，CGM）](../Getting-Started/CompatiblesCgms.md)
-Secondly, you have to **setup your software components**: [AAPS](../SettingUpAaps/BuildingAaps.md), [CGM/FGM source](../Getting-Started/CompatiblesCgms.md) and a [reporting server](../SettingUpAaps/SettingUpTheReportingServer.md).
+其次，您需要**配置以下软件组件**：[AAPS系统](../SettingUpAaps/BuildingAaps.md)、[持续/闪速血糖监测数据源](../Getting-Started/CompatiblesCgms.md)以及[报告服务器](../SettingUpAaps/SettingUpTheReportingServer.md)。
-Thirdly, you have to learn and **understand the OpenAPS reference design to check your treatment factors**. The founding principle of closed looping is that your [basal rate and carb ratio](../SettingUpAaps/YourAapsProfile.md) are accurate. All recommendations assume that your basal needs are met and any peaks or troughs you're seeing are a result of other factors which therefore require some one-off adjustments (exercise, stress etc.). The adjustments the closed loop can make for safety have been limited (see maximum allowed temporary basal rate in [OpenAPS Reference Design](https://openaps.org/reference-design/)), which means that you don't want to waste the allowed dosing on correcting a wrong underlying basal. If for example you are frequently low temping on the approach of a meal then it is likely your basal needs adjusting. You can use [Autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html#phase-c-running-autotune-for-suggested-adjustments-without-an-openaps-rig) to consider a large pool of data to suggest whether and how basals and/or ISF need to be adjusted, and also whether carb ratio needs to be changed. Or you can test and set your basal the [old-fashioned way](https://integrateddiabetes.com/basal-testing/).
+第三，您需要学习并**理解OpenAPS参考设计，以核验您的治疗参数**。 闭环治疗的基本原则是确保您的[基础率和碳水系数](../SettingUpAaps/YourAapsProfile.md)准确无误。 所有建议均基于您的基础率需求已得到满足这一前提，若观测到血糖波峰或波谷，应视为其他因素（如运动、压力等）所致，因此仅需进行一次性调整。 闭环系统为保障安全所能进行的调整存在严格限制（参见[OpenAPS参考设计](https://openaps.org/reference-design/)中允许的最大临时基础率），这意味着您不应将有限的剂量调整额度浪费在纠正错误的基础率上。 例如，若您经常在临近用餐时出现低血糖而需要临时调低基础率，则很可能需要重新调整您的基础率设置。 您可以使用[Autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html#phase-c-running-autotune-for-suggested-adjustments-without-an-openaps-rig)分析大量数据，从而判断是否需要调整基础率和/或胰岛素敏感系数（ISF）以及如何调整，同时评估碳水比率是否需要修改。 或者，您也可以采用[传统方法](https://integrateddiabetes.com/basal-testing/)测试和设置基础代谢率。
-### What practicalities of looping do I have?
+### 闭环有哪些实际应用要点？
-#### Password protection
+#### 密码保护
-If you don't want your preferences to be easily changed then you can password protect the preferences menu by selecting in the preferences menu "password for settings" and type the password you choose. The next time you go into preferences menu it will ask for that password before going any further. If you later want to remove the password option then go into "password for settings" and delete the text.
+如果您不希望偏好设置被轻易更改，可以在偏好设置菜单中选择“为设置添加密码”，然后输入您设定的密码，即可对偏好设置菜单进行密码保护。 下次进入偏好设置菜单时，系统将要求输入该密码，验证通过后方可继续操作。 若之后想取消密码保护功能，请进入“设置密码”选项并清空文本框内容。
-#### Android Wear Smartwatches
+#### Android Wear智能手表
-If you plan to use the android wear app to bolus or change settings then you need to ensure notifications from AAPS are not blocked. Confirmation of action comes via notification.
+如果您计划通过 Android Wear 应用进行推注或更改设置，请确保未屏蔽来自 AAPS 的通知。 操作确认将通过通知发送。
(FAQ-disconnect-pump)=
-#### Disconnect pump
+#### 断开泵连接
-If you take your pump off for showering, bathing, swimming, sports or other activities you must let AAPS know that no insulin is delivered to keep IOB correct.
+若因淋浴、沐浴、游泳、运动或其他活动需摘除胰岛素泵，必须告知 AAPS 系统停止输注，以保持活性胰岛素（IOB）计算准确。
-The pump can be disconnected using the Loop Status icon on the [AAPS Home Screen](#AapsScreens-loop-status).
+您可通过[AAPS 主屏幕](#AapsScreens-loop-status)上的<1>循环状态图标断开胰岛素泵连接。
-#### Recommendations not only based on one single CGM reading
+#### 建议不仅基于单次CGM读数
-For safety, recommendations made are based on not one CGM reading but the average delta. Therefore, if you miss some readings it may take a while after getting data back before AAPS kicks in looping again.
+出于安全考虑，系统建议并非基于单次CGM读数，而是基于平均变化率（delta）。 因此，若出现监测数据缺失，恢复数据后AAPS可能需要一定时间才能重新启动循环功能。
-#### Further readings
+#### 进一步阅读
-There are several blogs with good tips to help you understand the practicalities of looping:
+以下精选博客提供实用技巧，助您掌握闭环系统的操作要点：
-- [Fine-tuning Settings](https://seemycgm.com/2017/10/29/fine-tuning-settings/) See my CGM
-- [Why DIA matters](https://seemycgm.com/2017/08/09/why-dia-matters/) See my CGM
-- [Limiting meal spikes](https://diyps.org/2016/07/11/picture-this-how-to-do-eating-soon-mode/) #DIYPS
-- [Hormones and autosens](https://seemycgm.com/2017/06/06/hormones-2/) See my CGM
+- [微调设置](https://seemycgm.com/2017/10/29/fine-tuning-settings/) - See my CGM
+- [为什么DIA很重要](https://seemycgm.com/2017/08/09/why-dia-matters/) - See my CGM
+- [限制餐后血糖飙升](https://diyps.org/2016/07/11/picture-this-how-to-do-eating-soon-mode/) - #DIYPS
+- [激素和autosens](https://seemycgm.com/2017/06/06/hormones-2/) - See my CGM
-### What emergency equipment is recommended to take with me?
+### 推荐携带的急救设备有哪些？
-You have to have the same emergency equipment with you like every other T1D with insulin pump therapy. When looping with AAPS it is strongly recommended to have the following additional equipment with or near to you:
+你必须和其他所有使用胰岛素泵治疗的1型糖尿病患者一样，随身携带相同的应急装备。 在使用AAPS闭环系统时，强烈建议随身或在附近备有以下额外设备：
-- Battery pack and cables to charge your smartphone, watch and (if needed) BT reader or Link device
-- Pump batteries
-- Current [apk](../SettingUpAaps/BuildingAaps.md) and [preferences files](../Maintenance/ExportImportSettings.md) for AAPS and any other apps you use (e.g. xDrip+, BYO Dexcom) both locally and in the cloud (Dropbox, Google Drive).
+- 备用电源及充电线（用于智能手机、智能手表，以及蓝牙血糖仪/Link设备等需充电配件）
+- 胰岛素泵电池
+- 当前版本的 [AAPS安装包](../SettingUpAaps/BuildingAaps.md) 和 [配置文件](../Maintenance/ExportImportSettings.md)（包括其他相关应用如xDrip+、BYO Dexcom等），需在本地和云端（Dropbox、Google Drive）双重备份。
-### How can I safely and securely attach the CGM/FGM?
+### 如何安全牢固地附着CGM/FGM？
-You can tape it. There are several pre-perforated 'overpatches' for common CGM systems available (search Google, eBay or Amazon). Some loopers use the cheaper standard kinesiology tape or rocktape.
+你可以用胶带粘起来。 市场上有多种针对常见CGM系统的预穿孔"加固贴片"可供选择（可通过Google、eBay或Amazon搜索购买）。 部分闭环系统使用者会选用更经济的标准肌效贴或RockTape品牌产品。
-You can fix it. You can also purchase upper arm bracelets that fix the CGM/FGM with a band (search Google, eBay or Amazon).
+你可以搞定它。 您还可以购买通过绑带固定CGM/FGM传感器的上臂护套（可通过Google、eBay或Amazon搜索选购）。
-## APS algorithm
+## APS算法
-### Why does it show "dia:3" in the "OPENAPS AMA"-tab even though I have a different DIA in my profile?
+### 为什么我的个人资料中设置了不同的DIA值，但"OPENAPS AMA"标签页仍显示"dia:3"？
-In AMA, DIA actually doesn't mean the 'duration of insulin acting'. It is a parameter, which used to be connected to the DIA. Now, it means, 'in which time should the correction be finished'. It has nothing to do with the calculation of the IOB. In OpenAPS SMB, there is no need for this parameter any longer.
+在AMA算法中，DIA实际上并不表示"胰岛素作用时长"。 这是一个参数，过去曾与DIA相关联。 现在，它表示"应在多长时间内完成校正"。 该参数与活性胰岛素（IOB）的计算完全无关。 在OpenAPS的SMB模式中，此参数已不再需要。
-## Other settings
+## 其他设置
-### Nightscout settings
+### Nightscout设置
-#### AAPSClient says 'not allowed' and does not upload data. What can I do?
+#### AAPS客户端显示"未获授权"并停止数据上传。 我能做些什么？
-In AAPSClient check 'Connection settings'. Maybe you actually are not in an allowed WLAN or you have activated 'Only if charging' and your charging cable is not attached.
+在 AAPSClient 中检查 "连接设置"。 也许你实际上并不在允许的WLAN中，或者你已经激活了“仅当充电时”，而你的充电电缆没有连接。
-### CGM settings
+### CGM设置
-#### Why does AAPS say 'BG source doesn't support advanced filtering'?
+#### 为什么AAPS说“BG源不支持高级过滤”？
-If you do use another CGM/FGM than Dexcom G5 or G6 in xDrip native mode, you'll get this alert in AAPS OpenAPS-tab. See [Smoothing blood glucose data](../CompatibleCgms/SmoothingBloodGlucoseData.md) for more details.
+如果你使用的是xDrip原生模式下的非Dexcom G5或G6 CGM/FGM，你会在AAPS的OpenAPS标签中看到这个警告。 请参阅[平滑血糖数据](../CompatibleCgms/SmoothingBloodGlucoseData.md)。
-### Pump
+### 胰岛素泵
-#### Where to place the pump?
+#### 泵放在哪里？
-There are innumerable possibilities to place the pump. It does not matter if you are looping or not.
+放置泵的位置有无数种可能。 是否使用闭环并不重要。
-#### Batteries
+#### 电池
-Looping can reduce the pump battery faster than normal use because the system interacts through bluetooth far more than a manual user does. It is best to change battery at 25% as communication becomes challenging then. You can set warning alarms for pump battery by using the PUMP_WARN_BATT_P variable in your Nightscout site. Tricks to increase battery life include:
+闭环系统运行会加速胰岛素泵电池消耗（相比手动操作模式），因为系统通过蓝牙的交互频率远高于人工操作。 建议在电池电量剩余25%时更换，因电量过低会导致通信稳定性下降。 您可以通过在Nightscout网站中设置PUMP_WARN_BATT_P参数来启用胰岛素泵电池低电量预警警报。 增加电池寿命的技巧包括：
-- reduce the length of time the LCD stays on (within pump settings menu)
-- reduce the length of time the backlight stays on (within pump settings menu)
-- select notification settings to a beep rather than vibrate (within pump settings menu)
-- only press the buttons on the pump to reload, use AAPS to view all history, battery level and reservoir volume.
-- AAPS app may often be closed to save energy or free RAM on some phones. When AAPS is reinitialized at each startup it establishes a Bluetooth connection to the pump, and re-reads the current basal rate and bolus history. This consumes battery. To see if this is happening, go to Preferences > NSClient and enable 'Log app start to NS'. Nightscout will receive an event at every restart of AAPS, which makes it easy to track the issue. To reduce this happening, whitelist AAPS app in the phone battery settings to stop the app power monitor closing it down.
+- 缩短LCD屏幕持续亮屏时间（需在胰岛素泵设置菜单内调整）
+- 请通过胰岛素泵设置菜单缩短背光持续时间
+- 请将胰岛素泵的通知设置从震动模式调整为蜂鸣提示（需在泵体设置菜单内操作）。
+- 请仅通过胰岛素泵按键执行重新加载操作，所有历史数据、电池电量和储药器余量均需通过AAPS查看。
+- 为节省电量或释放手机内存，有的手机会频繁关闭AAPS应用。 每次启动时，AAPS都会重新初始化并与胰岛素泵建立蓝牙连接，同时重新读取当前基础率及大剂量历史记录。 这会消耗电量。 要确认是否发生此情况，请前往【设置】>【NS客户端】并启用"记录应用启动至Nightscout"功能。 每次AAPS重启时，Nightscout都会接收到相应事件记录，便于追踪该问题。 为避免此情况发生，请在手机电池设置中将AAPS应用加入白名单，以防止系统电源管理强制关闭该应用。
- For example, to whitelist on a Samsung phone running Android Pie:
+ 例如，在运行Android Pie系统的三星手机上设置白名单的操作步骤如下：
- - Go to Settings -> Device Care -> Battery
- - Scroll until you find AAPS and select it
- - De-select "Put app to sleep"
- - ALSO go to Settings -> Apps -> (Three circle symbol in the top-right of the screen) select "special access" -> Optimize battery usage
- - Scroll to AAPS and make sure it is de-selected.
+ - 转到“设置”->“设备护理”->“电池”
+ - 滚动直到找到AAPS并选择它
+ - 取消选中“使应用进入休眠状态”
+ - 还要转到“设置”->“应用”->（屏幕右上角的三个圆圈符号）选择“特殊访问”->“优化电池使用”
+ - 滚动到AAPS并确保它被取消选中。
-- clean battery terminals with alcohol wipe to ensure no manufacturing wax/grease remains.
+- 使用酒精棉片清洁电池触点，确保去除所有出厂残留的蜡质/油脂。
-- for [Dana R/RS pumps](../CompatiblePumps/DanaRS-Insulin-Pump.md) the startup procedure draws a high current across the battery to purposefully break the passivation film (prevents loss of energy whilst in storage) but it doesn't always work to break it 100%. Either remove and reinsert battery 2-3 times until it does show 100% on screen, or use battery key to briefly short circuit battery before insertion by applying to both terminals for a split second.
-- see also more tips for [particular types of battery](#Accu-Chek-Combo-Tips-for-Basic-usage-battery-type-and-causes-of-short-battery-life)
+- 对于[Dana R/RS胰岛素泵](../CompatiblePumps/DanaRS-Insulin-Pump.md)，其启动程序会施加高电流以刻意击穿电池钝化膜（该膜用于防止存储期间能量损耗），但这一过程并不总能实现100%的完全击穿。 请反复取出并重新插入电池2-3次，直至屏幕显示100%电量；或使用电池钥匙在安装前瞬间短接电池两极（接触时间不超过0.5秒）。
+- 另请参阅针对[特定电池类型](#Accu-Chek-Combo-Tips-for-Basic-usage-battery-type-and-causes-of-short-battery-life)的更多使用技巧。
-#### Changing reservoirs and cannulas
+#### 更换储药器与输注管路
-The change of cartridge cannot be done via AAPS but must be carried out as before directly via the pump.
+更换储药器操作无法通过AAPS完成，仍需像往常一样直接在胰岛素泵上执行。
-- Long press on "Open Loop"/"Closed Loop" on the Home tab of AAPS and select 'Suspend Loop for 1h'
-- Now nnect the pump and change the reservoir as per pump instructions.
-- Also priming and filling tube and cannula can be done directly on the pump. In this case use [PRIME/FILL button](#screens-action-tab) in the actions tab just to record the change.
-- Once reconnected to the pump continue the loop by long pressing on 'Suspended (X m)'.
+- 在AAPS的「首页」选项卡中长按"开环"/"闭环"按钮，选择「暂停闭环1小时」。
+- 现在断开泵的连接，并按照泵的说明更换储药器。
+- 此外，管路与输注套管的预充操作也可直接在胰岛素泵上完成。 这种情况下，请使用操作选项卡中的[PRIME/FILL按钮](#screens-action-tab)仅用于记录更换操作。
+- 重新连接胰岛素泵后，长按"已暂停（剩余X分钟）"按钮即可恢复闭环运行。
-The change of a cannula however does not use the "prime infusion set" function of the pump, but fills the infusion set and/or cannula using a bolus which does not appear in the bolus history. This means it does not interrupt a currently running temporary basal rate. On the Actions (Act) tab, use the [PRIME/FILL button](#screens-action-tab) to set the amount of insulin needed to fill the infusion set and start the priming. If the amount is not enough, repeat filling. You can set default amount buttons in the Preferences > Other > Fill/Prime standard insulin amounts. See the instruction booklet in your cannula box for how many units should be primed depending on needle length and tubing length.
+然而，更换输注管路时并不使用胰岛素泵自带的"充盈管路"功能，而是通过大剂量注射（该操作不会出现在大剂量历史记录中）来完成管路和/或套管的填充。 这意味着该操作不会中断当前正在运行的临时基础率。 在操作（Act）选项卡中，使用[PRIME/FILL按钮](#screens-action-tab)设置充盈输注管路所需的胰岛素量并启动预充程序。 若剂量不足，请重复执行充盈操作。 您可以在【设置】>【其他】>【充盈/预充标准胰岛素量】中配置默认剂量快捷按钮。 请参阅输注套管包装内的说明书，根据针头长度和管路长度确定所需预充胰岛素单位数。
-### Wallpaper
+### 壁纸
-You can find the AAPS wallpaper for your phone on the [phones page](#Phones-phone-wallpaper).
+您可以在[手机页面](#Phones-phone-wallpaper)上找到适用于您手机的AAPS壁纸。
-### Daily usage
+### 日常使用
-#### Hygiene
+#### 卫生
-##### What to do when taking a shower or bath?
+##### 淋浴或泡澡时需要注意什么？
-You can remove the pump while taking a shower or bath. For this short period of time you may not need it, but you should tell AAPS that you've disconnected so that the IOB calculations are correct. See [description above](#FAQ-disconnect-pump).
+您可以在淋浴或洗澡时取下泵。 在这短时间内，您可能不需要它，但您应告知 AAPS 您已断开连接，以便 IOB 计算正确无误。 见<0>上面的描述。
-#### Work
+#### 工作
-Depending on your job, you may choose to use different treatment factors on workdays. As a looper you should consider a [profile switch](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md) for your typical working day. For example, you may switch to a profile higher than 100% if you have a less demanding job (e.g. sitting at a desk), or less than 100% if you are active and on your feet all day. You could also consider a high or low temporary target or a [time shift of your profile](#ProfileSwitch-ProfilePercentage-time-shift-of-the-circadian-percentage-profile) when working much earlier or later than regular, of if you work different shifts. You can also create a second profile (e.g. 'home' and 'workday') and do a daily profile switch to the profile you actually need.
+根据您的工作，您可以选择在工作日使用不同的胰岛素系数。 作为闭环用户，您应该为典型的工作日考虑一个 <0>配置切换。 例如，如果您的工作强度较低（如坐在办公桌前），您可以切换到高于 100% 的配置；如果您整天活动且站立，则可以切换到低于 100% 的配置。 您还可以考虑设置较高或较低的临时目标，或在工作时间比平时早很多或晚很多时，或轮班工作时，进行 [配置时间调整](#ProfileSwitch-ProfilePercentage-time-shift-of-the-circadian-percentage-profile)。 您还可以创建第二个配置（例如“家庭”和“工作日”），并根据需要每天切换到实际需要的配置。
-### Leisure activities
+### 休闲活动
(FAQ-sports)=
-#### Sports
+#### 运动
-You have to rework your old sports habits from pre-loop times. If you simply consume one or more sports carbs as before, the closed loop system will recognize them and correct them accordingly.
+您需要重新调整闭环前的旧运动习惯。 如果您像以前一样简单地摄入一份或多份运动碳水，闭环系统会识别并相应地进行校正。
-So, you would have more carbohydrates on board, but at the same time the loop would counteract and release insulin.
+因此，你的体内会有更多碳水化合物储备，但同时闭环系统会进行抵消并释放胰岛素。
-When looping you should try these steps:
+当使用循环时，您可以尝试以下步骤：
-- Make a [profile switch](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md) < 100%.
-- Set an [activity temp target](#TempTargets-activity-temp-target) above your standard target.
-- If you are using SMB make sure ["Enable SMB with high temp targets"](#Open-APS-features-enable-smb-with-high-temp-targets) and ["Enable SMB always"](#Open-APS-features-enable-smb-always) are disabled.
+- 将[配置文件切换](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md)设置为小于100%。
+- 将[活动临时目标](#TempTargets-activity-temp-target)设置为高于你的标准目标。
+- 如果使用SMB，请确保禁用["在高临时目标时启用SMB"](#Open-APS-features-enable-smb-with-high-temp-targets)和["始终启用SMB"](#Open-APS-features-enable-smb-always)选项。
-Pre- and post-processing of these settings is important. Make the changes in time before sport and consider the effect of muscle filling.
+这些设置的前后处理非常重要。 请在运动前及时进行调整，并考虑肌肉充血的影响。
-If you do sports regularly at the same time (i.e. sports class in your gym) you can consider using [automation](../DailyLifeWithAaps/Automations.md) for profile switch and TT. Location based automation might also be an idea but makes preprocessing more difficult.
+如果您定期在相同时间进行运动（例如健身房的体育课），可以考虑使用 [自动化](../DailyLifeWithAaps/Automations.md) 来切换配置和 TT。 基于位置的自动化也是一种选择，但会使预处理变得更加困难。
-The percentage of the profile switch, the value for your activity temp target and best time for the changes are individual. Start on the safe side if you are looking for the right value for you (start with lower percentage and higher TT).
+配置文件切换的百分比、活动临时目标值以及最佳调整时间都是因人而异的。 如果您在寻找适合自己的数值，请从安全范围开始（先使用较低百分比和较高临时目标）。
-#### Sex
+#### 性生活
-You can remove the pump to be 'free', but you should tell AAPS so that the IOB calculations are correct. See [description above](#FAQ-disconnect-pump).
+您可以摘除胰岛素泵以获得"自由"，但应告知AAPS以确保活性胰岛素(IOB)计算准确。 见<0>上面的描述。
-#### Drinking alcohol
+#### 饮酒
-Drinking alcohol is risky in closed loop mode as the algorithm cannot predict the alcohol influenced BG correctly. You have to check out your own method for treating this using the following functions in AAPS:
+在闭环模式下饮酒存在风险，因为算法无法准确预测酒精对血糖的影响。 您需要通过AAPS的以下功能来探索适合自己的处理方法：
-- Deactivating closed loop mode and treating the diabetes manually or
-- setting high temp targets and deactivating UAM to avoid the loop increasing IOB due to an unattended meal or
-- do a profile switch to noticeably less than 100%
+- 停用闭环模式并手动控制糖尿病
+- 设置较高的临时目标并停用未标记餐食(UAM)功能，以防止闭环系统因未记录的餐食而增加活性胰岛素(IOB)
+- 将配置文件切换至明显低于100%的比例
-When drinking alcohol, you always have to have an eye on your CGM to manually avoid a hypoglycemia by eating carbs.
+饮酒时，您必须始终关注连续血糖监测仪(CGM)，以便通过摄入碳水化合物来手动预防低血糖。
-#### Sleeping
+#### 睡眠
-##### How can I loop during the night without mobile and WIFI radiation?
+##### 如何在夜间运行闭环时避免手机和WiFi辐射？
-Many users turn the phone into airplane mode at night. If you want the loop to support you when you are sleeping, proceed as follows (this will only work with a local BG-source such as xDrip+ or ['Build your own Dexcom App'](#DexcomG6-if-using-g6-with-build-your-own-dexcom-app), it will NOT work if you get the BG-readings via Nightscout):
+许多用户会在夜间将手机切换至飞行模式。 如果您希望闭环系统在睡眠时继续工作，请按以下步骤操作（此方法仅适用于使用本地血糖数据源的情况，如xDrip+或['自建Dexcom应用'](#DexcomG6-if-using-g6-with-build-your-own-dexcom-app)，若通过Nightscout获取血糖读数则无法使用）：
-1. Turn on airplane mode in your mobile.
-2. Wait until the airplane mode is active.
-3. Turn on Bluetooth.
+1. 将您的手机设置为飞行模式。
+2. 等待直至飞行模式生效。
+3. 打开蓝牙。
-You are not receiving calls now, nor are you connected to the internet. But the loop is still running.
+您现在既无法接听电话，也无法连接互联网。 但闭环仍在运行。
-Some people have discovered problems with local broadcast (AAPS not receiving BG values from xDrip+) when phone is in airplane mode. Go to Settings > Inter-app settings > Identify receiver and enter `info.nightscout.androidaps`.
+一些用户发现，当手机处于飞行模式时会出现本地广播问题（AAPS无法接收来自xDrip+的血糖值数据）。 进入设置 > 应用间设置 > 识别接收器，输入 `info.nightscout.androidaps`。
-#### Travelling
+#### 旅行
-##### How to deal with time zone changes?
+##### 如何应对时区变化？
-With Dana R and Dana R Korean you don't have to do anything. For other pumps see [time zone travelling](../DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md) page for more details.
+使用 Dana R 和 Dana R Korean 无需进行任何操作。 对于其他泵，请参阅 [时区旅行](../DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md) 页面了解更多详情。
-### Medical topics
+### 医疗话题
-#### Hospitalization
+#### 住院
-If you want to share some information about AAPS and DIY looping with your clinicians, you can print out the [guide to AAPS for clinicians](../UsefulLinks/ClinicianGuideToAaps.md).
+如果您想与临床医生分享有关AAPS和DIY闭环系统的一些信息，可以打印[AAPS临床医生指南](../UsefulLinks/ClinicianGuideToAaps.md)。
-#### Medical appointment with your endocrinologist
+#### 内分泌科医生的医疗预约
-##### Reporting
+##### 报告
-You can either show your Nightscout reports (https://YOUR-NS-SITE.com/report) or check [Nightscout Reporter](https://nightscout-reporter.zreptil.de/).
+您可以选择展示您的Nightscout报告(https://YOUR-NS-SITE.com/report)，或者查看[Nightscout Reporter](https://nightscout-reporter.zreptil.de/)。
-## Frequent questions on Discord and their answers...
+## Discord上的常见问题及其解答...
-### My problem is not listed here.
+### 我的问题不在此列。
-[Information to get help.](../GettingHelp/WhereCanIGetHelp.md)
+[获取帮助的相关信息。](../GettingHelp/WhereCanIGetHelp.md)
-### My problem is not listed here but I found the solution
+### 我的问题不在列表中，但我已找到解决方法
-[Information to get help.](../GettingHelp/WhereCanIGetHelp.md)
+[获取帮助的相关信息。](../GettingHelp/WhereCanIGetHelp.md)
-**Remind us to add your solution to this list!**
+**提醒我们将您的解决方案添加到此列表中！**
-### AAPS stops everyday around the same time.
+### AAPS每天大约在同一时间停止运行。
-Stop Google Play Protect. Check for "cleaning" apps (ie CCleaner etc) and uninstall them. AAPS / 3 dots menu / About / follow the link "Keep app running in the background" to stop all battery optimizations.
+停止 Google Play Protect。 检查“清理”应用程序（例如 CCleaner 等）并卸载它们。 AAPS / 三点菜单 / 关于 / 点击"保持应用在后台运行"链接以关闭所有电池优化设置。
-### How to organize my backups ?
+### 如何整理我的备份？
-Export settings very regularly: after each pod change, after modifying your profile, when you have validated an objective, if you change your pump… Even if nothing changes, export once a month. Keep several old export files.
+请定期导出设置：每次更换Pod后、修改个人配置后、完成目标验证后，或是更换胰岛素泵时...即使没有任何改动，也请每月至少导出一次。 保留多份旧的导出文件。
-Copy on an internet drive (Dropbox, Google etc) : all the apks you used to install apps on your phone (AAPS, xDrip, BYODA, Patched LibreLink…) as well as the exported setting files from all your apps.
+请将以下文件备份至网络云盘（如Dropbox、Google等）：您手机上用于安装应用程序的所有apk文件（包括AAPS、xDrip、BYODA、Patched LibreLink等），以及从所有应用程序导出的设置文件。
-### I have problems, errors building the app.
+### 我在构建应用程序时遇到问题和错误。
-Please
+请
-- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and
-- the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po).
+- 请查看[Android Studio故障排除](../GettingHelp/TroubleshootingAndroidStudio)以了解典型错误及其解决方案。
+- 以及[逐步操作指南](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po)中的提示。
-### I'm stuck on an objective and need help.
+### 我被卡在一个目标上，需要帮助。
-Screen capture the question and answers. Post-it on the Discord AAPS channel. Don't forget to tell which options you choose (or not) and why. You'll get hints and help but you'll need to find the answers.
+截屏问题和答案。 将其发布到 Discord 的 AAPS 频道。 别忘了说明您选择的选项（或未选择的）以及原因。 您会得到提示和帮助，但您需要自己找到答案。
-### How to reset the password in AAPS v2.8.x ?
+### 如何在AAPS v2.8.x中重置密码？
-Open the hamburger menu, start the Configuration wizard and enter new password when asked. You can quit the wizard after the password phase.
+打开汉堡菜单，启动配置向导并在提示时输入新密码。 您可以在密码阶段之后退出向导。
-### How to reset the password in AAPS v3.x
+### 如何在AAPS v3.x中重置密码？
-You find the documentation [here](#Update3_0-reset-master-password).
+你可以在[这里](#Update3_0-reset-master-password)找到文档。
-### My link/pump/pod is unresponsive (RL/OL/EmaLink…)
+### 我的连接/胰岛素泵/Pod无响应（RL/OL/EmaLink等设备）
-With some phones, there are Bluetooth disconnects from the Links (RL/OL/EmaL...).
+对于某些手机，蓝牙可能会断开与链接（RL/OL/EmaL 等）的连接。
-Some also have non responsive Links (AAPS says that they are connected but the Links can't reach or command the pump.)
+部分用户还会遇到链接无响应的情况（AAPS显示设备已连接，但链接无法访问或控制胰岛素泵）。
-The easiest way to get all these parts working together is : 1/ Delete Link from AAPS 2/ Power off Link 3/ AAPS 3 dot menu, quit AAPS 4/ Long press AAPS icon, Android menu, info on app AAPS, Force stop AAPS and then Delete cache memory (Do not delete main memory !) 4bis/ Rarely some phones may need a reboot here. You can try without reboot. 5/Power on Link 6/Start AAPS 7/Pod tab, 3 dot menu, search and connect Link
+让所有部件恢复正常工作的最简单方法是： 1/ 在AAPS中删除Link连接 2/ 关闭Link设备电源 3/ 通过AAPS三点菜单退出AAPS应用 4/ 长按AAPS图标→进入Android应用信息→强制停止AAPS→清除缓存（切勿清除主存储！） 4之补充/ 少数手机可能需要在此步骤重启。 您可以尝试不重启。 5/ 开启Link设备电源 6/ 启动AAPS应用 7/ 进入Pod标签页→三点菜单→搜索并连接Link设备
-### Build error: file name too long
+### 构建错误：文件名太长
-While trying to build I get an error stating the file name is too long. Possible solutions: Move your sources to a directory closer to the root directory of your drive (e.g. "c:\src\AndroidAPS-EROS").
+尝试构建时出现文件名过长的错误。 可能的解决方案： 将您的源代码移至更靠近驱动器根目录的目录（例如 "c:\src\AndroidAPS-EROS"）。
-From Android Studio: Make sure "Gradle" is done syncing and indexing after opening the project and pulling from GitHub. Execute a Build->Clean Project before doing a Rebuild Project. Execute File->Invalidate Caches and Restart Android Studio.
+在Android Studio中： 请确保在打开项目并从GitHub拉取代码后，"Gradle"已完成同步和索引工作。 在重新构建项目之前执行 Build->Clean Project。 执行 文件→使缓存无效并重启Android Studio。
-### Alert: Running dev version. Closed loop is disabled
+### 警告：正在运行开发版本。 闭环已禁用。
-AAPS is not running in "developer mode". AAPS shows the following message: "running dev version. Closed loop is disabled".
+AAPS 未在"开发者模式"下运行。 AAPS 显示以下消息：“运行开发版本， 闭环已禁用。”
-Make sure AAPS is running in "developer mode": Place a file named "engineering_mode" at the location "AAPS/extra". Any file will do as long as it is properly named. Make sure to restart AAPS for it to find the file and go into "developer mode".
+请确保 AAPS 在"开发者模式"下运行： 在 "AAPS/extra" 目录下放置一个名为 "engineering_mode" 的文件。 任何文件都可以，只要命名正确。 确保重新启动 AAPS，以便找到文件并进入“开发者模式”。
-Hint: Make a copy of an existing logfile and rename it to "engineering_mode" (note: no file extension!).
+提示：复制一份现有的日志文件，并将其重命名为"engineering_mode"（注意：不要有文件扩展名！）。
-### Where can I find settings files?
+### 在哪里可以找到设置文件？
-Settings files will be stored on your phone's internal storage in the directory "/AAPS/preferences". WARNING: Make sure not to lose your password as without it you will not be able to import an encrypted settings file!
+设置文件将存储在您手机的内部存储中，位于"/AAPS/preferences"目录下。 警告：请务必保管好您的密码，否则将无法导入加密的设置文件！
-### How to configure battery savings?
+### 如何配置电池节能设置？
-Properly configuring Power Management is important to prevent your Phone's OS to suspend AAPS and related app's and services when your phone is not being used. As a result AAPS can not do its work and/or Bluetooth connections for sensor and Rileylink (RL) may be shut down causing "pump disconnected" alerts and communication errors. On the phone, go to settings->Apps and disable battery savings for: AAPS xDrip or BYODA/Dexcom app The Bluetooth system app (you may need to select for viewing system apps first) Alternatively, fully disable all battery savings on the phone. As a result your battery may drain faster but it is a good way to find out if battery savings is causing your problem. The way battery savings is implemented greatly depends on the phone's brand, model and/or OS version. Because of this it is almost impossible to give instructions to properly set battery savings for your setup. Experiment on what settings work best for you. For additional information, see also Don't kill my app
+正确配置电源管理非常重要，可防止手机在闲置时系统自动挂起AAPS及相关应用和服务。 这将导致AAPS无法正常工作，且传感器与Rileylink(RL)的蓝牙连接可能中断，从而触发"胰岛素泵断开"警报并引发通信错误。 在手机上进入 设置 -> 应用，并为以下应用禁用电池优化： AAPS、xDrip 或 BYODA/Dexcom 应用、蓝牙系统应用（可能需要先选择显示系统应用），或者直接完全关闭手机上的所有电池优化功能。 因此，您的电池可能会消耗得更快，但这是判断电池优化是否导致问题的有效方法。 电池节能功能的实现方式很大程度上取决于手机品牌、型号和/或操作系统版本。 由于这个原因，几乎不可能为您的具体配置提供正确设置电池优化的指导说明。 尝试调整设置，找到最适合您的配置方案。 更多信息，请参阅"Don't kill my app"。
-### Pump unreachable alerts several times a day or at night.
+### 胰岛素泵无法连接警报每天或夜间多次出现。
-Your phone may be suspending AAPS services or even Bluetooth causing it to loose connection to RL (see battery savings) Consider configuring unreachable alerts to 120 minutes by going to the top right-hand side three-dot menu, selecting Preferences->Local Alerts->Pump unreachable threshold [min].
+您的手机可能正在暂停AAPS服务甚至蓝牙功能，导致与RL的连接中断（请参阅电池优化设置部分）。 建议通过右上角三点菜单进入 偏好设置→本地警报→胰岛素泵不可达阈值[分钟]，将该值配置为120分钟。
-### Where can I delete treatments in AAPS v3 ?
+### 我可以在AAPS v3中删除治疗记录吗？
-3 dots menu, select treatments, then 3 dots menu again and you have different options available.
+点击右上角三点菜单 → 选择"治疗记录" → 再次点击三点菜单 → 即可看到可用的不同操作选项。
-### Configuring and Using the AAPSClient remote app
+### 配置和使用AAPSClient远程应用程序
-AAPS can be monitored and controlled remotely via the AAPSClient app and optionally via the associated Wear app running on Android Wear watches. Note that the AAPSClient (remote) app is distinct from the NSClient configuration in AAPS, and the AAPSClient (remote) Wear app is distinct from the AAPS Wear app--for clarity the remote apps will be referred to as 'AAPSClient remote' and 'AAPS remote Wear' apps.
+AAPS可以通过AAPSClient应用程序进行远程监控和操作，同时也可选择通过运行在Android Wear智能手表上的配套Wear应用来实现这一功能。 请注意，AAPSClient（远程）应用程序与AAPS中的NSClient配置不同，且AAPSClient（远程）Wear应用程序也不同于AAPS Wear应用程序——为明确起见，远程应用程序将被称为“AAPSClient远程”和“AAPS远程Wear”应用程序。
-To enable AAPSClient remote functionality you must: 1) Install the AAPSClient remote app (the version should match the version of AAPS being used) 2) Run the AAPSClient remote app and proceed through the configuration wizard to grant required permissions and configure access to your Nightscout site. 3) At this point you may want to disable some of the Alarm options, and/or advanced settings which log the start of the AAPSClient remote app to your Nightscout site. Once this is done, AAPSClient remote will download Profile data from your Nightscout site, the 'Overview' tab will display CGM data and some AAPS data, but but may not display graph data, and will indicate that a profile isn't yet set. 4) To activate the profile:
+要启用AAPSClient远程功能，您必须： 1）安装AAPSClient远程应用程序（版本需与使用的AAPS版本匹配）。 2）运行AAPSClient远程应用程序，按照配置向导完成必要权限授予及Nightscout站点访问配置。 3）此时您可能需要禁用部分警报选项，和/或关闭将AAPSClient远程应用启动记录到Nightscout站点的高级设置。 完成此操作后，AAPSClient远程应用将从您的Nightscout站点下载配置文件数据。"概览"选项卡将显示CGM数据和部分AAPS数据，但可能不会显示图表数据，并会提示尚未设置配置文件。 4) 激活配置：
-- Enable remote profile synchronization in AAPS > NSClient > Options
-- Activate the profile in NSClient remote > Profile After doing so, the profile will be set, and AAPSClient remote should display all data from AAPS. Hint: If the graph is still missing, try changing the graph settings to trigger an update. 5) To enable remote control by the AAPSClient, selectively enable the aspects of AAPS (Profile changes, Temp Targets, Carbs, etc.) that you would like to be able to control remotely via AAPS > NSClient > Options . Once these changes are made, you'll be able to remotely control AAPS via either Nightscout or AAPSClient remote.
+- 在 AAPS > NSClient > 选项中启用远程配置同步
+- 在NSClient远程端 > 配置文件中激活该配置文件 完成此操作后，配置文件即被设定，AAPSClient远程端将显示来自AAPS的所有数据 提示：如果图表仍然缺失，尝试更改图表设置以触发更新。 5) 要通过 AAPSClient 启用远程控制，请选择性启用 AAPS 的相关功能（配置更改、临时目标、碳水等），路径为 AAPS > NSClient > 选项。 完成这些更改后，您将能够通过 Nightscout 或 AAPSClient 远程控制 AAPS。
-If you'd like to monitor/control AAPS via the AAPSClient remote Wear App, you'll need both AAPSClient remote and the associated Wear app to be installed. To compile the AAPSClient remote Wear app, follow the standard instructions for installing/configuring the AAPS wear app, except when compiling it, choose the AAPSClient variant.
+如需通过AAPSClient远程Wear应用监控/控制AAPS，需同时安装AAPSClient远程主应用及其配套的Wear应用。 编译AAPSClient远程Wear应用时，请遵循安装/配置AAPS穿戴应用的标准说明，但在编译环节需选择AAPSClient变体版本。
-### I have a red triangle / AAPS won't enable closed loop / Loops stays in LGS / I have a yellow triangle
+### 我出现红色三角形警告 / AAPS无法启用闭环模式 / 循环始终处于LGS状态 / 我出现黄色三角形警告
-The red and yellow triangles are a security feature in AAPS v3.
+红色和黄色三角形是AAPS v3版本中的安全警示功能。
-Red triangle means that you have duplicate BGs and AAPS can't calculate precisely the deltas. You can't close the loop. You need to delete one BG of each duplicated value in order to clear the red triangle. Go to BYODA or xDRIP tab, long press one line you want to delete, check one of each lines that are doubled (or via 3 dots menu and Delete, depending on your AAPS version). You may need to reset the AAPS databases if there are too many double BGs. In this case, you'll also loose stats, IOB, COB, selected profile.
+红色三角形表示存在重复的血糖值（BGs），导致AAPS无法准确计算血糖变化率（deltas）。 无法启用闭环模式。 您需要删除每组重复血糖值中的一条记录，才能消除红色三角形警告。 进入BYODA或xDrip选项卡，长按要删除的某行数据，在重复出现的每组数据中勾选其中一条（或通过三点菜单选择删除，具体操作取决于您的AAPS版本）。 如果存在过多重复血糖值，您可能需要重置AAPS数据库。 在这种情况下，您还将丢失统计数据、活性胰岛素(IOB)、活性碳水化合物(COB)以及当前选定的配置文件。
-Possible origin of the problem: xDrip and/or NS backfilling BGs.
+问题可能源于：xDrip和/或Nightscout(NS)的血糖数据回填功能。
-The yellow triangle means unstable delay between each BG reading. You don't receive BGs every 5 min regularly or missing BGs. It is often a Libre problem. It also happens when you change G6 transmitter. If the yellow triangle is related to the G6 tansmitter change, it will go away by itself after several hours (around 24h). In case of Libre, the yellow triangle will stay. The loop can be closed and works correctly.
+黄色三角形表示各次血糖读数间存在不稳定的时间延迟。 您的血糖数据未规律性地每5分钟更新一次，或存在数据缺失。 这通常是Libre传感器的问题。 更换G6发射器时也会出现此问题。 若黄色三角警告与更换G6发射器有关，该警告将在数小时后（约24小时）自动消失。 若是Libre传感器，黄色三角警告将持续存在。 闭环功能可以正常启用并运行。
-### Can I move an active DASH Pod to other hardware?
+### 能否将运行中的DASH Pod迁移到其他硬件？
-This is possible. Note that as moving is "unsupported" and "untested" there is some risk involved. Best to try the procedure when your Pod is about to expire so when things go wrong not much is lost.
+这是可行的。 请注意，由于迁移操作属于"不受支持"且"未经测试"的行为，存在一定风险。 建议在Pod即将到期时尝试此操作，这样即使出现问题，损失也较小。
-Critical is that pump "state" (which includes it's MAC address) in AAPS and DASH match on reconnecting
+关键在于重新连接时，AAPS中的泵"状态"（包括其MAC地址）必须与DASH完全匹配。
-### Procedure I follow in this:
+### 我在此过程中遵循的操作流程如下：
-1) Suspend the DASH pump. This makes sure there are no running or queued commands active when DASH loses connection 2) Put the phone into airplane mode to disable BT (as well as WiFi and Mobile data). This way it is guaranteed AAPS and DASH can not communicate. 3) Export settings (which includes the DASH state) 4) Copy the settings file just exported from the phone (as it is in airplane mode and we do not want to change that, easiest way is using USB cable) 5) Copy the settings file to the alternate phone. 6) Import settings on the alternate phones AAPS. 7) Check the DASH tab to verify it is seeing the Pod. 8) Un-suspend the Pod. 9) Check the DASH tab and confirm it is communicating with the Pod (use the refresh button)
+1) 暂停 DASH 泵 这能确保当DASH断开连接时，系统不会执行任何正在运行或排队的指令 2）将手机切换至飞行模式以禁用蓝牙（同时关闭WiFi和移动数据） 这样就能确保AAPS和DASH无法通信。 3）导出设置（包含DASH状态）。 4）将刚导出的设置文件从手机复制出来（由于手机处于飞行模式且我们不想改变该状态，最简单的方法是使用USB数据线）。 5）将设置文件复制到备用手机上。 6) 在备用手机的 AAPS 中导入设置。 7) 检查 DASH 选项卡以验证它是否能看到 Pod。 8）取消暂停 Pod。 9）检查 DASH 选项卡并确认它是否正在与 Pod 通信（使用刷新按钮）。
-Congratulations: you did it!
+恭喜：完成了！
-*Wait!* You still have the main phone thinking it can reconnect to the same DASH:
+*等等！* 您的主手机仍然认为它可以重新连接到相同的 DASH：
-1) On the main phone choose "deactivate". This is safe because the phone has no way of communicating with DASH to actually deactivated the Pod (it is still in airplane mode) 2) Deactivation will result in a communications error - this is expected. 3) Just hit "retry" a couple of times until AAPS offers the option to "Discard" the Pod.
+1）在主手机上选择“停用”。 这很安全，因为手机无法与DASH通信来实际停用Pod（仍处于飞行模式） 2）停用操作会导致通信错误——这是预期情况。 3）只需重试几次，直到 AAPS 提供“丢弃” Pod 的选项。
-When Discarded, verify AAPS is reporting "No Active Pod". You can now safely disable airplane mode again.
+当丢弃后，验证 AAPS 是否报告“无活动 Pod”。 现在您可以安全地禁用飞行模式了。
-### How do I import settings from earlier versions of AAPS into AAPS v3 ?
+### 如何将早期版本的AAPS设置导入到AAPS v3中？
-You can only import settings (in AAPS v3) that were exported using AAPS v2.8x or v3.x. If you were using a version of AAPS older than v2.8x or you need to use setting exports older than v2.8x, then you need to install AAPS v2.8 first. Import the older settings of v2.x in v2.8. After checking that all is OK, you can export settings from v2.8. Install AAPS v3 and import v2.8 settings in v3.
+您只能导入通过AAPS v2.8x或v3.x版本导出的设置（在AAPS v3中）。如果您之前使用的AAPS版本低于v2.8x，或者需要使用v2.8x之前的设置导出文件，则需要先安装AAPS v2.8版本。 在 v2.x 中导入旧设置到 v2.8。检查一切正常后，可以从 v2.8 导出设置。安装 AAPS v3，并在 v3 中导入 v2.8 设置。
-If you use the same key to build v2.8 and v3, you won't even have to import settings. You can install v3 over v2.8.
+如果您使用相同的密钥构建 v2.8 和 v3，则甚至不需要导入设置。 您可以直接在 v2.8 上安装 v3。
-There were some new objectives added. You'll need to validate them.
\ No newline at end of file
+添加了一些新的目标。 您需要验证它们。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/UsefulLinks/Glossary.md b/docs/CROWDIN/zh_CN/UsefulLinks/Glossary.md
index 24e958a09fc0..418a96d6c81e 100644
--- a/docs/CROWDIN/zh_CN/UsefulLinks/Glossary.md
+++ b/docs/CROWDIN/zh_CN/UsefulLinks/Glossary.md
@@ -1,145 +1,145 @@
-# Glossary
+# 术语表
-**AAPS** = AndroidAPS is the name of the Android app.
+**AAPS** = AndroidAPS 是 Android 应用程序的名称。
-**AAPSClient** (or **NSClient**) = a remote control feature that can be used by caregivers via a follower phone to follow a user’s **AAPS** by connecting to the user’s **Nightscout's** site. Further info → Wiki - 'NS Client'. Objectives learning program within **AAPS** provides step by step guidance. Further info → Wiki - 'objectives'.
+**AAPSClient**（或 **NSClient**） = 远程控制功能，护理人员可以通过跟随手机连接到用户的 **Nightscout** 网站来跟踪用户的 **AAPS**。 更多信息 → 维基 - 'NS Client'。 在 **AAPS** 中的目标学习程序提供逐步指导。 更多信息 → 维基 - '目标'。
-**APS** = Artificial Pancreas System.
+**APS** = 人工胰腺系统，Artificial Pancreas System。
-**AMA** = Advanced Meal Assist. An algorithm which allows **AAPS** to increase the user’s basal more aggressively after a meal bolus. Further info → Wiki - 'AMA'.
+**AMA** = 高级膳食助理。 一种算法，允许**AAPS**在餐后大剂量注射后更积极地增加用户的基础率。 更多信息 → 维基 - 'AMA'。
-**Adjustment Factor** = used within **DynamicISF** and is a value set within a user's **Preferences** between 1% and 300%. This acts as a multiplier on the **TDD** value.
+**调整系数** = 用于**动态胰岛素敏感系数**功能，是用户在**偏好设置**中设定的1%至300%之间的数值。 这相当于对**总日剂量(TDD)**值设置了一个乘数因子。
-- increasing the **Adjustment Factor** value above 100 % makes **DynamicISF** more aggressive: the **ISF** values become smaller (i.e. more insulin required to decrease **BG** levels a small amount)
-- lowering the **Adjustment Factor** value under 100% makes **DynamicISF** less aggressive: the **ISF** values become larger (i.e. less insulin required to decrease **BG** levels a small amount).
+- 将**调整系数**提高到100%以上会使**动态胰岛素敏感系数**更激进：**胰岛素敏感系数(ISF)**值会变小（即需要更多胰岛素来少量降低**血糖(BG)**水平）
+- 将**调整系数**降至100%以下会使**动态胰岛素敏感系数**趋于保守：**胰岛素敏感系数(ISF)**值会增大（即需要更少胰岛素即可少量降低**血糖(BG)**水平）。
-**Android Auto** = a system used to host certain functions of an Android smartphone’s features, including **AAPS**, within a car's display. Further info → Wiki - 'android auto'.
+**Android Auto** = 一种车载系统，可在汽车显示屏上运行Android智能手机的特定功能（包括**AAPS**）。 更多信息 → 维基 - 'android auto'。
-**APK** = Android application Package. A software installation file. Further info → Wiki - 'Building APK'.
+**APK** = Android 应用程序包。 一个软件安装文件。 更多信息 → 维基 - '构建 APK'。
-**Autosens** = calculation of sensitivity to insulin between a period of a 24 and 8 hour window etc. Further info → DIABETTECH - **Autosens**.
+**Autosens** = 计算 24 小时到 8 小时窗口之间的胰岛素敏感性等。 更多信息 → DIABETTECH - **Autosens**。
-**Azure** = cloud computing platform to host **Nightscout** web app Azure → see also **Nightscout**.
+**Azure** = 云计算平台，用于托管 **Nightscout** 网页应用程序 Azure → 参见 **Nightscout**。
-**BAT** = status light low battery on **AAPS’** home screen **Preferences**, Screenshots → see also **CAN** / **RES** / **SEN**.
+**BAT** = 在 **AAPS** 的主屏幕上显示低电量状态灯 **偏好设置**，截图 → 参见 **CAN** / **RES** / **SEN**。
-**BG** = blood glucose.
+**BG** = 血糖。
-**BGI** = blood glucose impact. The degree to which **BG** 'should' rise or fall based on insulin activity alone.
+**BGI** = 血糖影响。 **血糖(BG)**仅基于胰岛素作用"应当"升高或降低的程度。
-**BG source** = the source of the user’s **BG** values derived from either **CGM** or **FGM** through a system integration software like **BYODA**, **xDrip+** etc. Further info → Wiki - 'BG source'
+**血糖数据源** = 用户**血糖(BG)**值的来源，通过**BYODA**、**xDrip+**等系统集成软件从**连续血糖监测(CGM)**或**闪速葡萄糖监测(FGM)**设备获取。 更多信息 → 维基 - 'BG 来源'
-**Bridge** = an additional device transforming **FGM** to **CGM**.
+**桥接** = 一个额外的设备，将 **FGM** 转换为 **CGM**。
-**BR** = Basal Rate. The amount of insulin in a given time block to maintain **BG** at a stable level. → see also **IC** / **ISF**.
+**BR** = 基础率。 基础率 = 在特定时间段内维持**血糖(BG)**稳定水平所需的胰岛素量。 → 参见 **IC** / **ISF**。
-**BYODA** = Build Your Own Dexcom App. A way to generate the user’s own Dexcom App for reading out the sensor data Dexcom G6.
+**BYODA** = 构建您自己的 Dexcom 应用。 一种生成用户自有 Dexcom 应用程序的方式，用于读取 Dexcom G6 的传感器数据。
-**CAGE** = Cannula AGE. Displayed on **AAPS’** homescreen and Nightscout providing the user’s information entered in the Actions tab / menu → see also **Nightscout**.
+**CAGE** = 导管年龄。 在 **AAPS** 的主屏幕和 Nightscout 上显示，提供用户在操作标签/菜单中输入的信息 → 参见 **Nightscout**。
-**CAN** = status light overdue cannula change on the **AAPS’** homescreen **Preferences'** → see also **BAT** / **RES** / **SEN**.
+**CAN** = **AAPS**主屏幕上的"管路更换超期"状态指示灯（位于**偏好设置**中）→ 另请参阅**BAT**(电池)/**RES**(储药器)/**SEN**(传感器)状态指示。
-**CGM** = Continuous Glucose Monitor → see also **FGM**.
+**CGM** = 连续血糖监测器 → 参见 **FGM**。
-**Closed Loop** = a closed loop system which makes automatic adjustments to the user’s basal delivery based on an **AAPS’s** algorithm and the user’s **Profile** settings without requiring the user’s-approval. Further info → Wiki - 'closed loop'.
+**闭环** = 一个闭环系统，根据 **AAPS** 的算法和用户的 **配置文件** 设置，自动调整用户的基础胰岛素输送，无需用户批准。 更多信息 → 维基 - '闭环'。
-**COB** = Carbs On Board. This is the amount of carbohydrates currently available for the user's digestion → see also IOB.
+**COB** = 活性碳水化合物量。 这是用户当前可供消化的碳水化合物量 → 参见 IOB。
-**CSF** =Carbs Sensitivity Factor. i.e. how much does the user’s **BG** increase for 1g of carbs absorbed.
+**CSF** = 碳水系数。 即：用户的 **BG** 在吸收 1 克碳水化合物后会增加多少。
-**DIA** = Duration of Insulin Action. Further info → Wiki - 'insulin types' and see also → DIABETTECH - 'DIA'.
+**DIA** = 胰岛素作用持续时间 更多信息 → 维基 - '胰岛素类型'，另见 → DIABETTECH - 'DIA'.
-**DST** = Daylight Savings Time Wiki DST.
+**DST** = 夏令时 维基 DST。
-**Dynamic ISF (or DynISF)** = a feature within **AAPS** that adapts the insulin sensitivity factor (**ISF**) dynamically based on the user’s:
+**动态胰岛素敏感系数（Dynamic ISF或DynISF）** = **AAPS**中的一项功能，可根据用户的以下因素动态调整胰岛素敏感系数(**ISF**)：
-- Total Daily Dose of insulin (**TDD**); and
-- current and predicted **BG** values.
+- **每日胰岛素总剂量（Total Daily Dose of insulin, TDD）**
+- 当前及预测的**血糖(BG)**值。
-**eCarbs** = extended Carbs. Carbs split up over several hours to accommodate/protein and permits **AAPS** to deliver extended boluses. Further info → Wiki - 'eCarbs', 'eCarbs use'.
+**缓释碳水化合物(eCarbs)** = 延时释放的碳水化合物(extended Carbs)。 将碳水化合物分配至数小时摄入，用以匹配蛋白质吸收，并允许**AAPS**进行扩展大剂量输注。 更多信息 → 维基 - 'eCarbs'，'eCarbs 使用'。
-**FGM** = Flash Glucose Monitor manufactured by Freestyle Libre. Further info → Wiki - 'BG source' and see also 'CGM'.
+**FGM** = 由Freestyle Libre生产的闪速葡萄糖监测仪(Flash Glucose Monitor)。 更多信息 → 维基 - 'BG 来源'，另见 'CGM'。
-**git** = a tool used store and download the **AAPS’** source code.
+**git** = 一种用于存储和下载 **AAPS** 源代码的工具。
-**GitHub** = a web-based hosting service and build process for the **AAPS’** software version-control system for tracking changes in computer files and coordinating work on those files especially for teams. It is also necessary for **APK** updates. Further info → Wiki - 'update APK'.
+**GitHub** = 一个基于网络的托管服务和构建流程，专为**AAPS**软件版本控制系统设计，用于追踪计算机文件的变更并协调团队对这些文件的协作工作。 它对于 **APK** 更新也是必需的。 更多信息 → 维基 - '更新 APK'。
-**Glimp** = an app to collect values from Freestyle Libre Glimp.
+**Glimp** = 用于收集 Freestyle Libre Glimp 数据的应用。
-**IC (or I:C)** = Insulin to Carb ratio. (i.e. how many carbs are covered by one unit of insulin?).
+**IC (或 I:C)** = 胰岛素与碳水化合物比率。 （即：一单位胰岛素可以覆盖多少碳水化合物？）
-**IOB** = Insulin On Board. Insulin active in the user’s body.
+**IOB** = 活性胰岛素，Insulin On Board。 用户体内的活性胰岛素。
-**ISF** = Insulin Sensitivity Factor. The expected decrease in BG as a result of one unit of insulin.
+**ISF** = 胰岛素敏感性因子。 一单位胰岛素预计会减少的血糖量。
-**LGS** = Low Glucose Suspend. **AAPS** will reduce basal if **BG** is dropping and if **BG** is rising, then it will only increase basal if **IOB** is negative (from a previous **LGS**), otherwise basal rates will remain the same as the user’s selected **Profile**. The user may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. → see also objective 6.
+**LGS** = 低血糖暂停。 如果 **BG** 下降，**AAPS** 将减少基础胰岛素；如果 **BG** 上升，则只有当 **IOB** 为负时（来自之前的 **LGS**）才会增加基础胰岛素，否则基础胰岛素将保持用户选择的 **配置文件** 设置。 用户可能在处理低血糖后暂时出现血糖飙升，且在反弹期无法增加基础胰岛素量。 → 另见目标 6。
-**LineageOS** = free and open-source operating system for smartphones etc. (When using Accu-Chek Combo see Wiki - Combo pump).
+**LineageOS** = 用于智能手机等设备的免费开源操作系统。 （使用 Accu-Chek Combo 时请参见维基 - Combo 泵）。
-**Log files** = **AAPS’** records of the user's actions (useful for troubleshooting and debugging). Further info → Wiki - 'log files'.
+**Log 文件** = **AAPS’** 记录用户操作的文件（用于故障排除和调试）。 更多信息 → 维基 - '日志文件'。
-**maxIOB** = maximum total IOB. This is a safety feature and prevents **AAPS** delivering insulin over the user’s settings. Further info → Wiki - 'SMB'.
+**maxIOB** = 活性胰岛素总量上限。 这是一项安全功能，可防止**AAPS**超出用户设定值输送胰岛素。 更多信息 → 维基 - 'SMB'。
-**min_5m_carbimpact** = safety feature that is a calculation of default carb decay when carb absorption cannot be determined based on the user’s blood’s reactions. This is a safety feature. Further info → Wiki - 'config builder'.
+**min_5m_carbimpact** = 安全功能参数，当系统无法根据使用者的血糖反应确定碳水化合物吸收率时，该参数将作为默认碳水化合物衰减率的计算基准。 这是一个安全功能。 更多信息 → 维基 - '配置构建器'。
-**Nightscout** = open source project to access and report **CGM** data. The central data hub for the user’ **AAPS** data and can generate reports to view the user’s historical **NIghtscout** data expected HbA1c, time in range) or search for patterns in the data via percentile chart etc.
+**Nightscout** = 开源项目，用于访问和报告 **CGM** 数据。 用户**AAPS**数据的核心处理中心，可生成报告用于查看用户在**Nightscout**中的历史数据（包括预期糖化血红蛋白HbA1c、达标时间等），或通过百分位图表等方式分析数据规律。
-**Nightscout** → see also **Nightscout Reporter**. This is particularly useful for parents following their child's diabetes management.
+**Nightscout** → 另见 **Nightscout Reporter**。 这对于跟踪儿童糖尿病管理的父母特别有用。
-**Nightscout Reporter Tool** = a tool which generates PDFs reports from Nightscout web app data. See 'Nightscout Reporter', 'NS Reporter' @ Facebook.
+**Nightscout Reporter 工具** = 从 Nightscout 网页应用程序数据生成 PDF 报告的工具。 参见 'Nightscout Reporter'，'NS Reporter' @ Facebook。
-**NSClient** ( or **‘AAPSClient’)** = see **AAPSClient**.
+**NSClient**（或 **‘AAPSClient’**） = 见**AAPSClient**。
-**OpenAPS** = Open Artificial Pancreas System.
+**OpenAPS** = 开放人工胰腺系统。
-**Open Loop system** = an **AAPS** feature that will recommend adjustments and which must be performed manually by the user on **AAPS**. Further info → Wiki - 'config builder'.
+**开环系统** = **AAPS**的一项功能，它会推荐调整方案，但需要用户在**AAPS**上手动执行这些调整。 更多信息 → 维基 - '配置构建器'。
-**Oref0 / Oref1** = sensitivity detection and "reference design implementation version 0/1". It is the key algorithm behind OpenAPS Wiki - sensitivity detection.
+**Oref0 / Oref1** = 敏感性检测及"参考设计实现版本0/1"。 它是 OpenAPS 背后的关键算法 维基 - 敏感性检测
-**Peak time** = time of maximum effect of insulin given. Further info → Wiki - 'config builder'.
+**峰值时间** = 胰岛素的最大效应时间。 更多信息 → 维基 - '配置构建器'。
-**PH** = Pump History. This can be accessed in **AAPS’** treatments which are located on the 3 dot menu on the right side of **AAPS** main screen Screenshots.
+**PH** = 泵历史记录。 可以在 **AAPS’** 治疗记录中访问，位于 **AAPS** 主屏幕右侧的三点菜单中 截图。
-**Predictions** = predictions for **BG** in the future based on different calculations. Further info → Wiki - 'prediction lines'.
+**Predictions** = 基于不同计算方法预测未来的**BG**值。 更多信息 → Wiki - '预测曲线'。
-**Profile** = the user’s basic treatment settings (basal rate, **DIA**, **IC**, **ISF**, **BG** target). AAPSv3 only supports local profiles created within **AAPS** but **Nightscout** **Profiles** can be copied (synchronised) to **AAPS**. Further info → Wiki - 'profile'.
+**Profile** = 用户的基本治疗设置（基础率、**DIA**、**IC**、**ISF**、**BG**目标）。 AAPSv3仅支持在**AAPS**内创建的本地档案，但可以将**Nightscout** **Profiles**复制（同步）到**AAPS**。 更多信息 → Wiki - '档案'。
-**Profile switch** = (temporary) switch of the user’ **Profile** to a different **Profile** saved within **AAPS**.
+**Profile switch** = 将用户的**Profile**（暂时）切换为存储在**AAPS**中的不同**Profile**。
-**Profile Percentage** = a (temporary_ percentage increase or decrease applied to a user’s **Profile** for a selected time period.
+**Profile Percentage** = 在选定的时间段内，对用户的**Profile**应用（暂时的）百分比增加或减少。
-**RES** = status light overdue reservoir change on the **AAPS’** homescreen Preferences, Screenshots → see also **BAT** / **CAN** / **SEN**.
+**RES** = 在**AAPS**主屏幕上的状态灯提醒更换过期储药器。 首选项、屏幕截图 → 参见**BAT** / **CAN** / **SEN**。
-**RileyLink** = open source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz (used for old Medtronic pumps) or 433MHz (used for Omnipod Eros pumps) wireless communication RileyLink.
+**RileyLink** = 开源硬件设备，用于桥接蓝牙低功耗（BLE）与916MHz（旧款美敦力泵使用）或433MHz（Omnipod Eros泵使用）无线通信。
-**SAGE** = sensor age. This is displayed on the homescreen of **AAPS** and in **Nightscout** if information was entered in the Actions tab / menu → see also **Nightscout**.
+**SAGE** = 传感器使用时间。 如果在操作选项卡/菜单中输入信息，则会显示在**AAPS**主屏幕和**Nightscout**中 → 参见**Nightscout**。
-**SEN** = status light sensor change on home screen Preferences, Screenshots → see also **BAT** / **CAN** / **RES**.
+**SEN** = 主屏幕首选项中的传感器状态指示灯变化（截图请参见相关设置）→ 另见**BAT**/**CAN**/**RES**条目
-**Sensivity detection** = calculation of sensitivity to insulin as a result of exercise, hormones etc. see also → DIABETTECH - 'Autosens'.
+**Sensivity detection** = 计算由于运动、荷尔蒙等引起的胰岛素敏感性变化。 参见 → DIABETTECH - 'Autosens'。
-**Sensor noise** = a term used to describe the unstable **CGM’s** readings leading to "jumping" **BG** values. Further info → Wiki - 'sensor noise'.
+**Sensor noise** = 描述**CGM**读取值不稳定导致**BG**值“跳动”的术语。 更多信息 → Wiki - '传感器噪声'。
-**SMB** = Super Micro Bolus. An **AAPS** feature for faster insulin delivery in order to adjust **BG**. Further info → Wiki - '**SMB**' and see also **UAM**.
+**SMB** = 超微大剂量（Super Micro Bolus）。 **AAPS**的一项功能，用于快速注射胰岛素以调整**BG**。 更多信息 → Wiki - '**SMB**'，参见**UAM**。
-**Super bolus** = shift of basal to bolus insulin for faster **BG** adjustment.
+**Super bolus** = 超级大剂量，将基础胰岛素调整为餐前胰岛素以更快速地调整**BG**。
-**TBB** = total base basal (sum of basal rate within 24 hours) → see also **TBR** / **TDD**.
+**TBB** = 总基础胰岛素（24小时基础率总和） → 参见**TBR** / **TDD**。
-**TBR** = temporary basal rate→ see also **TBB** / **TDD**.
+**TBR** = 暂时基础率 → 参见**TBB** / **TDD**。
-**TDD** = total daily dose (bolus + basal per day) → see also **TBB** / **TBR**.
+**TDD** = 每日总剂量（每日餐前胰岛素+基础胰岛素） → 参见**TBB** / **TBR**。
-**TT** = temporary target temporary increase/decrease of the user’s **BG** target (range) e.g. for eating or sport activities. Further info → Wiki - 'temp targets'.
+**TT** = 暂时目标，暂时增加/减少用户的**BG**目标（范围），例如用于进食或运动。 更多信息 → Wiki - '临时目标'。
-**UAM** = unannounced meals. Detection of significant increase in **BG** levels due to meals, adrenaline or other influences and attempt to adjust this. Further info → Wiki - 'UAM' and see also **SMB**.
+**UAM** = 未报告的进食。 检测因饮食、肾上腺素或其他因素导致的**血糖**水平显著升高，并尝试对此进行调整。 更多信息 → Wiki - 'UAM'，参见**SMB**。
-**Virtual pump** = an **AAPS** feature which allows the user to try **AAPS’** functions or for PWD using a pump model with no **AAPS** driver for looping → see also **Open Loop**.
+**Virtual pump，虚拟泵** = **AAPS**的一项功能，允许用户试用**AAPS**的功能，或供使用无**AAPS**闭环驱动泵型的糖尿病患者使用 → 另见**开环系统**。
-**Wallpaper** = **AAPS** background image see phones page.
+**Wallpaper** = **AAPS**背景图片，参见手机页面。
-**xDrip+** = open source software to read **CGM** systems xDrip+.
+**xDrip+** = 开源软件，用于读取**CGM**系统 xDrip+。
-**Zero-temp** = temporary basal rate with 0% (no basal insulin delivery).
+**Zero-temp** = 暂时基础率为0%（无基础胰岛素注射）。
-→ see also [the OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html)
\ No newline at end of file
+→ 参见[OpenAPS文档](https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html)
\ No newline at end of file