2 |
|
All strings — 192 words | Browse Translate Zen |
---|---|---|---|
2 |
|
Translated strings — 192 words | Browse Translate Zen |
Other components
Component | Translated | Unfinished | Unfinished words | Unfinished characters | Untranslated | Checks | Suggestions | Comments | |
---|---|---|---|---|---|---|---|---|---|
SelfPrivacy App | 79% | 107 | 725 | 4,150 | 103 | 4 | 0 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_fallback_ssh
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
|||||||||
SelfPrivacy App Markdown: how_cloudflare
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
|||||||||
SelfPrivacy App Markdown: how_digital_ocean
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
|||||||||
SelfPrivacy App Markdown: how_fallback_terminal
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
|||||||||
SelfPrivacy App Markdown: how_backblaze
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
|||||||||
SelfPrivacy App Markdown: about
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
|||||||||
SelfPrivacy App Markdown: how_fallback_old
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
|||||||||
Glossary SelfPrivacy | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
Overview
Project website | selfprivacy.org |
---|---|
Project maintainers |
![]() ![]() ![]() |
Translation process |
|
Source code repository |
https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app
|
Repository branch | master |
Last remote commit |
Merge pull request 'feat: Add copy-to-clipboard for email on user page' (#329) from email-copy into master
9eedc02
NaiJi ✨ authored 6 days ago |
Last commit in Weblate |
Translated using Weblate (Czech)
21e7597
![]() |
Weblate repository |
http://weblate.selfprivacy.org/git/selfprivacy/selfprivacy-app/
|
File mask | assets/markdown/how_hetzner-*.md |
Monolingual base language file | assets/markdown/how_hetzner-en.md |
Translation file |
Download
assets/markdown/how_hetzner-pl.md
|
Last change | April 28, 2023, 2:35 p.m. |
Last author | Mithras |
String statistics
Strings percent | Hosted strings | Words percent | Hosted words | Characters percent | Hosted characters | |
---|---|---|---|---|---|---|
Total | 2 | 192 | 1,238 | |||
Translated | 100% | 2 | 100% | 192 | 100% | 1,238 |
Needs editing | 0% | 0 | 0% | 0 | 0% | 0 |
Read-only | 0% | 0 | 0% | 0 | 0% | 0 |
Failing checks | 0% | 0 | 0% | 0 | 0% | 0 |
Strings with suggestions | 0% | 0 | 0% | 0 | 0% | 0 |
Untranslated strings | 0% | 0 | 0% | 0 | 0% | 0 |
Browse all translation changes
2 | File in original format as translated in the repository | Plain text file | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
2 | All strings, converted files enriched with comments; suitable for offline translation | Android String Resource | CSV | JSON | gettext PO | iOS strings | TBX | TMX | XLIFF 1.1 with gettext extensions | XLIFF 1.1 | XLSX |
1. Visit the following [link](https://console.hetzner.cloud/) and sign
into newly created account.
2. Enter into previously created project. If you haven't created one,
then please proceed.
3. Hover side panel with mouse cursor. Panel should expand and show us
a menu. We're interested in the last one — **Security** (icon of a
key).
4. Next, in the upper part of an interface, we can see approximately
the following: **SSH Keys, API Tokens, Certificates, Members.** You
need **API Tokens**. Click on it.
5. In the right part of the interface, there should be **Generate API
token** button. If you're using mobile version og a webpage, in the
lower right corner you'll see **red cross**. Push that button.
6. In the **Description** field, give our token a name (this can be any
name that you like. It doesn't influence the essence.
7. Under the **Description** field we can see a possibility to choose
**permissions**. Pick **Read & Write**.
8. Click **Generate API Token.**
9. After that, our key will be shown. Store it in the reliable place,
or in the password manager, which is better.
1. Odwiedź następujący [link](https://console.hetzner.cloud/) i zaloguj się
na nowo utworzone konto.
2. Wejdź do wcześniej utworzonego projektu. Jeśli jeszcze go nie stworzyłeś,
to proszę przejść dalej.
3. Najedź kursorem myszy na panel boczny. Panel powinien się rozwinąć i pokazać nam
menu. Nas interesuje ostatnie z nich - **Security** (ikona klucza).
.
4. Następnie w górnej części interfejsu możemy zobaczyć ok.
następujące elementy: ***SSH Keys, API Tokens, Certificates, Members.**
Klikamy na nie.
5. W prawej części interfejsu powinien znajdować się przycisk **Generate API
token**. Jeśli korzystasz z mobilnej wersji strony, w prawym dolnym rogu pojawi się
dolnym prawym rogu pojawi się **red cross**. Wciśnij ten przycisk.
6. W polu **Description** nadaj naszemu tokenowi nazwę (może to być dowolna nazwa).
nazwa, która Ci się podoba. Nie ma ona wpływu na istotę.
7. Pod polem **Description** widzimy możliwość wyboru.
**permissions**. Pick **Read & Write**.
8. Klikamy **Generate API Token**.
9. Po tej czynności pojawi się nasz klucz. Przechowuj go w wiarygodnym miejscu,
lub w menedżerze haseł, co jest lepsze.