ldapsaisie/src/lang/fr_FR.UTF8/LC_MESSAGES/ldapsaisie.po

2758 lines
113 KiB
Text
Raw Normal View History

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: LdapSaisie\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: \n"
"PO-Revision-Date: 2021-02-05 10:32+0100\n"
"Last-Translator: Benjamin Renard <brenard@zionetrix.net>\n"
"Language-Team: LdapSaisie <ldapsaisie-users@lists.labs.libre-entreprise."
"org>\n"
"Language: fr_FR\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-SourceCharset: utf-8\n"
"X-Poedit-Basepath: /var/www/ldapsaisie/trunk\n"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
"X-Generator: Poedit 2.4.2\n"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.samba.php:27
msgid "SAMBA Support: Unable to load smbHash class."
2018-08-31 17:28:55 +02:00
msgstr "Support SAMBA : Impossible de charger la classe smbHash."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.samba.php:30
msgid "SAMBA Support: The constant %{const} is not defined."
2018-08-31 17:28:55 +02:00
msgstr "Support SAMBA : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.samba.php:34
2018-06-09 00:07:44 +02:00
msgid ""
"SAMBA Support: The constants LS_SAMBA_SID_BASE_USER and "
2018-08-31 17:28:55 +02:00
"LS_SAMBA_SID_BASE_GROUP must'nt have the same parity to keep SambaSID's "
"unicity."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Support SAMBA : Les constantes LS_SAMBA_SID_BASE_USER et "
"LS_SAMBA_SID_BASE_GROUP ne doivent pas avoir la même parité pour préserver "
"l'unicité des SambaSID."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.samba.php:39
2018-06-09 00:07:44 +02:00
msgid ""
"SAMBA Support: The attribute %{dependency} is missing. Unable to forge the "
2018-08-31 17:28:55 +02:00
"attribute %{attr}."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Support SAMBA : L'attribut %{dependency} est manquant. Impossible de générer "
"l'attribut %{attr}."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.samba.php:42
msgid "SAMBA Support: Can't get the sambaUnixIdPool object."
msgstr "SAMBA Support : Impossible de récupérer l'objet sambaUnixIdPool."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.samba.php:45
msgid "SAMBA Support: Error modifying the sambaUnixIdPool object."
msgstr ""
"SAMBA Support : Erreur durant la modification de l'objet sambaUnixIdPool."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.samba.php:48
msgid "SAMBA Support: The %{attr} of the sambaUnixIdPool object is incorrect."
2018-06-09 00:07:44 +02:00
msgstr ""
"SAMBA Support : L'attribut %{attr} de l'objet sambaUnixIdPool est incorrect."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:31
msgid "SSH Support : PhpSecLib is missing."
msgstr "Support SSH : la librairie PhpSecLib est manquante."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:35
msgid "SSH Support : The constant %{const} is not defined."
msgstr "Support SSH : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:41
msgid "SSH : Invalid connection paramater : %{param} parameter is missing."
msgstr ""
"SSH : Paramètre de connexion invalide : le paramètre %{param} est manquant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:44
msgid ""
"SSH : Authentication key file not found (or not accessible, file path : "
"'%{path}')"
msgstr ""
"SSH : le fichier de la clé d'authentification est introuvable (ou "
"inaccessible, chemin du fichier '%{path}')"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:47
msgid "SSH : Fail to load authentication key (%{path})."
msgstr "SSH : Impossible de chargé la clé d'authentification (%{path})"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:50
msgid "SSH : Unable to connect to SSH Server (%{host}:%{port})."
msgstr "SSH : Impossible de se connecter au serveur SSH (%{host}:%{port})."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:53
msgid "SSH : Unable to make directory %{dir} on the remote server."
msgstr "SSH : Impossible de créer le dossier %{dir} sur le serveur distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:56
msgid "SSH : Unable to delete directory %{dir} on the remote server."
msgstr ""
"SSH : Impossible de supprimer le dossier %{dir} sur le serveur distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ssh.php:59
msgid ""
"SSH : Unable to rename folder from %{old} to %{new} on the remote server."
msgstr "SSH : Impossible de renommer le dossier %{dir} sur le serveur distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.exportSearchResultAsCSV.php:27
2018-08-31 17:28:55 +02:00
msgid "ExportSearchResultAsCSV Support : function fputcsv is not available."
msgstr ""
"Support ExportSearchResultAsCSV : la fonction fputcsv n'est pas disponible."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.exportSearchResultAsCSV.php:30
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"ExportSearchResultAsCSV Support : The constant %{const} is not defined.."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Support ExportSearchResultAsCSV : La constante %{const} n'est pas définie."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.exportSearchResultAsCSV.php:35
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"ExportSearchResultAsCSV Error : An error occured generating CSV outfile "
"memory space."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Erreur ExportSearchResultAsCSV : Une erreur est survenue en générant "
"l'espace mémoire pour le fichier CSV."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.exportSearchResultAsCSV.php:38
2018-08-31 17:28:55 +02:00
msgid "ExportSearchResultAsCSV Error : An error occured executing the search."
msgstr ""
"Erreur ExportSearchResultAsCSV : Une erreur est survenue en exécutant la "
"recherche."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.exportSearchResultAsCSV.php:41
2018-08-31 17:28:55 +02:00
msgid "ExportSearchResultAsCSV Error : An error occured writing CSV header."
msgstr ""
"Erreur ExportSearchResultAsCSV : Une erreur est survenue en écrivant les "
"entêtes CSV."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.exportSearchResultAsCSV.php:44
2018-08-31 17:28:55 +02:00
msgid "ExportSearchResultAsCSV Error : An error occured writing a CSV row."
msgstr ""
"Erreur ExportSearchResultAsCSV : Une erreur est survenue en écrivant une "
"ligne CSV."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mail.php:27
2018-08-31 17:28:55 +02:00
msgid "MAIL Support : Pear::MAIL is missing."
msgstr "Support MAIL : Pear::MAIL est manquant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mail.php:30
2020-04-29 15:38:41 +02:00
msgid "MAIL Support : Pear::MAIL_MIME is missing."
msgstr "Support MAIL : Pear::MAIL_MIME est manquant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mail.php:35
2018-08-31 17:28:55 +02:00
msgid "MAIL Error : %{msg}"
msgstr "Erreur MAIL : %{msg}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mail.php:39
2018-08-31 17:28:55 +02:00
msgid "MAIL : Error sending your email"
2020-04-29 15:38:41 +02:00
msgstr "MAIL : Erreur durant l'envoie de votre mail"
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.phpldapadmin.php:27
msgid "PhpLdapAdmin Support : The constant %{const} is not defined."
msgstr "Support PhpLdapAdmin : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.posix.php:27
2018-06-09 00:07:44 +02:00
msgid "POSIX Support : The constant %{const} is not defined."
msgstr "Support POSIX : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.posix.php:31
2018-06-09 00:07:44 +02:00
msgid "POSIX Support : Unable to load LSaddon::FTP."
msgstr "Support POSIX : Impossible de charger LSaddon::FTP."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.posix.php:36
2018-06-09 00:07:44 +02:00
msgid ""
"POSIX : The attribute %{dependency} is missing. Unable to forge the "
"attribute %{attr}."
msgstr ""
"Support POSIX : L'attribut %{dependency} est manquant. Impossible de générer "
"l'attribut %{attr}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:27
2018-08-31 17:28:55 +02:00
msgid "SUPANN Support : The constant %{const} is not defined."
msgstr "Support SUPPAN : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:30
2018-08-31 17:28:55 +02:00
msgid ""
"SUPANN Support : The LSobject type %{type} does not exist. Can't work with "
"entities.."
msgstr ""
"Support SUPPAN : Le type d'LSobject %{type} n'existe pas. Impossible de "
"travailler sur avec les entités.."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:33
2018-08-31 17:28:55 +02:00
msgid "SUPANN Support : The global array %{array} is not defined."
msgstr "Support SUPPAN : Le tableau global %{array} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:38
2018-08-31 17:28:55 +02:00
msgid ""
"SUPANN: The attribute %{dependency} is missing. Unable to forge the "
2018-08-31 17:28:55 +02:00
"attribute %{attr}."
msgstr ""
"SUPANN : L'attribut %{dependency} est manquant. Impossible de générer "
"l'attribut %{attr}."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:41
2018-08-31 17:28:55 +02:00
msgid ""
"SUPANN: Can't get the basedn of entities. Unable to forge the attribute "
"%{attr}."
2018-08-31 17:28:55 +02:00
msgstr ""
"SUPANN : Impossible de récupérer le basedn des entités. Impossible de "
"générer l'attribut %{attr}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:44
msgid "SUPANN: This entity have children entities and could be deleted."
msgstr "SUPANN : Cette entité a des entités filles et ne peut être supprimée."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:319
msgid "Entity %{id} (unrecognized)"
msgstr "Entité %{id} (non-reconnue)"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.supann.php:414
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select.php:58
2020-05-19 18:26:41 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:102
msgid "%{value} (unrecognized value)"
msgstr "%{value} (valeur non-reconnue)"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.LSaccessRightsMatrixView.php:26
2019-10-10 18:28:58 +02:00
msgid "Access Right Matrix Support : The global array %{array} is not defined."
msgstr ""
"Support Matrice des droits d'accès : Le tableau global %{array} n'est pas "
"défini."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.LSaccessRightsMatrixView.php:52
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.LSaccessRightsMatrixView.php:187
2019-10-10 18:28:58 +02:00
msgid "Access rights matrix"
msgstr "Matrice des droits d'accès"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.LSaccessRightsMatrixView.php:62
msgid "All connected users"
msgstr "Tous les utilisateurs connectés"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.LSaccessRightsMatrixView.php:183
msgid "The user him-self"
msgstr "L'utilisateur lui-même"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:27
2018-06-09 00:07:44 +02:00
msgid "FTP Support : Pear::Net_FTP is missing."
msgstr "Support FTP : Pear::Net_FTP n'est pas installé."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:31
2018-06-09 00:07:44 +02:00
msgid "FTP Support : The constant %{const} is not defined."
msgstr "Support FTP : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:37
2018-06-09 00:07:44 +02:00
msgid "Net_FTP Error : %{msg}"
msgstr "Net_FTP Erreur : %{msg}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:41
2018-06-09 00:07:44 +02:00
msgid "FTP Support : Unable to connect to FTP Server (Step : %{step})."
msgstr ""
"Support FTP : Impossible de se connecter au serveur FTP (Étape : %{step})"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:44
2018-06-09 00:07:44 +02:00
msgid "FTP Support : Unable to make directory %{dir} on the remote server."
msgstr ""
"Support FTP : Impossible de créer le dossier %{dir} sur le serveur distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:47
2018-06-09 00:07:44 +02:00
msgid "FTP Support : Unable to delete directory %{dir} on the remote server."
msgstr ""
"Support FTP : Impossible de supprimer le dossier %{dir} sur le serveur "
"distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:50
2018-06-09 00:07:44 +02:00
msgid ""
"FTP Support : Unable to modify rights on the directory %{dir} on the remote "
"server."
msgstr ""
"Support FTP : Impossible de modifier les droits sur le dossier %{dir} sur le "
"serveur distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.ftp.php:53
2018-06-09 00:07:44 +02:00
msgid ""
"FTP Support : Unable to rename folder from %{old} to %{new} on the remote "
"server."
msgstr ""
"Support FTP : Impossible de renommer le dossier %{old} en %{new} sur le "
"serveur distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mailquota.php:27
2019-06-17 12:36:01 +02:00
msgid "MAILQUOTA Support : The constant %{const} is not defined."
msgstr "Support MAILQUOTA : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mailquota.php:30
2019-06-17 12:36:01 +02:00
msgid "MAILQUOTA Support : The IMAP PHP module is not available."
msgstr "Support MAILQUOTA : Le module IMAP pour PHP n'est pas disponible."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mailquota.php:35
2019-06-17 12:36:01 +02:00
msgid "MAILQUOTA : Fail to connect on IMAP server : %{error}"
msgstr "MAILQUOTA : Impossible de se connecter au serveur IMAP : %{error}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mailquota.php:38
2019-06-17 12:36:01 +02:00
msgid "MAILQUOTA : Unexpected error occured retreiving mailbox quota usage."
msgstr ""
"MAILQUOTA : Une erreur inattendue est survenue en récupérant l'utilisation "
"du quota de la boîte mail."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mailquota.php:41
2019-06-17 12:36:01 +02:00
msgid "MAILQUOTA : Fail to compose IMAP mailbox username."
msgstr ""
"MAILQUOTA : Impossible de composer l'identifiant IMAP de la boîte mail."
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mailquota.php:150
2019-06-17 12:36:01 +02:00
msgid "Mailbox quota usage : %{usage} / %{limit}"
msgstr "Utilisation de la boîte mail : %{usage} / %{limit}"
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.mailquota.php:158
2019-06-17 12:36:01 +02:00
msgid "Unlimited"
msgstr "Illimité"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.maildir.php:27
msgid "MAILDIR Support : Unable to load LSaddon::FTP."
msgstr "Support MAILDIR : Impossible de charger LSaddon::FTP."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.maildir.php:30
msgid "MAILDIR Support : The constant %{const} is not defined."
msgstr "Support MAILDIR : La constante %{const} n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.maildir.php:35
msgid "MAILDIR : Error creating maildir on the remote server."
msgstr ""
"MAILDIR : Erreur durant la création du dossier des mails sur le serveur "
"distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.maildir.php:38
msgid "MAILDIR : Error deleting the maildir on the remote server."
msgstr ""
"MAILDIR : Erreur durant la suppression du dossier des mails sur le serveur "
"distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.maildir.php:41
msgid "MAILDIR : Error renaming the maildir on the remote server."
msgstr ""
"MAILDIR : Erreur durant le renommage du dossier des mails sur le serveur "
"distant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.maildir.php:44
msgid "MAILDIR : Error retrieving remote path of the maildir."
msgstr ""
"MAILDIR : Erreur durant la récupération du chemin distant du dossier des "
"mails."
2020-09-21 15:47:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:63
#: templates/default/showTechInfo.tpl:16
msgid "Structural object class"
msgstr "Classe d'objet structurelle"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:64
msgid "Creation date"
msgstr "Date de création"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:65
msgid "Creator DN"
msgstr "DN du créateur"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:66
msgid "Last modification date"
msgstr "Date de dernière modification"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:67
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:68
msgid "Last modifier DN"
msgstr "DN de l'utilisateur ayant modifié en dernier l'objet"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:69
msgid "LDAP entry change sequence number"
msgstr "Numéro séquence de changement de l'entrée LDAP"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:70
msgid "LDAP entry UUID"
msgstr "UUID de l'entrée LDAP"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:71
msgid "LDAP entry has children"
msgstr "L'entrée LDAP as des enfants"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:92
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_boolean.php:60
msgid "Yes"
msgstr "Oui"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:94
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_boolean.php:61
msgid "No"
msgstr "Non"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:114
msgid "%{name}: Technical information"
msgstr "%{name} : Informations techniques"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.showTechInfo.php:118
msgid "Go back"
msgstr "Retour"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.asterisk.php:27
2018-08-31 17:28:55 +02:00
msgid "Asterisk Support : The constant %{const} is not defined."
msgstr "Support Asterisk : La constante %{const} n'est pas définie."
2015-07-30 16:46:29 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.asterisk.php:30
2018-08-31 17:28:55 +02:00
msgid "Asterisk : The function %{function} only work with %{objectName}."
msgstr ""
"Asterisk : La fonction %{function} ne fonctionne qu'avec %{objectName}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.asterisk.php:33
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"Asterisk : The attribute %{dependency} is missing. Unable to generate MD5 "
"hashed password."
msgstr ""
2018-08-31 17:28:55 +02:00
"Asterisk : L'attribut %{dependency} est manquant. Impossible de générer le "
"mot de passe haché en MD5."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/addons/LSaddons.asterisk.php:36
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"Asterisk : Clear password not availlable. Unable to generate MD5 hashed "
"password."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Asterisk : Le mot de passe en clair est indisponible. Impossible de générer "
"le mot de passe haché en MD5."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSmail.php:74
2018-08-31 17:28:55 +02:00
msgid "Your message has been sent successfully."
msgstr "Votre message a bien été envoyé."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule.php:84
msgid "LSformRule_%{type}: Parameter %{param} is not found."
2018-08-31 17:28:55 +02:00
msgstr "LSformRule_%{type} : Le paramètre %{param} n'est pas défini."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule.php:87
msgid "LSformRule: Unknown rule type %{type}."
msgstr "LSformRule : Type de règle %{type} inconnu."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:208
msgid "Failed to set post data on creation form."
msgstr "Impossible de définir les données dans le formulaire de création."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:214
msgid "Error validating creation form."
msgstr "Une erreur est survenue en validant le formulaire de création."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:219
msgid "Failed to validate object data."
msgstr "Impossible de valider les données de l'objet."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:226
msgid "Failed to generate DN for this object."
msgstr "Impossible de générer le DN de cet objet."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:240
msgid "Error creating object on LDAP server."
msgstr "Une erreur est survenue en création cet objet dans l'annuaire LDAP."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:246
msgid "An object already exist on LDAP server with DN %{dn}."
msgstr "Un objet existe déjà dans l'annuaire LDAP avec le DN %{dn}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:257
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"Failed to load existing object %{dn} from LDAP server. Can't update object."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Impossible de charger l'objet existant %{dn} depuis l'annuaire LDAP. "
"Impossible de mettre à jour cet objet."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:265
msgid "Failed to set post data on update form."
msgstr "Impossible de définir les données dans le formulaire de mise à jours."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:271
msgid "Error validating update form."
msgstr "Une erreur est survenue en validant le formulaire de mise à jour."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:281
msgid "Error updating object on LDAP server."
msgstr ""
"Une erreur est survenue en mettant à jour cet objet dans l'annuaire LDAP."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:327
msgid "LSimport: Post data not found or not completed."
2018-08-31 17:28:55 +02:00
msgstr "LSimport : les données transmises sont introuvables ou incomplètes."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:330
msgid "LSimport: object type invalid."
2018-08-31 17:28:55 +02:00
msgstr "LSimport : type d'objet invalide."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:333
msgid "LSimport: input/output format %{format} invalid."
2018-08-31 17:28:55 +02:00
msgstr "LSimport : Le format d'entrée/sortie %{format} est invalide."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:336
msgid "LSimport: Fail to initialize input/output driver."
msgstr "LSimport : Impossible d'initialiser le pilote d'entrée/sortie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSimport.php:339
msgid "LSimport: Fail to load objects's data from input file."
msgstr ""
"LSimport: Impossible de charger les données des objets depuis le fichier "
"d'import."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_pwdHistory.php:76
msgid "Unknown (%{raw_value})"
msgstr "Inconnue (%{raw_value})"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSconfirmBox.php:35
msgid "Confirmation"
msgstr "Confirmation"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSconfirmBox.php:36
msgid "You confirm your choice ?"
msgstr "Confirmez-vous votre choix ?"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSconfirmBox.php:37
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsmoothbox.php:39
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:74
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:623
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1279
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1421
2020-09-03 18:31:53 +02:00
#: templates/default/recoverpassword.tpl:21
2020-05-04 14:25:11 +02:00
msgid "Validate"
msgstr "Valider"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSconfirmBox.php:38
msgid "Cancel"
msgstr "Annuler"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauthMethod_anonymous.php:72
2018-08-31 17:28:55 +02:00
msgid ""
"LSauthMethod_anonymous : You must define the LSAUTHMETHOD_ANONYMOUS_USER "
"contant in the configuration file."
msgstr ""
"LSauthMethod_anonymous : Vous devez définir la constante "
"LSAUTHMETHOD_ANONYMOUS_USER dans le fichier de configuration."
2015-07-30 16:46:29 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement.php:193
2018-08-31 17:28:55 +02:00
msgid "Attribute"
msgstr "Attribut"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_mailQuota.php:98
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_valueWithUnit.php:108
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_quota.php:100
#: templates/default/LSformElement_mailQuota_field.tpl:17
2018-08-31 17:28:55 +02:00
msgid "Incorrect value"
msgstr "Valeur incorrecte"
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_mailQuota.php:168
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_labeledValue.php:135
msgid "Invalid value : \"%{value}\"."
msgstr "Valeur invalide : \"%{value}\"."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:136
msgid "Account types"
msgstr "Types de comptes"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:137
msgid "Regular user account"
msgstr "Compte utilisateur standard"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:138
msgid "Workstation Trust Account"
msgstr "Compte de poste de travail approuvé"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:139
msgid "Server Trust Account"
msgstr "Compte de serveur approuvé"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:140
msgid "Domain Trust Account"
msgstr "Compte de domaine approuvé"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:141
msgid "Majority Node Set (MNS) logon account"
msgstr "Compte de connexion Majority Node Set (MNS)"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:143
msgid "Account settings"
msgstr "Paramètres de compte"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:144
msgid "Home directory required"
msgstr "Dossier personnel requis"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:145
msgid "Account without password"
msgstr "Compte sans mot de passe"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:146
msgid "Password does not expire"
msgstr "Le mot de passe n'expire jamais"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:147
msgid "Account disabled"
msgstr "Compte désactivé"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:148
msgid "Temporary duplicate of other account"
msgstr "Copie temporaire d'un autre compte"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:149
msgid "Account automatically locked"
msgstr "Compte automatiquement bloqué"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:160
msgid ""
"LSattr_ldap_sambaAcctFlags: invalid attribute values count. This attribute "
"type could only handle single value attribute."
msgstr ""
"LSattr_ldap_sambaAcctFlags : nombre de valeurs de l'attribut incorrect. Ce "
"type d'attribut ne peut gérer que des attributs mono-valués."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:163
msgid ""
"LSattr_ldap_sambaAcctFlags: invalid attribute value. Fail to parse current "
"flags set."
msgstr ""
"LSattr_ldap_sambaAcctFlags : valeur de l'attribut incorrect. Impossible de "
"détecter les drapeaux actuellement définis."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_sambaAcctFlags.php:166
msgid ""
"LSattr_ldap_sambaAcctFlags: invalid flag '%{flag}'. Can't format the LDAP "
"attribute value."
msgstr ""
"LSattr_ldap_sambaAcctFlags : drapeau '%{flag}' invalide. Impossible de "
"formater la valeur de l'attribut LDAP."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_ssh_key.php:57
2018-08-31 17:28:55 +02:00
msgid "Display the full key."
msgstr "Affichier la clé en entier."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_ssh_key.php:79
2018-08-31 17:28:55 +02:00
msgid "Unknown type"
msgstr "Type inconnu"
2018-06-09 00:07:44 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_valueWithUnit.php:230
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSformElement_valueWithUnit : Units configuration data are missing for the "
"attribute %{attr}."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSformElement_valueWithUnit : La configuration des unités est manquante pour "
"l'attribut %{attr}."
2017-06-15 18:47:54 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html.php:143
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSattr_html : The method addToForm() of the HTML type of the attribute "
"%{attr} is not defined."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattr_html : La méthode addToForm() du type HTML de l'attribut %{attr} "
"n'est pas encore définie."
2017-06-15 18:47:54 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html.php:147
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSattr_html_%{type} : Multiple data are not supported for this field type."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattr_html_%{type} : Les données multiples ne sont pas supportées pour ce "
"type de champ."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:106
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:701
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:68
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannLabeledValue.php:62
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearchEntry.php:174
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1039
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1207
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1292
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1434
2020-05-04 10:49:11 +02:00
msgid "Modify"
msgstr "Modifier"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:107
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:75
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannLabeledValue.php:63
msgid "No set value"
msgstr "Aucune valeur définie"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:108
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:76
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_mail.php:63
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannLabeledValue.php:64
2018-08-31 17:28:55 +02:00
msgid "No result"
msgstr "Aucun résultat"
2017-06-15 18:47:54 +02:00
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:209
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_jsonCompositeAttribute.php:345
msgid "Component %{c} must be defined"
2020-04-29 15:38:41 +02:00
msgstr "Le composant %{c} est obligatoire"
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:220
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:229
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:242
msgid "Invalid value for component %{c}."
msgstr "Valeur du composant %{c} invalide."
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:224
msgid "Unparsable value for component %{c}."
msgstr "Valeur du composant %{c} non-analysable."
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannCompositeAttribute.php:247
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_jsonCompositeAttribute.php:425
msgid "Can't validate value of component %{c}."
msgstr "Impossible de valider la valeur du composant %{c}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_labeledValue.php:64
msgid "(unrecognized value)"
msgstr "(valeur non-reconnue)"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_labeledValue.php:65
msgid "(unrecognized label)"
msgstr "(label non-reconnue)"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_date.php:164
2018-08-31 17:28:55 +02:00
msgid "Now."
msgstr "Maintenant."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_date.php:165
2018-08-31 17:28:55 +02:00
msgid "Today."
msgstr "Aujourd'hui."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_date.php:166
2020-09-11 13:38:07 +02:00
msgid "Clear selected date."
msgstr "Supprimer la date sélectionnée."
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:116
2020-04-29 15:38:41 +02:00
msgid "LStemplate : compile directory is not writable (dir : %{dir})"
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LStemplate : Le dossier de compilation n'est pas accessible en écriture "
2020-04-29 15:38:41 +02:00
"(dossier : %{dir})"
2018-06-09 00:07:44 +02:00
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:135
2018-08-31 17:28:55 +02:00
msgid "LStemplate : Can't load Smarty 2 support file"
2020-04-29 15:38:41 +02:00
msgstr "LStemplate : Impossible de charger le fichier de support de Smarty 2"
2018-06-09 00:07:44 +02:00
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:142
2018-08-31 17:28:55 +02:00
msgid "LStemplate : Can't load Smarty 3 support file"
2020-04-29 15:38:41 +02:00
msgstr "LStemplate : Impossible de charger le fichier de support de Smarty 3"
2018-06-09 00:07:44 +02:00
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:146
2018-08-31 17:28:55 +02:00
msgid "LStemplate : Smarty version not recognized."
msgstr "LStemplate : Version de Smarty non reconnue."
2018-06-09 00:07:44 +02:00
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:169
2018-08-31 17:28:55 +02:00
msgid "LStemplate : Can't load Smarty."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LStemplate : Impossible de charger le moteur de gestion de template Smarty."
2018-06-09 00:07:44 +02:00
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:296
2020-05-12 19:24:53 +02:00
msgid ""
"LStemplate : Request template '%{tpl}' is now deprecated. Please refer to "
"upgrade documentation to adapt your templates."
msgstr ""
"LStemplate : Le fichier de template '%{tpl}' est maintenant déprécié. Merci "
"de mettre à jour vos templates en vous référant à la documentation."
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:426
2019-06-28 18:08:46 +02:00
msgid "Smarty - An exception occured displaying template '%{template}'"
msgstr ""
"Smarty - Un erreur est survenue en affichant le modèle de page '%{template}'."
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:446
2019-06-28 18:08:46 +02:00
msgid "Smarty - An exception occured fetching template '%{template}'"
msgstr "Smarty - Un erreur est survenue en générant le modèle '%{template}'."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:461
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:471
msgid "A fatal error occured. If problem persist, please contact support."
msgstr ""
"Une erreur irrécupérable est survenue. Si le problème persiste, merci de "
"contacter le support."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:470
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
msgid "A fatal error occured."
msgstr "Une erreur fatale est survenue."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:670
2018-08-31 17:28:55 +02:00
msgid "LStemplate : Template %{file} not found."
msgstr "LStemplate : le template %{file} est introuvable."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:673
msgid ""
"LStemplate : Fail to execute trigger %{callable} on event %{event} : is not "
"callable."
msgstr ""
"LStemplate : Échec d'exécution du déclencheur %{callable} lors de événement "
"%{event} : il n'est pas un callable."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LStemplate.php:676
msgid ""
"LStemplate : Error during the execution of the trigger %{callable} on event "
"%{event}."
msgstr ""
"LStemplate : Erreur durant l'exécution du déclencheur %{callable} lors de "
"événement %{event}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_object.php:399
2017-06-15 18:47:54 +02:00
msgid ""
2020-05-19 18:26:41 +02:00
"LSattr_html_select_object : parameter '%{parameter}' is missing (attribute : "
2017-06-15 18:47:54 +02:00
"%{attr})."
2020-05-19 18:26:41 +02:00
msgstr ""
"LSattr_html_select_objet : Le type paramètre %{parameter} n'est pas définie "
"(attribut : %{attr})."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_object.php:402
2017-06-15 18:47:54 +02:00
msgid ""
"LSattr_html_select_object : the value of the parameter value_attribute in "
2020-05-19 18:26:41 +02:00
"the configuration of the attribute %{attr} is incorrect. Object "
"%{object_type} have no attribute %{value_attribute}."
2017-06-15 18:47:54 +02:00
msgstr ""
"LSattr_html_select_object : La valeur du paramètre value_attribute dans la "
2020-05-19 18:26:41 +02:00
"configuration de l'attribut %{attr} est incorrecte. Les objets "
"%{object_type} n'ont pas d'attribut %{value_attribute}."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_object.php:405
2017-06-15 18:47:54 +02:00
msgid ""
"LSattr_html_select_object : more than one object returned corresponding to "
"value %{val} of attribute %{attr}."
msgstr ""
"LSattr_html_select_objet : plus d'un objet retourné en correspondance à la "
"valeur %{val} de l'attribut %{attr}."
2015-07-30 16:46:29 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_object.php:408
2020-05-19 18:26:41 +02:00
msgid ""
"LSattr_html_select_object : selection of object type %{type} is configured "
"multiple time for attribute %{attr}."
msgstr ""
"LSattr_html_select_objet : La sélection du type d'objet %{type} est "
"configurée plusieurs fois pour l'attribut %{attr}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_object.php:411
2020-05-19 18:26:41 +02:00
msgid ""
"LSattr_html_select_object : the value '%{value}' seem to be duplicated in "
"values of the attribute %{attr}."
msgstr ""
"LSattr_html_select_objet : La valeur '%{value}' semble dupliquée dans les "
"valeurs de l'attribut %{attr}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_object.php:414
2020-05-19 18:26:41 +02:00
msgid ""
"LSattr_html_select_object : selected object %{name} has no attribute %{attr} "
"value, you can't select it."
msgstr ""
"LSattr_html_select_objet : l'objet sélectionné %{name} n'a pas de valeur "
"dans son attribut %{attr}, vous ne pouvez pas le sélectionner."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSexport.php:93
msgid "LSexport: input/output format %{format} invalid."
msgstr "LSimport : Le format d'entrée/sortie %{format} est invalide."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSexport.php:96
msgid "LSexport: Fail to initialize input/output driver."
msgstr "LSexport : Impossible d'initialiser le pilote d'entrée/sortie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSexport.php:99
msgid "LSexport: Fail to load objects's data to export from LDAP directory."
msgstr ""
"LSexport: Impossible de charger les données des objets à exporter depuis "
"l'annuaire LDAP."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSexport.php:102
msgid "LSexport: Fail to export objects's data."
msgstr "LSexport: Impossible d'exporter les données des objets."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_differentPassword.php:90
2019-06-20 20:21:31 +02:00
msgid ""
"LSformRule_differentPassword : Other password attribute is not configured."
msgstr ""
"LSformRule_differentPassword : L'autre attribut mot de passe n'est pas "
"configuré."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_differentPassword.php:93
2019-06-20 20:21:31 +02:00
msgid ""
"LSformRule_differentPassword : Fail to load LSattr_ldap :: password class."
msgstr ""
"LSformRule_differentPassword : Impossible de charger la classe "
"LSattr_ldap :: password."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_differentPassword.php:96
2019-06-20 20:21:31 +02:00
msgid ""
"LSformRule_differentPassword : The other password attribute %{attr} does not "
"exist."
msgstr ""
"LSformRule_differentPassword : L'autre attribut mot de passe %{attr} "
"n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_differentPassword.php:99
2019-06-20 20:21:31 +02:00
msgid ""
"LSformRule_differentPassword : The other password attribute could not be the "
"same of the current one."
msgstr ""
"LSformRule_differentPassword : L'autre attribut mot de passe ne peut être le "
"même que l'attribut courant."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_differentPassword.php:102
2019-06-20 20:21:31 +02:00
msgid ""
"LSformRule_differentPassword : The other password attributes must use "
"LSattr_ldap :: password. It's not the case of the attribure %{attr}."
msgstr ""
"LSformRule_differentPassword : Les autres attributs mots de passe doivent "
"utiliser LSattr_ldap :: password. Ce n'est pas le cas de l'attribut %{attr}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:250
2018-08-31 17:28:55 +02:00
msgid "The value of field %{label} is invalid."
msgstr "La valeur du champ %{label} est incorrecte."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:738
msgid ""
2018-08-31 17:28:55 +02:00
"LSattribute : Attribute %{attr} : LDAP or HTML types unknow (LDAP = %{ldap} "
"& HTML = %{html})."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattribute : Attribut %{attr} : Les types LDAP ou HTML sont inconnus (LDAP "
"= %{ldap} & HTML = %{html})."
2015-07-30 16:46:29 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:741
2015-07-30 16:46:29 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSattribute : The function %{func} to display the attribute %{attr} is "
"unknow."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattribute : La fonction %{func} pour afficher l'attribut %{attr} est "
"inconnue."
2009-11-11 22:23:35 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:744
msgid ""
2018-08-31 17:28:55 +02:00
"LSattribute : The rule %{rule} to validate the attribute %{attr} is unknow."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattribute : La règle %{rule} de validation de l'attribut %{attr} n'existe "
"pas."
2011-06-27 15:51:39 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:747
msgid ""
2018-08-31 17:28:55 +02:00
"LSattribute : Configuration data to verify the attribute %{attr} are "
"incorrect."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattribute : Les données de configuration pour vérifier l'attribut %{attr} "
"sont incorrecte."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:750
msgid ""
2018-08-31 17:28:55 +02:00
"LSattribute : The function %{func} to save the attribute %{attr} is unknow."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattribute : La fonction %{func} pour sauvegarder l'attribut %{attr} est "
"inconnue."
2013-06-18 00:28:19 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:753
2018-08-31 17:28:55 +02:00
msgid "LSattribute : The value of the attribute %{attr} can't be generated."
msgstr "LSattribute : La valeur de l'attribut %{attr} ne peut être générée."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:756
2018-08-31 17:28:55 +02:00
msgid "LSattribute : Generation of the attribute %{attr} failed."
msgstr "LSattribute : La génération de l'attribut %{attr} a échouée."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:759
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSattribute : Generation of the attribute %{attr} did not return a correct "
"value."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattribute : La génération de l'attribut %{attr} n'a pas retournée de "
"valeur correcte."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattribute.php:762
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSattribute : The attr_%{type} of the attribute %{name} is not yet defined."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattribute : L'objet attr_%{type} de l'attribut %{name} n'est pas encore "
"défini."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_callable.php:66
2018-08-31 17:28:55 +02:00
msgid "LSformRule_callable : The given callable option is not callable"
2020-04-29 15:38:41 +02:00
msgstr "LSformRule_callable : Le paramètre fournis n'est pas exécutable"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_postaladdress.php:73
2018-08-31 17:28:55 +02:00
msgid "View on map"
msgstr "Voir sur une carte"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_postaladdress.php:89
2018-08-31 17:28:55 +02:00
msgid ""
"LSformElement_postaladdress : Map URL pattern generate function is not "
"callabled (%{function})."
msgstr ""
"LSformElement_postaladdress : La fonction de génération de l'URL de la carte "
"n'est pas exécutable (%{function})."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select.php:52
2018-08-31 17:28:55 +02:00
msgid "Reset selection."
msgstr "Réinitiliser la sélection."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsmoothbox.php:38
2018-08-31 17:28:55 +02:00
msgid "Are you sure to want to close this window and lose all changes ?"
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Êtes-vous sûre de vouloir femer cette fenêtre et de perdre tous vos "
"changements ?"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_textarea.php:51
2018-08-31 17:28:55 +02:00
msgid "Clear"
msgstr "Nettoyer"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:1424
2018-08-31 17:28:55 +02:00
msgid "Connection"
msgstr "Connexion"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:1446
2018-08-31 17:28:55 +02:00
msgid "Recovery of your credentials"
msgstr "Récupération de votre mot de passe"
2013-06-18 00:28:19 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:1455
2018-08-31 17:28:55 +02:00
msgid "Please fill the identifier field to proceed recovery procedure"
msgstr ""
"Merci d'entrer votre identifiant pour poursuivre la procédure de récupération"
2013-06-18 00:28:19 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:1460
2018-08-31 17:28:55 +02:00
msgid ""
"An email has been sent to %{mail}. Please follow the instructions on it."
msgstr ""
"Un e-mail vient de vous être envoyé à l'adresse %{mail}. Merci de suivre les "
"indications qu'il contient."
2013-06-18 00:28:19 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:1469
2020-04-29 15:38:41 +02:00
msgid "Your new password has been sent to %{mail}."
2018-08-31 17:28:55 +02:00
msgstr "Votre nouveau mot de passe vous a été envoyé à l'adresse %{mail}."
2013-06-18 00:28:19 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:1640
2020-09-03 18:31:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:156
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:467
2020-05-19 18:26:41 +02:00
#: templates/default/select.tpl:29
2020-05-03 18:48:33 +02:00
msgid "Refresh"
msgstr "Rafraîchir"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2718
2020-09-03 18:31:53 +02:00
#: templates/default/select.tpl:20 templates/default/recoverpassword.tpl:17
#: templates/default/login.tpl:16
2020-05-12 19:24:53 +02:00
msgid "Level"
msgstr "Niveau"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2876
2020-09-03 18:31:53 +02:00
msgid "LSsession : The constant '%{const}' is not defined."
msgstr "LSsession : La constante '%{const}' n'est pas définie."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2879
msgid ""
2020-09-03 18:31:53 +02:00
"LSsession : The addon '%{addon}' support is uncertain. Verify system "
"compatibility and the add-on configuration."
msgstr ""
2020-09-03 18:31:53 +02:00
"LSsession : Le support de l'addon '%{addon}' est incertain. Vérifiez la "
"compatibilité du système et la configuration de l'add-on."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2882
msgid ""
2018-08-31 17:28:55 +02:00
"LSsession : LDAP server's configuration data are invalid. Can't connect."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSsession : Les données de configuration du serveur LDAP sont invalide. "
"Impossible de s'y connecter."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2885
2020-09-03 18:31:53 +02:00
msgid "LSsession : Failed to load LSobject type '%{type}' : unknon type."
msgstr ""
2020-09-03 18:31:53 +02:00
"LSsession : Impossible de charger le type d'LSobject '%{type}' : type "
"inconnu."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2888
2020-09-03 18:31:53 +02:00
msgid "LSsession : Failed to load LSclass '%{class}'."
msgstr "LSsession : Impossible de charger la LSclass '%{class}'."
2018-08-31 17:28:55 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2891
2018-08-31 17:28:55 +02:00
msgid "LSsession : Login or password incorrect."
msgstr "LSsession : Identifiant ou mot de passe incorrects."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2894
2018-08-31 17:28:55 +02:00
msgid "LSsession : Impossible to identify you : Duplication of identities."
msgstr "LSsession : Impossible de vous identifier : Duplication d'identité."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2897
2018-08-31 17:28:55 +02:00
msgid "LSsession : Can't load class of authentification (%{class})."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSsession : Impossible de charger la classe d'authentification (%{class})."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2900
2018-08-31 17:28:55 +02:00
msgid "LSsession : Can't connect to LDAP server."
msgstr "LSsession : Impossible de se connecter au serveur LDAP."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2903
2018-08-31 17:28:55 +02:00
msgid "LSsession : Impossible to authenticate you."
msgstr "LSsession : Impossible de vous identifier."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2906
2018-08-31 17:28:55 +02:00
msgid "LSsession : Your are not authorized to do this action."
msgstr "LSsession : Vous n'êtes pas autorisé à faire cette action."
2009-11-11 22:23:35 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2909
2018-08-31 17:28:55 +02:00
msgid "LSsession : Some informations are missing to display this page."
msgstr "LSsession : Des informations sont manquant pour afficher cette page."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2912
2018-08-31 17:28:55 +02:00
msgid ""
"LSsession : The function '%{function}' of the custom action "
"'%{customAction}' does not exists or is not configured."
2018-08-31 17:28:55 +02:00
msgstr ""
"LSsession : La fonction '%{function}' de l'action personnalisée "
"'%{customAction}' n'existe pas ou n'est pas configurée."
2009-11-11 22:23:35 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2915
2018-08-31 17:28:55 +02:00
msgid "LSsession : Fail to retreive user's LDAP credentials from LSauth."
msgstr ""
"LSsession : Erreur en récupérant les identifiants LDAP de l'utilisateur "
"depuis LSauth."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2918
msgid ""
2018-08-31 17:28:55 +02:00
"LSsession : Fail to reconnect to LDAP server with user's LDAP credentials."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSsession : Impossible de se reconnecter au serveur LDAP avec les "
"identifiants de l'utilisateur."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2921
2018-08-31 17:28:55 +02:00
msgid "LSsession : No import/export format define for this object type."
msgstr "LSsession : Aucun format d'entrée/sortie définie pour ce type d'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2924
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSsession : Error during creation of list of levels. Contact administrators. "
"(Code : %{code})"
msgstr ""
2018-08-31 17:28:55 +02:00
"LSsession : Erreur durant la création de la liste des niveaux. Contacter les "
"administrateurs. (Code : %{type})"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2927
2018-08-31 17:28:55 +02:00
msgid "LSsession : The password recovery is disabled for this LDAP server."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSsession : La récupération de mot de passe est désactivée pour ce serveur "
"LDAP."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2930
2015-08-21 15:15:40 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSsession : Some informations are missing to recover your password. Contact "
"administrators."
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSsession : Des informations sont manques pour pouvoir récupérer votre mot "
"de passe. Contacter les administrateurs."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2933
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSsession : Error during password recovery. Contact administrators.(Step : "
"%{step})"
2018-06-09 00:07:44 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSsession : Erreur durant la récupération de votre mot de passe. Contacter "
"les administrateurs. (Etape : %{step})"
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2936
2018-06-09 00:07:44 +02:00
msgid ""
2020-09-03 18:31:53 +02:00
"LSsession : The function '%{func}' configured for the view '%{view}' of the "
"LSaddon '%{addon}' is not declared in the LSaddon file."
2018-06-09 00:07:44 +02:00
msgstr ""
2020-09-03 18:31:53 +02:00
"LSsession : la fonction '%{func}' configurée pour la vue '%{view}' du "
"LSaddon '%{addon}' n'est pas déclaré dans le fichier du LSaddon."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2940
2020-09-03 18:31:53 +02:00
msgid ""
"LSsession : The function '%{func}' configured for the view '%{view}' of the "
"LSaddon '%{addon}' doesn't exist."
2018-06-09 00:07:44 +02:00
msgstr ""
2020-09-03 18:31:53 +02:00
"LSsession : la fonction '%{func}' configurée pour la vue '%{view}' du "
"LSaddon '%{addon}' n'existe pas."
2018-06-09 00:07:44 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2943
2018-08-31 17:28:55 +02:00
msgid "LSsession : invalid related object's DN pass in parameter."
msgstr "LSsession : DN d'objet en relation incorrect dans les paramètres."
2017-08-02 12:00:11 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2946
2020-05-02 18:32:31 +02:00
msgid ""
"LSsession : the LSaddon %{addon} keep using old-style addon view URL. Please "
"upgrade it."
msgstr ""
"LSsession : le LSaddon %{addon} utilise toujours l'ancien type d'URL de "
"vues. Merci de le mettre à jour."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2949
2020-05-03 18:48:33 +02:00
msgid ""
"LSsession : You have been redirect from an old-style URL %{url}. Please "
"upgrade this link."
msgstr ""
"LSsession : Vous avez été redirigé depuis une ancienne URL %{url}. Merci de "
"le mettre à jour ce lien."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsession.php:2952
msgid ""
2020-05-28 19:48:27 +02:00
"LSsession : You always seem to use %{old} in your custom code: Please "
"upgrade it and use %{new}.<pre>\n"
"Context:\n"
"%{context}</pre>"
msgstr ""
2020-05-28 19:48:27 +02:00
"LSsession : Vous semblez toujours utilisé %{old} dans votre code "
"personnalisé. Merci de mettre à jour ce code et d'utiliser %{new}.<pre>\n"
"Context:\n"
"%{context}</pre>"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:489
2017-06-15 18:47:54 +02:00
msgid "The attribute %{attr} is not valid."
msgstr "L'attribut %{attr} n'est pas valide."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3058
2017-06-15 18:47:54 +02:00
msgid "LSldapObject : Object type unknown."
msgstr "LSldapObject : Type d'objet inconnu."
2010-11-19 18:51:29 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3061
2017-06-15 18:47:54 +02:00
msgid "LSldapObject : Update form is not defined for the object %{obj}."
msgstr ""
"LSldapObject : Le formulaire de mise à jour n'est pas défini pour l'objet "
"%{obj}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3064
2017-06-15 18:47:54 +02:00
msgid "LSldapObject : No form exists for the object %{obj}."
msgstr "LSldapObject : Aucun formulaire n'existe pour l'objet %{obj}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3067
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : The function %{func} to validate the attribute %{attr} the "
"object %{obj} is unknow."
msgstr ""
"LSldapObject : La fonction %{func} pour valider l'attribut %{attr} de "
"l'objet %{obj} est inconnu."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3070
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Configuration data are missing to validate the attribute "
"%{attr} of the object %{obj}."
msgstr ""
"LSldapObject : Des données de configurations sont manquant pour pouvoir "
"valider l'attribut %{attr} de l'objet %{obj}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3074
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : The function %{func} to be executed on the object event "
"%{event} doesn't exist."
msgstr ""
"LSldapObject : La fonction %{func} devant être exécutée lors de l'évènement "
"%{event} de l'objet n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3077
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : The %{func} execution on the object event %{event} failed."
msgstr ""
"LSldapObject : L'exécution de la fonction %{func} lors de l'évènement "
"%{event} de l'objet a échouée."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3081
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Class %{class}, which method %{meth} to be executed on the "
"object event %{event}, doesn't exist."
msgstr ""
"La classe %{class}, contenant la méthode %{meth} devant être exécutée lors "
"de l'évènement %{event} de l'objet, n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3084
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Method %{meth} within %{class} class to be executed on object "
"event %{event}, doesn't exist."
msgstr ""
"LSldapObject : La méthode %{meth} de la classe %{class} devant être exécutée "
"lors de l'évènement %{event} de l'objet n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3087
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during execute %{meth} method within %{class} class, to "
"be executed on object event %{event}."
msgstr ""
"LSldapObject : Erreur durant l'exécution de la méthode %{meth} de la classe "
"%{class} devant être exécutée lors de l'évènement %{event} de l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3091
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Some configuration data of the object type %{obj} are missing "
"to generate the DN of the new object."
msgstr ""
"LSldapObject : Des informations de configuration du type d'objet %{obj} sont "
"manquantes pour la génération du DN du nouvel objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3094
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : The attibute %{attr} of the object is not yet defined. Can't "
"generate DN."
msgstr ""
"LSldapObjet : L'attribut %{attr} de l'objet n'est pas encore défini. "
"Impossible de générer le DN."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3097
2017-06-15 18:47:54 +02:00
msgid "LSldapObject : Without DN, the object could not be changed."
msgstr "LSldapObject : Sans DN, l'objet ne peut pas être modifié."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3100
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : The attribute %{attr_depend} depending on the attribute "
"%{attr} doesn't exist."
msgstr ""
"LSldapObject : L'attritbut %{attr_depend} dépendant de l'attribut %{attr} "
"n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3103
2017-06-15 18:47:54 +02:00
msgid "LSldapObject : Error during deleting the object %{objectname}."
msgstr "LSldapObject : Erreur durant la suppression de l'objet %{objectname}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3107
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during actions to be executed before renaming the objet."
msgstr ""
"LSldapObject : Erreur durant les actions devant être exécutée avant de "
"renommer l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3110
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during actions to be executed after renaming the objet."
msgstr ""
"LSldapObject : Erreur durant les actions devant être exécutée après avoir "
"renommé l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3114
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during actions to be executed before deleting the objet."
msgstr ""
"LSldapObject : Erreur durant les actions devant être exécutée avant de "
"supprimer l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3117
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during actions to be executed after deleting the objet."
msgstr ""
"LSldapObject : Erreur durant les actions devant être exécutée après avoir "
"supprimé l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3121
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during the actions to be executed before creating the "
"object."
msgstr ""
"LSldapObject : Erreur durant les actions devant être exécutée avant de créer "
"l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3124
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during the actions to be executed after creating the "
"object. It was created anyway."
msgstr ""
"LSldapObject : Erreur durant les actions devant être exécutées après la "
"création de l'objet. Il a tout de même été créé."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3128
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : The function %{func} to be executed before creating the "
"object doesn't exist."
msgstr ""
"LSldapObject : La fonction %{func} devant être exécutée avant la création de "
"l'objet n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3131
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error executing the function %{func} to be execute after "
"deleting the object."
msgstr ""
"LSldapObject : Erreur durant l'exécution de la fonction %{func} devant être "
"exécutée après la suppression de l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3134
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : The function %{func} to be executed after deleting the object "
"doesn't exist."
msgstr ""
"LSldapObject : La fonction %{func} devant être exécutée après la suppression "
"de l'objet n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3137
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error executing the function %{func} to be execute after "
"creating the object."
msgstr ""
"LSldapObject : Erreur durant l'exécution de la fonction %{func} devant être "
"exécutée après la création de l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3141
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : %{func} function, to be executed on object event %{event}, "
"doesn't exist."
msgstr ""
"LSldapObject : La fonction %{func}, devant être exécutée lors de l'évènement "
"%{event} de l'objet, n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3144
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during the execution of %{func} function on object "
"event %{event}."
msgstr ""
"LSldapObject : Erreur durant l'exécution de la fonction %{func} lors de "
"l'évènement %{event} de l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3148
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : %{meth} method, to be executed on object event %{event}, "
"doesn't exist."
msgstr ""
"LSldapObject : La méthode %{meth}, devant être exécutée lors de l'évènement "
"%{event} de l'objet, n'existe pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3151
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during execution of %{meth} method on object event "
"%{event}."
msgstr ""
"LSldapObject : Erreur durant l'exécution de la méthode %{meth} lors de "
"l'évènement %{event} de l'objet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3154
2017-06-15 18:47:54 +02:00
msgid "LSldapObject : Error during generate LDAP filter for %{LSobject}."
msgstr ""
"LSldapObject : Erreur durant la génération du filtre LDAP de l'objet "
"%{LSobject}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3158
2017-06-15 18:47:54 +02:00
msgid ""
"LSldapObject : Error during execution of the custom action %{customAction} "
"on %{objectname}."
msgstr ""
"LSldapObject : Erreur durant l'exécution de l'action personnalisée "
"%{customAction} sur l'objet %{objectname}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3162
msgid "LSldapObject : Fail to retrieve container DN."
msgstr "LSldapObject : Impossible de récupérer le DN parent."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3165
msgid ""
"LSldapObject : The function %{func} to generate container DN is not callable."
msgstr ""
"LSldapObject : La fonction %{func} pour générer le DN parent n'est pas "
"exécutable."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3168
msgid "LSldapObject : Error during generating container DN : %{error}"
msgstr "LSldapObject : Erreur durant la génération du DN parent : %{error}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3171
msgid ""
"LSldapObject : An LDAP object with the same DN as generated for this new one "
"already exists. Please verify your configuration."
msgstr ""
"LSldapObject : Un objet LDAP avec le même DN que celui généré pour ce nouvel "
"objet existe déjà. Merci de vérifier votre configuration."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldapObject.php:3176
2017-06-15 18:47:54 +02:00
msgid ""
"LSrelation : Some parameters are missing in the call of methods to handle "
"standard relations (Method : %{meth})."
msgstr ""
"LSrelation : Des paramètres sont manquant dans l'appel des méthodes de "
"manipulation des relations standards."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_password.php:101
2018-08-31 17:28:55 +02:00
msgid ""
"LSformRule_password : Invalid regex configured : %{regex}. You must use PCRE "
"(begining by '/' caracter)."
msgstr ""
"LSformRule_password : Regex invalide configurée : %{regex}. Vous devez "
"utiliser des regex de type PCRE (commencant par le caractère '/')."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:581
msgid "LSldap: Error during the LDAP server connection (%{msg})."
2017-06-15 18:47:54 +02:00
msgstr "LSldap : Erreur durant la connexion au serveur LDAP (%{msg})."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:584
msgid "LSldap: Error during the LDAP search (%{msg})."
2017-06-15 18:47:54 +02:00
msgstr "LSldap : Erreur pendant la recherche LDAP (%{msg})."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:587
msgid "LSldap: Object type unknown."
2017-06-15 18:47:54 +02:00
msgstr "LSldap : Type d'objet inconnu."
2015-07-30 16:46:29 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:590
msgid "LSldap: Error while fetching the LDAP entry."
2017-06-15 18:47:54 +02:00
msgstr "LSldap : Erreur durant la récupération de l'entrée LDAP."
2015-07-30 16:46:29 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:593
msgid "LSldap: Error while changing the LDAP entry (DN : %{dn})."
2017-06-15 18:47:54 +02:00
msgstr "LSldap : Erreur durant la modification de l'entrée LDAP (DN : %{dn})."
2015-07-30 16:46:29 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:596
msgid "LSldap: Error while deleting empty attributes."
2017-06-15 18:47:54 +02:00
msgstr "LSldap : Erreur durant la suppression des attributs vides."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:599
msgid "LSldap: Error while changing the DN of the object."
2017-06-15 18:47:54 +02:00
msgstr "LSldap : Erreur pendant la modification du DN de l'objet."
2009-11-11 22:23:35 +01:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSldap.php:602
msgid "LSldap: LDAP server base DN not configured."
msgstr "LSldap : Le base DN du serveur LDAP n'est pas configuré."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:331
2018-08-31 17:28:55 +02:00
msgid "listing related objects"
msgstr "énumaration des objets liés"
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:397
2018-08-31 17:28:55 +02:00
msgid "getting key value"
msgstr "récupération de la valeur clé"
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:449
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:551
2018-08-31 17:28:55 +02:00
msgid "checking right on relation with specific object"
msgstr "vérification des droits sur la relation avec un objet en particulier"
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:498
2018-08-31 17:28:55 +02:00
msgid "removing relation with specific object"
msgstr "suppression de la relation avec un object en particulier"
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:623
2018-08-31 17:28:55 +02:00
msgid "updating relations"
msgstr "mise à jour des relations"
2017-06-15 18:47:54 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:642
2018-08-31 17:28:55 +02:00
msgid "Do you really want to delete"
msgstr "Voulez-vous vraiment supprimer"
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:643
2018-08-31 17:28:55 +02:00
msgid "Warning"
msgstr "Attention"
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:644
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:248
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:69
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:85
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearchEntry.php:190
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1055
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1199
2020-05-04 10:49:11 +02:00
msgid "Delete"
msgstr "Supprimer"
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:682
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:929
2018-08-31 17:28:55 +02:00
msgid "No object."
msgstr "Aucun objet."
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:712
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:449
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:984
2020-05-04 10:49:11 +02:00
msgid "New"
msgstr "Nouveau"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:998
2018-06-09 00:07:44 +02:00
msgid ""
2020-05-19 18:26:41 +02:00
"LSrelation : Invalid parameter '%{parameter}' of the relation %{relation}: "
"objects %{LSobject} have no function '%{function}'."
msgstr ""
2020-05-19 18:26:41 +02:00
"LSrelation : Le paramètre '%{parametre}' de la relation %{relation} est "
"invalide: les objets %{LSobject} n'ont pas de fonction '%{function}'."
2013-06-18 00:28:19 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:1001
2018-08-31 17:28:55 +02:00
msgid "LSrelation : Relation %{relation} of object type %{LSobject} unknown."
msgstr ""
"LSrelation : La relation %{relation} du type d'objet %{LSobject} est "
"inconnue."
2013-06-18 00:28:19 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:1004
2018-08-31 17:28:55 +02:00
msgid "LSrelation : Error during relation update of the relation %{relation}."
msgstr "LSsession : Erreur durant la mise à jour de la relation %{relation}"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:1007
2018-08-31 17:28:55 +02:00
msgid "LSrelation : Object type %{LSobject} unknown (Relation : %{relation})."
msgstr ""
"LSsession : La fonction de mise à jour de la relation %{relation} est "
"inconnue."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:1010
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSrelation : Incomplete configuration for LSrelation %{relation} of object "
"type %{LSobject} for action : %{action}."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSrelation : Configuration incomplète de la LSrelation %{relation} du type "
"d'objet %{LSobject} pour l'action : %{action}."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:1013
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSrelation : Invalid editable attribute for LSrelation %{relation} with "
"LSobject %{LSobject}."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSrelation : Attribut éditable invalide pour la LSrelation %{relation} du "
"type d'objet %{LSobject}."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:1016
2020-05-19 18:26:41 +02:00
msgid ""
"LSrelation : The configuration parameter '%{parameter}' of the relation "
"%{relation} of %{LSobject} is missing."
msgstr ""
2020-09-03 18:07:45 +02:00
"LSrelation : Le paramètre '%{parameter}' est manquant dans la configuration "
2020-05-19 18:26:41 +02:00
"de la relation %{relation} des objets %{LSobject}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSrelation.php:1019
2020-05-19 18:26:41 +02:00
msgid ""
"LSrelation : The configuration parameter '%{parameter}' of the relation "
"%{relation} of %{LSobject} is invalid."
msgstr ""
2020-09-03 18:07:45 +02:00
"LSrelation : Le paramètre '%{parameter}' est invalide dans la configuration "
2020-05-19 18:26:41 +02:00
"de la relation %{relation} des objets %{LSobject}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:85
2020-06-30 10:01:06 +02:00
msgid "%{label}: passwords entered did not match."
msgstr "%{label} : les mots de passe saisies ne correspondent pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:133
msgid "%{label}: invalid email address provided to send new password."
msgstr ""
"%{label} : une adresse mail invalide a été fournie pour l'envoi du nouveau "
"mot de passe."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:170
2018-08-31 17:28:55 +02:00
msgid "Generate a password."
msgstr "Générer un mot de passe."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:171
2018-08-31 17:28:55 +02:00
msgid "Compare with stored password."
msgstr "Comparer avec le mot de passe stocké."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:172
2018-08-31 17:28:55 +02:00
msgid "Display password."
msgstr "Afficher le mot de passe."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:173
2018-08-31 17:28:55 +02:00
msgid "Display hashed password."
msgstr "Afficher le mot de passe haché."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:174
2018-08-31 17:28:55 +02:00
msgid "Hide password."
msgstr "Cacher le mot de passe."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:175
2018-08-31 17:28:55 +02:00
msgid ""
"The password will be sent by mail if changed. Click to disable automatic "
"notification."
msgstr ""
2018-08-31 17:28:55 +02:00
"Le mot de passe sera envoyé par e-mail en cas de modification. Cliquer pour "
"désactiver la notification."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:176
2018-08-31 17:28:55 +02:00
msgid ""
"The password will not be sent if changed. Click to enable automatic "
"notification."
msgstr ""
"Le mot de passe ne sera pas envoyé en cas de modification. Cliquer pour "
"activer la notification automatique."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:177
2018-08-31 17:28:55 +02:00
msgid "Modify the mail sent to notice the user"
msgstr "Modifier mail de notification de l'utilisateur"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:195
2020-06-30 10:01:06 +02:00
msgid "%{label}: Do you confirm the password change?"
msgstr "%{label} : Confirmez-vous la modification du mot de passe ?"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:200
2020-06-30 10:01:06 +02:00
msgid "Passwords entered did not match."
msgstr "Les mots de passe saisies ne correspondent pas."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:323
2018-08-31 17:28:55 +02:00
msgid "Notice mail sent."
msgstr "Le mail de notification a été envoyé."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:418
msgid ""
"LSformElement_password : No valid contact mail address available : Can't "
"send new password."
2018-08-31 17:28:55 +02:00
msgstr ""
"LSformElement_password : Aucun mail de contact valide disponible : "
"impossible d'envoyer le nouveau mot de passe."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:421
msgid "LSformElement_password : Fail to send new password by email to %{mail}."
2017-06-15 18:47:54 +02:00
msgstr ""
"LSformElement_password : Une erreur est survenue en envoyant le nouveau mot "
"de passe à %{mail}."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:424
2018-08-31 17:28:55 +02:00
msgid ""
"LSformElement_password : Fail to exec pwgen. Check it's correctly installed."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSformElement_password : Impossible d'exécuter pwgen. Vérifier qu'il est "
"bien installé."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:427
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSformElement_password : Fail to determine witch e-mail attribute to use to "
"send new password : get_mail_attr_function parameter not refer to a valid "
"function."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSformElement_password : Impossible de déterminer quel attribut e-mail doit "
"être utilisé pour l'envoi du mot de passe : le paramètre "
"get_mail_attr_function ne fait pas référence à une fonction valide."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_password.php:430
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSformElement_password : Fail to determine witch e-mail attribute to use to "
"send new password : get_mail_attr_function throwed an exception : %{msg}"
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSformElement_password : Impossible de déterminer quel attribut e-mail doit "
"être utilisé pour l'envoi du mot de passe : le fonction "
"get_mail_attr_function a déclenchée une exception : %{msg}."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_url.php:51
2018-08-31 17:28:55 +02:00
msgid "Display this website."
msgstr "Afficher le site internet."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_url.php:52
2018-08-31 17:28:55 +02:00
msgid "Add this website to my bookmarks."
msgstr "Ajouter ce site internet à mes favoris."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_text.php:57
2018-08-31 17:28:55 +02:00
msgid "Generate the value"
msgstr "Générer une valeur"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauthMethod_CAS.php:140
2018-08-31 17:28:55 +02:00
msgid "LSauthMethod_CAS : Failed to load phpCAS."
msgstr "LSauthMethod_CAS : Impossible de charger phpCAS."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauthMethod_CAS.php:143
2019-07-02 14:21:04 +02:00
msgid ""
"LSauthMethod_CAS : Please check your configuration : you must configure CAS "
"server SSL certificate validation using one of the following constant : "
"LSAUTH_CAS_SERVER_SSL_CACERT or LSAUTH_CAS_SERVER_NO_SSL_VALIDATION"
2019-07-02 14:21:04 +02:00
msgstr ""
"LSauthMethod_CAS : Merci de vérifier votre configuration : vous devez "
"configurer la validation du certificat SSL du serveur CAS en utilisant une "
"des constantes suivantes : LSAUTH_CAS_SERVER_SSL_CACERT ou "
"LSAUTH_CAS_SERVER_NO_SSL_VALIDATION"
2019-07-02 14:21:04 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:126
2018-08-31 17:28:55 +02:00
msgid "Add a field to add another values."
msgstr "Ajouter une autre valeur à ce champ."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:127
2018-08-31 17:28:55 +02:00
msgid "Delete this field."
msgstr "Supprimer cette valeur."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:229
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:619
2020-05-04 14:25:11 +02:00
msgid "Do you really want to execute custom action %{title} on this search ?"
msgstr ""
"Êtes-vous vraiment sûre de vouloir exécuter l'action personnalisée %{title} "
"sur cette recherche ?"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:235
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1415
2018-08-31 17:28:55 +02:00
msgid ""
"Do you really want to execute custom action %{customAction} on "
"%{objectname} ?"
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"Êtes-vous vraiment sûre de vouloir exécuter l'action personnalisée "
"%{customAction} sur %{objectname} ?"
2013-06-18 00:28:19 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:246
msgid "Do you really want to delete \"%{name}\"?"
msgstr "Voulez-vous vraiment supprimer \"%{name}\" ?"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:247
2018-08-31 17:28:55 +02:00
msgid "Caution"
msgstr "Attention"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:301
2018-08-31 17:28:55 +02:00
msgid "%{label} attribute data is not valid."
msgstr "Les données de l'attribut %{label} sont incorrectes."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:384
2018-08-31 17:28:55 +02:00
msgid "Mandatory field"
msgstr "Champ obligatoire"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:873
2018-08-31 17:28:55 +02:00
msgid "LSform : Error during the recovery of the values of the form."
msgstr "LSform : Erreur durant la récupération des valeurs du formulaire."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:876
msgid ""
2018-08-31 17:28:55 +02:00
"LSform : Error durring the recovery of the value of the field '%{element}'."
2015-07-30 16:46:29 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSform : Erreur durant la recupération de la valeur du champ %{element}."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:883
2018-08-31 17:28:55 +02:00
msgid "LSform : The field %{element} doesn't exist."
msgstr "LSform : Le champ %{element} n'existe pas."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:886
2018-08-31 17:28:55 +02:00
msgid "LSfom : Field type unknow (%{type})."
msgstr "LSform : Type de champ inconnu (%{type})."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:889
2018-08-31 17:28:55 +02:00
msgid "LSform : Error during the creation of the element '%{element}'."
msgstr "LSform : Erreur durant la création de l'élément %{element}."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:892
2018-08-31 17:28:55 +02:00
msgid "LSform : The data entry form %{name} doesn't exist."
msgstr "LSform : Le masque de saisie %{name} n'existe pas."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:895
2018-08-31 17:28:55 +02:00
msgid "LSform : The data entry form %{name} is not correctly configured."
msgstr "LSform : Le masque de saisie %{name} n'est pas correctement configuré."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSform.php:898
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSform : The element %{name}, listed as displayed in data entry form "
"configuration, doesn't exist."
2015-07-30 16:46:29 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSform : L'élement %{name}, listé comme affiché dans la configuration du "
"masque de saisie, n'existe pas."
2015-07-30 16:46:29 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_maildir.php:68
2018-06-09 00:07:44 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"Maildir creation/modification on user creation/modification is enabled. "
"Click to disable."
msgstr ""
2018-08-31 17:28:55 +02:00
"La création/modification de la maildir en même temps que la création/"
"modification de l'utilisateur est activée. Cliquer pour désactiver."
2013-06-18 00:28:19 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_maildir.php:69
2018-08-31 17:28:55 +02:00
msgid ""
"Click to enable maildir creation/modification on user creation/modification."
msgstr ""
"Cliquer pour activer la création/modification de la maildir en même temps "
"que la création/modification du l'utilisateur."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_regex.php:62
2018-08-31 17:28:55 +02:00
msgid "LSformRule_regex : Regex has not been configured to validate data."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSformRule_regex : L'expression régulière de vérification des données n'est "
"pas configurée."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:70
2018-08-31 17:28:55 +02:00
msgid "Move up"
msgstr "Monter"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:71
2018-08-31 17:28:55 +02:00
msgid "Move down"
msgstr "Descendre"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:83
2018-08-31 17:28:55 +02:00
msgid "Fast Add"
msgstr "Ajout rapide"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_select_object.php:84
2018-08-31 17:28:55 +02:00
msgid "Display advanced search and selection panel."
msgstr "Afficher la fenêtre de recherche et de sélection étendue."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSurl.php:108
msgid "Fail to determine the requested URL."
msgstr "Impossible de déterminer l'URL demandée."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSurl.php:112
msgid "No URL patterns configured !"
msgstr "Aucun modèle d'URL configuré !"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSurl.php:216
msgid "Fail to determine the requested URL (loop detected)."
msgstr "Impossible de déterminer l'URL demandée (boucle détectée)."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSurl.php:238
msgid "The requested page was not found."
msgstr "La page demandée est introuvable."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSurl.php:263
msgid "This request could not be handled."
msgstr "Cette requête ne peut être traitée."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSurl.php:282
msgid "This request could not be processed correctly."
msgstr "Cette requête ne peut être traitée correctement."
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_date.php:47
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:63
2018-08-31 17:28:55 +02:00
msgid "Invalid value"
msgstr "Valeur invalide"
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauthMethod_HTTP.php:103
msgid "LdapSaisie - Authentication required"
msgstr "LdapSaisie - Authentification requise"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauthMethod_HTTP.php:150
msgid "LSauthMethod_HTTP : the %{var} environnement variable is missing."
msgstr "LSauthMethod_HTTP : la variable d'environnement %{var} est manquante."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_mail.php:56
2018-08-31 17:28:55 +02:00
msgid "Send a mail from here."
msgstr "Envoyer un mail depuis l'interface."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_boolean.php:52
2018-08-31 17:28:55 +02:00
msgid "Reset the choice."
msgstr "Réinitialiser le choix."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_rss.php:50
2018-06-09 00:07:44 +02:00
msgid "Display RSS stack."
msgstr "Afficher la file RSS."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_password.php:100
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:579
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1365
msgid "undefined"
msgstr "non-définie"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_password.php:350
2018-08-31 17:28:55 +02:00
msgid ""
"LSattr_ldap_password : Encoding type %{type} is not supported. This password "
"will be stored in clear text."
msgstr ""
"LSattr_ldap_password : Le type d'encodage %{type} n'est pas supporté. Le mot "
"de passe sera stocké en clair."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_ldap_password.php:353
2018-08-31 17:28:55 +02:00
msgid ""
"LSattr_ldap_password : Encoding function %{function} is not callable. This "
"password will be stored in clear text."
msgstr ""
"LSattr_ldap_password : La fonction d'encodage %{function} n'est pas "
"disponible. Le mot de passe sera stocké en clair."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:308
2018-08-31 17:28:55 +02:00
msgid "LSauth : Login or password incorrect."
msgstr "LSauth : Identifiant ou mot de passe incorrects."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:311
2018-08-31 17:28:55 +02:00
msgid "LSauth : Impossible to identify you : Duplication of identities."
msgstr "LSauth : Impossible de vous identifier : Duplication d'identité."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:314
2020-05-12 19:24:53 +02:00
msgid "LSauth : Could not load type of identifiable objects %{type}."
msgstr "LSauth : Impossible de charger le type d'objets identifiables %{type}."
2018-08-31 17:28:55 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:317
2018-08-31 17:28:55 +02:00
msgid "LSauth : Can't load authentication method %{method}."
msgstr ""
"LSauth : Impossible de charger la méthode d'authentification %{method}."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:320
2018-08-31 17:28:55 +02:00
msgid "LSauth : Failed to build the authentication provider %{method}."
msgstr ""
"LSauth : Impossible de construire le gestionnaire d'authentification "
"%{method}."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:323
2018-08-31 17:28:55 +02:00
msgid "LSauth : Not correctly initialized."
msgstr "LSauth : Mauvaise initialisation."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:326
2018-08-31 17:28:55 +02:00
msgid "LSauth : Failed to get authentication informations from provider."
msgstr ""
"LSauth : Impossible de récupérer les informations authentification auprès du "
"gestionnaire."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSauth.php:329
msgid "LSauth : Method %{method} configured doesn't support API mode."
msgstr "LSauth : La méthode %{method} configurée ne supporte pas le mode API."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:41
2018-08-31 17:28:55 +02:00
msgid "Organism"
msgstr "Etablissement"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:47
2018-08-31 17:28:55 +02:00
msgid "Registration year"
msgstr "Année d'inscription"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:52
2018-08-31 17:28:55 +02:00
msgid "Registration year must be an integer"
msgstr "L'année d'inscription doit être un entier"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:61
2018-08-31 17:28:55 +02:00
msgid "Registration regime"
msgstr "Régime d'inscription"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:67
2018-08-31 17:28:55 +02:00
msgid "Discipline sector"
msgstr "Secteur disciplinaire"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:73
2018-08-31 17:28:55 +02:00
msgid "Diploma type"
msgstr "Type de diplôme"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:79
2018-08-31 17:28:55 +02:00
msgid "Cursus & Year"
msgstr "Cursus et année"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:91
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannRoleEntite.php:52
2018-08-31 17:28:55 +02:00
msgid "Entity"
msgstr "Entité"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:96
2018-08-31 17:28:55 +02:00
msgid "Diploma"
msgstr "Diplôme"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:102
2018-08-31 17:28:55 +02:00
msgid "Step"
msgstr "Étape"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannEtuInscription.php:108
2018-08-31 17:28:55 +02:00
msgid "Pedagogical element"
msgstr "Élement pédagogique"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1200
2018-08-31 17:28:55 +02:00
msgid "Actions"
msgstr "Actions"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1203
#: templates/default/global_search.tpl:16
2018-08-31 17:28:55 +02:00
msgid "This search didn't get any result."
2020-04-29 15:38:41 +02:00
msgstr "Cette recherche n'a retournée aucun résultat."
2018-08-31 17:28:55 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1842
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Invalid filter : %{filter}."
msgstr "LSsearch : Filtre invalide : %{filter}."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1845
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Invalid basedn : %{basedn}."
msgstr "LSsearch : Base DN invalide."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1848
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Invalid value for %{param} parameter."
msgstr "LSsearch : La valeur du paramètre %{param} est incorrecte."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1851
2018-08-31 17:28:55 +02:00
msgid ""
"LSsearch : Invalid size limit. Must be an integer greater or equal to 0."
msgstr ""
"LSsearch : Limite de taille de recherche invalide. Elle doit être un entier "
"supérieur ou égal à 0."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1854
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Invalid parameter %{attr}. Must be an boolean."
msgstr "LSsearch : Paramètre %{param} invalide. Il doit être un booléen."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1857
2018-08-31 17:28:55 +02:00
msgid ""
"LSsearch : Invalid parameter attributes. Must be an string or an array of "
"strings."
msgstr ""
"LSsearch : Paramètre 'attributes' invalide. Il doit être une chaîne de "
"caractères ou un tableau de chaînes de caractères."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1860
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Can't build attributes list for make filter."
msgstr ""
"LSsearch : Impossible de construire la liste des attributs pour faire le "
"filtre."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1863
2018-08-31 17:28:55 +02:00
msgid ""
"LSsearch : Error building filter with attribute '%{attr}' and pattern "
"'%{pattern}'"
msgstr ""
"LSsearch : Problème en construisant le filtre avec l'attribut '%{attr}' et "
"le mot clé '%{pattern}'"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1866
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Error combining filters."
msgstr "LSsearch : Problème en combinant les filtres."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1869
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Invalid pattern."
msgstr "LSsearch : Mot clé invalide."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1872
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Invalid attribute %{attr} in parameters."
msgstr "LSsearch : Attribut %{attr} incorrect dans les paramètres."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1875
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Error during the search."
msgstr "LSsearch : Erreur pendant la recherche."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1878
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Error sorting the search."
msgstr "LSsearch : Erreur pendant le trie de la recherche."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1881
2018-08-31 17:28:55 +02:00
msgid ""
"LSsearch : The function of the custum information %{name} is not callable."
msgstr ""
"LSsearch : La fonction de l'information personnalisée %{name} n'est pas "
"exécutable."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1884
2018-08-31 17:28:55 +02:00
msgid ""
"LSsearch : Invalid predefinedFilter for LSobject type %{type} : %{label} "
"(filter : %{filter})."
msgstr ""
"LSsearch : PredefinedFilter invalide pour le type d'LSobject %{type} : "
"%{label} (filtre : %{filter})."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1887
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Error during execution of the custom action %{customAction}."
msgstr ""
"LSldapObject : Erreur durant l'exécution de l'action personnalisée "
"%{customAction}."
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearch.php:1890
2018-08-31 17:28:55 +02:00
msgid "LSsearch : Invalid search pattern."
2020-04-29 15:38:41 +02:00
msgstr "LSsearch : Mot clé de recherche invalide."
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:53
2018-08-31 17:28:55 +02:00
msgid "Click to enlarge."
msgstr "Cliquer pour agrandir."
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:54
2018-08-31 17:28:55 +02:00
msgid "Click to delete the picture."
msgstr "Cliquer pour supprimer cette photo."
2013-06-18 00:28:19 +02:00
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:149
msgid "The uploaded file size exceeds the limit accepted by the server."
msgstr "La taille du fichier envoyé dépasse la limite acceptée par le serveur."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:151
msgid "The uploaded file size exceeds the limit accepted by the HTML form."
msgstr ""
"La taille du fichier envoyé dépasse la limite acceptée par le formulaire "
"HTML."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:153
msgid "The file was only partially uploaded."
msgstr "Le fichier n'a été que partiellement envoyé."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:155
msgid "No file was uploaded."
msgstr "Aucun fichier n'a été envoyé."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:157
msgid "No temporary folder found to store this uploaded file."
msgstr ""
"Aucun dossier temporaire n'a été trouvé pour stocker le fichier envoyé."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:159
msgid "Failed to write file on server disk."
msgstr "Impossible d'écrire le fichier temporaire sur le disque du serveur."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:161
msgid "A PHP extension stopped the file upload."
msgstr "Une extension PHP a stoppé l'envoi de fichier."
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_image.php:164
msgid "An unknown error occured sending this file."
msgstr "Une erreur inconnue est survenue durant l'envoi de ce fichier."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_xmpp.php:50
2018-08-31 17:28:55 +02:00
msgid "Chat with this person."
msgstr "Discuter avec cette personne."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannLabeledValue.php:93
#, php-format
msgid "%s (Unparsable value)"
msgstr "%s (valeur non-analysable)"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:436
2017-06-15 18:47:54 +02:00
msgid ""
"LSattr_html_select_list: Configuration data are missing to generate the "
2018-08-31 17:28:55 +02:00
"select list of the attribute %{attr}."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattr_html_select_list : Des données de configuration sont manquantes pour "
"générer la liste de sélection de l'attribut %{attr}."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:439
2018-08-31 17:28:55 +02:00
msgid ""
"LSattr_html_select_list: Invalid attribute %{attr} reference as "
2018-08-31 17:28:55 +02:00
"OTHER_ATTRIBUTE possible values."
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattr_html_select_list : Référence invalide à l'attribut %{attr} comme "
"valeurs possibles (OTHER_ATTRIBUTE)."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:442
2018-08-31 17:28:55 +02:00
msgid ""
"LSattr_html_select_list: Attribute %{attr} referenced as OTHER_ATTRIBUTE "
2018-08-31 17:28:55 +02:00
"possible values is not a jsonCompositeAttribute."
msgstr ""
"LSattr_html_select_list : L'attribute %{attr} référencé comme valeurs "
"possibles (OTHER_ATTRIBUTE) n'est pas du type jsonCompositeAttribute."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:445
2018-08-31 17:28:55 +02:00
msgid ""
"LSattr_html_select_list: Fail to decode the following attribute %{attr} "
2018-08-31 17:28:55 +02:00
"value as JSON : %{value}"
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattr_html_select_list : Impossible de décodé la valeur JSON suivante de "
"l'attribut %{attr} : %{value}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:448
msgid ""
"LSattr_html_select_list: No component %{component} found in the following "
2018-08-31 17:28:55 +02:00
"attribute %{attr} JSON value : %{value}"
msgstr ""
2018-08-31 17:28:55 +02:00
"LSattr_html_select_list : Le composant %{component} n'a pas été trouvé dans "
"la valeur JSON de l'attribut %{attr} : %{value}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:451
msgid ""
"LSattr_html_select_list: Invalid get_possible_values parameter found in "
"configuration of attribute %{attr}: must be a callable."
msgstr ""
"LSattr_html_select_list : Paramètre get_possible_values invalide trouvé dans "
"la configuration de l'attribut %{attr} : cela doit être un callable."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_select_list.php:454
msgid ""
"LSattr_html_select_list: fail to retreive possible values of attribute "
"%{attr} using configured function %{callable}."
msgstr ""
"LSattr_html_select_list : Impossible de récupérer les valeurs possibles de "
"l'attribut %{attr} en utilisant la fonction configurée %{callable}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_inarray.php:57
2017-06-15 18:47:54 +02:00
msgid ""
2018-08-31 17:28:55 +02:00
"LSformRule_inarray : Possible values has not been configured to validate "
"data."
2017-06-15 18:47:54 +02:00
msgstr ""
2018-08-31 17:28:55 +02:00
"LSformRule_inarray : Les valeurs possibles n'ont pas été configurées pour "
"valider les données."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_jsonCompositeAttribute.php:260
msgid "Fail to decode JSON value #%{idx}."
msgstr "Impossible de décoder la valeur JSON #%{idx}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_jsonCompositeAttribute.php:392
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_jsonCompositeAttribute.php:415
2018-08-31 17:28:55 +02:00
msgid "Invalid value \"%{value}\" for component %{component}."
2020-04-29 15:38:41 +02:00
msgstr "Valeur invalide pour le composant %{component} : \"%{value}\"."
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformRule_date.php:66
2018-08-31 17:28:55 +02:00
msgid "LSformRule_date : No date format specify."
msgstr "LSformRule_date : Aucun format de date spécifié."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_maildir.php:58
2018-08-31 17:28:55 +02:00
msgid "The mailbox has been moved."
msgstr "La boîte mail a été déplacée."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_maildir.php:65
2018-08-31 17:28:55 +02:00
msgid "The mailbox has been created."
msgstr "La boîte mail a été créée."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_maildir.php:85
2018-08-31 17:28:55 +02:00
msgid "The mailbox has been archived successfully."
msgstr "Le dossier mail a bien été archivée."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSattr_html_maildir.php:96
2018-08-31 17:28:55 +02:00
msgid "The mailbox has been deleted."
msgstr "La boîte mail a été supprimée."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannRoleEntite.php:40
2018-08-31 17:28:55 +02:00
msgid "Role"
msgstr "Rôle"
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSformElement_supannRoleEntite.php:46
2018-08-31 17:28:55 +02:00
msgid "Entity type"
msgstr "Type d'entité"
2017-06-15 18:47:54 +02:00
2020-09-03 18:31:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LScli.php:210
2020-04-29 15:38:41 +02:00
msgid ""
"Invalid parameter \"%{parameter}\".\n"
"Note: Command's parameter/argument must be place after the command."
msgstr ""
"Paramètre \"%{parameter}\" invalide.\n"
"Note: Les paramètres/arguments de la commande doivent être placés après "
"celle-ci."
2020-09-03 18:31:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LScli.php:779
2020-04-29 15:38:41 +02:00
msgid "LScli : The CLI command '%{command}' already exists."
msgstr "LScli : La commande CLI '%{command}' existe déjà."
2020-09-03 18:31:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LScli.php:782
2020-04-29 15:38:41 +02:00
msgid "LScli : The CLI command '%{command}' handler is not callable."
msgstr ""
"LScli : La fonction de prise en charge de la commande CLI '%{command}' n'est "
"pas exécutable."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSioFormatCSV.php:236
msgid "LSioFormatCSV: function fputcsv is not available."
msgstr "LSioFormatCSV : la fonction fputcsv n'est pas disponible."
2020-09-03 18:31:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSlog.php:478
2019-06-28 18:08:46 +02:00
msgid "LSlog : Fail to load logging handler %{handler}."
msgstr "LSlog : Impossible de charger l'handler %{handler}."
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSerror.php:112
#: templates/default/import.tpl:43
2018-08-31 17:28:55 +02:00
msgid "Errors"
msgstr "Erreurs"
2017-06-15 18:47:54 +02:00
2020-05-28 19:48:27 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSerror.php:115
2018-08-31 17:28:55 +02:00
msgid "Stop"
msgstr "Stop"
2017-06-15 18:47:54 +02:00
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSerror.php:158
2020-05-28 19:48:27 +02:00
msgid "Unknown error"
msgstr "Erreur inconnue"
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSerror.php:213
2018-08-31 17:28:55 +02:00
msgid "Unknown error : %{error}"
msgstr "Erreur inconnu : %{error}"
2017-06-15 18:47:54 +02:00
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearchEntry.php:166
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1191
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1284
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1426
2020-05-04 10:49:11 +02:00
msgid "View"
msgstr "Voir"
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearchEntry.php:182
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1047
2020-05-03 18:48:33 +02:00
msgid "Copy"
msgstr "Copier"
2020-09-09 19:05:01 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearchEntry.php:258
msgid "Unknown property !"
msgstr "Propriété inconnue !"
2020-09-11 13:38:07 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSsearchEntry.php:280
2018-08-31 17:28:55 +02:00
msgid ""
"LSsearchEntry : Invalid formaterFunction %{func} for extraDisplayedColumns "
"%{column}."
msgstr ""
"LSsearchEntry : formaterFunction %{func} invalide utilisé pour "
"l'extraDisplayedColumns %{column}."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/class/class.LSioFormat.php:144
2018-08-31 17:28:55 +02:00
msgid "LSioFormat : IOformat driver %{driver} invalid or unavailable."
msgstr ""
"LSioFormat : Le pilote d'IOformat %{driver} est invalide ou n'est pas "
"disponible."
2017-06-15 18:47:54 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:39
msgid "Home"
msgstr "Accueil"
2020-09-03 18:31:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:150
msgid "You must provide pattern for global search."
msgstr "Vous devez fournir un mot clé pour les recherches globales."
Add API feature Some major changes have been made to handle this new feature : - LSsession now have a flag about API mode. The displayTemplate() and displayAjaxReturn() methods have been adjust to correctly handle this mode. - LSauth system have been adjust to handle a custom API mode : - LSauthMethod can support or not this mode : the $api_mode_supported permit to defined if supported (default, false). Currently, only HTTP (default in API mode) and annonymous mode support it. - An api_access parameter permit to configure witch type of user LSobject types could use the API. This flag must be set to True to allow a type of LSobject (default: False). In a same way, a web_access parameter now permit to disable Web access for some types of users (but this parameter is optional and its default value is True). - The HTTP method is the privileged first method for API mode. In this mode, if auth data aren't present in environment, it will request it by triggered a 403 HTTP error. Realm can be configured with new LSAUTHMETHOD_HTTP_API_REALM constant. - The LStemplate system handle API mode to correctly react on errors: it return a JSON answer instead of HTML page. Error pages also now return adjusted HTTP code (404 or 500). - The LSurl system have been adjust to handle API mode : - On declaring handlers, we could now specify if it's an API view with new $api_mode paremeter of add_handler() method - The LSurlRequest object have a new attribute to check if it's an API request - The error_404() method handle the API mode to return JSON answer. Furthermore, if no handlers matched with the requested URL, API mode is automatically enabled if the requested URL starts with 'api/'. - LSform implement it own API mode flag and a new submited flag that be toggle via the new setSubmited() method. Some major changes also occured on LSformElement classes to specifically handle API input/output for each types of attributes: - a new getApiValue() method permit to retrieve the API value of the attribute (on show API view) - the getPostData() method now have to correctly handle API input for the attribute (on create/modify API views). A programmatic way have been adopted for each types of attributes. - The LSimport and LScli create/modify commands also evolved to enable API mode of the LSform. This permit to take advantage of the new capability of LSform/LSformElement to handle input values with a programmatic way. - New routes have been add to handle API views. All this new routes start with 'api/1.0/' and use the same URL schema as the web UI. The API currently permit to search/show/add/modify/remove LSobjects and manages their relations.
2021-02-03 14:40:28 +01:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:455
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:803
2020-05-04 14:25:11 +02:00
msgid "Import"
msgstr "Importer"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:460
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:871
msgid "Export"
msgstr "Exporter"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:472
2020-05-03 18:48:33 +02:00
msgid "Reset"
msgstr "Réinitialiser"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:510
2020-05-19 18:26:41 +02:00
#: templates/default/select.tpl:28 templates/default/global_search.tpl:6
msgid "Search"
msgstr "Rechercher"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:511
2020-05-19 18:26:41 +02:00
#: templates/default/select.tpl:31
msgid "Approximative search"
msgstr "Recherche approximative"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:512
2020-05-19 18:26:41 +02:00
#: templates/default/select.tpl:32
msgid "Recursive search"
msgstr "Recherche récursive"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:598
2020-05-04 14:25:11 +02:00
msgid ""
"The custom action %{title} have been successfully execute on this search."
msgstr ""
"L'action personnalisée %{title} a été correctement exécutée sur cette "
"recherche."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:943
2020-05-04 10:49:11 +02:00
msgid "Data entry form"
msgstr "Masque de saisie"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:949
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1665
2020-05-04 10:49:11 +02:00
msgid "Object has been added."
msgstr "L'objet a été ajouté."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1086
2020-05-03 18:48:33 +02:00
msgid "My account"
msgstr "Mon compte"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1149
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1755
2020-05-04 10:49:11 +02:00
msgid "The object has been partially modified."
msgstr "L'objet a été partiellement modifié."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1152
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1758
2020-05-04 10:49:11 +02:00
msgid "The object has been modified successfully."
msgstr "L'objet a bien été modifié."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1267
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1799
2020-05-04 10:49:11 +02:00
msgid "%{objectname} has been successfully deleted."
msgstr "%{objectname} a bien été supprimé."
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1276
2020-05-04 10:49:11 +02:00
msgid "Deleting : %{objectname}"
msgstr "Suppression : %{objectname}"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1277
2020-05-04 10:49:11 +02:00
msgid "Do you really want to delete <strong>%{displayName}</strong> ?"
msgstr "Voulez-vous vraiment supprimer <strong>%{displayName}</strong> ?"
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/routes.php:1387
2020-05-04 14:25:11 +02:00
msgid ""
"The custom action %{customAction} have been successfully execute on "
"%{objectname}."
msgstr ""
"L'action personnalisée %{customAction} a été correctement exécutée sur "
"%{objectname}."
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/functions.php:115
msgid ""
"Function 'getFData' : The method %{meth} of the object %{obj} doesn't exist."
msgstr "Fonction getFData : La méthode %{meth} de l'objet %{obj} n'existe pas."
2013-06-18 00:28:19 +02:00
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/functions.php:208
msgid "[not string value]"
msgstr "[pas une chaîne de caractères]"
2013-06-18 00:28:19 +02:00
2020-05-12 19:24:53 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/includes/functions.php:254
msgid "Folder not found"
msgstr "Dossier introuvable"
2013-06-18 00:28:19 +02:00
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:53
msgid "Affiliate"
msgstr "Affilié"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:54
msgid "Alumnus"
msgstr "Ancien apprenant"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:55
msgid "Employee"
msgstr "Employé"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:56
msgid "Faculty"
msgstr "Faculté"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:57
msgid "Member"
msgstr "Membre"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:58
msgid "Student"
msgstr "Étudiant"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:59
msgid "Retired"
msgstr "Retraité"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:60
msgid "Teacher"
msgstr "Enseignant"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:61
msgid "Staff"
msgstr "Staff"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:62
msgid "Researcher"
msgstr "Chercheur"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:63
msgid "Emeritus teacher"
msgstr "Professeur émérite"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:64
msgid "Library - walk-in"
msgstr "Bibliothèque - Accès libre"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:65
msgid "Library - registered"
msgstr "Bibliothèque - Inscrit"
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:70
msgid "Mrs."
msgstr "Mme."
#: /home/brenard/dev/ldapsaisie_clean3/src/conf/LSaddons/config.LSaddons.supann.php:71
msgid "Mr."
msgstr "M."
#: templates/default/LSaccessRightsMatrixView.tpl:95
#: templates/default/LSaccessRightsMatrixView.tpl:129
msgid "Allowed"
msgstr "Autorisé"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:18
msgid "Attributes / Profiles"
msgstr "Attributs / Profils"
2020-09-03 18:31:53 +02:00
#: templates/default/recoverpassword.tpl:28
2020-05-12 19:24:53 +02:00
msgid "Back"
msgstr "Retour"
#: templates/default/login.tpl:30
msgid "Connect"
msgstr "Se connecter"
#: templates/default/base_connected.tpl:49
2020-05-28 19:48:27 +02:00
msgid "Connected as"
msgstr "Connecté en tant que"
#: templates/default/LSaccessRightsMatrixView.tpl:87
msgid "Custom actions"
msgstr "Actions personnalisées"
#: templates/default/LSaccessRightsMatrixView.tpl:92
#: templates/default/LSaccessRightsMatrixView.tpl:126
msgid "Custom actions / Profiles"
msgstr "Actions personnalisées / Profils"
#: templates/default/LSaccessRightsMatrixView.tpl:121
msgid "Custom search actions"
msgstr "Actions personnalisées sur les recherches"
2020-05-12 19:24:53 +02:00
#: templates/default/error.tpl:16
msgid "Details"
msgstr "Détails"
#: templates/default/LSmail.tpl:3
msgid "Email"
msgstr "E-mail"
2020-05-12 19:24:53 +02:00
#: templates/default/import.tpl:10
msgid "File"
msgstr "Fichier"
2020-05-12 19:24:53 +02:00
#: templates/default/login.tpl:34
msgid "Forgot your password ?"
msgstr "Mot de passe perdu ?"
#: templates/default/export.tpl:8 templates/default/import.tpl:13
msgid "Format"
msgstr "Format"
2020-05-12 19:24:53 +02:00
#: templates/default/global_search.tpl:9
#: templates/default/base_connected.tpl:23
#: templates/default/base_connected.tpl:24
msgid "Global search"
msgstr "Recherche globale"
2020-09-03 18:31:53 +02:00
#: templates/default/recoverpassword.tpl:19 templates/default/login.tpl:18
2020-05-12 19:24:53 +02:00
msgid "Identifier"
msgstr "Identifiant"
#: templates/default/import.tpl:85
msgid "Imported objects"
msgstr "Objets importés"
2020-05-12 19:24:53 +02:00
#: templates/default/recoverpassword.tpl:13 templates/default/login.tpl:12
msgid "LDAP server"
msgstr "Serveur LDAP"
2020-09-03 18:31:53 +02:00
#: templates/default/recoverpassword.tpl:27 templates/default/login.tpl:22
#: templates/default/login.tpl:33 templates/default/base_connected.tpl:40
msgid "Language"
msgstr "Langue"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:20
#: templates/default/LSaccessRightsMatrixView.tpl:56
#: templates/default/LSaccessRightsMatrixView.tpl:94
#: templates/default/LSaccessRightsMatrixView.tpl:128
msgid "Legend:"
msgstr "Légende :"
#: templates/default/base_connected.tpl:51
msgid "Logout"
msgstr "Déconnexion"
#: templates/default/LSmail.tpl:28
msgid "Message"
msgstr "Message"
#: templates/default/viewSearch.tpl:113
msgid "Nb / page :"
msgstr "Nb / page :"
#: templates/default/LSform_view.tpl:34
msgid "No field."
msgstr "Aucun champ."
#: templates/default/import.tpl:90
msgid "No imported object"
msgstr "Aucun objet importé"
#: templates/default/import.tpl:58
msgid "No value"
msgstr "Aucune valeur"
2020-09-21 15:47:07 +02:00
#: templates/default/showTechInfo.tpl:11
msgid "Object classes"
msgstr "Classes d'objet"
#: templates/default/import.tpl:30
msgid "Only validate data"
msgstr "Validation des données uniquement"
2020-09-21 15:47:07 +02:00
#: templates/default/showTechInfo.tpl:41
msgid "Other internal attributes"
msgstr "Autres attributs techniques"
2020-05-12 19:24:53 +02:00
#: templates/default/login.tpl:20
msgid "Password"
msgstr "Mot de passe"
2020-06-30 10:01:06 +02:00
#: templates/default/LSformElement_password_field.tpl:14
msgid "Please confirm new password:"
msgstr "Merci de confirmer le nouveau mot de passe :"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:21
#: templates/default/LSaccessRightsMatrixView.tpl:38
2020-05-28 19:48:27 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:57
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:73
msgid "R"
msgstr "L"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:23
#: templates/default/LSaccessRightsMatrixView.tpl:40
2020-05-28 19:48:27 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:59
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:75
msgid "R/W"
msgstr "L/É"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:21
#: templates/default/LSaccessRightsMatrixView.tpl:57
msgid "Readable"
msgstr "Lecture"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:23
#: templates/default/LSaccessRightsMatrixView.tpl:59
msgid "Readable / Writable"
msgstr "Lecture / Écriture"
#: templates/default/base_connected.tpl:50
msgid "Refresh my access rights"
msgstr "Rafraîchir mes droits d'accès"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:54
msgid "Relations / Profiles"
msgstr "Relations / Profils"
#: templates/default/import.tpl:41
msgid "Result"
msgstr "Résultat"
#: templates/default/base_connected.tpl:6
msgid "Show/hide menu"
msgstr "Afficher/cacher le menu"
#: templates/default/LSmail.tpl:21
msgid "Subject"
msgstr "Sujet"
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:49
msgid "Their relations with other objects"
msgstr "Leurs relations avec les autres objets"
#: templates/default/LSaccessRightsMatrixView.tpl:118
msgid "This object type has no configured custom action."
msgstr "Ce type d'objet n'a aucune action personnalisée de configurée."
#: templates/default/LSaccessRightsMatrixView.tpl:152
msgid "This object type has no configured custom search action."
msgstr ""
"Ce type d'objet n'a aucune action personnalisée sur les recherches de "
"configurée."
2020-05-12 19:24:53 +02:00
#: templates/default/LSaccessRightsMatrixView.tpl:84
msgid "This object type has no configured relation."
msgstr "Ce type d'objet n'a aucune relation de configurée."
#: templates/default/import.tpl:24
msgid "Update objects if exists"
msgstr "Mise à jour des objets existants"
#: templates/default/import.tpl:95
msgid "Updated objects"
msgstr "Objets mis à jour"
#: templates/default/export.tpl:15 templates/default/import.tpl:36
msgid "Valid"
msgstr "Valider"
#: templates/default/import.tpl:27 templates/default/import.tpl:33
msgid "no"
msgstr "non"
#: templates/default/import.tpl:26 templates/default/import.tpl:32
msgid "yes"
msgstr "oui"
2020-09-03 18:31:53 +02:00
#~ msgid ""
#~ "LSsession : call function %{func} do not provided from LSaddon %{addon}."
#~ msgstr ""
#~ "LSsession : la fonction %{func} n'est pas fournie par le LSaddon %{addon}."
#~ msgid "LSsession : problem during initialisation."
#~ msgstr "LSsession : Problème durant l'initialisation."
#~ msgid ""
#~ "LSformElement_password : Contact mail invalid (%{mail}). Can't send "
#~ "password."
#~ msgstr ""
#~ "LSformElement_password : Mail de contact invalide (%{mail}). Impossible "
#~ "d'envoyer le mot de passe."
#~ msgid "Only one command could be executed !"
#~ msgstr "Une seule commande peut-être exécutée !"
#~ msgid "Title"
#~ msgstr "Titre"
2020-05-19 18:26:41 +02:00
#~ msgid "deleting"
#~ msgstr "suppression"
#~ msgid "renaming"
#~ msgstr "renommage"
#~ msgid "updating"
#~ msgstr "mise à jour"
2020-05-04 10:49:11 +02:00
#~ msgid "Deleting"
#~ msgstr "Suppression"
#~ msgid "has been deleted successfully"
#~ msgstr "a bien été supprimé"
2020-05-02 18:32:31 +02:00
#~ msgid "Missing parameter"
#~ msgstr "Paramètre manquant"
2019-06-28 18:08:46 +02:00
#~ msgid "PHP error : %{error}"
#~ msgstr "Erreur PHP : %{error}"
#~ msgid "SSH Support : Unable to connect to SSH Server (%{host}:%{port})."
#~ msgstr ""
#~ "Support SSH : Impossible de se connecter au serveur SSH (%{host}:%{port})."
#, fuzzy
#~ msgid "delete"
#~ msgstr "Supprimer"
#~ msgid ""
#~ "LSrelation : The update function of the relation %{relation} is unknow."
#~ msgstr ""
#~ "LSsession : La fonction de mise à jour de la relation %{relation} est "
#~ "inconnue."
2013-06-18 00:28:19 +02:00
#, fuzzy
#~ msgid "Administration"
#~ msgstr "Confirmation"
2011-06-27 15:51:39 +02:00
#~ msgid "Select in a calendar."
#~ msgstr "Choisir dans un calendrier."