Hello folks, I will list done here the changes that you should to in order to update the exploits file. First of all can see the new file at http://docs.dal.net/xml/csaccess/ Now remember to use utf-8 and surrogate ^c~u. ******* NOTE: In the beginning you will see these changes are too much, but when you read the all txt file you will find that you may take less than 5 minutes to update your language file. To sum it up for you, you only need to add Manager to each related section and subsection and its missing commands. ******* YOU have to do the Change #1 to be updated in filesdone. The rest of the changes are optional. ******* Please open your translated file and go the follow lines: change #1 **THE MOST IMPRTANT CHANGE** find the line:

If your channel encounters problems such as abusive behaviour or a takeover, and you are not there, you will need AOPs and possibly SOPs so that the problem can be solved.

change it to:

If your channel encounters problems such as abusive behaviour or a takeover, and you are not there, you will need AOPs and possibly SOps/Managers so that the problem can be solved.

We have added a Manager access in Channels oplist, to know more about how to add managers please visit http://docs.dal.net/docs/chanserv.html#5.

********* The rest are OPTIONAL ********* change #2: find the line:

If your channel becomes large, you may need SOPs to help manage it.

change it to:

If your channel becomes large, you may need Managers to help manage it.

****** change #3: find the line:

Adding the wrong people as AOPs or SOPs, or adding AOPs or SOPs in the wrong way, can cause security loopholes that might let unfriendly users cause problems in the channel, so you should be fully informed about using these features.

change it to:

Adding the wrong people as AOPs/SOPs/Managers, or adding AOPs/SOPs/Managers in the wrong way, can cause security loopholes that might let unfriendly users cause problems in the channel, so you should be fully informed about using these features.

****** change #4: find the line(s):
What AOPs and SOPs are

AOPs and SOPs are people whom you trust enough to allow them certain powers on your channel.

SOPs are a "higher" level than AOPs and have all the AOP privileges in addition to some extra powers. As the founder, you are at a higher level still and you have all the SOP and AOP privileges, plus some founder-only powers. There is no need to add yourself to the SOP or AOP lists.

change them to:
What AOPs / SOPs and Managers are

AOPs / SOPs and Managers people whom you trust enough to allow them certain powers on your channel.

Managers are the "highest" level of channel ops (@). They have *almost* full control over the channel with the exception of changing the channel's foundership. Please visit http://docs.dal.net/docs/chanserv.html#5 for more instructions.

SOPs are a "higher" level than AOPs and have all the AOP privileges in addition to some extra powers. As the founder, you are at a higher level still and you have all the SOP and AOP privileges, plus some founder-only powers. There is no need to add yourself to the SOP or AOP lists.

****** change #3: fine the line:

It is possible to set channels so that only ops can change the topic. (However it's also possible to set them so that only SOPs or only the founder can change the topic.) ( /chanserv help set topiclock )

change it to:

It is possible to set channels so that only ops can change the topic. (However it's also possible to set them so that only Managers/SOPs or only the founder can change the topic.) ( /chanserv help set topiclock )

****** change #4: find the line(s): /memoserv help sendsop )

**add under**

Managers have the following additional powers:

Channel managers can: - Manage the SOP list (add/remove SOPs) - Change WEBPASSWD - Wipe AOP/SOP lists - Change channel description - Masskick and massdeop a channel up to and including the access level of AOp - Set/unset OPGUARD - Set/unset MLOCK - Set/unset IDENT - Set/unset KEEPTOPIC - Set/unset RESTRICT - Set/unset URL - Set/unset VERBOSE - Set/unset TOPICLOCK (unless it's locked to the founder) - Set/unset LEAVEOPS - Set/unset PRIVATE - Set/unset MEMO level (unless it's locked to the founder) - See successor's nick with ChanServ INFO Channel managers can *NOT*: - Change channel password - Change founder - Set/unset successor - Set/unset mailblock - Add/remove other managers - Set/unset UNSECURE (currently broken and doesn't do anything) - Use sendpass
change #4:Things to consider when giving op (@) access privileges change under the line to :

AOPs/SOPs and Managers are the people who can handle channel problems such as flooding and takeovers when you are not there. If you intend to run a successful channel, it is your reponsibility to ensure there are sufficient AOPs (especially) and SOPs so that order in the channel can be maintained. If the channel is being used with no AOPs present, then it is an easy target for flooding and abuse.

****** change #5: change the title and under: How to add or remove AOPs and SOPs

The channel founder is the only one who can give or take away SOP privileges. SOPs and the founder can give or take away AOP privileges. The two list commands are available to AOPs or SOPs and the founder, but not to ordinary users.

change it to: How to add or remove AOPs/SOPs and Managers

The channel founder or manager are the only ones who can give or take away SOP privileges. However, the founder is the only one who can give or take away SOP priviledges. Managers/SOPs and the founder can give or take away AOP privileges. The two list commands are available to AOPs/SOPs or Managers and the founder, but not to ordinary users.

****** change #6 all in section and subsection 4: (1) Listing current SOPs or AOPs to Listing current Managers/SOPs or AOPs (2) /chanserv sop #channel list !! add before it the following lines: /chanserv manager #channel list (2) **find:

These commands list all the SOPs or AOPs (respectively) on the channel.

If you have a large channel, you may find it useful to list only selected SOPs or AOPs based on their nicknames or masks:

**change to:

These commands list all the Managers/SOPs or AOPs (respectively) on the channel.

If you have a large channel, you may find it useful to list only selected Managers/SOPs or AOPs based on their nicknames or masks:

(3) /chanserv sop #channel list wildcard !! add before it the following lines: /chanserv manager #channel list wildcard (4)

find:

Whichever list command you use, each AOP or SOP is listed with a number which makes it easier to remove them if necessary (see below).

change to:

Whichever list command you use, each AOP or SOP or Manager is listed with a number which makes it easier to remove them if necessary (see below).

(5) Adding SOPs or AOPs to: Adding Managers/SOPs or AOPs find: /chanserv sop #channel add nick or mask add before ^ this: /chanserv manager #channel add nick or mask find:

These commands add people to the SOP or AOP lists. This is equivalent to giving people SOP or AOP privileges.

change to:

These commands add people to the MANAGER/SOP or AOP lists. This is equivalent to giving people MANAGER/SOP or AOP privileges.

find:

Generally you should add AOPs or SOPs using their nick (which should be registered) but you can also do so with a mask if necessary. Masks work in the same way as channel ban masks - though of course here they have the effect of granting AOP or SOP privileges to the target, not banning them - and are not explained in this guide; for more information see the Ban Guide.

change to:

Generally you should add AOPs or SOPs or Managers using their nick (which should be registered) but you can also do so with a mask if necessary. Masks work in the same way as channel ban masks - though of course here they have the effect of granting AOP or SOP or Managers privileges to the target, not banning them - and are not explained in this guide; for more information see the Ban Guide.

find: Removing SOPs or AOPs change it to: Removing Managers/SOPs or AOPs find: /chanserv sop #channel del number or entry in list add before ^^ this: /chanserv manager #channel del number or entry in list find:

These commands are used to remove people from the SOP or AOP lists. SOPs and AOPs may be removed for misconduct or for whatever the reason may be.

change to:

These commands are used to remove people from the Manager/SOP or AOP lists. Managers/SOPs and AOPs may be removed for misconduct or for whatever the reason may be.

find:

If the VERBOSE mode is turned on for a channel, then whenever there is a change to certain aspects of the channel (in particularly, when somebody adds or removes AOP/SOPs or AKICKs), all ops currently on the channel will be informed with a notice.

change to:

If the VERBOSE mode is turned on for a channel, then whenever there is a change to certain aspects of the channel (in particularly, when somebody adds or removes AOP/SOPs/Managers or AKICKs), all ops currently on the channel will be informed with a notice.

****** change #7: find: Advice on using address masks in your AOP/SOP lists

It's generally best to use nicknames, rather than address masks, in AOP/SOP lists. There are several reasons for this:

change to: Advice on using address masks in your AOp/SOp or Manager lists

It's generally best to use nicknames, rather than address masks, in op(@) access lists. There are several reasons for this:

find:

You can always tell exactly who has AOPs or SOPs.

change to:

You can always tell exactly who has AOPs/SOPs or Managers.

****** change #8: find: Problems with the wrong people getting AOPs/SOPs change to: Problems with the wrong people getting AOPs/SOPs or Managers find:

People can also get ops if they are given them by somebody who already has ops (e.g. an AOP or SOP). If you do not want to allow this, you can use a feature called OPGUARD which is explained at the end of this section.

change to:

People can also get ops if they are given them by somebody who already has ops (e.g. an AOP/SOP or Managers). If you do not want to allow this, you can use a feature called OPGUARD which is explained at the end of this section.

find:

To discover why somebody has AOP or SOP privileges in a channel, you can use the ChanServ why command:

change to:

To discover why somebody has AOP/SOP or Manager privileges in a channel, you can use the ChanServ why command:

find:

This will explain the AOP or SOP list entry (if any) that is responsible for granting that person privileges, so it can be temporarily removed if there is a problem.

change to:

This will explain the op (@) list entry (if any) that is responsible for granting that person privileges, so it can be temporarily removed if there is a problem.

find:

The founder can set IDENT mode for a channel using

change to:

The founder and manager can set IDENT mode for a channel using

find:

If you as channel founder do not want this to happen, you can enable the OPGUARD feature. When this feature is turned on, ChanServ will not allow people to have ops (@) on a channel (even temporarily) unless they are on the AOP or SOP list or are the founder. If somebody else is given ops, ChanServ will remove their ops immediately.

change to:

If you as channel founder or manager and you do not want this to happen, you can enable the OPGUARD feature. When this feature is turned on, ChanServ will not allow people to have ops (@) on a channel (even temporarily) unless they are on the AOP/SOP/Manager list or are the founder. If somebody else is given ops, ChanServ will remove their ops immediately.

****** changes #9: akick section: find:

Only channel founders and SOPs have the power to add or remove AKICKs.

change to:

Only channel founders/managers and SOPs have the power to add or remove AKICKs.

find:

This command, which can be used by channel AOPs as well as SOPs and the founder, lists all of the AKICKs currently in place on the channel.

change to:

This command, which can be used by channel AOPs/SOps as well as Managers and the founder, lists all of the AKICKs currently in place on the channel.

changes #10 : find:

SOPs and AOPs are people you trust enough to give them some power on your channel. Among other things, this means that they will automatically be given ops (@) when they enter. SOPs also have the ability to add and remove AOPs and AKICKs (permanent bans from the channel), so you should be especially careful when making people SOPs.

change it to:

Managers/SOPs and AOPs are people you trust enough to give them some power on your channel. Among other things, this means that they will automatically be given ops (@) when they enter. Managers can change some of the channel's settings, can add or remove SOPs/AOPs and AKICKs (only trusted users can gain this access). SOPs also have the ability to add and remove AOPs and AKICKs (permanent bans from the channel), so you should be especially careful when making people SOPs.

find: If your channel needs an SOP for some reason - for instance if it is a large channel and you need help with channel management such as choosing AOPs

Be certain you can trust the person you'd like to make an SOP, and check their nick is registered as above. Then type /chanserv sop #channel add nick .

change to: If your channel needs a Manager or SOP for some reason - for instance if it is a large channel and you need help with channel management such as choosing AOPs

Be certain you can trust the person you'd like to make an Manager or Sop, and check their nick is registered as above. Then type /chanserv manager #channel add nick . /chanserv sop #channel add nick .

find: If at a later date you need to remove an AOP or SOP from the channel list because they have proven untrustworthy, left IRC, or similar change to: If at a later date you need to remove an AOP or SOP or Manager from the channel list because they have proven untrustworthy, left IRC, or similar find: /chanserv aop or sop #channel list change to: /chanserv aop or sop or manager #channel list find line: You (or an SOP on the channel; not AOPs) can add them to the AKICK list by using change to: You (or an Manager or SOP on the channel; not AOPs) can add them to the AKICK list by using - ***** save the file as xml format under the name ( csaccess** 1.1.5.xml (** stands for your language)) and send it to Fredfred@dal.net. ***** Thats all.. H @ DALnet #DocsTeam