Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Global i18n 0% 98% 7 66 463 1 76 0 0
Glossary Immersive Document Translation 0% 0% 4 8 85 4 0 0 0
Immersive Translate Document App 0% 99% 6 23 206 3 117 0 0
Official 0% 99% 1 53 393 0 157 0 0
Official Footer 0% 0 0 0 0 22 0 0
Official Navbar 0% 0 0 0 0 18 0 0

Overview

Project website app.immersivetranslate.com
Instructions for translators

Immersive Translate Document Translation
Project maintainers User avatar theowenyoung User avatar zhoulink90 User avatar marshmolly2b
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,955 20,393 141,224
Approved 0% 0 0% 0 0% 0
Waiting for review 99% 1,937 99% 20,243 99% 140,077
Translated 99% 1,937 99% 20,243 99% 140,077
Needs editing 1% 10 1% 118 1% 853
Read-only 0% 0 0% 0 0% 0
Failing checks 19% 390 23% 4,732 22% 31,920
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 8 1% 32 1% 294
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1,612 changes 0 changes 0 changes 0 changes 367 changes 0 changes 221 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

20,393
Hosted words
1,955
Hosted strings
99%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+11%
Hosted words
+100%
+10%
Hosted strings
+100%
−1%
Translated
+99%
−100%
Contributors
+100%
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Global i18n
  3. Chinese (Simplified)
The “global-i18n/zh-CN.json” file was changed. yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Global i18n
  3. Chinese (Simplified)
Currently, OpenAI uses gpt-4.1-mini, Claude uses claude-3-5-haiku-20241022, Gemini uses gemini-2.5-flash, Zhipu uses glm-4-plus, and DeepSeek uses DeepSeek V3 0324
目前，OpenAI 使用 gpt-4.1-mini, Claude 使用 claude-3-5-haiku-20241022, Gemini 使用 gemini-2.05-flash, 智谱使用 glm-4-plus, DeepSeek 使用 DeepSeek V3 0324
yesterday
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Official
  3. Chinese (Simplified)
The “official/i18n/zh-Hans/code.json” file was changed. yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Official
  3. Chinese (Simplified)
AO3,Immersive Translate,Immersive Translate Plugin,Immersive Translate Official Website
AoO3,沉浸式翻译,沉浸式翻译插件,沉浸式翻译官网
yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Official
  3. Chinese (Simplified)
AO3 - Immersive Translate
AoO3 - 沉浸式翻译
yesterday
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Global i18n
  3. Chinese (Simplified)
The “global-i18n/zh-CN.json” file was changed. yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Global i18n
  3. Chinese (Simplified)
AO3
AoO3
yesterday
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Immersive Translate Document App
  3. Chinese (Simplified)
The “app/src/i18n/zh-CN.json” file was changed. 2 days ago
User avatar None

String added in the repository

  1. Immersive Translate Site
  2. Immersive Translate Document App
  3. Chinese (Simplified)
<ol><li>Security Risk: BabelDOC uses a backend translation architecture, and if custom APIs are allowed, users must submit their API Key to the backend. This not only involves key security issues but also risks malicious attacks (such as DDoS) due to the exposure of backend server IPs, severely affecting service stability.</li><li>Network Uncertainty: The backend needs to actively access the API provided by the user, which may cause the overall translation process to be abnormal due to network delays, cross-regional access failures, or unstable intermediate links.</li><li>Uncontrollable Performance: BabelDOC's backend may issue hundreds of concurrent requests per second. We cannot predict the processing capacity of user APIs, and if the concurrency capacity is low, it will directly affect the overall translation speed and stability.</li><li>Disproportionate Resource Costs: If delays occur due to insufficient performance of user-customized APIs, the system will need to allocate additional computing resources for compensation. This will lead to resource wastage, and there is currently no reasonable way to account for costs and share charges.</li><li>High Architectural Complexity: If custom APIs are called via frontend relay, it will introduce more network hops and reliability challenges, and have a significant negative impact on performance, stability, and user experience.</li></ol><br/>In conclusion, BabelDOC will not support the integration of custom APIs at this stage. Our current focus is on continuously improving the translation quality and stability of BabelDOC. In the future, as the system matures, we will further explore and evaluate more flexible business models and possibilities for functional expansion.
<ol><li>安全性风险：BabelDOC 采用后端翻译架构，若允许自定义 API，用户需将 API Key 提交至后端。这不仅涉及密钥安全问题，还存在因暴露后端服务器 IP 而可能被恶意攻击（如 DDoS）的风险，严重影响服务稳定性。</li><li>网络不确定性：后端需主动访问用户提供的 API，可能因网络延迟、跨地域访问失败或中间链路不稳定，导致整体翻译流程异常。</li><li>性能不可控：BabelDOC 后端每秒可能发出上百个并发请求。我们无法预测用户 API 的处理能力，一旦并发能力较低，将直接影响整体翻译速度与稳定性。</li><li>资源成本不对等：若因用户自定义 API 性能不足导致任务延迟，系统需额外分配算力资源进行补偿。这将造成资源浪费，而现阶段并无合理方式进行成本核算与收费分摊。</li><li>架构复杂度高：如通过前端中转调用自定义 API，则会引入更多网络跳数和可靠性挑战，并对性能、稳定性及用户体验造成重大负面影响。</li></ol><br/>综上，BabelDOC 在现阶段不会支持自定义 API 的接入。我们当前的重点是持续提升 BabelDOC 的翻译质量与稳定性。未来在系统更加成熟之后，我们会进一步探索和评估更灵活的商业模式与功能拓展可能。
2 days ago
User avatar None

String added in the repository

  1. Immersive Translate Site
  2. Immersive Translate Document App
  3. Chinese (Simplified)
Why doesn't BabelDOC support custom APIs?
为什么 BabelDOC 不支持自定义 API？
2 days ago
Browse all changes for this language