Language Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Arabic GPL-3.0 23% 23% 13 350 2,374 13 1 0 0
Bulgarian GPL-3.0 5% 5% 16 356 2,449 16 0 0 0
Catalan GPL-3.0 0 0 0 0 0 0 0
Chinese (Taiwan) (zh_TW) GPL-3.0 23% 58% 7 178 1,228 1 4 0 0
Chinese (zh) GPL-3.0 23% 23% 13 350 2,374 13 1 0 0
English GPL-3.0 0 0 0 0 3 0 0
French GPL-3.0 0 0 0 0 0 0 0
German GPL-3.0 70% 0 0 0 0 1 0 0
Indonesian GPL-3.0 23% 23% 13 350 2,374 13 0 0 0
Italian GPL-3.0 23% 23% 13 350 2,374 13 1 0 0
Persian GPL-3.0 23% 76% 4 164 1,140 0 0 0 0
Polish GPL-3.0 23% 23% 13 350 2,374 13 2 0 0
Portuguese GPL-3.0 11% 23% 13 350 2,374 13 0 13 0
Russian GPL-3.0 23% 23% 13 350 2,374 13 1 0 0
Serbian (latin) GPL-3.0 23% 23% 13 350 2,374 13 1 0 0
Spanish GPL-3.0 52% 58% 7 193 1,356 7 0 0 0
Turkish GPL-3.0 23% 23% 13 350 2,374 13 0 0 0
Please sign in to see the alerts.

Overview

Project website tails.boum.org
Instructions for translators

https://tails.boum.org/contribute/how/translate/ Mailing list for translators: <<tails-l10n@boum.org>
Translation license GNU General Public License v3.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository gitolite@puppet-git.lizard:tails
Repository branch master
Last remote commit updated PO files a37f672d585
IkiWiki authored yesterday
Last commit in Weblate Translated using Weblate (Spanish) 1959e4058ce
victordargallo authored 2 weeks ago
Weblate repository https://translate.tails.net/git/tails/index/
File mask wiki/src/news/new_SSL_certificate.*.po
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 289 6,171 42,466
Source 17 363 2,498
Approved 28% 82 18% 1,123 19% 8,095
Waiting for review 8% 23 8% 532 8% 3,550
Translated 47% 138 34% 2,130 35% 14,927
Needs editing 3% 10 4% 300 4% 2,099
Read-only 11% 33 7% 475 7% 3,282
Failing checks 5% 15 1% 48 1% 560
Strings with suggestions 4% 13 5% 350 5% 2,374
Untranslated strings 48% 141 60% 3,741 59% 25,440
Last 12 months Previous

Activity in last 12 months

7 changes 47 changes 2 changes 19 changes 0 changes 0 changes 1 change 17 changes 5 changes 0 changes 14 changes 25 changes 2 changes 49 changes 8 changes 66 changes 66 changes 48 changes 57 changes 8 changes 36 changes 6 changes 18 changes 24 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

6,171
Hosted words
289
Hosted strings
47%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

+5%
Hosted words
+100%
+5%
Hosted strings
+100%
−2%
Translated
+50%
+50%
Contributors
+100%
None

Resource updated

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
File wiki/src/news/new_SSL_certificate.bg.po was added. 2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
Our website now is only available with HTTPS enabled. This may be important to provide some confidentiality while posting on the forum for example.
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
It makes it harder to setup a simplistic man-in-the-middle attacks against the people who didn't use HTTPS so far to visit our website.
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
Still we decided to get a commercial certificate for the following reasons:
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
Why get a commercial certificate then?
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
It is clear for us that getting an commercial SSL certificate is not enough to strongly authenticate our website, and for example authenticity of our releases. That's why we always propose you stronger ways of authenticating our Tails release using OpenPGP signatures.
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
But this trust system has proven to be flawed in many ways. For example, during 2011, two certificate authorities were compromised, and many fake certificates were issued and used in the wild. See [Comodo: The Recent RA Compromise](https://blog.comodo.com/other/the-recent-ra-compromise/) and [The Tor Project: The DigiNotar Debacle, and what you should do about it](https://blog.torproject.org/blog/diginotar-debacle-and-what-you-should-do-about-it).
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
Weaknesses of the system
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
Commercial certificate authorities are making a living out of selling SSL certificates; they are usually trusted automatically by most of the browsers. Other non-commercial authorities, such as [CACert](http://www.cacert.org/), need to be installed by the operating system or by the user to avoid displaying a security warning when visiting the website.
 
2 weeks ago
None

String updated in the repository

  1. Tails
  2. wiki/src/news/new_SSL_certificate.*.po
  3. Bulgarian
SSL certificates try to solve this problem. A SSL certificate is usually issued by a certificate authority to certify the identity of a server. When you reach a website your web browser might trust an SSL certificate automatically if it trusts the authority that issued it.
 
2 weeks ago
Browse all component changes