Files
Termix/plugins/alerts/locales/translated/fr_FR.json
T
Luke GustafsonandZacharyZcR 6b708106e1 release-2.9.1 (#1557)
* fix(sso): send the PKCE verifier for GitHub login (#1534)

* fix(remote-desktop): clip cursor overflow without disabling zoom (#1535)

* test(remote-desktop): preserve sessions beyond one hour (#1536)

* fix(hosts): expose controls for overflowing editor tabs (#1537)

* fix(hosts): expose controls for overflowing editor tabs

* test(hosts): mock resize observation in admin panel tests

* fix(status): skip TCP probes while host sessions are active (#1538)

* fix(database): batch session activity persistence (#1539)

* docs(api): describe cookie and API key authentication (#1540)

* fix(snippets): repair missing note column on SQLite upgrades (#1541)

* fix(docker): retain stored SSH credential association (#1543)

* fix(file-manager): render transfer toasts without plugin hooks (#1546)

* feat(hosts): keep compact row actions inline (#1547)

* fix(auth): allow retrying unavailable second-factor interfaces (#1549)

* fix(auth): reject unresolved legacy identity provisioning (#1550)

* fix(desktop): ship the plugin SDK inside Mac App Store builds (#1551)

* fix(tmux): pass full session info to the terminal's session picker (#1552)

The tmux.sessions service reduced detected sessions to bare names, but the
picker reads session.name, so every entry rendered blank and selecting one
sent an empty name, which created a new session instead of attaching.

* fix(ssh): read force keyboard-interactive as a boolean when resolving hosts (#1553)

The column holds the text "true"/"false", and the resolver passed it
through as-is. The string "false" is truthy, so the password provider
treated every saved host as forced keyboard-interactive and left the
password out. Jump hops are built straight from the resolved host, so a
password hop whose server doesn't offer keyboard-interactive failed with
"All configured authentication methods failed".

* fix(database): batch database saves for bulk host writes (#1554)

* fix(database): yield to the event loop between database saves

Each SQLite save serializes and encrypts the whole database into new
buffers, which V8 only releases once the event loop turns. Boot
migrations and bulk host import write plugin settings per host and per
key in an awaited loop, so hundreds of full copies piled up and the
container ran out of memory.

* fix(database): save once per bulk host write instead of once per row

On SQLite every repository write force-saves the whole database. Boot
plugin data migrations, host defaults materialization and the bulk
host routes write one row per host per setting, so they serialized and
encrypted the full database hundreds of times in a row.

DatabaseSaveTrigger.batched wraps a function so force saves made while
it runs collapse into a single save when it finishes. Nested scopes fold
into the outer one, and work that outlives its scope saves normally.

* feat(hosts): add instance-wide predefined tag suggestions (#1548)

* feat(hosts): add shared predefined tag suggestions

* style(hosts): format tag catalog routes

* test(database): advance fake timers past the save yield (#1555)

* fix(i18n): complete Simplified Chinese core and plugin translations (#1542)

* fix(i18n): complete Chinese onboarding and navigation labels

* fix(i18n): translate remaining Chinese core and plugin interfaces

* fix(i18n): translate host editor tab overflow controls

* fix(i18n): use consistent Chinese fleet terminology

* fix(i18n): localize hardcoded controls and plugin views

* fix(i18n): translate built-in homepage widget catalog

* test(homepage): follow translated timezone placeholder

* fix(i18n): translate plugin-provided homepage widgets

* fix(i18n): localize feature settings section titles

* fix: 2.8 oidc accounts unable to sign in after upgrading (#1381)

* fix: plugins losing the saved ssh login when copying a host (#1391)

* fix: fleets, proxmox and automations not getting the host sudo password

* fix: host imports running a defaults pass and metrics restart per host (#1384)

* fix: high cpu from status probes and full database saves on every sample (#1300)

* fix: user data export freezing the server (#1393)

* fix: op:// secret references rejected as ssh keys on credentials (#1394)

* fix: slow file deletes from the trash lookups on every delete (#1390)

* fix: add openapi docs and error handling to host tag routes

* test: compare download stream buffers directly so it stops timing out

* chore: drop em dash from host row comment

* chore: update release notes for 2.9.1

* fix: restore space to add host tags and redesign predefined tags editor

* fix: host key silently accepted when the host is missing from the database (#1397)

* fix: clearer host login failed status label and fix its translations (#1396)

* chore: add host key and status label fixes to release notes

* fix: sso and ldap provider dialogs overflowing the screen and using mismatched toggles

* chore: increment ver

* fix(audit): store plugin entries with no acting user as a null user_id (#1556)

Plugin audit entries written outside a request used the literal "system"
as user_id. That column references users.id, so the insert was refused
(Postgres logs it as an FK violation) and the entry was silently dropped.
Write null instead and keep "system" / plugin:<id> in username.

* chore: add sso/ldap dialog and audit log fixes to release notes

* fix: tunnels and host settings missing from shared hosts on desktop

* fix: remote desktop logins missing from shared hosts on desktop

* fix: simplify host status to online/offline and keep it live without a refresh

* chore: sync Crowdin translations for 2.9.1

---------

Co-authored-by: ZacharyZcR <zacharyzcr1984@gmail.com>
2026-10-04 15:11:41 -05:00

176 lines
6.6 KiB
JSON
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"nav": {
"alerts": "Alertes"
},
"permissions": {
"use": {
"title": "Utiliser les alertes",
"description": "Recevez des alertes dans votre boîte de réception et transférez-les sur vos propres canaux."
}
},
"onboarding": {
"feature": "Alertes",
"featureDesc": "Toutes les alertes dans une seule boîte de réception, envoyées sur Discord, ntfy, par e-mail ou via un webhook si vous le souhaitez."
},
"settings": {
"group": {
"general": "Général",
"email": "E-mail"
},
"admin": {
"announcements": {
"label": "Annonces de Termix",
"description": "Afficher les actualités de l'équipe Termix, telles que les avis de sécurité et les nouvelles versions, dans la boîte de réception de tous."
},
"retentionDays": {
"label": "Conserver les alertes pendant (jours)",
"description": "Les alertes les plus anciennes sont supprimées de chaque boîte de réception."
},
"smtpHost": {
"label": "Serveur SMTP",
"description": "Nécessaire pour les canaux de messagerie. Laisser vide pour désactiver les e-mails.",
"placeholder": "smtp.example.com"
},
"smtpPort": {
"label": "Port SMTP",
"description": "Généralement 587 avec STARTTLS ou 465 avec TLS."
},
"smtpSecure": {
"label": "Utilisez TLS dès le début",
"description": "Activez le port 465. Désactivez le port 587, qui passe automatiquement au protocole TLS."
},
"smtpUser": {
"label": "Nom d'utilisateur SMTP",
"description": "Laissez ce champ vide si le serveur ne nécessite pas d'authentification."
},
"smtpPassword": {
"label": "Mot de passe SMTP",
"description": "Stocké de manière cryptée."
},
"smtpFrom": {
"label": "Adresse de départ",
"description": "L'expéditeur des alertes provient de :",
"placeholder": "Termix <alerts@example.com>"
}
},
"user": {
"popups": {
"label": "fenêtres contextuelles d'alerte",
"description": "Quelles nouvelles alertes s'affichent lorsque vous utilisez Termix ? Elles arrivent toujours dans votre boîte de réception.",
"all": "Toutes les alertes",
"warning": "Avertissements et critiques",
"critical": "Critique uniquement",
"off": "Aucune"
}
}
},
"sections": {
"inbox": "Boîte de réception",
"channels": "Canaux",
"rules": "Règles de livraison"
},
"severity": {
"info": "Info",
"success": "Succès",
"warning": "Avertissement",
"critical": "Critique"
},
"inbox": {
"sourceTermix": "Termix",
"openLink": "Ouvrir",
"view": "Consultation",
"unread": "Non lu",
"deliveryFailed_one": "Le canal {{count}} a échoué",
"deliveryFailed_other": "Les canaux {{count}} ont échoué",
"markRead": "Marquer comme lu",
"markUnread": "Marquer comme non lu",
"markAllRead": "Marquer tout comme lu",
"delete": "Supprimer",
"clearRead": "Supprimer les alertes de lecture",
"cleared_one": "Alerte {{count}} supprimée",
"cleared_other": "Alertes supprimées {{count}}",
"filterAll": "Tout",
"filterUnread": "Non lu",
"anySeverity": "Toute gravité",
"anySource": "Toute source",
"openAll": "Ouvrir dans un onglet",
"empty": "Aucune alerte pour le moment.",
"emptyUnread": "Vous êtes à jour.",
"loadMore": "Charger plus"
},
"channels": {
"intro": "Les canaux permettent aux alertes de sortir de Termix. Les règles de diffusion déterminent quelles alertes les utilisent.",
"add": "Ajouter une chaîne",
"edit": "Modifier la chaîne",
"test": "Envoyer un test",
"testSent": "Alerte de test envoyée",
"testFailed": "Test échoué : {{error}}",
"deleteConfirm": "Supprimer le canal \"{{name}}\"?",
"deleted": "Chaîne supprimée",
"empty": "Aucune chaîne pour le moment.",
"enabled": "Activé",
"needsSave": "Ce canal doit être ouvert et enregistré à nouveau avant de pouvoir envoyer des données.",
"name": "Nom",
"nameRequired": "Le nom est obligatoire",
"type": "Type",
"types": {
"webhook": "Webhook",
"ntfy": "ntfy",
"discord": "Discord",
"email": "E-mail"
},
"emailUnavailable": "La messagerie électronique nécessite un serveur SMTP, que l'administrateur configure dans les paramètres d'alertes.",
"webhookUrl": "URL",
"webhookHint": "Récupère un corps JSON pour chaque alerte.",
"method": "Méthode",
"headers": "En-têtes",
"headersHint": "Une par ligne, comme Nom : valeur.",
"ntfyServer": "URL du serveur",
"ntfyTopic": "Sujet",
"ntfyToken": "Jeton d'accès (facultatif)",
"discordUrl": "URL du webhook Discord",
"discordHint": "Dans les paramètres de la chaîne sur Discord, sous Intégrations.",
"discordUsername": "Nom d'affichage (facultatif)",
"discordAvatar": "URL de l'avatar (facultatif)",
"emailTo": "Envoyer à",
"emailHint": "Séparez les adresses multiples par des virgules.",
"privateNetwork": "Autoriser une adresse réseau privée",
"privateNetworkHint": "Fonctionne uniquement pour les hôtes autorisés par un administrateur dans la liste des points de terminaison privés."
},
"rules": {
"intro": "Une règle de diffusion envoie des alertes correspondantes à vos canaux. Les alertes restent également disponibles dans votre boîte de réception.",
"add": "Ajouter une règle",
"edit": "Règle de modification",
"empty": "Aucune règle n'a encore été définie, les alertes n'apparaissent donc que dans la boîte de réception.",
"needChannel": "Commencez par ajouter un canal.",
"enabled": "Activé",
"name": "Nom",
"nameRequired": "Le nom est obligatoire",
"match": "Alertes à envoyer",
"matchHint": "* Pour tout, les automatisations.* Pour tout ce qui concerne les automatisations, ou un type précis.",
"minSeverity": "Au moins",
"channels": "Envoyer à",
"channelRequired": "Choisissez au moins une chaîne",
"deleteConfirm": "Supprimer la règle \"{{name}}\"?",
"everything": "Tout",
"summary": "{{match}}, {{severity}} ou supérieur, à {{channels}}"
},
"actions": {
"cancel": "Annuler",
"save": "Enregistrer",
"saving": "Enregistrement…",
"delete": "Supprimer"
},
"widget": {
"name": "Flux d'alertes",
"description": "Vos dernières alertes, avec un moyen rapide de les marquer comme lues",
"maxItems": "Articles maximum",
"showRead": "Afficher les alertes de lecture",
"allClear": "Aucune alerte",
"loading": "Chargement..."
},
"plugin": {
"name": "Alerts"
}
}