GitHub/ergo
3
0
Fork 0
mirror of https://github.com/ergochat/ergo.git synced 2024-11-26 05:49:25 +01:00
Code Issues Projects Releases Wiki Activity

New translations help.lang.json (Bosnian)

Browse Source
This commit is contained in:
Daniel Oaks 2019-05-17 02:28:57 +10:00
parent af821c34b0
commit 9578d2f4cf
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
languages/bs-BA-help.lang.json
View File

@ -16,7 +16,7 @@
"DLINE [ANDKILL] [MYSELF] [duration] <ip>/<net> [ON <server>] [reason [| oper reason]]\nDLINE LIST\n\nBans an IP address or network from connecting to the server. If the duration is\ngiven then only for that long. The reason is shown to the user themselves, but\neveryone else will see a standard message. The oper reason is shown to\noperators getting info about the DLINEs that exist.\n\nBans are saved across subsequent launches of the server.\n\n\"ANDKILL\" means that all matching clients are also removed from the server.\n\n\"MYSELF\" is required when the DLINE matches the address the person applying it is connected\nfrom. If \"MYSELF\" is not given, trying to DLINE yourself will result in an error.\n\n[duration] can be of the following forms:\n\t1y 12mo 31d 10h 8m 13s\n\n<net> is specified in typical CIDR notation. For example:\n\t127.0.0.1/8\n\t8.8.8.8/24\n\nON <server> specifies that the ban is to be set on that specific server.\n\n[reason] and [oper reason], if they exist, are separated by a vertical bar (|).\n\nIf \"DLINE LIST\" is sent, the server sends back a list of our current DLINEs.": "",
"HELP <argument>\n\nGet an explanation of <argument>, or \"index\" for a list of help topics.": "",
"HELPOP <argument>\n\nGet an explanation of <argument>, or \"index\" for a list of help topics.": "",
"HISTORY <target> [limit]\n\nReplay message history. <target> can be a channel name, \"me\" to replay direct\nmessage history, or a nickname to replay another client's direct message\nhistory (they must be logged into the same account as you). At most [limit]\nmessages will be replayed.": "",
"HISTORY <target> [limit]\n\nReplay message history. <target> can be a channel name, \"me\" to replay direct\nmessage history, or a nickname to replay another client's direct message\nhistory (they must be logged into the same account as you). At most [limit]\nmessages will be replayed.": "-> HISTORY <target> [limit]\n\nPonovi povijest poruka. <target> može biti naziv kanala, \"ja\" za ponavljanje izravne povijesti poruka, ili nadimak (nickname) za ponavljanje povijesti izravih poruke drugih korisnika (oni moraju biti prijavljeni na isti račun kao i vi). Ponovit će se najviše [limit] poruka.",
"HOSTSERV <command> [params]\n\nHostServ lets you manage your vhost (a string displayed in place of your\nreal hostname).": "",
"HS <command> [params]\n\nHostServ lets you manage your vhost (a string displayed in place of your\nreal hostname).": "",
"INFO\n\nSends information about the server, developers, etc.": "",
@ -55,7 +55,7 @@
"SAMODE <target> [<modestring> [<mode arguments>...]]\n\nForcibly sets and removes modes from the given target -- only available to\nopers. For more specific information on mode characters, see the help for\n\"cmode\" and \"umode\".": "",
"SANICK <currentnick> <newnick>\n\nGives the given user a new nickname.": "",
"SCENE <target> <text to be sent>\n\nThe SCENE command is used to send a scene notification to the given target.": "",
"SETNAME <realname>\n\nThe SETNAME command updates the realname to be the newly-given one.": "",
"SETNAME <realname>\n\nThe SETNAME command updates the realname to be the newly-given one.": "SETNAME <realname>\n\nSETNAME naredba ažurira pravoime, kako bi ono bilo novo-dano ime.",
"TIME [server]\n\nShows the time of the current, or the given, server.": "",
"TOPIC <channel> [topic]\n\nIf [topic] is given, sets the topic in the channel to that. If [topic] is not\ngiven, views the current topic on the channel.": "",
"UNDLINE <ip>/<net>\n\nRemoves an existing ban on an IP address or a network.\n\n<net> is specified in typical CIDR notation. For example:\n\t127.0.0.1/8\n\t8.8.8.8/24": "",