Language Translated Untranslated Untranslated words Checks Suggestions Comments
English This translation is used for source strings. This component is linked to the Censorship.no!/summary repository. Fix this component to clear its alerts. MIT
Persian This component is linked to the Censorship.no!/summary repository. Fix this component to clear its alerts. MIT 2% 39 1,345
Spanish This component is linked to the Censorship.no!/summary repository. Fix this component to clear its alerts. MIT 0% 40 1,346
Please sign in to see the alerts.

Overview

Project website censorship.no
Project maintainers User avatar jnny User avatar Ivan Vilata i Balaguer User avatar jorge User avatar Peter User avatar ivilata
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language is editable.
Translation license MIT License
Source code repository https://github.com/censorship-no/ceno-docs.git
Repository branch i18n
Last remote commit adding top-level readme .po file 5f4b790
jnny authored a month ago
Weblate repository https://hosted.weblate.org/git/censorship-no/user-manual/
Filemask user-manual/*/browser/troubleshooting.po
Monolingual base language file user-manual/en/browser/troubleshooting.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 120 4,038 24,318
Source 40 1,346 8,106
Translated 34% 41 33% 1,347 33% 8,121
Needs editing 1% 2 3% 148 3% 870
Failing checks 0% 0 0% 0 0% 0
Last year 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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

4,038
Hosted words
120
Hosted strings
34%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+34%
Translated
—
+100%
Contributors
—
User avatar jnny

Translation changed

Censorship.no! / browser/troubleshooting — English

If the previous step works, but another device with only the *Shared by other CENO users* source enabled still shows "Failed to retrieve the resource…", there are two possible scenarios. If both devices are in the same network (e.g. on the same Wi-Fi access point), it could be that the network does not allow direct communication between devices connected to it. This happens in some public Wi-Fi networks, so try using a private one.
If the previous step works, but another device with only the *Shared by other CENO users* source enabled still shows "Failed to retrieve the resource…", there are two possible scenarios. If both devices are in the same network (e.g. on the same Wi-Fi access point), it could be that the network does not allow direct communication between devices connected to it. This happens in some public Wi-Fi networks, so try using a private one.
2 days ago
User avatar jnny

Source string changed

Censorship.no! / browser/troubleshooting — Spanish

**Technical note:** If your device reports *undecided* reachability and you can change the configuration of the access point, you may create a permanent port forwarding rule towards your client. See [here](bridging.md) for further instructions.
2 days ago
User avatar jnny

Source string changed

Censorship.no! / browser/troubleshooting — Persian

**Technical note:** If your device reports *undecided* reachability and you can change the configuration of the access point, you may create a permanent port forwarding rule towards your client. See [here](bridging.md) for further instructions.
2 days ago
User avatar jnny

New translation

Censorship.no! / browser/troubleshooting — English

**Technical note:** If your device reports *undecided* reachability and you can change the configuration of the access point, you may create a permanent port forwarding rule towards your client. See [here](bridging.md) for further instructions.
**Technical note:** If your device reports *undecided* reachability and you can change the configuration of the access point, you may create a permanent port forwarding rule towards your client. See [here](bridging.md) for further instructions.
2 days ago
User avatar jnny

Source string changed

Censorship.no! / browser/troubleshooting — Spanish

If the devices are in different networks, it could be due to a variety of reasons. One of them is that the network of the first device does not allow incoming connections: if you open its *CENO Settings* page, under *Reachability status* it should say *reachable* or *likely reachable*. Otherwise seeding may not be possible from that network as it is.
2 days ago
User avatar jnny

Source string changed

Censorship.no! / browser/troubleshooting — Persian

If the devices are in different networks, it could be due to a variety of reasons. One of them is that the network of the first device does not allow incoming connections: if you open its *CENO Settings* page, under *Reachability status* it should say *reachable* or *likely reachable*. Otherwise seeding may not be possible from that network as it is.
2 days ago
User avatar jnny

New translation

Censorship.no! / browser/troubleshooting — English

If the devices are in different networks, it could be due to a variety of reasons. One of them is that the network of the first device does not allow incoming connections: if you open its *CENO Settings* page, under *Reachability status* it should say *reachable* or *likely reachable*. Otherwise seeding may not be possible from that network as it is.
If the devices are in different networks, it could be due to a variety of reasons. One of them is that the network of the first device does not allow incoming connections: if you open its *CENO Settings* page, under *Reachability status* it should say *reachable* or *likely reachable*. Otherwise seeding may not be possible from that network as it is.
2 days ago
User avatar jnny

Source string changed

Censorship.no! / browser/troubleshooting — Persian

If the previous step works, but another device with only the *Shared by other CENO users* source enabled still shows "Failed to retrieve the resource…", there are two possible scenarios. If both devices are in the same network (e.g. on the same Wi-Fi access point), it could be that the network does not allow direct communication between devices connected to it. This happens in some public Wi-Fi networks, so try using a private one.
2 days ago
User avatar jnny

Source string changed

Censorship.no! / browser/troubleshooting — Spanish

If the previous step works, but another device with only the *Shared by other CENO users* source enabled still shows "Failed to retrieve the resource…", there are two possible scenarios. If both devices are in the same network (e.g. on the same Wi-Fi access point), it could be that the network does not allow direct communication between devices connected to it. This happens in some public Wi-Fi networks, so try using a private one.
2 days ago
User avatar jnny

Marked for edit

Censorship.no! / browser/troubleshooting — English

If the previous step works, but another device with only the *Shared by other CENO users* source enabled still shows "Failed to retrieve the resource…", there are two possible scenarios. If both devices are in the same network (e.g. on the same Wi-Fi access point), it could be that the network does not allow direct communication between devices connected to it. This happens in some public Wi-Fi networks, so try using a private one.
If the previous step works, but another device with only the *Shared by other CENO users* source enabled still shows "Failed to retrieve the resource…", there are two possible scenarios. If both devices are in the same network (e.g. on the same Wi-Fi access point), it could be that the network does not allow direct communication between devices connected to it. This happens in some public Wi-Fi networks, so try using a private one.
2 days ago
Browse all component changes