mirror of
https://github.com/ergochat/ergo.git
synced 2024-11-11 06:29:29 +01:00
New translations nickserv.lang.json (Afrikaans)
This commit is contained in:
parent
60c13c9533
commit
eaf0d679fc
53
languages/af-ZA-nickserv.lang.json
vendored
53
languages/af-ZA-nickserv.lang.json
vendored
@ -1,16 +1,55 @@
|
||||
{
|
||||
"NickServ lets you register and login to an account.\n\nTo see in-depth help for a specific NickServ command, try:\n $b/NS HELP <command>$b\n\nHere are the commands you can use:\n%s": "",
|
||||
"$bALWAYS-ON$b\n'always-on' controls whether your nickname/identity will remain active\neven while you are disconnected from the server. Your options are 'true',\n'false', and 'default' (use the server default value).": "",
|
||||
"$bAUTO-AWAY$b\n'auto-away' is only effective for always-on clients. If enabled, you will\nautomatically be marked away when all your sessions are disconnected, and\nautomatically return from away when you connect again.": "",
|
||||
"$bAUTOREPLAY-LINES$b\n'autoreplay-lines' controls the number of lines of channel history that will\nbe replayed to you automatically when joining a channel. Your options are any\npositive number, 0 to disable the feature, and 'default' to use the server\ndefault.": "",
|
||||
"$bAUTOREPLAY-MISSED$b\n'autoreplay-missed' is only effective for always-on clients. If enabled,\nif you have at most one active session, the server will remember the time\nyou disconnect and then replay missed messages to you when you reconnect.\nYour options are 'on' and 'off'.": "",
|
||||
"$bCERT$b controls a user account's certificate fingerprints": "",
|
||||
"$bDM-HISTORY$b\n'dm-history' is only effective for always-on clients. It lets you control\nhow the history of your direct messages is stored. Your options are:\n1. 'off' [no history]\n2. 'ephemeral' [a limited amount of temporary history, not stored on disk]\n3. 'on' [history stored in a permanent database, if available]\n4. 'default' [use the server default]": "",
|
||||
"$bDROP$b de-links your current (or the given) nickname from your user account.": "",
|
||||
"$bENFORCE$b\n'enforce' lets you specify a custom enforcement mechanism for your registered\nnicknames. Your options are:\n1. 'none' [no enforcement, overriding the server default]\n or else they will be renamed]\n2. 'strict' [you must already be authenticated to use the nick]\n3. 'default' [use the server default]": "",
|
||||
"$bERASE$b erases all records of an account, allowing reuse.": "",
|
||||
"$bGET$b queries the current values of your account settings": "",
|
||||
"$bGHOST$b reclaims your nickname.": "",
|
||||
"$bGROUP$b links your current nickname to your user account.": "",
|
||||
"$bIDENTIFY$b lets you login to your account.": "",
|
||||
"$bINFO$b gives you information on a user account.": "",
|
||||
"$bLIST$b searches the list of registered nicknames.": "",
|
||||
"$bMULTICLIENT$b\nIf 'multiclient' is enabled and you are already logged in and using a nick, a\nsecond client of yours that authenticates with SASL and requests the same nick\nis allowed to attach to the nick as well (this is comparable to the behavior\nof IRC \"bouncers\" like ZNC). Your options are 'on' (allow this behavior),\n'off' (disallow it), and 'default' (use the server default value).": "",
|
||||
"$bPASSWD$b lets you change your password.": "",
|
||||
"$bREGISTER$b lets you register a user account.": "",
|
||||
"$bREPLAY-JOINS$b\n'replay-joins' controls whether replayed channel history will include\nlines for join and part. This provides more information about the context of\nmessages, but may be spammy. Your options are 'always', 'never', and the default\nof 'commands-only' (the messages will be replayed in /HISTORY output, but not\nduring autoreplay).": "",
|
||||
"$bSADROP$b forcibly de-links the given nickname from its user account.": "",
|
||||
"$bSAGET$b queries the current values of another user's account settings": "",
|
||||
"$bSAREGISTER$b registers an account on someone else's behalf.": "",
|
||||
"$bSASET$b modifies another user's account settings": "",
|
||||
"$bSESSIONS$b lists the sessions attached to a nickname.": "",
|
||||
"$bSET$b modifies your account settings": "",
|
||||
"$bUNREGISTER$b lets you delete your user account.": "",
|
||||
"$bVERIFY$b lets you complete account registration.": "",
|
||||
"Insufficient privileges": "",
|
||||
"Invalid parameters": "",
|
||||
"NickServ lets you register, log in to, and manage an account.": "",
|
||||
"Password incorrect": "",
|
||||
"Passwords do not match": "",
|
||||
"Syntax $bSET <setting> <value>$b\n\nSET modifies your account settings. The following settings are available:": "",
|
||||
"Syntax: $bCERT <LIST | ADD | DEL> [account] [certfp]$b\n\nCERT examines or modifies the TLS certificate fingerprints that can be used to\nlog into an account. Specifically, $bCERT LIST$b lists the authorized\nfingerprints, $bCERT ADD <fingerprint>$b adds a new fingerprint, and\n$bCERT DEL <fingerprint>$b removes a fingerprint. If you're an IRC operator\nwith the correct permissions, you can act on another user's account, for\nexample with $bCERT ADD <account> <fingerprint>$b.": "",
|
||||
"Syntax: $bDROP [nickname]$b\n\nDROP de-links the given (or your current) nickname from your user account.": "",
|
||||
"Syntax: $bENFORCE [method]$b\n\nENFORCE lets you specify a custom enforcement mechanism for your registered\nnicknames. Your options are:\n1. 'none' [no enforcement, overriding the server default]\n2. 'timeout' [anyone using the nick must authenticate before a deadline,\n or else they will be renamed]\n3. 'strict' [you must already be authenticated to use the nick]\n4. 'default' [use the server default]\nWith no arguments, queries your current enforcement status.": "",
|
||||
"Syntax: $bENFORCE [method]$b\n\nENFORCE is an alias for $bGET enforce$b and $bSET enforce$b. See the help\nentry for $bSET$b for more information.": "",
|
||||
"Syntax: $bERASE <username> [code]$b\n\nERASE deletes all records of an account, allowing it to be re-registered.\nThis should be used with caution, because it violates an expectation that\naccount names are permanent identifiers. Typically, UNREGISTER should be\nused instead. A confirmation code is required; invoking the command\nwithout a code will display the necessary code.": "",
|
||||
"Syntax: $bGET <setting>$b\n\nGET queries the current values of your account settings. For more information\non the settings and their possible values, see HELP SET.": "",
|
||||
"Syntax: $bGHOST <nickname>$b\n\nGHOST disconnects the given user from the network if they're logged in with the\nsame user account, letting you reclaim your nickname.": "",
|
||||
"Syntax: $bGROUP$b\n\nGROUP links your current nickname with your logged-in account, so other people\nwill not be able to use it.": "",
|
||||
"Syntax: $bIDENTIFY <username> [password]$b\n\nIDENTIFY lets you login to the given username using either password auth, or\ncertfp (your client certificate) if a password is not given.": "",
|
||||
"Syntax: $bINFO [username]$b\n\nINFO gives you information about the given (or your own) user account.": "",
|
||||
"Syntax: $bPASSWD <current> <new> <new_again>$b\nOr: $bPASSWD <username> <new>$b\n\nPASSWD lets you change your account password. You must supply your current\npassword and confirm the new one by typing it twice. If you're an IRC operator\nwith the correct permissions, you can use PASSWD to reset someone else's\npassword by supplying their username and then the desired password.": "",
|
||||
"Syntax: $bREGISTER <username> <email> [password]$b\n\nREGISTER lets you register a user account. If the server allows anonymous\nregistration, you can send an asterisk (*) as the email address.\n\nIf the password is left out, your account will be registered to your TLS client\ncertificate (and you will need to use that certificate to login in future).": "",
|
||||
"Syntax: $bLIST [regex]$b\n\nLIST returns the list of registered nicknames, which match the given regex.\nIf no regex is provided, all registered nicknames are returned.": "",
|
||||
"Syntax: $bPASSWD <current> <new> <new_again>$b\nOr: $bPASSWD <username> <new>$b\n\nPASSWD lets you change your account password. You must supply your current\npassword and confirm the new one by typing it twice. If you're an IRC operator\nwith the correct permissions, you can use PASSWD to reset someone else's\npassword by supplying their username and then the desired password. To\nindicate an empty password, use * instead.": "",
|
||||
"Syntax: $bREGISTER <password> [email]$b\n\nREGISTER lets you register your current nickname as a user account. If the\nserver allows anonymous registration, you can omit the e-mail address.\n\nIf you are currently logged in with a TLS client certificate and wish to use\nit instead of a password to log in, send * as the password.": "",
|
||||
"Syntax: $bSADROP <nickname>$b\n\nSADROP forcibly de-links the given nickname from the attached user account.": "",
|
||||
"Syntax: $bSAREGISTER <username> <password>$b\n\nSAREGISTER registers an account on someone else's behalf.\nThis is for use in configurations that require SASL for all connections;\nan administrator can set use this command to set up user accounts.": "",
|
||||
"Syntax: $bSESSIONS [nickname]$b\n\nSESSIONS lists information about the sessions currently attached, via\nthe server's bouncer functionality, to your nickname. An administrator\ncan use this command to list another user's sessions.": "",
|
||||
"Syntax: $bSAGET <account> <setting>$b\n\nSAGET queries the values of someone else's account settings. For more\ninformation on the settings and their possible values, see HELP SET.": "",
|
||||
"Syntax: $bSAREGISTER <username> [password]$b\n\nSAREGISTER registers an account on someone else's behalf.\nThis is for use in configurations that require SASL for all connections;\nan administrator can set use this command to set up user accounts.": "",
|
||||
"Syntax: $bSASET <account> <setting> <value>$b\n\nSASET modifies the values of someone else's account settings. For more\ninformation on the settings and their possible values, see HELP SET.": "",
|
||||
"Syntax: $bSESSIONS [nickname]$b\n\nSESSIONS lists information about the sessions currently attached, via\nthe server's multiclient functionality, to your nickname. An administrator\ncan use this command to list another user's sessions.": "",
|
||||
"Syntax: $bUNREGISTER <username> [code]$b\n\nUNREGISTER lets you delete your user account (or someone else's, if you're an\nIRC operator with the correct permissions). To prevent accidental\nunregistrations, a verification code is required; invoking the command without\na code will display the necessary code.": "",
|
||||
"Syntax: $bVERIFY <username> <code>$b\n\nVERIFY lets you complete an account registration, if the server requires email\nor other verification.": ""
|
||||
"Syntax: $bVERIFY <username> <code>$b\n\nVERIFY lets you complete an account registration, if the server requires email\nor other verification.": "",
|
||||
"You're not logged into an account": ""
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user