Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
admin AGPL-3.0 1% 550 3,965 24,598 550 2 0 0
core AGPL-3.0 1% 804 9,666 63,328 804 2 0 0
moulinette AGPL-3.0 4% 43 265 1,675 43 0 0 0
portal AGPL-3.0 42% 33 154 947 33 2 0 0
readme-generator 0% 39 274 2,144 39 0 0 0
SSOwat AGPL-3.0 0 0 0 0 2 0 0
store AGPL-3.0 0% 154 987 6,286 154 0 0 0
Glossary YunoHost AGPL-3.0 0 0 0 0 0 0 0

Overview

Project website yunohost.org
Translation license AGPL-3.0 moulinette SSOwat portal store core admin YunoHost
9 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,704 15,651 101,113
Translated 4% 81 2% 340 2% 2,135
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 8 1% 194 1% 1,179
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 95% 1,623 97% 15,311 97% 98,978
Last 12 months Previous

Activity in last 12 months

0 changes 22 changes 27 changes 0 changes 1 change 18 changes 103 changes 3 changes 93 changes 3 changes 16 changes 3 changes 85 changes 74 changes 18 changes 105 changes 8 changes 176 changes 1 change 7 changes 0 changes 61 changes 9 changes 8 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

15,651
Hosted words
1,704
Hosted strings
4%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+2%
Hosted words
+100%
+1%
Hosted strings
+100%
—
Translated
+4%
−100%
Contributors
+100%
User avatar None

Resource updated

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
The "locales/en.json" file was changed. 9 days ago
User avatar None

String updated in the repository

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
Your system is not fully up-to-date. Please perform a regular upgrade before running the migration to Bookworm.
 
9 days ago
User avatar None

Resource updated

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
The "locales/en.json" file was changed. 2 weeks ago
User avatar None

Resource updated

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
The "locales/en.json" file was changed. 2 weeks ago
User avatar None

String updated in the repository

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
Something went wrong during the main upgrade, the system appears to still be on Debian Bullseye.
 
2 weeks ago
User avatar None

String updated in the repository

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
Starting migration to Bookworm…
 
2 weeks ago
User avatar None

String updated in the repository

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
Patching the sources.lists file…
 
2 weeks ago
User avatar None

String updated in the repository

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
The current Debian distribution is not Bullseye! If you already ran the Bullseye -> Bookworm migration, then this error is symptomatic of the fact that the migration procedure was not 100% succesful (otherwise YunoHost would have flagged it as completed). It is recommended to investigate what happened with the support team, who will need the **full** log of the migration, which can be found in Tools > Logs in the webadmin.
 
2 weeks ago
User avatar None

String updated in the repository

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
Please note that this migration is a delicate operation. The YunoHost team did its best to review and test it, but the migration might still break parts of the system or its apps.

Therefore, it is recommended to:
- Perform a backup of any critical data or app. More info on https://yunohost.org/backup;
- Be patient after launching the migration: Depending on your Internet connection and hardware, it might take up to a few hours for everything to upgrade properly.
 
2 weeks ago
User avatar None

String updated in the repository

  1. YunoHost
  2. core
  3. Bengali (Bangladesh)
The current Debian distribution is not Buster! If you already ran the Buster -> Bullseye migration, then this error is symptomatic of the fact that the migration procedure was not 100% succesful (otherwise YunoHost would have flagged it as completed). It is recommended to investigate what happened with the support team, who will need the **full** log of the migration, which can be found in Tools > Logs in the webadmin.
 
2 weeks ago
Browse all changes for this language