Next: , Previous: , Up: Reading a Tosser Configuration File (Areafile)   [Index]


6.5.2.2 AreafileFlags

Syntax:

AreafileFlags flags

Example:

AreafileFlags 8u

There is one big problem with reading echo definitions from tosser configuration files: Those files do not contain all information that can be specified in a manual area configuration. Certain features of MsgEd TE need a flag that has to be set for each area in order to enable that feature. For example, in order to be able to write mails with umlauts, cyrillic characters etc., you must set the 8 flag for each area, designating that high ASCII characters are allowable therin. This is where you use the AreafileFlags keyword.

The flags parameter has the same syntax as the flags parameter of the Fido, Quick and Squish keywords (see Manual Area Definition).

You must specify the AreaFileFlags keyword before the AreaFile keyword which it should apply to. Then, all areas imported from the area files will have the specified flags.

If you want only a few, but not all areas form an areafile to have some flags, you can manually redefine areas with the syntax described in the preceding section. For this to work, the manual redefinition must come after the AreaFile keyword. Vice versa, if you want almost all areas from an areafile to have a certain flag, but want a few exemptions, you should use the AreaFileFlags and AreaFile keywords to import all areas from the areafile with the specific flag set. After that, you can redefine some areas manually without this flag.

Note: Using AreaFileFlags to globally turn on the ‘u’ flag probably won’t hurt you. On the other hand, you should only use AreaFileFlags to globally turn on the ‘8’ flag if you know that the moderators of the echo areas that you are posting in do not forbid 8-bit-codes.


Next: Areafile, Previous: AreaDesc, Up: Reading a Tosser Configuration File (Areafile)   [Index]