Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Global i18n 0% 99% 2 9 75 0 103 0 0
Glossary Immersive Document Translation 0% 0% 4 8 85 4 0 0 0
Immersive Translate Document App 0% 99% 4 17 152 3 104 0 0
Official 0% 96% 24 151 947 2 160 0 0
Official Footer 0% 0 0 0 0 21 0 0
Official Navbar 0% 0 0 0 0 26 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 98% 1,921 99% 20,208 99% 139,965
Translated 98% 1,921 99% 20,208 99% 139,965
Needs editing 1% 25 1% 151 1% 933
Read-only 0% 0 0% 0 0% 0
Failing checks 21% 414 19% 4,011 19% 27,530
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 9 1% 34 1% 326
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,011 changes 0 changes 0 changes 0 changes 929 changes 0 changes 242 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

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

Trends of last 30 days

+45%
Hosted words
+100%
+47%
Hosted strings
+100%
−1%
Translated
+99%
—
Contributors
+100%
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Global i18n
  3. Spanish
The “global-i18n/es-ES.json” file was changed. yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Global i18n
  3. Spanish
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
Actualmente, OpenAI utiliza gpt-4.1-mini, Claude utiliza claude-3-5-haiku-20241022, Gemini utiliza gemini-2.05-flash, Zhipu utiliza glm-4-plus y DeepSeek utiliza DeepSeek V3 0324.
yesterday
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Official
  3. Spanish
The “official/i18n/es-ES/code.json” file was changed. yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Official
  3. Spanish
AO3,Immersive Translate,Immersive Translate Plugin,Immersive Translate Official Website
AoO3, Immersive Translate, Plugin de Immersive Translate, Sitio Oficial de Immersive Translate
yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Official
  3. Spanish
AO3 - Immersive Translate
AoO3 - Traducción Inmersiva
yesterday
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Global i18n
  3. Spanish
The “global-i18n/es-ES.json” file was changed. yesterday
User avatar None

String updated in the repository

  1. Immersive Translate Site
  2. Global i18n
  3. Spanish
AO3
AoO3
yesterday
User avatar None

Resource updated

  1. Immersive Translate Site
  2. Immersive Translate Document App
  3. Spanish
The “app/src/i18n/es.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. Spanish
<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>Riesgos de seguridad: BabelDOC utiliza una arquitectura de traducción de backend, y si se permite la API personalizada, los usuarios deben enviar la clave API al backend. Esto no solo implica problemas de seguridad de la clave, sino que también existe el riesgo de ataques maliciosos (como DDoS) debido a la exposición de la IP del servidor backend, afectando gravemente la estabilidad del servicio.</li><li>Incertidumbre de la red: el backend necesita acceder activamente a la API proporcionada por el usuario, lo que puede causar anomalías en el proceso de traducción completo debido a retrasos en la red, fallos de acceso transregional o inestabilidad en los enlaces intermedios.</li><li>Rendimiento incontrolable: el backend de BabelDOC puede emitir cientos de solicitudes concurrentes por segundo. No podemos predecir la capacidad de procesamiento de la API del usuario, y si la capacidad concurrente es baja, afectará directamente la velocidad y estabilidad de la traducción general.</li><li>Costos de recursos desiguales: si el rendimiento insuficiente de la API personalizada del usuario causa retrasos en las tareas, el sistema necesita asignar recursos de computación adicionales para compensar. Esto resultará en un desperdicio de recursos, y actualmente no hay una manera razonable de realizar la contabilidad de costos y la distribución de cargos.</li><li>Alta complejidad de la arquitectura: si se llama a la API personalizada a través de un intermediario en el frontend, esto introducirá más saltos de red y desafíos de fiabilidad, y tendrá un impacto negativo significativo en el rendimiento, la estabilidad y la experiencia del usuario.</li></ol><br/>En resumen, BabelDOC no admitirá la integración de API personalizadas en la etapa actual. Nuestro enfoque actual es continuar mejorando la calidad y estabilidad de la traducción de BabelDOC. En el futuro, cuando el sistema sea más maduro, exploraremos y evaluaremos más a fondo modelos comerciales flexibles y posibilidades de expansión de funciones.
2 days ago
User avatar None

String added in the repository

  1. Immersive Translate Site
  2. Immersive Translate Document App
  3. Spanish
Why doesn't BabelDOC support custom APIs?
¿Por qué BabelDOC no admite API personalizadas?
2 days ago
Browse all changes for this language