User Tools

Site Tools


encoding

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
encoding [2014/04/05 16:29]
sgrubnick
encoding [2014/04/05 16:30] (current)
sgrubnick
Line 16: Line 16:
   -- A target part (a nick or a channel)   -- A target part (a nick or a channel)
  
-Either side is optional, along with the slash. ​ Server parts are expected to contain dots, and channels are expected to start with a channel name char (#, &, +, etc), and a nick is everything else.  You should always include the slash if you think EPIC might misinterpret your nick or server as the other.+Either side is optional, along with the slash. ​ Server parts are expected to contain dots, and channels are expected to start with a channel name char (#, &, +, etc), and a nick is everything else.  You should always include the slash if you think EPIC might misinterpret your nick or server as the other (such as when you use server groups -- see examples below)
  
 =====Syntax Forms===== =====Syntax Forms=====
Line 57: Line 57:
  
     /ENCODING EFNet/ CP437     /ENCODING EFNet/ CP437
-Any server belonging to group "​EFNet",​ and anybody who doesn'​t have their own rule uses CP437.+Any server belonging to group "​EFNet",​ and anybody who doesn'​t have their own rule uses CP437.  Note the trailing slash is necessary because otherwise "​EFNet"​ would be considered a nickname.
  
     /ENCODING hop ISO-8859-1     /ENCODING hop ISO-8859-1
encoding.txt ยท Last modified: 2014/04/05 16:30 by sgrubnick