Merge pull request #3651 from vitorpamplona/l10n_crowdin_translations

New Crowdin Translations
This commit is contained in:
Vitor Pamplona
2026-07-20 15:12:11 -04:00
committed by GitHub
41 changed files with 615 additions and 0 deletions
@@ -36,6 +36,7 @@
<string name="channel_image">صورة القناة</string>
<string name="referenced_event_not_found">لم يتم العثور على الحدث المشار إليه</string>
<string name="could_not_decrypt_the_message">لا يمكن فك تشفير الرسالة</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">صورة المجموعة</string>
<string name="explicit_content">محتوى فاضح</string>
<string name="relay_notice">إشعار relay</string>
@@ -730,6 +731,7 @@
<string name="napplet_consent_query">يريد هذا nApplet قراءة الأحداث من relay الخاصة بك.</string>
<string name="napplet_consent_storage">يريد هذا nApplet استخدام مساحة التخزين الخاصة به.</string>
<string name="napplet_consent_pay">يريد هذا nApplet دفع فاتورة Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">يريد هذا nApplet جلب مورد ويب.</string>
<string name="napplet_consent_upload">يريد هذا nApplet تحميل ملف إلى خادم الوسائط الخاص بك.</string>
<string name="napplet_consent_notify">يريد هذا nApplet عرض إشعارات لك.</string>
@@ -742,11 +744,24 @@
<item quantity="many">يريد هذا nApplet دفع فاتورة Lightning بقيمة %1$d sats.</item>
<item quantity="other">يريد هذا nApplet دفع فاتورة Lightning بقيمة %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">চ্যানেল ইমেজ</string>
<string name="referenced_event_not_found">উল্লেখিত ইভেন্টটি পাওয়া যায় নি</string>
<string name="could_not_decrypt_the_message">মেসেজটি ডিক্রিপ্ট করা যায় নি</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">দলগত ছবি</string>
<string name="explicit_content">খোলামেলা আধেয়</string>
<string name="relay_notice">রিলে নোটিশ</string>
@@ -703,6 +704,7 @@
<string name="napplet_consent_query">এই nApplet আপনার relay-গুলো থেকে ইভেন্ট পড়তে চায়।</string>
<string name="napplet_consent_storage">এই nApplet তার প্রাইভেট স্টোরেজ ব্যবহার করতে চায়।</string>
<string name="napplet_consent_pay">এই nApplet একটি Lightning ইনভয়েস পরিশোধ করতে চায়।</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">এই nApplet একটি ওয়েব রিসোর্স আনতে চায়।</string>
<string name="napplet_consent_upload">এই nApplet আপনার মিডিয়া সার্ভারে একটি ফাইল আপলোড করতে চায়।</string>
<string name="napplet_consent_notify">এই nApplet আপনাকে বিজ্ঞপ্তি দেখাতে চায়।</string>
@@ -711,11 +713,24 @@
<item quantity="one">এই nApplet %1$d sat-এর জন্য একটি Lightning ইনভয়েস পরিশোধ করতে চায়।</item>
<item quantity="other">এই nApplet %1$d sats-এর জন্য একটি Lightning ইনভয়েস পরিশোধ করতে চায়।</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -31,6 +31,7 @@
<string name="channel_image">Obrázek kanálu</string>
<string name="referenced_event_not_found">Odkazovaná událost nebyla nalezena</string>
<string name="could_not_decrypt_the_message">Nepodařilo se dešifrovat zprávu</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Obrázek skupiny</string>
<string name="explicit_content">Explicitní obsah</string>
<string name="relay_notice">Oznámení relé</string>
@@ -832,6 +833,7 @@
<string name="napplet_consent_query">Tento nApplet chce číst eventy z vašich relays.</string>
<string name="napplet_consent_storage">Tento nApplet chce používat své soukromé úložiště.</string>
<string name="napplet_consent_pay">Tento nApplet chce zaplatit Lightning fakturu.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Tento nApplet chce načíst webový zdroj.</string>
<string name="napplet_consent_upload">Tento nApplet chce nahrát soubor na váš mediální server.</string>
<string name="napplet_consent_notify">Tento nApplet vám chce zobrazovat oznámení.</string>
@@ -842,6 +844,15 @@
<item quantity="many">Tento nApplet chce zaplatit Lightning fakturu za %1$d sats.</item>
<item quantity="other">Tento nApplet chce zaplatit Lightning fakturu za %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Připojit k Nostr</string>
<string name="napplet_connect_subtitle">se chce připojit k vašemu účtu Nostr</string>
@@ -877,6 +888,10 @@
<string name="napplet_op_encrypt">zašifrovat zprávu</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">číst vaše soukromé zprávy</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Připojené aplikace</string>
<string name="napplet_permissions_revoke_all">Odvolat všechna oprávnění</string>
@@ -25,6 +25,7 @@
<string name="channel_image">Kanalbild</string>
<string name="referenced_event_not_found">Referenziertes Ereignis nicht gefunden</string>
<string name="could_not_decrypt_the_message">Nachricht konnte nicht entschlüsselt werden</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Gruppenbild</string>
<string name="explicit_content">Anstößiger Inhalt</string>
<string name="relay_notice">Relay-Hinweis</string>
@@ -810,6 +811,7 @@
<string name="napplet_consent_query">Dieses nApplet möchte Ereignisse von Ihren Relays lesen.</string>
<string name="napplet_consent_storage">Dieses nApplet möchte seinen privaten Speicher verwenden.</string>
<string name="napplet_consent_pay">Dieses nApplet möchte eine Lightning-Rechnung bezahlen.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Dieses nApplet möchte eine Web-Ressource abrufen.</string>
<string name="napplet_consent_upload">Dieses nApplet möchte eine Datei auf Ihren Medienserver hochladen.</string>
<string name="napplet_consent_notify">Dieses nApplet möchte Ihnen Benachrichtigungen anzeigen.</string>
@@ -818,6 +820,15 @@
<item quantity="one">Dieses nApplet möchte eine Lightning-Rechnung über %1$d sat bezahlen.</item>
<item quantity="other">Dieses nApplet möchte eine Lightning-Rechnung über %1$d sats bezahlen.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Mit Nostr verbinden</string>
<string name="napplet_connect_subtitle">möchte sich mit deinem Nostr-Konto verbinden</string>
@@ -853,6 +864,10 @@
<string name="napplet_op_encrypt">eine Nachricht verschlüsseln</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">deine privaten Nachrichten lesen</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Verbundene Apps</string>
<string name="napplet_permissions_revoke_all">Alle Berechtigungen widerrufen</string>
@@ -24,6 +24,7 @@
<string name="channel_image">Εικόνα Καναλιού</string>
<string name="referenced_event_not_found">Η δημοσίευση δεν βρέθηκε</string>
<string name="could_not_decrypt_the_message">Αδυναμία αποκρυπτογράφησης μηνύματος</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Εικόνα Ομάδας</string>
<string name="explicit_content">Ακριβές Περιεχόμενο</string>
<string name="relay_notice">Ειδοποίηση relay</string>
@@ -691,6 +692,7 @@
<string name="napplet_consent_query">Αυτό το nApplet θέλει να διαβάσει συμβάντα από τα relay σας.</string>
<string name="napplet_consent_storage">Αυτό το nApplet θέλει να χρησιμοποιήσει την ιδιωτική του αποθήκευση.</string>
<string name="napplet_consent_pay">Αυτό το nApplet θέλει να πληρώσει ένα Lightning τιμολόγιο.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Αυτό το nApplet θέλει να λάβει έναν πόρο από το διαδίκτυο.</string>
<string name="napplet_consent_upload">Αυτό το nApplet θέλει να μεταφορτώσει ένα αρχείο στον διακομιστή πολυμέσων σας.</string>
<string name="napplet_consent_notify">Αυτό το nApplet θέλει να σας εμφανίσει ειδοποιήσεις.</string>
@@ -699,11 +701,24 @@
<item quantity="one">Αυτό το nApplet θέλει να πληρώσει ένα Lightning τιμολόγιο αξίας %1$d sat.</item>
<item quantity="other">Αυτό το nApplet θέλει να πληρώσει ένα Lightning τιμολόγιο αξίας %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -7,6 +7,7 @@
<string name="scan_qr">Scan QR</string>
<string name="show_anyway">Show Anyway</string>
<string name="post_not_found_short">👀</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<!-- Reply-mode toggle in the chat composer: reply inline in the timeline vs pull it aside into a thread. -->
<!-- Title of the minichat (thread) screen opened from a chat message. -->
<!-- Chip on a chat message that opens its thread ("minichat") of kind-1111 replies. -->
@@ -15,11 +16,25 @@
<!-- Napplet sandbox chrome (host top bar + live action notices) -->
<!-- Napplet capability names -->
<!-- Napplet consent dialog -->
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -24,6 +24,7 @@
<string name="channel_image">Kanala Bildo</string>
<string name="referenced_event_not_found">Referencita evento netrovita</string>
<string name="could_not_decrypt_the_message">Mesaĝo nemalĉifrebla</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Grupa Bildo</string>
<string name="explicit_content">Eksplicita Enhavo</string>
<string name="relay_notice">Relay-avizo</string>
@@ -700,6 +701,7 @@
<string name="napplet_consent_query">Ĉi tiu nApplet volas legi eventojn el viaj relay-oj.</string>
<string name="napplet_consent_storage">Ĉi tiu nApplet volas uzi sian privatan stokadan lokon.</string>
<string name="napplet_consent_pay">Ĉi tiu nApplet volas pagi Lightning-fakturon.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Ĉi tiu nApplet volas alporti retan rimedon.</string>
<string name="napplet_consent_upload">Ĉi tiu nApplet volas alŝuti dosieron al via amaskomunikilara servilo.</string>
<string name="napplet_consent_notify">Ĉi tiu nApplet volas montri al vi sciigojn.</string>
@@ -708,11 +710,24 @@
<item quantity="one">Ĉi tiu nApplet volas pagi Lightning-fakturon por %1$d sat.</item>
<item quantity="other">Ĉi tiu nApplet volas pagi Lightning-fakturon por %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">Imagen del canal</string>
<string name="referenced_event_not_found">Evento referenciado no encontrado</string>
<string name="could_not_decrypt_the_message">No se pudo desencriptar el mensaje</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Imagen de grupo</string>
<string name="explicit_content">Contenido explícito</string>
<string name="relay_notice">aviso_relé</string>
@@ -716,6 +717,7 @@
<string name="napplet_consent_query">Este nApplet quiere leer eventos de tus relés.</string>
<string name="napplet_consent_storage">Este nApplet quiere utilizar su almacenamiento privado.</string>
<string name="napplet_consent_pay">Este nApplet quiere pagar una factura Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Este nApplet quiere obtener un recurso web.</string>
<string name="napplet_consent_upload">Este nApplet quiere subir un archivo a tu servidor de medios.</string>
<string name="napplet_consent_notify">Este nApplet quiere mostrarte notificaciones.</string>
@@ -724,11 +726,24 @@
<item quantity="one">Este nApplet quiere pagar una factura Lightning de %1$d sat.</item>
<item quantity="other">Este nApplet quiere pagar una factura Lightning de %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">Imagen del canal</string>
<string name="referenced_event_not_found">No se encontró el evento referenciado</string>
<string name="could_not_decrypt_the_message">No se pudo desencriptar el mensaje</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Foto de grupo</string>
<string name="explicit_content">Contenido explícito</string>
<string name="relay_notice">aviso_relé</string>
@@ -709,6 +710,7 @@
<string name="napplet_consent_query">Este nApplet quiere leer eventos de tus relés.</string>
<string name="napplet_consent_storage">Este nApplet quiere utilizar su almacenamiento privado.</string>
<string name="napplet_consent_pay">Este nApplet quiere pagar una factura Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Este nApplet quiere obtener un recurso web.</string>
<string name="napplet_consent_upload">Este nApplet quiere subir un archivo a tu servidor de medios.</string>
<string name="napplet_consent_notify">Este nApplet quiere mostrarte notificaciones.</string>
@@ -717,11 +719,24 @@
<item quantity="one">Este nApplet quiere pagar una factura Lightning de %1$d sat.</item>
<item quantity="other">Este nApplet quiere pagar una factura Lightning de %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">Imagen del canal</string>
<string name="referenced_event_not_found">No se encontró el evento referenciado</string>
<string name="could_not_decrypt_the_message">No se pudo desencriptar el mensaje</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Imagen del grupo</string>
<string name="explicit_content">Contenido explícito</string>
<string name="relay_notice">aviso_relé</string>
@@ -709,6 +710,7 @@
<string name="napplet_consent_query">Este nApplet quiere leer eventos de tus relés.</string>
<string name="napplet_consent_storage">Este nApplet quiere utilizar su almacenamiento privado.</string>
<string name="napplet_consent_pay">Este nApplet quiere pagar una factura Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Este nApplet quiere obtener un recurso web.</string>
<string name="napplet_consent_upload">Este nApplet quiere subir un archivo a tu servidor de medios.</string>
<string name="napplet_consent_notify">Este nApplet quiere mostrarte notificaciones.</string>
@@ -717,11 +719,24 @@
<item quantity="one">Este nApplet quiere pagar una factura Lightning de %1$d sat.</item>
<item quantity="other">Este nApplet quiere pagar una factura Lightning de %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">تصویر کانال</string>
<string name="referenced_event_not_found">رویداد مورد نظر یافت نشد</string>
<string name="could_not_decrypt_the_message">پیام رمزگشایی نشد</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">تصویر گروه</string>
<string name="explicit_content">محتوای نامناسب</string>
<string name="relay_notice">اطلاعیه relay</string>
@@ -702,6 +703,7 @@
<string name="napplet_consent_query">این nApplet می‌خواهد رویدادها را از relay‌های شما بخواند.</string>
<string name="napplet_consent_storage">این nApplet می‌خواهد از ذخیره‌سازی خصوصی خود استفاده کند.</string>
<string name="napplet_consent_pay">این nApplet می‌خواهد یک فاکتور Lightning پرداخت کند.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">این nApplet می‌خواهد یک منبع وب دریافت کند.</string>
<string name="napplet_consent_upload">این nApplet می‌خواهد یک فایل به سرور رسانه‌ای شما بارگذاری کند.</string>
<string name="napplet_consent_notify">این nApplet می‌خواهد به شما اعلان نشان دهد.</string>
@@ -710,11 +712,24 @@
<item quantity="one">این nApplet می‌خواهد یک فاکتور Lightning به مبلغ %1$d sat پرداخت کند.</item>
<item quantity="other">این nApplet می‌خواهد یک فاکتور Lightning به مبلغ %1$d sat پرداخت کند.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -24,6 +24,7 @@
<string name="channel_image">Kanavan kuva</string>
<string name="referenced_event_not_found">Viitattua tapahtumaa ei löytynyt</string>
<string name="could_not_decrypt_the_message">Viestin purku epäonnistui</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Ryhmäkuva</string>
<string name="explicit_content">Julkeaa sisältöä</string>
<string name="relay_notice">relay-ilmoitus</string>
@@ -693,6 +694,7 @@
<string name="napplet_consent_query">Tämä nApplet haluaa lukea tapahtumia relayistasi.</string>
<string name="napplet_consent_storage">Tämä nApplet haluaa käyttää yksityistä tallennustaan.</string>
<string name="napplet_consent_pay">Tämä nApplet haluaa maksaa Lightning-laskun.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Tämä nApplet haluaa hakea verkkoresurssin.</string>
<string name="napplet_consent_upload">Tämä nApplet haluaa ladata tiedoston mediapalvelimellesi.</string>
<string name="napplet_consent_notify">Tämä nApplet haluaa näyttää sinulle ilmoituksia.</string>
@@ -701,11 +703,24 @@
<item quantity="one">Tämä nApplet haluaa maksaa Lightning-laskun, jonka arvo on %1$d sat.</item>
<item quantity="other">Tämä nApplet haluaa maksaa Lightning-laskun, jonka arvo on %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -24,6 +24,7 @@
<string name="channel_image">Image du canal</string>
<string name="referenced_event_not_found">référence de l\'évènement non trouvée</string>
<string name="could_not_decrypt_the_message">Impossible de déchiffrer le message</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Image de groupe</string>
<string name="explicit_content">Contenu choquant</string>
<string name="relay_notice">Annonce du serveur</string>
@@ -671,6 +672,7 @@
<string name="napplet_consent_query">Ce nApplet veut lire des événements depuis vos relais.</string>
<string name="napplet_consent_storage">Ce nApplet veut utiliser son stockage privé.</string>
<string name="napplet_consent_pay">Ce nApplet veut payer une facture Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Ce nApplet veut récupérer une ressource web.</string>
<string name="napplet_consent_upload">Ce nApplet veut téléverser un fichier sur votre serveur multimédia.</string>
<string name="napplet_consent_notify">Ce nApplet veut vous afficher des notifications.</string>
@@ -679,11 +681,24 @@
<item quantity="one">Ce nApplet veut payer une facture Lightning de %1$d sat.</item>
<item quantity="other">Ce nApplet veut payer une facture Lightning de %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">Image du canal</string>
<string name="referenced_event_not_found">référence de l\'évènement non trouvée</string>
<string name="could_not_decrypt_the_message">Impossible de déchiffrer le message</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Image de groupe</string>
<string name="explicit_content">Contenu choquant</string>
<string name="relay_notice">Annonce du serveur</string>
@@ -721,6 +722,7 @@
<string name="napplet_consent_query">Ce nApplet veut lire des événements depuis vos relais.</string>
<string name="napplet_consent_storage">Ce nApplet veut utiliser son stockage privé.</string>
<string name="napplet_consent_pay">Ce nApplet veut payer une facture Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Ce nApplet veut récupérer une ressource web.</string>
<string name="napplet_consent_upload">Ce nApplet veut téléverser un fichier sur votre serveur multimédia.</string>
<string name="napplet_consent_notify">Ce nApplet veut vous afficher des notifications.</string>
@@ -729,6 +731,15 @@
<item quantity="one">Ce nApplet veut payer une facture Lightning de %1$d sat.</item>
<item quantity="other">Ce nApplet veut payer une facture Lightning de %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Se connecter à Nostr</string>
<!-- Signer trust levels -->
@@ -760,6 +771,10 @@
<string name="napplet_op_encrypt">chiffrer un message</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">lire vos messages privés</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Applications connectées</string>
<string name="napplet_permissions_revoke_all">Révoquer toutes les autorisations</string>
@@ -25,6 +25,7 @@
<string name="channel_image">प्रणाली चित्र</string>
<string name="referenced_event_not_found">उद्धृत घटना अप्राप्त</string>
<string name="could_not_decrypt_the_message">सन्देश का अरहस्यीकरण असफल</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">समूह चित्र</string>
<string name="explicit_content">अभद्र विषयवस्तु</string>
<string name="relay_notice">पुनःप्रसारक सूचना</string>
@@ -810,6 +811,7 @@
<string name="napplet_consent_query">यह नोस्टर संलग्नक्रमक आपके पुनःप्रसारकों से घटनाओं को पढना चाहता है।</string>
<string name="napplet_consent_storage">यह नोस्टर संलग्नक्रमक अपना निजी भण्डार का प्रयेग करना चाहता है।</string>
<string name="napplet_consent_pay">यह नोस्टर संलग्नक्रमक एक लैटनिंग चालान का भुगतान करना चाहता है।</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">यह नोस्टर संलग्नक्रमक एक जाल संसाधन लाना चाहता है।</string>
<string name="napplet_consent_upload">यह नोस्टर संलग्नक्रमक एक अभिलेख को आपके प्रसारसंगणक तक आरोहण करना चाहता है।</string>
<string name="napplet_consent_notify">यह नोस्टर संलग्नक्रमक आपको सूचनाएँ दिखाना चाहता है।</string>
@@ -818,6 +820,15 @@
<item quantity="one">यह नोस्टर संलग्नक्रमक %1$d साट् का एक लैटनिंग चालान का भुगतान करना चाहता है।</item>
<item quantity="other">यह नोस्टर संलग्नक्रमक %1$d साट्स का एक लैटनिंग चालान का भुगतान करना चाहता है।</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">नोस्टर से संयोजन</string>
<string name="napplet_connect_subtitle">आपके नोस्टर लेखा के साथ संयोजन करना चाहता है</string>
@@ -853,6 +864,10 @@
<string name="napplet_op_encrypt">सन्देश रहस्यीकरण</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">आपके निजी सन्देशों का पठन</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">संयोजित क्रमक</string>
<string name="napplet_permissions_revoke_all">सभी अनुमतियों का निराकरण</string>
@@ -25,6 +25,7 @@
<string name="channel_image">Csatorna profilképe</string>
<string name="referenced_event_not_found">A hivatkozott esemény nem található</string>
<string name="could_not_decrypt_the_message">Nem sikerült visszafejteni az üzenetet</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Csoport profilképe</string>
<string name="explicit_content">Szókimondó tartalom</string>
<string name="relay_notice">Átjátszóval kapcsolatos megjegyzések</string>
@@ -811,6 +812,7 @@
<string name="napplet_consent_query">Ez a nKisalkalmazás eseményeket szeretne olvasni az Ön átjátszóiról.</string>
<string name="napplet_consent_storage">Ez a nKisalkalmazás az Ön privát tárhelyét szeretné használni.</string>
<string name="napplet_consent_pay">Ez a nKisalkalmazás ki szeretne fizetni egy Lightning számlát.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Ez a nKisalkalmazás le szeretne kérni egy webes erőforrást.</string>
<string name="napplet_consent_upload">Ez a nKisalkalmazás fel szeretne tölteni egy fájlt az Ön médiakiszolgálójára.</string>
<string name="napplet_consent_notify">Ez a nKisalkalmazás értesítéseket szeretne megjeleníteni Önnek.</string>
@@ -819,6 +821,15 @@
<item quantity="one">Ez a nKisalkalmazás ki szeretne fizetni egy %1$d satoshi értékű Lightning számlát.</item>
<item quantity="other">Ez a nKisalkalmazás ki szeretne fizetni egy %1$d satoshi értékű Lightning számlát.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Kapcsolódás a NOSTR-hoz</string>
<string name="napplet_connect_subtitle">szeretne csatlakozni a saját Nostr-fiókjához</string>
@@ -854,6 +865,10 @@
<string name="napplet_op_encrypt">egy üzenet titkosítása</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">saját privát üzenetek olvasása</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Összekapcsolt alkalmazások</string>
<string name="napplet_permissions_revoke_all">Minden engedély visszavonása</string>
@@ -21,6 +21,7 @@
<string name="channel_image">Gambar Kanal</string>
<string name="referenced_event_not_found">Referensi event tidak dapat ditemukan</string>
<string name="could_not_decrypt_the_message">Tidak dapat mendekripsi pesan</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Gambar Grup</string>
<string name="explicit_content">Konten Eksplisit</string>
<string name="relay_notice">Pemberitahuan relay</string>
@@ -679,6 +680,7 @@
<string name="napplet_consent_query">nApplet ini ingin membaca event dari relay Anda.</string>
<string name="napplet_consent_storage">nApplet ini ingin menggunakan penyimpanan pribadinya.</string>
<string name="napplet_consent_pay">nApplet ini ingin membayar invoice Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">nApplet ini ingin mengambil sumber daya web.</string>
<string name="napplet_consent_upload">nApplet ini ingin mengunggah file ke server media Anda.</string>
<string name="napplet_consent_notify">nApplet ini ingin menampilkan notifikasi kepada Anda.</string>
@@ -686,11 +688,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">nApplet ini ingin membayar invoice Lightning sebesar %1$d sat.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -24,6 +24,7 @@
<string name="channel_image">Foto del canale</string>
<string name="referenced_event_not_found">L\'evento di riferimento non è stato trovato</string>
<string name="could_not_decrypt_the_message">Impossibile decriptare il messaggio</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Foto del gruppo</string>
<string name="explicit_content">Contenuto esplicito</string>
<string name="relay_notice">Avviso relay</string>
@@ -683,6 +684,7 @@
<string name="napplet_consent_query">Questa nApplet vuole leggere eventi dai tuoi relay.</string>
<string name="napplet_consent_storage">Questa nApplet vuole utilizzare la propria archiviazione privata.</string>
<string name="napplet_consent_pay">Questa nApplet vuole pagare una fattura Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Questa nApplet vuole recuperare una risorsa web.</string>
<string name="napplet_consent_upload">Questa nApplet vuole caricare un file sul tuo server multimediale.</string>
<string name="napplet_consent_notify">Questa nApplet vuole mostrarti delle notifiche.</string>
@@ -691,11 +693,24 @@
<item quantity="one">Questa nApplet vuole pagare una fattura Lightning di %1$d sat.</item>
<item quantity="other">Questa nApplet vuole pagare una fattura Lightning di %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -21,6 +21,7 @@
<string name="channel_image">チャンネル画像</string>
<string name="referenced_event_not_found">参照先のイベントが見つかりません</string>
<string name="could_not_decrypt_the_message">メッセージが復号できませんでした</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">グループ画像</string>
<string name="explicit_content">露骨なコンテンツ</string>
<string name="relay_notice">relay 通知</string>
@@ -691,6 +692,7 @@
<string name="napplet_consent_query">この nApplet はあなたの relay からイベントを読み取ろうとしています。</string>
<string name="napplet_consent_storage">この nApplet はプライベートストレージを使用しようとしています。</string>
<string name="napplet_consent_pay">この nApplet は Lightning インボイスを支払おうとしています。</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">この nApplet はウェブリソースを取得しようとしています。</string>
<string name="napplet_consent_upload">この nApplet はメディアサーバーにファイルをアップロードしようとしています。</string>
<string name="napplet_consent_notify">この nApplet はあなたに通知を表示しようとしています。</string>
@@ -698,11 +700,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">この nApplet は %1$d sats の Lightning インボイスを支払おうとしています。</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -21,6 +21,7 @@
<string name="channel_image">채널 이미지</string>
<string name="referenced_event_not_found">참조된 이벤트를 찾을 수 없습니다</string>
<string name="could_not_decrypt_the_message">메시지를 복호화할 수 없습니다</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">그룹 사진</string>
<string name="explicit_content">성인 콘텐츠</string>
<string name="relay_notice">relay 공지</string>
@@ -688,6 +689,7 @@
<string name="napplet_consent_query">이 nApplet이 relay에서 이벤트를 읽으려고 합니다.</string>
<string name="napplet_consent_storage">이 nApplet이 개인 저장소를 사용하려고 합니다.</string>
<string name="napplet_consent_pay">이 nApplet이 Lightning 인보이스를 결제하려고 합니다.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">이 nApplet이 웹 리소스를 가져오려고 합니다.</string>
<string name="napplet_consent_upload">이 nApplet이 미디어 서버에 파일을 업로드하려고 합니다.</string>
<string name="napplet_consent_notify">이 nApplet이 알림을 표시하려고 합니다.</string>
@@ -695,11 +697,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">이 nApplet이 %1$d sats의 Lightning 인보이스를 결제하려고 합니다.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -28,6 +28,7 @@
<string name="channel_image">Kanāla attēls</string>
<string name="referenced_event_not_found">Atsaucētais notikums nav atrasts</string>
<string name="could_not_decrypt_the_message">Neizdevās atšifrēt ziņojumu</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Grupas attēls</string>
<string name="explicit_content">Nepiedienīgs saturs</string>
<string name="relay_notice">Relay paziņojums</string>
@@ -704,6 +705,7 @@
<string name="napplet_consent_query">Šis nApplet vēlas lasīt notikumus no jūsu relays.</string>
<string name="napplet_consent_storage">Šis nApplet vēlas izmantot savu privāto krātuvi.</string>
<string name="napplet_consent_pay">Šis nApplet vēlas apmaksāt Lightning rēķinu.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Šis nApplet vēlas iegūt tīmekļa resursu.</string>
<string name="napplet_consent_upload">Šis nApplet vēlas augšupielādēt failu uz jūsu mediju serveri.</string>
<string name="napplet_consent_notify">Šis nApplet vēlas rādīt jums paziņojumus.</string>
@@ -713,11 +715,24 @@
<item quantity="one">Šī nApplet vēlas apmaksāt Lightning rēķinu par %1$d sat.</item>
<item quantity="other">Šī nApplet vēlas apmaksāt Lightning rēķinu par %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">Kanaalafbeelding</string>
<string name="referenced_event_not_found">Verwezen bericht niet gevonden</string>
<string name="could_not_decrypt_the_message">Kon bericht niet ontsleutelen</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Groepsafbeelding</string>
<string name="explicit_content">Expliciete inhoud</string>
<string name="relay_notice">Relay-bericht</string>
@@ -711,6 +712,7 @@
<string name="napplet_consent_query">Deze nApplet wil events van je relays lezen.</string>
<string name="napplet_consent_storage">Deze nApplet wil gebruikmaken van zijn privéopslag.</string>
<string name="napplet_consent_pay">Deze nApplet wil een Lightning-invoice betalen.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Deze nApplet wil een webbron ophalen.</string>
<string name="napplet_consent_upload">Deze nApplet wil een bestand uploaden naar je mediaserver.</string>
<string name="napplet_consent_notify">Deze nApplet wil je meldingen tonen.</string>
@@ -719,6 +721,15 @@
<item quantity="one">Deze nApplet wil een Lightning-invoice van %1$d sat betalen.</item>
<item quantity="other">Deze nApplet wil een Lightning-invoice van %1$d sats betalen.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Verbinden met Nostr</string>
<string name="napplet_connect_subtitle">wil verbinding maken met je Nostr-account</string>
@@ -754,6 +765,10 @@
<string name="napplet_op_encrypt">een bericht versleutelen</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">je privéberichten lezen</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Verbonden apps</string>
<string name="napplet_permissions_revoke_all">Alle machtigingen intrekken</string>
@@ -31,6 +31,7 @@
<string name="channel_image">Zdjęcie kanału</string>
<string name="referenced_event_not_found">Przywołane zdarzenie nie zostało znalezione</string>
<string name="could_not_decrypt_the_message">Nie można odszyfrować wiadomości</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Zdjęcie grupy</string>
<string name="explicit_content">Niedozwolona zawartość</string>
<string name="relay_notice">Uwagi transmitera</string>
@@ -832,6 +833,7 @@ Zaplanowane posty z innych kont nie zostaną opublikowane, dopóki to konto jest
<string name="napplet_consent_query">Ten nApplet chce odczytywać wydarzenia z twoich transmiterów.</string>
<string name="napplet_consent_storage">Ta aplikacja nApplet chce korzystać ze swojego prywatnego schowka.</string>
<string name="napplet_consent_pay">Ta aplikacja nApplet chce zapłacić fakturę w systemie Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Ten nApplet chce pobrać zasób internetowy.</string>
<string name="napplet_consent_upload">Ten nApplet chce przesłać plik na Twój serwer multimedialny.</string>
<string name="napplet_consent_notify">Ten nApplet chce pokazywać Ci powiadomienia.</string>
@@ -842,6 +844,15 @@ Zaplanowane posty z innych kont nie zostaną opublikowane, dopóki to konto jest
<item quantity="many">Ta aplikacja nApplet chce opłacić fakturę Lightning w wysokości %1$d satoszy.</item>
<item quantity="other">Ta aplikacja nApplet chce opłacić fakturę Lightning w wysokości %1$d satoszów.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Połącz z Nostr</string>
<string name="napplet_connect_subtitle">chce połączyć się z Twoim kontem Nostr</string>
@@ -877,6 +888,10 @@ Zaplanowane posty z innych kont nie zostaną opublikowane, dopóki to konto jest
<string name="napplet_op_encrypt">zaszyfruj wiadomość</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">odczytaj prywatne wiadomości</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Podłączone aplikacje</string>
<string name="napplet_permissions_revoke_all">Cofnij wszystkie uprawnienia</string>
@@ -25,6 +25,7 @@
<string name="channel_image">Imagem do Canal</string>
<string name="referenced_event_not_found">Evento referenciado não encontrado</string>
<string name="could_not_decrypt_the_message">Não foi possível descriptografar a mensagem</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Imagem do grupo</string>
<string name="explicit_content">Conteúdo explícito</string>
<string name="relay_notice">Aviso do relay</string>
@@ -808,6 +809,7 @@
<string name="napplet_consent_query">Este nApplet quer ler eventos dos seus relays.</string>
<string name="napplet_consent_storage">Este nApplet quer usar seu armazenamento privado.</string>
<string name="napplet_consent_pay">Este nApplet quer pagar uma fatura Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Este nApplet quer buscar um recurso da web.</string>
<string name="napplet_consent_upload">Este nApplet quer enviar um arquivo para o seu servidor de mídia.</string>
<string name="napplet_consent_notify">Este nApplet quer mostrar notificações para você.</string>
@@ -816,6 +818,15 @@
<item quantity="one">Este nApplet quer pagar uma fatura Lightning de %1$d sat.</item>
<item quantity="other">Este nApplet quer pagar uma fatura Lightning de %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Conectar ao Nostr</string>
<string name="napplet_connect_subtitle">quer se conectar à sua conta Nostr</string>
@@ -851,6 +862,10 @@
<string name="napplet_op_encrypt">criptografar uma mensagem</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">ler suas mensagens privadas</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Apps conectados</string>
<string name="napplet_permissions_revoke_all">Revogar todas as permissões</string>
@@ -24,6 +24,7 @@
<string name="channel_image">Imagem do Canal</string>
<string name="referenced_event_not_found">Evento referenciado não encontrado</string>
<string name="could_not_decrypt_the_message">Não foi possível descriptografar a mensagem</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Imagem do grupo</string>
<string name="explicit_content">Conteúdo explícito</string>
<string name="relay_notice">Aviso do relay</string>
@@ -683,6 +684,7 @@
<string name="napplet_consent_query">Este nApplet quer ler eventos dos seus relays.</string>
<string name="napplet_consent_storage">Este nApplet quer usar seu armazenamento privado.</string>
<string name="napplet_consent_pay">Este nApplet quer pagar uma fatura Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Este nApplet quer buscar um recurso da web.</string>
<string name="napplet_consent_upload">Este nApplet quer enviar um arquivo para o seu servidor de mídia.</string>
<string name="napplet_consent_notify">Este nApplet quer mostrar notificações para você.</string>
@@ -691,11 +693,24 @@
<item quantity="one">Este nApplet quer pagar uma fatura Lightning de %1$d sat.</item>
<item quantity="other">Este nApplet quer pagar uma fatura Lightning de %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -31,6 +31,7 @@
<string name="channel_image">Фото канала</string>
<string name="referenced_event_not_found">Связанное событие не найдено</string>
<string name="could_not_decrypt_the_message">Не удалось расшифровать сообщение</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Фото группы</string>
<string name="explicit_content">Запрещённый контент</string>
<string name="relay_notice">Уведомление relay</string>
@@ -713,6 +714,7 @@
<string name="napplet_consent_query">Этот nApplet хочет читать события с ваших relay.</string>
<string name="napplet_consent_storage">Этот nApplet хочет использовать своё приватное хранилище.</string>
<string name="napplet_consent_pay">Этот nApplet хочет оплатить Lightning-инвойс.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Этот nApplet хочет загрузить веб-ресурс.</string>
<string name="napplet_consent_upload">Этот nApplet хочет загрузить файл на ваш медиасервер.</string>
<string name="napplet_consent_notify">Этот nApplet хочет показывать вам уведомления.</string>
@@ -723,11 +725,24 @@
<item quantity="many">Этот nApplet хочет оплатить Lightning-инвойс на %1$d sats.</item>
<item quantity="other">Этот nApplet хочет оплатить Lightning-инвойс на %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -30,6 +30,7 @@
<string name="channel_image">Изображение канала</string>
<string name="referenced_event_not_found">Указанное событие не найдено</string>
<string name="could_not_decrypt_the_message">Не удалось расшифровать сообщение</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Изображение группы</string>
<string name="explicit_content">Откровенный контент</string>
<string name="relay_notice">Уведомление relay</string>
@@ -701,6 +702,7 @@
<string name="napplet_consent_query">Этот nApplet хочет читать события с ваших relay.</string>
<string name="napplet_consent_storage">Этот nApplet хочет использовать своё приватное хранилище.</string>
<string name="napplet_consent_pay">Этот nApplet хочет оплатить Lightning-инвойс.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Этот nApplet хочет загрузить веб-ресурс.</string>
<string name="napplet_consent_upload">Этот nApplet хочет загрузить файл на ваш медиасервер.</string>
<string name="napplet_consent_notify">Этот nApplet хочет показывать вам уведомления.</string>
@@ -711,11 +713,24 @@
<item quantity="many">Этот nApplet хочет оплатить Lightning-инвойс на %1$d sats.</item>
<item quantity="other">Этот nApplet хочет оплатить Lightning-инвойс на %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -31,6 +31,7 @@
<string name="channel_image">Slika kanala</string>
<string name="referenced_event_not_found">Referenčni dogodek ni najden</string>
<string name="could_not_decrypt_the_message">Dešifriranje sporočila ni uspelo</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Slika skupine</string>
<string name="explicit_content">Eksplicitna vsebina</string>
<string name="relay_notice">Obvestilo releja</string>
@@ -783,6 +784,7 @@ Za podpisovanje se je potrebno prijaviti s privatnim ključem</string>
<string name="napplet_consent_query">Ta nApplet želi prebrati dogodke z vaših relejev.</string>
<string name="napplet_consent_storage">Ta nApplet želi uporabiti svojo zasebno shrambo.</string>
<string name="napplet_consent_pay">Ta nApplet želi plačati Lightning račun.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Ta nApplet želi pridobiti spletni vir.</string>
<string name="napplet_consent_upload">Ta nApplet želi naložiti datoteko na vaš medijski strežnik.</string>
<string name="napplet_consent_notify">Ta nApplet vam želi prikazati obvestila.</string>
@@ -793,6 +795,15 @@ Za podpisovanje se je potrebno prijaviti s privatnim ključem</string>
<item quantity="few">Ta nApplet želi plačati Lightning račun za %1$d sate.</item>
<item quantity="other">Ta nApplet želi plačati Lightning račun za %1$d satov.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Povezava z Nostrom</string>
<string name="napplet_connect_subtitle">se želi povezati z vašim nostr računom</string>
@@ -828,6 +839,10 @@ Za podpisovanje se je potrebno prijaviti s privatnim ključem</string>
<string name="napplet_op_encrypt">Šifriraj sporočilo</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">berem tvoja zasebna sporočila</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Povezane aplikacije</string>
<string name="napplet_permissions_revoke_all">Prekliči vsa dovoljenja</string>
@@ -27,6 +27,7 @@
<string name="channel_image">Слика канала</string>
<string name="referenced_event_not_found">Референтни догађај није пронађен</string>
<string name="could_not_decrypt_the_message">Није могуће дешифровати поруку</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Групна слика</string>
<string name="explicit_content">Експлицитни садржај</string>
<string name="relay_notice">Obaveštenje relay-a</string>
@@ -697,6 +698,7 @@
<string name="napplet_consent_query">Ovaj nApplet želi da pročita događaje sa vaših relay-a.</string>
<string name="napplet_consent_storage">Ovaj nApplet želi da koristi svoje privatno skladište.</string>
<string name="napplet_consent_pay">Ovaj nApplet želi da plati Lightning fakturu.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Ovaj nApplet želi da preuzme veb resurs.</string>
<string name="napplet_consent_upload">Ovaj nApplet želi da otpremi datoteku na vaš medija server.</string>
<string name="napplet_consent_notify">Ovaj nApplet želi da vam prikazuje obaveštenja.</string>
@@ -706,11 +708,24 @@
<item quantity="few">Ovaj nApplet želi da plati Lightning fakturu od %1$d sata.</item>
<item quantity="other">Ovaj nApplet želi da plati Lightning fakturu od %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">Kanal bild</string>
<string name="referenced_event_not_found">Refererad händelse hittades inte</string>
<string name="could_not_decrypt_the_message">Kunde inte dekryptera meddelandet</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Grupp bild</string>
<string name="explicit_content">Explicit Innehåll</string>
<string name="relay_notice">Relay-meddelande</string>
@@ -808,6 +809,7 @@
<string name="napplet_consent_query">Det här nApplet vill läsa händelser från dina reläer.</string>
<string name="napplet_consent_storage">Det här nApplet vill använda sin privata lagring.</string>
<string name="napplet_consent_pay">Det här nApplet vill betala en Lightning-faktura.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Det här nApplet vill hämta en webbresurs.</string>
<string name="napplet_consent_upload">Det här nApplet vill ladda upp en fil till din medieserver.</string>
<string name="napplet_consent_notify">Det här nApplet vill visa dig aviseringar.</string>
@@ -816,6 +818,15 @@
<item quantity="one">Det här nApplet vill betala en Lightning-faktura på %1$d sat.</item>
<item quantity="other">Det här nApplet vill betala en Lightning-faktura på %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">Anslut till Nostr</string>
<string name="napplet_connect_subtitle">vill ansluta till ditt Nostr-konto</string>
@@ -851,6 +862,10 @@
<string name="napplet_op_encrypt">kryptera ett meddelande</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">läsa dina privata meddelanden</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">Anslutna appar</string>
<string name="napplet_permissions_revoke_all">Återkalla alla behörigheter</string>
@@ -25,6 +25,7 @@
<string name="channel_image">Picha ya Kituo</string>
<string name="referenced_event_not_found">Tukio linalorejelewa halijapatikana</string>
<string name="could_not_decrypt_the_message">Haikuweza kusimbua ujumbe</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Picha ya Kikundi</string>
<string name="explicit_content">Maudhui Dhahiri</string>
<string name="relay_notice">Ilani ya Usambazaji</string>
@@ -693,6 +694,7 @@
<string name="napplet_consent_query">nApplet hii inataka kusoma matukio kutoka kwa relay zako.</string>
<string name="napplet_consent_storage">nApplet hii inataka kutumia hifadhi yake ya kibinafsi.</string>
<string name="napplet_consent_pay">nApplet hii inataka kulipa ankara ya Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">nApplet hii inataka kupata rasilimali ya wavuti.</string>
<string name="napplet_consent_upload">nApplet hii inataka kupakia faili kwenye seva yako ya media.</string>
<string name="napplet_consent_notify">nApplet hii inataka kukuonyesha arifa.</string>
@@ -701,11 +703,24 @@
<item quantity="one">nApplet hii inataka kulipa ankara ya Lightning ya sat %1$d.</item>
<item quantity="other">nApplet hii inataka kulipa ankara ya Lightning ya sats %1$d.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -24,6 +24,7 @@
<string name="channel_image">சேனல் படம்</string>
<string name="referenced_event_not_found">குறிப்பிடப்பட்ட நிகழ்வு கிடைக்கவில்லை</string>
<string name="could_not_decrypt_the_message">செய்தியை மறைகுறியாக்க முடியவில்லை</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">குழுப் படம்</string>
<string name="explicit_content">வெளிப்படையான உள்ளடக்கம்</string>
<string name="relay_notice">relay அறிவிப்பு</string>
@@ -697,6 +698,7 @@
<string name="napplet_consent_query">இந்த nApplet உங்கள் relays இலிருந்து நிகழ்வுகளை படிக்க விரும்புகிறது.</string>
<string name="napplet_consent_storage">இந்த nApplet அதன் தனிப்பட்ட சேமிப்பை பயன்படுத்த விரும்புகிறது.</string>
<string name="napplet_consent_pay">இந்த nApplet ஒரு Lightning இன்வாய்ஸை செலுத்த விரும்புகிறது.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">இந்த nApplet ஒரு இணைய வளத்தை பெற விரும்புகிறது.</string>
<string name="napplet_consent_upload">இந்த nApplet உங்கள் மீடியா சேவையகத்தில் ஒரு கோப்பை பதிவேற்ற விரும்புகிறது.</string>
<string name="napplet_consent_notify">இந்த nApplet உங்களுக்கு அறிவிப்புகளை காட்ட விரும்புகிறது.</string>
@@ -705,11 +707,24 @@
<item quantity="one">இந்த nApplet %1$d sat-க்கான Lightning invoice செலுத்த விரும்புகிறது.</item>
<item quantity="other">இந்த nApplet %1$d sats-க்கான Lightning invoice செலுத்த விரும்புகிறது.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -22,6 +22,7 @@
<string name="channel_image">รูปของ channel</string>
<string name="referenced_event_not_found">ไม่พบ event ที่อ้างอิง</string>
<string name="could_not_decrypt_the_message">ไม่สามารถเข้ารหัสข้อความได้</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">รูปภาพกลุ่ม</string>
<string name="explicit_content">เนื้อหาที่มีความรุนแรง</string>
<string name="relay_notice">การแจ้งเตือนจาก relay</string>
@@ -681,6 +682,7 @@
<string name="napplet_consent_query">nApplet นี้ต้องการอ่านอีเวนต์จาก relay ของคุณ</string>
<string name="napplet_consent_storage">nApplet นี้ต้องการใช้พื้นที่จัดเก็บส่วนตัวของตัวเอง</string>
<string name="napplet_consent_pay">nApplet นี้ต้องการชำระใบแจ้งหนี้ Lightning</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">nApplet นี้ต้องการดึงข้อมูลทรัพยากรเว็บ</string>
<string name="napplet_consent_upload">nApplet นี้ต้องการอัปโหลดไฟล์ไปยังเซิร์ฟเวอร์สื่อของคุณ</string>
<string name="napplet_consent_notify">nApplet นี้ต้องการแสดงการแจ้งเตือนให้คุณ</string>
@@ -688,11 +690,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">nApplet นี้ต้องการชำระใบแจ้งหนี้ Lightning เป็นจำนวน %1$d sats</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -24,6 +24,7 @@
<string name="channel_image">Kanal Resmi</string>
<string name="referenced_event_not_found">Referanslı etkinlik bulunamadı</string>
<string name="could_not_decrypt_the_message">Mesaj deşifre edilemedi</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Grup Resmi</string>
<string name="explicit_content">Müstehcen İçerik</string>
<string name="relay_notice">relay Bildirimi</string>
@@ -697,6 +698,7 @@
<string name="napplet_consent_query">Bu nApplet relay\'lerinden etkinlikleri okumak istiyor.</string>
<string name="napplet_consent_storage">Bu nApplet kendi özel depolamasını kullanmak istiyor.</string>
<string name="napplet_consent_pay">Bu nApplet bir Lightning faturası ödemek istiyor.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Bu nApplet bir web kaynağı getirmek istiyor.</string>
<string name="napplet_consent_upload">Bu nApplet medya sunucuna dosya yüklemek istiyor.</string>
<string name="napplet_consent_notify">Bu nApplet sana bildirim göstermek istiyor.</string>
@@ -705,11 +707,24 @@
<item quantity="one">Bu nApplet %1$d sat için bir Lightning faturası ödemek istiyor.</item>
<item quantity="other">Bu nApplet %1$d sat için bir Lightning faturası ödemek istiyor.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -30,6 +30,7 @@
<string name="channel_image">Фото каналу</string>
<string name="referenced_event_not_found">Пов\'язану подію не знайдено</string>
<string name="could_not_decrypt_the_message">Не вдалося розшифрувати повідомлення</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Фото групи</string>
<string name="explicit_content">Відвертий вміст</string>
<string name="relay_notice">Повідомлення relay</string>
@@ -710,6 +711,7 @@
<string name="napplet_consent_query">Цей nApplet хоче читати події з ваших relay.</string>
<string name="napplet_consent_storage">Цей nApplet хоче використовувати своє приватне сховище.</string>
<string name="napplet_consent_pay">Цей nApplet хоче оплатити Lightning-інвойс.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Цей nApplet хоче отримати веб-ресурс.</string>
<string name="napplet_consent_upload">Цей nApplet хоче завантажити файл на ваш медіасервер.</string>
<string name="napplet_consent_notify">Цей nApplet хоче показати вам сповіщення.</string>
@@ -720,11 +722,24 @@
<item quantity="many">Цей nApplet хоче оплатити Lightning-інвойс на %1$d sats.</item>
<item quantity="other">Цей nApplet хоче оплатити Lightning-інвойс на %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -25,6 +25,7 @@
<string name="channel_image">Kanal rasmi</string>
<string name="referenced_event_not_found">Havola qilingan post topilmadi</string>
<string name="could_not_decrypt_the_message">Xabarni shifrdan chiqarib bo\'lmadi</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Guruh rasmi</string>
<string name="explicit_content">Uyatsiz kontent</string>
<string name="relay_notice">Relay bildirishnomasi</string>
@@ -700,6 +701,7 @@
<string name="napplet_consent_query">Bu nApplet relaylaringizdan voqealarni o\'qishni xohlaydi.</string>
<string name="napplet_consent_storage">Bu nApplet o\'zining xususiy saqlash joyidan foydalanishni xohlaydi.</string>
<string name="napplet_consent_pay">Bu nApplet Lightning hisob-fakturasini to\'lashni xohlaydi.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">Bu nApplet veb resursini olishni xohlaydi.</string>
<string name="napplet_consent_upload">Bu nApplet media serveringizga fayl yuklashni xohlaydi.</string>
<string name="napplet_consent_notify">Bu nApplet sizga bildirishnomalar ko\'rsatishni xohlaydi.</string>
@@ -708,11 +710,24 @@
<item quantity="one">Bu nApplet %1$d sat uchun Lightning hisob-fakturasini to\'lamoqchi.</item>
<item quantity="other">Bu nApplet %1$d sats uchun Lightning hisob-fakturasini to\'lamoqchi.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -21,6 +21,7 @@
<string name="channel_image">Ảnh kênh</string>
<string name="referenced_event_not_found">Không tìm thấy sự kiện được tham chiếu</string>
<string name="could_not_decrypt_the_message">Không thể giải mã tin nhắn</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">Hình ảnh nhóm</string>
<string name="explicit_content">Nội dung người lớn</string>
<string name="relay_notice">Thông báo từ relay</string>
@@ -680,6 +681,7 @@
<string name="napplet_consent_query">nApplet này muốn đọc sự kiện từ các relay của bạn.</string>
<string name="napplet_consent_storage">nApplet này muốn sử dụng bộ nhớ riêng tư của nó.</string>
<string name="napplet_consent_pay">nApplet này muốn thanh toán một hóa đơn Lightning.</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">nApplet này muốn tải một tài nguyên web.</string>
<string name="napplet_consent_upload">nApplet này muốn tải tệp lên máy chủ phương tiện của bạn.</string>
<string name="napplet_consent_notify">nApplet này muốn hiển thị thông báo cho bạn.</string>
@@ -687,11 +689,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">nApplet này muốn thanh toán hóa đơn Lightning %1$d sats.</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -22,6 +22,7 @@
<string name="channel_image">频道图片</string>
<string name="referenced_event_not_found">未找到相关事件</string>
<string name="could_not_decrypt_the_message">无法解密消息</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">群聊图片</string>
<string name="explicit_content">露骨内容</string>
<string name="relay_notice">中继通知</string>
@@ -798,6 +799,7 @@
<string name="napplet_consent_query">此 nApplet 想要从您的中继读取事件。</string>
<string name="napplet_consent_storage">此 nApplet 想要使用其私密存储。</string>
<string name="napplet_consent_pay">此 nApplet 想要支付闪电发票。</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">此 nApplet 想要获取一个 web 资源。</string>
<string name="napplet_consent_upload">此 nApplet 想要上传一个文件到您的媒体服务器。</string>
<string name="napplet_consent_notify">此 nApplet 想要向您显示通知。</string>
@@ -805,6 +807,15 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">此 nApplet 想要支付 %1$d sat 的闪电发票。</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<string name="napplet_connect_title">连接到 Nostr</string>
<string name="napplet_connect_subtitle">想要连接到您的 Nostr 帐户</string>
@@ -840,6 +851,10 @@
<string name="napplet_op_encrypt">加密消息</string>
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<string name="napplet_op_decrypt">读取您的私信</string>
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<string name="napplet_permissions_title">已连接的应用程序</string>
<string name="napplet_permissions_revoke_all">撤销所有权限</string>
@@ -21,6 +21,7 @@
<string name="channel_image">頻道圖片</string>
<string name="referenced_event_not_found">未找到相關事件</string>
<string name="could_not_decrypt_the_message">無法解密消息</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">羣聊圖片</string>
<string name="explicit_content">明確內容</string>
<string name="relay_notice">中继通知</string>
@@ -696,6 +697,7 @@
<string name="napplet_consent_query">此 nApplet 想要从您的中继读取事件。</string>
<string name="napplet_consent_storage">此 nApplet 想要使用其私密存储。</string>
<string name="napplet_consent_pay">此 nApplet 想要支付闪电发票。</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">此 nApplet 想要获取一个 web 资源。</string>
<string name="napplet_consent_upload">此 nApplet 想要上传一个文件到您的媒体服务器。</string>
<string name="napplet_consent_notify">此 nApplet 想要向您显示通知。</string>
@@ -703,11 +705,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">此 nApplet 想要支付 %1$d sat 的闪电发票。</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -21,6 +21,7 @@
<string name="channel_image">频道图片</string>
<string name="referenced_event_not_found">未找到相关事件</string>
<string name="could_not_decrypt_the_message">无法解密消息</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">群聊图片</string>
<string name="explicit_content">露骨内容</string>
<string name="relay_notice">中继通知</string>
@@ -696,6 +697,7 @@
<string name="napplet_consent_query">此 nApplet 想要从您的中继读取事件。</string>
<string name="napplet_consent_storage">此 nApplet 想要使用其私密存储。</string>
<string name="napplet_consent_pay">此 nApplet 想要支付闪电发票。</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">此 nApplet 想要获取一个 web 资源。</string>
<string name="napplet_consent_upload">此 nApplet 想要上传一个文件到您的媒体服务器。</string>
<string name="napplet_consent_notify">此 nApplet 想要向您显示通知。</string>
@@ -703,11 +705,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">此 nApplet 想要支付 %1$d sat 的闪电发票。</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->
@@ -22,6 +22,7 @@
<string name="channel_image">頻道圖片</string>
<string name="referenced_event_not_found">未找到相關事件</string>
<string name="could_not_decrypt_the_message">無法解密消息</string>
<!-- Placeholder shown in a chat row while an encrypted message is still being decrypted -->
<string name="group_picture">群組圖片</string>
<string name="explicit_content">露骨內容</string>
<string name="relay_notice">Relay 通知</string>
@@ -690,6 +691,7 @@
<string name="napplet_consent_query">此 nApplet 想要從您的 relay 讀取事件。</string>
<string name="napplet_consent_storage">此 nApplet 想要使用其私有儲存空間。</string>
<string name="napplet_consent_pay">此 nApplet 想要支付一筆 Lightning 發票。</string>
<!-- An amountless BOLT11: the payee decides how much. Never render this as "0 sats". -->
<string name="napplet_consent_resource">此 nApplet 想要擷取一個網路資源。</string>
<string name="napplet_consent_upload">此 nApplet 想要上傳檔案至您的媒體伺服器。</string>
<string name="napplet_consent_notify">此 nApplet 想要向您顯示通知。</string>
@@ -697,11 +699,24 @@
<plurals name="napplet_consent_pay_amount">
<item quantity="other">此 nApplet 想要支付一筆 %1$d sats 的 Lightning 發票。</item>
</plurals>
<!-- Consequence lines for event kinds whose payload lives entirely in the tags, so a
kind-only summary would hide what is actually being signed. These replaceable lists are
already cached on the account, so the dialog diffs the proposed list against the current
one and reports what actually changes rather than a raw total. -->
<!-- Single-account edits, by far the common case: name who it is instead of counting. %1$s is
the display name, shown next to their avatar. -->
<!-- %1$s is the joined change list, e.g. "follows 2 new accounts and UNFOLLOWS 130 accounts". -->
<!-- Re-publishing an identical list is harmless; say so rather than raising a false alarm. -->
<!-- No cached copy to compare against, so the whole list is what gets written. -->
<!-- Signer permissions: first-connect dialog -->
<!-- Signer trust levels -->
<!-- Signer per-op consent dialog -->
<!-- Signer op labels -->
<!-- Decrypt: the message is already decrypted by Amethyst; the permission is to expose it to the app -->
<!-- Decrypt scoped to one counterparty. %1$s is that person's name (or a shortened npub) -->
<!-- Narrower "remember" choice offered next to "Always allow". %1$s is the counterparty's name -->
<!-- Shown as the preview when Amethyst itself cannot decrypt the message the app asked to read -->
<!-- Label above the counterparty avatar in the decrypt consent dialog -->
<!-- Permissions management screen -->
<!-- NIP-46 remote signer (bunker) -->
<!-- Relay Authentication (NIP-42) settings -->