diff --git a/cfgs/charset/866_ukr.chs b/cfgs/charset/866_ukr.chs index c92287a..1182856 100755 --- a/cfgs/charset/866_ukr.chs +++ b/cfgs/charset/866_ukr.chs @@ -1,148 +1,148 @@ -; -; %Id: rus_ukr.chs,v 0.2 1999/07/28 porokh Exp $ -; v 0.3 2003/01/20 Liutyi -; -; GoldED charset conversion module -; -; From: Cyrillic DOS (Alt_Codes aka CP866) encoding -; To: Ukrainian RUSCII (RST 2018-91 aka CP1125) encoding -; -0 ; ID number -1 ; version number -; -2 ; level number -; -CP866 ; from set -CP1125 ; to set -; -; replace in from UNICODE char name in CP866 -; CP1125 <-- CP866 -\0 \x80 ; 0x80 CYRILLIC CAPITAL LETTER A -\0 \x81 ; 0x81 CYRILLIC CAPITAL LETTER BE -\0 \x82 ; 0x82 CYRILLIC CAPITAL LETTER VE -\0 \x83 ; 0x83 CYRILLIC CAPITAL LETTER GHE -\0 \x84 ; 0x84 CYRILLIC CAPITAL LETTER DE -\0 \x85 ; 0x85 CYRILLIC CAPITAL LETTER IE -\0 \x86 ; 0x86 CYRILLIC CAPITAL LETTER ZHE -\0 \x87 ; 0x87 CYRILLIC CAPITAL LETTER ZE -\0 \x88 ; 0x88 CYRILLIC CAPITAL LETTER I -\0 \x89 ; 0x89 CYRILLIC CAPITAL LETTER SHORT I -\0 \x8a ; 0x8a CYRILLIC CAPITAL LETTER KA -\0 \x8b ; 0x8b CYRILLIC CAPITAL LETTER EL -\0 \x8c ; 0x8c CYRILLIC CAPITAL LETTER EM -\0 \x8d ; 0x8d CYRILLIC CAPITAL LETTER EN -\0 \x8e ; 0x8e CYRILLIC CAPITAL LETTER O -\0 \x8f ; 0x8f CYRILLIC CAPITAL LETTER PE -\0 \x90 ; 0x90 CYRILLIC CAPITAL LETTER ER -\0 \x91 ; 0x91 CYRILLIC CAPITAL LETTER ES -\0 \x92 ; 0x92 CYRILLIC CAPITAL LETTER TE -\0 \x93 ; 0x93 CYRILLIC CAPITAL LETTER U -\0 \x94 ; 0x94 CYRILLIC CAPITAL LETTER EF -\0 \x95 ; 0x95 CYRILLIC CAPITAL LETTER HA -\0 \x96 ; 0x96 CYRILLIC CAPITAL LETTER TSE -\0 \x97 ; 0x97 CYRILLIC CAPITAL LETTER CHE -\0 \x98 ; 0x98 CYRILLIC CAPITAL LETTER SHA -\0 \x99 ; 0x99 CYRILLIC CAPITAL LETTER SHCHA -\0 \x9a ; 0x9a CYRILLIC CAPITAL LETTER HARD SIGN -\0 \x9b ; 0x9b CYRILLIC CAPITAL LETTER YERU -\0 \x9c ; 0x9c CYRILLIC CAPITAL LETTER SOFT SIGN -\0 \x9d ; 0x9d CYRILLIC CAPITAL LETTER E -\0 \x9e ; 0x9e CYRILLIC CAPITAL LETTER YU -\0 \x9f ; 0x9f CYRILLIC CAPITAL LETTER YA -\0 \xa0 ; 0xa0 CYRILLIC SMALL LETTER A -\0 \xa1 ; 0xa1 CYRILLIC SMALL LETTER BE -\0 \xa2 ; 0xa2 CYRILLIC SMALL LETTER VE -\0 \xa3 ; 0xa3 CYRILLIC SMALL LETTER GHE -\0 \xa4 ; 0xa4 CYRILLIC SMALL LETTER DE -\0 \xa5 ; 0xa5 CYRILLIC SMALL LETTER IE -\0 \xa6 ; 0xa6 CYRILLIC SMALL LETTER ZHE -\0 \xa7 ; 0xa7 CYRILLIC SMALL LETTER ZE -\0 \xa8 ; 0xa8 CYRILLIC SMALL LETTER I -\0 \xa9 ; 0xa9 CYRILLIC SMALL LETTER SHORT I -\0 \xaa ; 0xaa CYRILLIC SMALL LETTER KA -\0 \xab ; 0xab CYRILLIC SMALL LETTER EL -\0 \xac ; 0xac CYRILLIC SMALL LETTER EM -\0 \xad ; 0xad CYRILLIC SMALL LETTER EN -\0 \xae ; 0xae CYRILLIC SMALL LETTER O -\0 \xaf ; 0xaf CYRILLIC SMALL LETTER PE -\0 \xb0 ; 0xb0 LIGHT SHADE -\0 \xb1 ; 0xb1 MEDIUM SHADE -\0 \xb2 ; 0xb2 DARK SHADE -\0 \xb3 ; 0xb3 BOX DRAWINGS LIGHT VERTICAL -\0 \xb4 ; 0xb4 BOX DRAWINGS LIGHT VERTICAL AND LEFT -\0 \xb5 ; 0xb5 BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE -\0 \xb6 ; 0xb6 BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE -\0 \xb7 ; 0xb7 BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE -\0 \xb8 ; 0xb8 BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE -\0 \xb9 ; 0xb9 BOX DRAWINGS DOUBLE VERTICAL AND LEFT -\0 \xba ; 0xba BOX DRAWINGS DOUBLE VERTICAL -\0 \xbb ; 0xbb BOX DRAWINGS DOUBLE DOWN AND LEFT -\0 \xbc ; 0xbc BOX DRAWINGS DOUBLE UP AND LEFT -\0 \xbd ; 0xbd BOX DRAWINGS UP DOUBLE AND LEFT SINGLE -\0 \xbe ; 0xbe BOX DRAWINGS UP SINGLE AND LEFT DOUBLE -\0 \xbf ; 0xbf BOX DRAWINGS LIGHT DOWN AND LEFT -\0 \xc0 ; 0xc0 BOX DRAWINGS LIGHT UP AND RIGHT -\0 \xc1 ; 0xc1 BOX DRAWINGS LIGHT UP AND HORIZONTAL -\0 \xc2 ; 0xc2 BOX DRAWINGS LIGHT DOWN AND HORIZONTAL -\0 \xc3 ; 0xc3 BOX DRAWINGS LIGHT VERTICAL AND RIGHT -\0 \xc4 ; 0xc4 BOX DRAWINGS LIGHT HORIZONTAL -\0 \xc5 ; 0xc5 BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL -\0 \xc6 ; 0xc6 BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE -\0 \xc7 ; 0xc7 BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE -\0 \xc8 ; 0xc8 BOX DRAWINGS DOUBLE UP AND RIGHT -\0 \xc9 ; 0xc9 BOX DRAWINGS DOUBLE DOWN AND RIGHT -\0 \xca ; 0xca BOX DRAWINGS DOUBLE UP AND HORIZONTAL -\0 \xcb ; 0xcb BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL -\0 \xcc ; 0xcc BOX DRAWINGS DOUBLE VERTICAL AND RIGHT -\0 \xcd ; 0xcd BOX DRAWINGS DOUBLE HORIZONTAL -\0 \xce ; 0xce BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL -\0 \xcf ; 0xcf BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE -\0 \xd0 ; 0xd0 BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE -\0 \xd1 ; 0xd1 BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE -\0 \xd2 ; 0xd2 BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE -\0 \xd3 ; 0xd3 BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE -\0 \xd4 ; 0xd4 BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE -\0 \xd5 ; 0xd5 BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE -\0 \xd6 ; 0xd6 BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE -\0 \xd7 ; 0xd7 BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE -\0 \xd8 ; 0xd8 BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE -\0 \xd9 ; 0xd9 BOX DRAWINGS LIGHT UP AND LEFT -\0 \xda ; 0xda BOX DRAWINGS LIGHT DOWN AND RIGHT -\0 \xdb ; 0xdb FULL BLOCK -\0 \xdc ; 0xdc LOWER HALF BLOCK -\0 \xdd ; 0xdd LEFT HALF BLOCK -\0 \xde ; 0xde RIGHT HALF BLOCK -\0 \xdf ; 0xdf UPPER HALF BLOCK -\0 \xe0 ; 0xe0 CYRILLIC SMALL LETTER ER -\0 \xe1 ; 0xe1 CYRILLIC SMALL LETTER ES -\0 \xe2 ; 0xe2 CYRILLIC SMALL LETTER TE -\0 \xe3 ; 0xe3 CYRILLIC SMALL LETTER U -\0 \xe4 ; 0xe4 CYRILLIC SMALL LETTER EF -\0 \xe5 ; 0xe5 CYRILLIC SMALL LETTER HA -\0 \xe6 ; 0xe6 CYRILLIC SMALL LETTER TSE -\0 \xe7 ; 0xe7 CYRILLIC SMALL LETTER CHE -\0 \xe8 ; 0xe8 CYRILLIC SMALL LETTER SHA -\0 \xe9 ; 0xe9 CYRILLIC SMALL LETTER SHCHA -\0 \xea ; 0xea CYRILLIC SMALL LETTER HARD SIGN -\0 \xeb ; 0xeb CYRILLIC SMALL LETTER YERU -\0 \xec ; 0xec CYRILLIC SMALL LETTER SOFT SIGN -\0 \xed ; 0xed CYRILLIC SMALL LETTER E -\0 \xee ; 0xee CYRILLIC SMALL LETTER YU -\0 \xef ; 0xef CYRILLIC SMALL LETTER YA -\0 \xf0 ; 0xf0 CYRILLIC CAPITAL LETTER IO -\0 \xf1 ; 0xf1 CYRILLIC SMALL LETTER IO -\0 \xf4 ; 0xf2 CYRILLIC CAPITAL LETTER UKRAINIAN IE -\0 \xf5 ; 0xf3 CYRILLIC SMALL LETTER UKRAINIAN IE -\0 \xf8 ; 0xf4 CYRILLIC CAPITAL LETTER YI -\0 \xf9 ; 0xf5 CYRILLIC SMALL LETTER YI -\0 \x93 ; 0xf6 CYRILLIC CAPITAL LETTER SHORT U -\0 \xe3 ; 0xf7 CYRILLIC SMALL LETTER SHORT U -\0 \x6f ; 0xf8 DEGREE SIGN -\0 \x2a ; 0xf9 BULLET OPERATOR -\0 \xfa ; 0xfa MIDDLE DOT -\0 \xfb ; 0xfb SQUARE ROOT -\0 \xfc ; 0xfc NUMERO SIGN -\0 \xfd ; 0xfd CURRENCY SIGN -\0 \xfe ; 0xfe BLACK SQUARE -\0 \xff ; 0xff NO-BREAK SPACE -END +; +; %Id: rus_ukr.chs,v 0.2 1999/07/28 porokh Exp $ +; v 0.3 2003/01/20 Liutyi +; +; GoldED charset conversion module +; +; From: Cyrillic DOS (Alt_Codes aka CP866) encoding +; To: Ukrainian RUSCII (RST 2018-91 aka CP1125) encoding +; +0 ; ID number +1 ; version number +; +2 ; level number +; +CP866 ; from set +CP1125 ; to set +; +; replace in from UNICODE char name in CP866 +; CP1125 <-- CP866 +\0 \x80 ; 0x80 CYRILLIC CAPITAL LETTER A +\0 \x81 ; 0x81 CYRILLIC CAPITAL LETTER BE +\0 \x82 ; 0x82 CYRILLIC CAPITAL LETTER VE +\0 \x83 ; 0x83 CYRILLIC CAPITAL LETTER GHE +\0 \x84 ; 0x84 CYRILLIC CAPITAL LETTER DE +\0 \x85 ; 0x85 CYRILLIC CAPITAL LETTER IE +\0 \x86 ; 0x86 CYRILLIC CAPITAL LETTER ZHE +\0 \x87 ; 0x87 CYRILLIC CAPITAL LETTER ZE +\0 \x88 ; 0x88 CYRILLIC CAPITAL LETTER I +\0 \x89 ; 0x89 CYRILLIC CAPITAL LETTER SHORT I +\0 \x8a ; 0x8a CYRILLIC CAPITAL LETTER KA +\0 \x8b ; 0x8b CYRILLIC CAPITAL LETTER EL +\0 \x8c ; 0x8c CYRILLIC CAPITAL LETTER EM +\0 \x8d ; 0x8d CYRILLIC CAPITAL LETTER EN +\0 \x8e ; 0x8e CYRILLIC CAPITAL LETTER O +\0 \x8f ; 0x8f CYRILLIC CAPITAL LETTER PE +\0 \x90 ; 0x90 CYRILLIC CAPITAL LETTER ER +\0 \x91 ; 0x91 CYRILLIC CAPITAL LETTER ES +\0 \x92 ; 0x92 CYRILLIC CAPITAL LETTER TE +\0 \x93 ; 0x93 CYRILLIC CAPITAL LETTER U +\0 \x94 ; 0x94 CYRILLIC CAPITAL LETTER EF +\0 \x95 ; 0x95 CYRILLIC CAPITAL LETTER HA +\0 \x96 ; 0x96 CYRILLIC CAPITAL LETTER TSE +\0 \x97 ; 0x97 CYRILLIC CAPITAL LETTER CHE +\0 \x98 ; 0x98 CYRILLIC CAPITAL LETTER SHA +\0 \x99 ; 0x99 CYRILLIC CAPITAL LETTER SHCHA +\0 \x9a ; 0x9a CYRILLIC CAPITAL LETTER HARD SIGN +\0 \x9b ; 0x9b CYRILLIC CAPITAL LETTER YERU +\0 \x9c ; 0x9c CYRILLIC CAPITAL LETTER SOFT SIGN +\0 \x9d ; 0x9d CYRILLIC CAPITAL LETTER E +\0 \x9e ; 0x9e CYRILLIC CAPITAL LETTER YU +\0 \x9f ; 0x9f CYRILLIC CAPITAL LETTER YA +\0 \xa0 ; 0xa0 CYRILLIC SMALL LETTER A +\0 \xa1 ; 0xa1 CYRILLIC SMALL LETTER BE +\0 \xa2 ; 0xa2 CYRILLIC SMALL LETTER VE +\0 \xa3 ; 0xa3 CYRILLIC SMALL LETTER GHE +\0 \xa4 ; 0xa4 CYRILLIC SMALL LETTER DE +\0 \xa5 ; 0xa5 CYRILLIC SMALL LETTER IE +\0 \xa6 ; 0xa6 CYRILLIC SMALL LETTER ZHE +\0 \xa7 ; 0xa7 CYRILLIC SMALL LETTER ZE +\0 \xa8 ; 0xa8 CYRILLIC SMALL LETTER I +\0 \xa9 ; 0xa9 CYRILLIC SMALL LETTER SHORT I +\0 \xaa ; 0xaa CYRILLIC SMALL LETTER KA +\0 \xab ; 0xab CYRILLIC SMALL LETTER EL +\0 \xac ; 0xac CYRILLIC SMALL LETTER EM +\0 \xad ; 0xad CYRILLIC SMALL LETTER EN +\0 \xae ; 0xae CYRILLIC SMALL LETTER O +\0 \xaf ; 0xaf CYRILLIC SMALL LETTER PE +\0 \xb0 ; 0xb0 LIGHT SHADE +\0 \xb1 ; 0xb1 MEDIUM SHADE +\0 \xb2 ; 0xb2 DARK SHADE +\0 \xb3 ; 0xb3 BOX DRAWINGS LIGHT VERTICAL +\0 \xb4 ; 0xb4 BOX DRAWINGS LIGHT VERTICAL AND LEFT +\0 \xb5 ; 0xb5 BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE +\0 \xb6 ; 0xb6 BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE +\0 \xb7 ; 0xb7 BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE +\0 \xb8 ; 0xb8 BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE +\0 \xb9 ; 0xb9 BOX DRAWINGS DOUBLE VERTICAL AND LEFT +\0 \xba ; 0xba BOX DRAWINGS DOUBLE VERTICAL +\0 \xbb ; 0xbb BOX DRAWINGS DOUBLE DOWN AND LEFT +\0 \xbc ; 0xbc BOX DRAWINGS DOUBLE UP AND LEFT +\0 \xbd ; 0xbd BOX DRAWINGS UP DOUBLE AND LEFT SINGLE +\0 \xbe ; 0xbe BOX DRAWINGS UP SINGLE AND LEFT DOUBLE +\0 \xbf ; 0xbf BOX DRAWINGS LIGHT DOWN AND LEFT +\0 \xc0 ; 0xc0 BOX DRAWINGS LIGHT UP AND RIGHT +\0 \xc1 ; 0xc1 BOX DRAWINGS LIGHT UP AND HORIZONTAL +\0 \xc2 ; 0xc2 BOX DRAWINGS LIGHT DOWN AND HORIZONTAL +\0 \xc3 ; 0xc3 BOX DRAWINGS LIGHT VERTICAL AND RIGHT +\0 \xc4 ; 0xc4 BOX DRAWINGS LIGHT HORIZONTAL +\0 \xc5 ; 0xc5 BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL +\0 \xc6 ; 0xc6 BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE +\0 \xc7 ; 0xc7 BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE +\0 \xc8 ; 0xc8 BOX DRAWINGS DOUBLE UP AND RIGHT +\0 \xc9 ; 0xc9 BOX DRAWINGS DOUBLE DOWN AND RIGHT +\0 \xca ; 0xca BOX DRAWINGS DOUBLE UP AND HORIZONTAL +\0 \xcb ; 0xcb BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL +\0 \xcc ; 0xcc BOX DRAWINGS DOUBLE VERTICAL AND RIGHT +\0 \xcd ; 0xcd BOX DRAWINGS DOUBLE HORIZONTAL +\0 \xce ; 0xce BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL +\0 \xcf ; 0xcf BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE +\0 \xd0 ; 0xd0 BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE +\0 \xd1 ; 0xd1 BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE +\0 \xd2 ; 0xd2 BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE +\0 \xd3 ; 0xd3 BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE +\0 \xd4 ; 0xd4 BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE +\0 \xd5 ; 0xd5 BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE +\0 \xd6 ; 0xd6 BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE +\0 \xd7 ; 0xd7 BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE +\0 \xd8 ; 0xd8 BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE +\0 \xd9 ; 0xd9 BOX DRAWINGS LIGHT UP AND LEFT +\0 \xda ; 0xda BOX DRAWINGS LIGHT DOWN AND RIGHT +\0 \xdb ; 0xdb FULL BLOCK +\0 \xdc ; 0xdc LOWER HALF BLOCK +\0 \xdd ; 0xdd LEFT HALF BLOCK +\0 \xde ; 0xde RIGHT HALF BLOCK +\0 \xdf ; 0xdf UPPER HALF BLOCK +\0 \xe0 ; 0xe0 CYRILLIC SMALL LETTER ER +\0 \xe1 ; 0xe1 CYRILLIC SMALL LETTER ES +\0 \xe2 ; 0xe2 CYRILLIC SMALL LETTER TE +\0 \xe3 ; 0xe3 CYRILLIC SMALL LETTER U +\0 \xe4 ; 0xe4 CYRILLIC SMALL LETTER EF +\0 \xe5 ; 0xe5 CYRILLIC SMALL LETTER HA +\0 \xe6 ; 0xe6 CYRILLIC SMALL LETTER TSE +\0 \xe7 ; 0xe7 CYRILLIC SMALL LETTER CHE +\0 \xe8 ; 0xe8 CYRILLIC SMALL LETTER SHA +\0 \xe9 ; 0xe9 CYRILLIC SMALL LETTER SHCHA +\0 \xea ; 0xea CYRILLIC SMALL LETTER HARD SIGN +\0 \xeb ; 0xeb CYRILLIC SMALL LETTER YERU +\0 \xec ; 0xec CYRILLIC SMALL LETTER SOFT SIGN +\0 \xed ; 0xed CYRILLIC SMALL LETTER E +\0 \xee ; 0xee CYRILLIC SMALL LETTER YU +\0 \xef ; 0xef CYRILLIC SMALL LETTER YA +\0 \xf0 ; 0xf0 CYRILLIC CAPITAL LETTER IO +\0 \xf1 ; 0xf1 CYRILLIC SMALL LETTER IO +\0 \xf4 ; 0xf2 CYRILLIC CAPITAL LETTER UKRAINIAN IE +\0 \xf5 ; 0xf3 CYRILLIC SMALL LETTER UKRAINIAN IE +\0 \xf8 ; 0xf4 CYRILLIC CAPITAL LETTER YI +\0 \xf9 ; 0xf5 CYRILLIC SMALL LETTER YI +\0 \x93 ; 0xf6 CYRILLIC CAPITAL LETTER SHORT U +\0 \xe3 ; 0xf7 CYRILLIC SMALL LETTER SHORT U +\0 \x6f ; 0xf8 DEGREE SIGN +\0 \x2a ; 0xf9 BULLET OPERATOR +\0 \xfa ; 0xfa MIDDLE DOT +\0 \xfb ; 0xfb SQUARE ROOT +\0 \xfc ; 0xfc NUMERO SIGN +\0 \xfd ; 0xfd CURRENCY SIGN +\0 \xfe ; 0xfe BLACK SQUARE +\0 \xff ; 0xff NO-BREAK SPACE +END diff --git a/cfgs/charset/ukr_866.chs b/cfgs/charset/ukr_866.chs index f367787..8a47ee1 100755 --- a/cfgs/charset/ukr_866.chs +++ b/cfgs/charset/ukr_866.chs @@ -1,148 +1,148 @@ -; -; %Id: ukr_rus.chs,v 0.2 1999/08/31 porokh Exp $ -; v 0.3 2003/01/20 Liutyi -; -; GoldED charset conversion module -; -; From: DOS Ukrainian (RUSCII aka RST 2018-91 aka CP1125) encoding -; To: DOS Cyrillic (Alt_Codes aka CP866) encoding -; -0 ; ID number -1 ; version number -; -2 ; level number -; -CP1125 ; from set (your local charset name) -CP866 ; to set (transport charset name, will appear in ^aCHRS) -; -; replace in from UNICODE char name in CP1125 -; CP866 <-- CP1125 -\0 \x80 ; 0x80 CYRILLIC CAPITAL LETTER A -\0 \x81 ; 0x81 CYRILLIC CAPITAL LETTER BE -\0 \x82 ; 0x82 CYRILLIC CAPITAL LETTER VE -\0 \x83 ; 0x83 CYRILLIC CAPITAL LETTER GHE -\0 \x84 ; 0x84 CYRILLIC CAPITAL LETTER DE -\0 \x85 ; 0x85 CYRILLIC CAPITAL LETTER IE -\0 \x86 ; 0x86 CYRILLIC CAPITAL LETTER ZHE -\0 \x87 ; 0x87 CYRILLIC CAPITAL LETTER ZE -\0 \x88 ; 0x88 CYRILLIC CAPITAL LETTER I -\0 \x89 ; 0x89 CYRILLIC CAPITAL LETTER SHORT I -\0 \x8a ; 0x8a CYRILLIC CAPITAL LETTER KA -\0 \x8b ; 0x8b CYRILLIC CAPITAL LETTER EL -\0 \x8c ; 0x8c CYRILLIC CAPITAL LETTER EM -\0 \x8d ; 0x8d CYRILLIC CAPITAL LETTER EN -\0 \x8e ; 0x8e CYRILLIC CAPITAL LETTER O -\0 \x8f ; 0x8f CYRILLIC CAPITAL LETTER PE -\0 \x90 ; 0x90 CYRILLIC CAPITAL LETTER ER -\0 \x91 ; 0x91 CYRILLIC CAPITAL LETTER ES -\0 \x92 ; 0x92 CYRILLIC CAPITAL LETTER TE -\0 \x93 ; 0x93 CYRILLIC CAPITAL LETTER U -\0 \x94 ; 0x94 CYRILLIC CAPITAL LETTER EF -\0 \x95 ; 0x95 CYRILLIC CAPITAL LETTER HA -\0 \x96 ; 0x96 CYRILLIC CAPITAL LETTER TSE -\0 \x97 ; 0x97 CYRILLIC CAPITAL LETTER CHE -\0 \x98 ; 0x98 CYRILLIC CAPITAL LETTER SHA -\0 \x99 ; 0x99 CYRILLIC CAPITAL LETTER SHCHA -\0 \x9a ; 0x9a CYRILLIC CAPITAL LETTER HARD SIGN -\0 \x9b ; 0x9b CYRILLIC CAPITAL LETTER YERU -\0 \x9c ; 0x9c CYRILLIC CAPITAL LETTER SOFT SIGN -\0 \x9d ; 0x9d CYRILLIC CAPITAL LETTER E -\0 \x9e ; 0x9e CYRILLIC CAPITAL LETTER YU -\0 \x9f ; 0x9f CYRILLIC CAPITAL LETTER YA -\0 \xa0 ; 0xa0 CYRILLIC SMALL LETTER A -\0 \xa1 ; 0xa1 CYRILLIC SMALL LETTER BE -\0 \xa2 ; 0xa2 CYRILLIC SMALL LETTER VE -\0 \xa3 ; 0xa3 CYRILLIC SMALL LETTER GHE -\0 \xa4 ; 0xa4 CYRILLIC SMALL LETTER DE -\0 \xa5 ; 0xa5 CYRILLIC SMALL LETTER IE -\0 \xa6 ; 0xa6 CYRILLIC SMALL LETTER ZHE -\0 \xa7 ; 0xa7 CYRILLIC SMALL LETTER ZE -\0 \xa8 ; 0xa8 CYRILLIC SMALL LETTER I -\0 \xa9 ; 0xa9 CYRILLIC SMALL LETTER SHORT I -\0 \xaa ; 0xaa CYRILLIC SMALL LETTER KA -\0 \xab ; 0xab CYRILLIC SMALL LETTER EL -\0 \xac ; 0xac CYRILLIC SMALL LETTER EM -\0 \xad ; 0xad CYRILLIC SMALL LETTER EN -\0 \xae ; 0xae CYRILLIC SMALL LETTER O -\0 \xaf ; 0xaf CYRILLIC SMALL LETTER PE -\0 \xb0 ; 0xb0 LIGHT SHADE -\0 \xb1 ; 0xb1 MEDIUM SHADE -\0 \xb2 ; 0xb2 DARK SHADE -\0 \xb3 ; 0xb3 BOX DRAWINGS LIGHT VERTICAL -\0 \xb4 ; 0xb4 BOX DRAWINGS LIGHT VERTICAL AND LEFT -\0 \xb5 ; 0xb5 BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE -\0 \xb6 ; 0xb6 BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE -\0 \xb7 ; 0xb7 BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE -\0 \xb8 ; 0xb8 BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE -\0 \xb9 ; 0xb9 BOX DRAWINGS DOUBLE VERTICAL AND LEFT -\0 \xba ; 0xba BOX DRAWINGS DOUBLE VERTICAL -\0 \xbb ; 0xbb BOX DRAWINGS DOUBLE DOWN AND LEFT -\0 \xbc ; 0xbc BOX DRAWINGS DOUBLE UP AND LEFT -\0 \xbd ; 0xbd BOX DRAWINGS UP DOUBLE AND LEFT SINGLE -\0 \xbe ; 0xbe BOX DRAWINGS UP SINGLE AND LEFT DOUBLE -\0 \xbf ; 0xbf BOX DRAWINGS LIGHT DOWN AND LEFT -\0 \xc0 ; 0xc0 BOX DRAWINGS LIGHT UP AND RIGHT -\0 \xc1 ; 0xc1 BOX DRAWINGS LIGHT UP AND HORIZONTAL -\0 \xc2 ; 0xc2 BOX DRAWINGS LIGHT DOWN AND HORIZONTAL -\0 \xc3 ; 0xc3 BOX DRAWINGS LIGHT VERTICAL AND RIGHT -\0 \xc4 ; 0xc4 BOX DRAWINGS LIGHT HORIZONTAL -\0 \xc5 ; 0xc5 BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL -\0 \xc6 ; 0xc6 BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE -\0 \xc7 ; 0xc7 BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE -\0 \xc8 ; 0xc8 BOX DRAWINGS DOUBLE UP AND RIGHT -\0 \xc9 ; 0xc9 BOX DRAWINGS DOUBLE DOWN AND RIGHT -\0 \xca ; 0xca BOX DRAWINGS DOUBLE UP AND HORIZONTAL -\0 \xcb ; 0xcb BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL -\0 \xcc ; 0xcc BOX DRAWINGS DOUBLE VERTICAL AND RIGHT -\0 \xcd ; 0xcd BOX DRAWINGS DOUBLE HORIZONTAL -\0 \xce ; 0xce BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL -\0 \xcf ; 0xcf BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE -\0 \xd0 ; 0xd0 BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE -\0 \xd1 ; 0xd1 BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE -\0 \xd2 ; 0xd2 BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE -\0 \xd3 ; 0xd3 BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE -\0 \xd4 ; 0xd4 BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE -\0 \xd5 ; 0xd5 BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE -\0 \xd6 ; 0xd6 BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE -\0 \xd7 ; 0xd7 BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE -\0 \xd8 ; 0xd8 BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE -\0 \xd9 ; 0xd9 BOX DRAWINGS LIGHT UP AND LEFT -\0 \xda ; 0xda BOX DRAWINGS LIGHT DOWN AND RIGHT -\0 \xdb ; 0xdb FULL BLOCK -\0 \xdc ; 0xdc LOWER HALF BLOCK -\0 \xdd ; 0xdd LEFT HALF BLOCK -\0 \xde ; 0xde RIGHT HALF BLOCK -\0 \xdf ; 0xdf UPPER HALF BLOCK -\0 \xe0 ; 0xe0 CYRILLIC SMALL LETTER ER -\0 \xe1 ; 0xe1 CYRILLIC SMALL LETTER ES -\0 \xe2 ; 0xe2 CYRILLIC SMALL LETTER TE -\0 \xe3 ; 0xe3 CYRILLIC SMALL LETTER U -\0 \xe4 ; 0xe4 CYRILLIC SMALL LETTER EF -\0 \xe5 ; 0xe5 CYRILLIC SMALL LETTER HA -\0 \xe6 ; 0xe6 CYRILLIC SMALL LETTER TSE -\0 \xe7 ; 0xe7 CYRILLIC SMALL LETTER CHE -\0 \xe8 ; 0xe8 CYRILLIC SMALL LETTER SHA -\0 \xe9 ; 0xe9 CYRILLIC SMALL LETTER SHCHA -\0 \xea ; 0xea CYRILLIC SMALL LETTER HARD SIGN -\0 \xeb ; 0xeb CYRILLIC SMALL LETTER YERU -\0 \xec ; 0xec CYRILLIC SMALL LETTER SOFT SIGN -\0 \xed ; 0xed CYRILLIC SMALL LETTER E -\0 \xee ; 0xee CYRILLIC SMALL LETTER YU -\0 \xef ; 0xef CYRILLIC SMALL LETTER YA -\0 \xf0 ; 0xf0 CYRILLIC CAPITAL LETTER IO -\0 \xf1 ; 0xf1 CYRILLIC SMALL LETTER IO -\0 \x83 ; 0xf2 CYRILLIC CAPITAL LETTER GHE WITH UPTURN -\0 \xa3 ; 0xf3 CYRILLIC SMALL LETTER GHE WITH UPTURN -\0 \xf2 ; 0xf4 CYRILLIC CAPITAL LETTER UKRAINIAN IE -\0 \xf3 ; 0xf5 CYRILLIC SMALL LETTER UKRAINIAN IE -\0 \x49 ; 0xf6 CYRILLIC CAPITAL LETTER BYELORUSSIAN-UKRAINIAN I -\0 \x69 ; 0xf7 CYRILLIC SMALL LETTER BYELORUSSIAN-UKRAINIAN I -\0 \xf4 ; 0xf8 CYRILLIC CAPITAL LETTER YI -\0 \xf5 ; 0xf9 CYRILLIC SMALL LETTER YI -\0 \xfa ; 0xfa MIDDLE DOT -\0 \xfb ; 0xfb SQUARE ROOT -\0 \xfc ; 0xfc NUMERO SIGN -\0 \xfd ; 0xfd CURRENCY SIGN -\0 \xfe ; 0xfe BLACK SQUARE -\0 \xff ; 0xff NO-BREAK SPACE -END +; +; %Id: ukr_rus.chs,v 0.2 1999/08/31 porokh Exp $ +; v 0.3 2003/01/20 Liutyi +; +; GoldED charset conversion module +; +; From: DOS Ukrainian (RUSCII aka RST 2018-91 aka CP1125) encoding +; To: DOS Cyrillic (Alt_Codes aka CP866) encoding +; +0 ; ID number +1 ; version number +; +2 ; level number +; +CP1125 ; from set (your local charset name) +CP866 ; to set (transport charset name, will appear in ^aCHRS) +; +; replace in from UNICODE char name in CP1125 +; CP866 <-- CP1125 +\0 \x80 ; 0x80 CYRILLIC CAPITAL LETTER A +\0 \x81 ; 0x81 CYRILLIC CAPITAL LETTER BE +\0 \x82 ; 0x82 CYRILLIC CAPITAL LETTER VE +\0 \x83 ; 0x83 CYRILLIC CAPITAL LETTER GHE +\0 \x84 ; 0x84 CYRILLIC CAPITAL LETTER DE +\0 \x85 ; 0x85 CYRILLIC CAPITAL LETTER IE +\0 \x86 ; 0x86 CYRILLIC CAPITAL LETTER ZHE +\0 \x87 ; 0x87 CYRILLIC CAPITAL LETTER ZE +\0 \x88 ; 0x88 CYRILLIC CAPITAL LETTER I +\0 \x89 ; 0x89 CYRILLIC CAPITAL LETTER SHORT I +\0 \x8a ; 0x8a CYRILLIC CAPITAL LETTER KA +\0 \x8b ; 0x8b CYRILLIC CAPITAL LETTER EL +\0 \x8c ; 0x8c CYRILLIC CAPITAL LETTER EM +\0 \x8d ; 0x8d CYRILLIC CAPITAL LETTER EN +\0 \x8e ; 0x8e CYRILLIC CAPITAL LETTER O +\0 \x8f ; 0x8f CYRILLIC CAPITAL LETTER PE +\0 \x90 ; 0x90 CYRILLIC CAPITAL LETTER ER +\0 \x91 ; 0x91 CYRILLIC CAPITAL LETTER ES +\0 \x92 ; 0x92 CYRILLIC CAPITAL LETTER TE +\0 \x93 ; 0x93 CYRILLIC CAPITAL LETTER U +\0 \x94 ; 0x94 CYRILLIC CAPITAL LETTER EF +\0 \x95 ; 0x95 CYRILLIC CAPITAL LETTER HA +\0 \x96 ; 0x96 CYRILLIC CAPITAL LETTER TSE +\0 \x97 ; 0x97 CYRILLIC CAPITAL LETTER CHE +\0 \x98 ; 0x98 CYRILLIC CAPITAL LETTER SHA +\0 \x99 ; 0x99 CYRILLIC CAPITAL LETTER SHCHA +\0 \x9a ; 0x9a CYRILLIC CAPITAL LETTER HARD SIGN +\0 \x9b ; 0x9b CYRILLIC CAPITAL LETTER YERU +\0 \x9c ; 0x9c CYRILLIC CAPITAL LETTER SOFT SIGN +\0 \x9d ; 0x9d CYRILLIC CAPITAL LETTER E +\0 \x9e ; 0x9e CYRILLIC CAPITAL LETTER YU +\0 \x9f ; 0x9f CYRILLIC CAPITAL LETTER YA +\0 \xa0 ; 0xa0 CYRILLIC SMALL LETTER A +\0 \xa1 ; 0xa1 CYRILLIC SMALL LETTER BE +\0 \xa2 ; 0xa2 CYRILLIC SMALL LETTER VE +\0 \xa3 ; 0xa3 CYRILLIC SMALL LETTER GHE +\0 \xa4 ; 0xa4 CYRILLIC SMALL LETTER DE +\0 \xa5 ; 0xa5 CYRILLIC SMALL LETTER IE +\0 \xa6 ; 0xa6 CYRILLIC SMALL LETTER ZHE +\0 \xa7 ; 0xa7 CYRILLIC SMALL LETTER ZE +\0 \xa8 ; 0xa8 CYRILLIC SMALL LETTER I +\0 \xa9 ; 0xa9 CYRILLIC SMALL LETTER SHORT I +\0 \xaa ; 0xaa CYRILLIC SMALL LETTER KA +\0 \xab ; 0xab CYRILLIC SMALL LETTER EL +\0 \xac ; 0xac CYRILLIC SMALL LETTER EM +\0 \xad ; 0xad CYRILLIC SMALL LETTER EN +\0 \xae ; 0xae CYRILLIC SMALL LETTER O +\0 \xaf ; 0xaf CYRILLIC SMALL LETTER PE +\0 \xb0 ; 0xb0 LIGHT SHADE +\0 \xb1 ; 0xb1 MEDIUM SHADE +\0 \xb2 ; 0xb2 DARK SHADE +\0 \xb3 ; 0xb3 BOX DRAWINGS LIGHT VERTICAL +\0 \xb4 ; 0xb4 BOX DRAWINGS LIGHT VERTICAL AND LEFT +\0 \xb5 ; 0xb5 BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE +\0 \xb6 ; 0xb6 BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE +\0 \xb7 ; 0xb7 BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE +\0 \xb8 ; 0xb8 BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE +\0 \xb9 ; 0xb9 BOX DRAWINGS DOUBLE VERTICAL AND LEFT +\0 \xba ; 0xba BOX DRAWINGS DOUBLE VERTICAL +\0 \xbb ; 0xbb BOX DRAWINGS DOUBLE DOWN AND LEFT +\0 \xbc ; 0xbc BOX DRAWINGS DOUBLE UP AND LEFT +\0 \xbd ; 0xbd BOX DRAWINGS UP DOUBLE AND LEFT SINGLE +\0 \xbe ; 0xbe BOX DRAWINGS UP SINGLE AND LEFT DOUBLE +\0 \xbf ; 0xbf BOX DRAWINGS LIGHT DOWN AND LEFT +\0 \xc0 ; 0xc0 BOX DRAWINGS LIGHT UP AND RIGHT +\0 \xc1 ; 0xc1 BOX DRAWINGS LIGHT UP AND HORIZONTAL +\0 \xc2 ; 0xc2 BOX DRAWINGS LIGHT DOWN AND HORIZONTAL +\0 \xc3 ; 0xc3 BOX DRAWINGS LIGHT VERTICAL AND RIGHT +\0 \xc4 ; 0xc4 BOX DRAWINGS LIGHT HORIZONTAL +\0 \xc5 ; 0xc5 BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL +\0 \xc6 ; 0xc6 BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE +\0 \xc7 ; 0xc7 BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE +\0 \xc8 ; 0xc8 BOX DRAWINGS DOUBLE UP AND RIGHT +\0 \xc9 ; 0xc9 BOX DRAWINGS DOUBLE DOWN AND RIGHT +\0 \xca ; 0xca BOX DRAWINGS DOUBLE UP AND HORIZONTAL +\0 \xcb ; 0xcb BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL +\0 \xcc ; 0xcc BOX DRAWINGS DOUBLE VERTICAL AND RIGHT +\0 \xcd ; 0xcd BOX DRAWINGS DOUBLE HORIZONTAL +\0 \xce ; 0xce BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL +\0 \xcf ; 0xcf BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE +\0 \xd0 ; 0xd0 BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE +\0 \xd1 ; 0xd1 BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE +\0 \xd2 ; 0xd2 BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE +\0 \xd3 ; 0xd3 BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE +\0 \xd4 ; 0xd4 BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE +\0 \xd5 ; 0xd5 BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE +\0 \xd6 ; 0xd6 BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE +\0 \xd7 ; 0xd7 BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE +\0 \xd8 ; 0xd8 BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE +\0 \xd9 ; 0xd9 BOX DRAWINGS LIGHT UP AND LEFT +\0 \xda ; 0xda BOX DRAWINGS LIGHT DOWN AND RIGHT +\0 \xdb ; 0xdb FULL BLOCK +\0 \xdc ; 0xdc LOWER HALF BLOCK +\0 \xdd ; 0xdd LEFT HALF BLOCK +\0 \xde ; 0xde RIGHT HALF BLOCK +\0 \xdf ; 0xdf UPPER HALF BLOCK +\0 \xe0 ; 0xe0 CYRILLIC SMALL LETTER ER +\0 \xe1 ; 0xe1 CYRILLIC SMALL LETTER ES +\0 \xe2 ; 0xe2 CYRILLIC SMALL LETTER TE +\0 \xe3 ; 0xe3 CYRILLIC SMALL LETTER U +\0 \xe4 ; 0xe4 CYRILLIC SMALL LETTER EF +\0 \xe5 ; 0xe5 CYRILLIC SMALL LETTER HA +\0 \xe6 ; 0xe6 CYRILLIC SMALL LETTER TSE +\0 \xe7 ; 0xe7 CYRILLIC SMALL LETTER CHE +\0 \xe8 ; 0xe8 CYRILLIC SMALL LETTER SHA +\0 \xe9 ; 0xe9 CYRILLIC SMALL LETTER SHCHA +\0 \xea ; 0xea CYRILLIC SMALL LETTER HARD SIGN +\0 \xeb ; 0xeb CYRILLIC SMALL LETTER YERU +\0 \xec ; 0xec CYRILLIC SMALL LETTER SOFT SIGN +\0 \xed ; 0xed CYRILLIC SMALL LETTER E +\0 \xee ; 0xee CYRILLIC SMALL LETTER YU +\0 \xef ; 0xef CYRILLIC SMALL LETTER YA +\0 \xf0 ; 0xf0 CYRILLIC CAPITAL LETTER IO +\0 \xf1 ; 0xf1 CYRILLIC SMALL LETTER IO +\0 \x83 ; 0xf2 CYRILLIC CAPITAL LETTER GHE WITH UPTURN +\0 \xa3 ; 0xf3 CYRILLIC SMALL LETTER GHE WITH UPTURN +\0 \xf2 ; 0xf4 CYRILLIC CAPITAL LETTER UKRAINIAN IE +\0 \xf3 ; 0xf5 CYRILLIC SMALL LETTER UKRAINIAN IE +\0 \x49 ; 0xf6 CYRILLIC CAPITAL LETTER BYELORUSSIAN-UKRAINIAN I +\0 \x69 ; 0xf7 CYRILLIC SMALL LETTER BYELORUSSIAN-UKRAINIAN I +\0 \xf4 ; 0xf8 CYRILLIC CAPITAL LETTER YI +\0 \xf5 ; 0xf9 CYRILLIC SMALL LETTER YI +\0 \xfa ; 0xfa MIDDLE DOT +\0 \xfb ; 0xfb SQUARE ROOT +\0 \xfc ; 0xfc NUMERO SIGN +\0 \xfd ; 0xfd CURRENCY SIGN +\0 \xfe ; 0xfe BLACK SQUARE +\0 \xff ; 0xff NO-BREAK SPACE +END diff --git a/cfgs/charset/ukr_ukr.chs b/cfgs/charset/ukr_ukr.chs index 27a5b22..a44f6be 100755 --- a/cfgs/charset/ukr_ukr.chs +++ b/cfgs/charset/ukr_ukr.chs @@ -1,148 +1,148 @@ -; -; %Id: ukr_ukr.chs,v 0.1 1999/08/26 porokh Exp $ -; 0.3 2003/01/20 Liutyi -; -; GoldED charset conversion module -; -; From: DOS Ukrainian (RUSCII aka RST 2018-91 aka CP1125) encoding -; To: DOS Ukrainian (... aka CP1125) encoding without any replacing -; -0 ; ID number -1 ; version number -; -2 ; level number -; -CP1125 ; from set (your local charset name) -CP1125 ; to set (transport charset name, will appear in ^aCHRS) -; -; replace in from UNICODE char name in CP1125 -; CP1125 <-- CP1125 -\0 \x80 ; 0x80 CYRILLIC CAPITAL LETTER A -\0 \x81 ; 0x81 CYRILLIC CAPITAL LETTER BE -\0 \x82 ; 0x82 CYRILLIC CAPITAL LETTER VE -\0 \x83 ; 0x83 CYRILLIC CAPITAL LETTER GHE -\0 \x84 ; 0x84 CYRILLIC CAPITAL LETTER DE -\0 \x85 ; 0x85 CYRILLIC CAPITAL LETTER IE -\0 \x86 ; 0x86 CYRILLIC CAPITAL LETTER ZHE -\0 \x87 ; 0x87 CYRILLIC CAPITAL LETTER ZE -\0 \x88 ; 0x88 CYRILLIC CAPITAL LETTER I -\0 \x89 ; 0x89 CYRILLIC CAPITAL LETTER SHORT I -\0 \x8a ; 0x8a CYRILLIC CAPITAL LETTER KA -\0 \x8b ; 0x8b CYRILLIC CAPITAL LETTER EL -\0 \x8c ; 0x8c CYRILLIC CAPITAL LETTER EM -\0 \x8d ; 0x8d CYRILLIC CAPITAL LETTER EN -\0 \x8e ; 0x8e CYRILLIC CAPITAL LETTER O -\0 \x8f ; 0x8f CYRILLIC CAPITAL LETTER PE -\0 \x90 ; 0x90 CYRILLIC CAPITAL LETTER ER -\0 \x91 ; 0x91 CYRILLIC CAPITAL LETTER ES -\0 \x92 ; 0x92 CYRILLIC CAPITAL LETTER TE -\0 \x93 ; 0x93 CYRILLIC CAPITAL LETTER U -\0 \x94 ; 0x94 CYRILLIC CAPITAL LETTER EF -\0 \x95 ; 0x95 CYRILLIC CAPITAL LETTER HA -\0 \x96 ; 0x96 CYRILLIC CAPITAL LETTER TSE -\0 \x97 ; 0x97 CYRILLIC CAPITAL LETTER CHE -\0 \x98 ; 0x98 CYRILLIC CAPITAL LETTER SHA -\0 \x99 ; 0x99 CYRILLIC CAPITAL LETTER SHCHA -\0 \x9a ; 0x9a CYRILLIC CAPITAL LETTER HARD SIGN -\0 \x9b ; 0x9b CYRILLIC CAPITAL LETTER YERU -\0 \x9c ; 0x9c CYRILLIC CAPITAL LETTER SOFT SIGN -\0 \x9d ; 0x9d CYRILLIC CAPITAL LETTER E -\0 \x9e ; 0x9e CYRILLIC CAPITAL LETTER YU -\0 \x9f ; 0x9f CYRILLIC CAPITAL LETTER YA -\0 \xa0 ; 0xa0 CYRILLIC SMALL LETTER A -\0 \xa1 ; 0xa1 CYRILLIC SMALL LETTER BE -\0 \xa2 ; 0xa2 CYRILLIC SMALL LETTER VE -\0 \xa3 ; 0xa3 CYRILLIC SMALL LETTER GHE -\0 \xa4 ; 0xa4 CYRILLIC SMALL LETTER DE -\0 \xa5 ; 0xa5 CYRILLIC SMALL LETTER IE -\0 \xa6 ; 0xa6 CYRILLIC SMALL LETTER ZHE -\0 \xa7 ; 0xa7 CYRILLIC SMALL LETTER ZE -\0 \xa8 ; 0xa8 CYRILLIC SMALL LETTER I -\0 \xa9 ; 0xa9 CYRILLIC SMALL LETTER SHORT I -\0 \xaa ; 0xaa CYRILLIC SMALL LETTER KA -\0 \xab ; 0xab CYRILLIC SMALL LETTER EL -\0 \xac ; 0xac CYRILLIC SMALL LETTER EM -\0 \xad ; 0xad CYRILLIC SMALL LETTER EN -\0 \xae ; 0xae CYRILLIC SMALL LETTER O -\0 \xaf ; 0xaf CYRILLIC SMALL LETTER PE -\0 \xb0 ; 0xb0 LIGHT SHADE -\0 \xb1 ; 0xb1 MEDIUM SHADE -\0 \xb2 ; 0xb2 DARK SHADE -\0 \xb3 ; 0xb3 BOX DRAWINGS LIGHT VERTICAL -\0 \xb4 ; 0xb4 BOX DRAWINGS LIGHT VERTICAL AND LEFT -\0 \xb5 ; 0xb5 BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE -\0 \xb6 ; 0xb6 BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE -\0 \xb7 ; 0xb7 BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE -\0 \xb8 ; 0xb8 BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE -\0 \xb9 ; 0xb9 BOX DRAWINGS DOUBLE VERTICAL AND LEFT -\0 \xba ; 0xba BOX DRAWINGS DOUBLE VERTICAL -\0 \xbb ; 0xbb BOX DRAWINGS DOUBLE DOWN AND LEFT -\0 \xbc ; 0xbc BOX DRAWINGS DOUBLE UP AND LEFT -\0 \xbd ; 0xbd BOX DRAWINGS UP DOUBLE AND LEFT SINGLE -\0 \xbe ; 0xbe BOX DRAWINGS UP SINGLE AND LEFT DOUBLE -\0 \xbf ; 0xbf BOX DRAWINGS LIGHT DOWN AND LEFT -\0 \xc0 ; 0xc0 BOX DRAWINGS LIGHT UP AND RIGHT -\0 \xc1 ; 0xc1 BOX DRAWINGS LIGHT UP AND HORIZONTAL -\0 \xc2 ; 0xc2 BOX DRAWINGS LIGHT DOWN AND HORIZONTAL -\0 \xc3 ; 0xc3 BOX DRAWINGS LIGHT VERTICAL AND RIGHT -\0 \xc4 ; 0xc4 BOX DRAWINGS LIGHT HORIZONTAL -\0 \xc5 ; 0xc5 BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL -\0 \xc6 ; 0xc6 BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE -\0 \xc7 ; 0xc7 BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE -\0 \xc8 ; 0xc8 BOX DRAWINGS DOUBLE UP AND RIGHT -\0 \xc9 ; 0xc9 BOX DRAWINGS DOUBLE DOWN AND RIGHT -\0 \xca ; 0xca BOX DRAWINGS DOUBLE UP AND HORIZONTAL -\0 \xcb ; 0xcb BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL -\0 \xcc ; 0xcc BOX DRAWINGS DOUBLE VERTICAL AND RIGHT -\0 \xcd ; 0xcd BOX DRAWINGS DOUBLE HORIZONTAL -\0 \xce ; 0xce BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL -\0 \xcf ; 0xcf BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE -\0 \xd0 ; 0xd0 BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE -\0 \xd1 ; 0xd1 BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE -\0 \xd2 ; 0xd2 BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE -\0 \xd3 ; 0xd3 BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE -\0 \xd4 ; 0xd4 BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE -\0 \xd5 ; 0xd5 BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE -\0 \xd6 ; 0xd6 BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE -\0 \xd7 ; 0xd7 BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE -\0 \xd8 ; 0xd8 BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE -\0 \xd9 ; 0xd9 BOX DRAWINGS LIGHT UP AND LEFT -\0 \xda ; 0xda BOX DRAWINGS LIGHT DOWN AND RIGHT -\0 \xdb ; 0xdb FULL BLOCK -\0 \xdc ; 0xdc LOWER HALF BLOCK -\0 \xdd ; 0xdd LEFT HALF BLOCK -\0 \xde ; 0xde RIGHT HALF BLOCK -\0 \xdf ; 0xdf UPPER HALF BLOCK -\0 \xe0 ; 0xe0 CYRILLIC SMALL LETTER ER -\0 \xe1 ; 0xe1 CYRILLIC SMALL LETTER ES -\0 \xe2 ; 0xe2 CYRILLIC SMALL LETTER TE -\0 \xe3 ; 0xe3 CYRILLIC SMALL LETTER U -\0 \xe4 ; 0xe4 CYRILLIC SMALL LETTER EF -\0 \xe5 ; 0xe5 CYRILLIC SMALL LETTER HA -\0 \xe6 ; 0xe6 CYRILLIC SMALL LETTER TSE -\0 \xe7 ; 0xe7 CYRILLIC SMALL LETTER CHE -\0 \xe8 ; 0xe8 CYRILLIC SMALL LETTER SHA -\0 \xe9 ; 0xe9 CYRILLIC SMALL LETTER SHCHA -\0 \xea ; 0xea CYRILLIC SMALL LETTER HARD SIGN -\0 \xeb ; 0xeb CYRILLIC SMALL LETTER YERU -\0 \xec ; 0xec CYRILLIC SMALL LETTER SOFT SIGN -\0 \xed ; 0xed CYRILLIC SMALL LETTER E -\0 \xee ; 0xee CYRILLIC SMALL LETTER YU -\0 \xef ; 0xef CYRILLIC SMALL LETTER YA -\0 \xf0 ; 0xf0 CYRILLIC CAPITAL LETTER IO -\0 \xf1 ; 0xf1 CYRILLIC SMALL LETTER IO -\0 \xf2 ; 0xf2 CYRILLIC CAPITAL LETTER GHE WITH UPTURN -\0 \xf3 ; 0xf3 CYRILLIC SMALL LETTER GHE WITH UPTURN -\0 \xf4 ; 0xf4 CYRILLIC CAPITAL LETTER UKRAINIAN IE -\0 \xf5 ; 0xf5 CYRILLIC SMALL LETTER UKRAINIAN IE -\0 \xf6 ; 0xf6 CYRILLIC CAPITAL LETTER BYELORUSSIAN-UKRAINIAN I -\0 \xf7 ; 0xf7 CYRILLIC SMALL LETTER BYELORUSSIAN-UKRAINIAN I -\0 \xf8 ; 0xf8 CYRILLIC CAPITAL LETTER YI -\0 \xf9 ; 0xf9 CYRILLIC SMALL LETTER YI -\0 \xfa ; 0xfa MIDDLE DOT -\0 \xfb ; 0xfb SQUARE ROOT -\0 \xfc ; 0xfc NUMERO SIGN -\0 \xfd ; 0xfd CURRENCY SIGN -\0 \xfe ; 0xfe BLACK SQUARE -\0 \xff ; 0xff NO-BREAK SPACE -END +; +; %Id: ukr_ukr.chs,v 0.1 1999/08/26 porokh Exp $ +; 0.3 2003/01/20 Liutyi +; +; GoldED charset conversion module +; +; From: DOS Ukrainian (RUSCII aka RST 2018-91 aka CP1125) encoding +; To: DOS Ukrainian (... aka CP1125) encoding without any replacing +; +0 ; ID number +1 ; version number +; +2 ; level number +; +CP1125 ; from set (your local charset name) +CP1125 ; to set (transport charset name, will appear in ^aCHRS) +; +; replace in from UNICODE char name in CP1125 +; CP1125 <-- CP1125 +\0 \x80 ; 0x80 CYRILLIC CAPITAL LETTER A +\0 \x81 ; 0x81 CYRILLIC CAPITAL LETTER BE +\0 \x82 ; 0x82 CYRILLIC CAPITAL LETTER VE +\0 \x83 ; 0x83 CYRILLIC CAPITAL LETTER GHE +\0 \x84 ; 0x84 CYRILLIC CAPITAL LETTER DE +\0 \x85 ; 0x85 CYRILLIC CAPITAL LETTER IE +\0 \x86 ; 0x86 CYRILLIC CAPITAL LETTER ZHE +\0 \x87 ; 0x87 CYRILLIC CAPITAL LETTER ZE +\0 \x88 ; 0x88 CYRILLIC CAPITAL LETTER I +\0 \x89 ; 0x89 CYRILLIC CAPITAL LETTER SHORT I +\0 \x8a ; 0x8a CYRILLIC CAPITAL LETTER KA +\0 \x8b ; 0x8b CYRILLIC CAPITAL LETTER EL +\0 \x8c ; 0x8c CYRILLIC CAPITAL LETTER EM +\0 \x8d ; 0x8d CYRILLIC CAPITAL LETTER EN +\0 \x8e ; 0x8e CYRILLIC CAPITAL LETTER O +\0 \x8f ; 0x8f CYRILLIC CAPITAL LETTER PE +\0 \x90 ; 0x90 CYRILLIC CAPITAL LETTER ER +\0 \x91 ; 0x91 CYRILLIC CAPITAL LETTER ES +\0 \x92 ; 0x92 CYRILLIC CAPITAL LETTER TE +\0 \x93 ; 0x93 CYRILLIC CAPITAL LETTER U +\0 \x94 ; 0x94 CYRILLIC CAPITAL LETTER EF +\0 \x95 ; 0x95 CYRILLIC CAPITAL LETTER HA +\0 \x96 ; 0x96 CYRILLIC CAPITAL LETTER TSE +\0 \x97 ; 0x97 CYRILLIC CAPITAL LETTER CHE +\0 \x98 ; 0x98 CYRILLIC CAPITAL LETTER SHA +\0 \x99 ; 0x99 CYRILLIC CAPITAL LETTER SHCHA +\0 \x9a ; 0x9a CYRILLIC CAPITAL LETTER HARD SIGN +\0 \x9b ; 0x9b CYRILLIC CAPITAL LETTER YERU +\0 \x9c ; 0x9c CYRILLIC CAPITAL LETTER SOFT SIGN +\0 \x9d ; 0x9d CYRILLIC CAPITAL LETTER E +\0 \x9e ; 0x9e CYRILLIC CAPITAL LETTER YU +\0 \x9f ; 0x9f CYRILLIC CAPITAL LETTER YA +\0 \xa0 ; 0xa0 CYRILLIC SMALL LETTER A +\0 \xa1 ; 0xa1 CYRILLIC SMALL LETTER BE +\0 \xa2 ; 0xa2 CYRILLIC SMALL LETTER VE +\0 \xa3 ; 0xa3 CYRILLIC SMALL LETTER GHE +\0 \xa4 ; 0xa4 CYRILLIC SMALL LETTER DE +\0 \xa5 ; 0xa5 CYRILLIC SMALL LETTER IE +\0 \xa6 ; 0xa6 CYRILLIC SMALL LETTER ZHE +\0 \xa7 ; 0xa7 CYRILLIC SMALL LETTER ZE +\0 \xa8 ; 0xa8 CYRILLIC SMALL LETTER I +\0 \xa9 ; 0xa9 CYRILLIC SMALL LETTER SHORT I +\0 \xaa ; 0xaa CYRILLIC SMALL LETTER KA +\0 \xab ; 0xab CYRILLIC SMALL LETTER EL +\0 \xac ; 0xac CYRILLIC SMALL LETTER EM +\0 \xad ; 0xad CYRILLIC SMALL LETTER EN +\0 \xae ; 0xae CYRILLIC SMALL LETTER O +\0 \xaf ; 0xaf CYRILLIC SMALL LETTER PE +\0 \xb0 ; 0xb0 LIGHT SHADE +\0 \xb1 ; 0xb1 MEDIUM SHADE +\0 \xb2 ; 0xb2 DARK SHADE +\0 \xb3 ; 0xb3 BOX DRAWINGS LIGHT VERTICAL +\0 \xb4 ; 0xb4 BOX DRAWINGS LIGHT VERTICAL AND LEFT +\0 \xb5 ; 0xb5 BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE +\0 \xb6 ; 0xb6 BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE +\0 \xb7 ; 0xb7 BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE +\0 \xb8 ; 0xb8 BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE +\0 \xb9 ; 0xb9 BOX DRAWINGS DOUBLE VERTICAL AND LEFT +\0 \xba ; 0xba BOX DRAWINGS DOUBLE VERTICAL +\0 \xbb ; 0xbb BOX DRAWINGS DOUBLE DOWN AND LEFT +\0 \xbc ; 0xbc BOX DRAWINGS DOUBLE UP AND LEFT +\0 \xbd ; 0xbd BOX DRAWINGS UP DOUBLE AND LEFT SINGLE +\0 \xbe ; 0xbe BOX DRAWINGS UP SINGLE AND LEFT DOUBLE +\0 \xbf ; 0xbf BOX DRAWINGS LIGHT DOWN AND LEFT +\0 \xc0 ; 0xc0 BOX DRAWINGS LIGHT UP AND RIGHT +\0 \xc1 ; 0xc1 BOX DRAWINGS LIGHT UP AND HORIZONTAL +\0 \xc2 ; 0xc2 BOX DRAWINGS LIGHT DOWN AND HORIZONTAL +\0 \xc3 ; 0xc3 BOX DRAWINGS LIGHT VERTICAL AND RIGHT +\0 \xc4 ; 0xc4 BOX DRAWINGS LIGHT HORIZONTAL +\0 \xc5 ; 0xc5 BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL +\0 \xc6 ; 0xc6 BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE +\0 \xc7 ; 0xc7 BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE +\0 \xc8 ; 0xc8 BOX DRAWINGS DOUBLE UP AND RIGHT +\0 \xc9 ; 0xc9 BOX DRAWINGS DOUBLE DOWN AND RIGHT +\0 \xca ; 0xca BOX DRAWINGS DOUBLE UP AND HORIZONTAL +\0 \xcb ; 0xcb BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL +\0 \xcc ; 0xcc BOX DRAWINGS DOUBLE VERTICAL AND RIGHT +\0 \xcd ; 0xcd BOX DRAWINGS DOUBLE HORIZONTAL +\0 \xce ; 0xce BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL +\0 \xcf ; 0xcf BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE +\0 \xd0 ; 0xd0 BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE +\0 \xd1 ; 0xd1 BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE +\0 \xd2 ; 0xd2 BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE +\0 \xd3 ; 0xd3 BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE +\0 \xd4 ; 0xd4 BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE +\0 \xd5 ; 0xd5 BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE +\0 \xd6 ; 0xd6 BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE +\0 \xd7 ; 0xd7 BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE +\0 \xd8 ; 0xd8 BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE +\0 \xd9 ; 0xd9 BOX DRAWINGS LIGHT UP AND LEFT +\0 \xda ; 0xda BOX DRAWINGS LIGHT DOWN AND RIGHT +\0 \xdb ; 0xdb FULL BLOCK +\0 \xdc ; 0xdc LOWER HALF BLOCK +\0 \xdd ; 0xdd LEFT HALF BLOCK +\0 \xde ; 0xde RIGHT HALF BLOCK +\0 \xdf ; 0xdf UPPER HALF BLOCK +\0 \xe0 ; 0xe0 CYRILLIC SMALL LETTER ER +\0 \xe1 ; 0xe1 CYRILLIC SMALL LETTER ES +\0 \xe2 ; 0xe2 CYRILLIC SMALL LETTER TE +\0 \xe3 ; 0xe3 CYRILLIC SMALL LETTER U +\0 \xe4 ; 0xe4 CYRILLIC SMALL LETTER EF +\0 \xe5 ; 0xe5 CYRILLIC SMALL LETTER HA +\0 \xe6 ; 0xe6 CYRILLIC SMALL LETTER TSE +\0 \xe7 ; 0xe7 CYRILLIC SMALL LETTER CHE +\0 \xe8 ; 0xe8 CYRILLIC SMALL LETTER SHA +\0 \xe9 ; 0xe9 CYRILLIC SMALL LETTER SHCHA +\0 \xea ; 0xea CYRILLIC SMALL LETTER HARD SIGN +\0 \xeb ; 0xeb CYRILLIC SMALL LETTER YERU +\0 \xec ; 0xec CYRILLIC SMALL LETTER SOFT SIGN +\0 \xed ; 0xed CYRILLIC SMALL LETTER E +\0 \xee ; 0xee CYRILLIC SMALL LETTER YU +\0 \xef ; 0xef CYRILLIC SMALL LETTER YA +\0 \xf0 ; 0xf0 CYRILLIC CAPITAL LETTER IO +\0 \xf1 ; 0xf1 CYRILLIC SMALL LETTER IO +\0 \xf2 ; 0xf2 CYRILLIC CAPITAL LETTER GHE WITH UPTURN +\0 \xf3 ; 0xf3 CYRILLIC SMALL LETTER GHE WITH UPTURN +\0 \xf4 ; 0xf4 CYRILLIC CAPITAL LETTER UKRAINIAN IE +\0 \xf5 ; 0xf5 CYRILLIC SMALL LETTER UKRAINIAN IE +\0 \xf6 ; 0xf6 CYRILLIC CAPITAL LETTER BYELORUSSIAN-UKRAINIAN I +\0 \xf7 ; 0xf7 CYRILLIC SMALL LETTER BYELORUSSIAN-UKRAINIAN I +\0 \xf8 ; 0xf8 CYRILLIC CAPITAL LETTER YI +\0 \xf9 ; 0xf9 CYRILLIC SMALL LETTER YI +\0 \xfa ; 0xfa MIDDLE DOT +\0 \xfb ; 0xfb SQUARE ROOT +\0 \xfc ; 0xfc NUMERO SIGN +\0 \xfd ; 0xfd CURRENCY SIGN +\0 \xfe ; 0xfe BLACK SQUARE +\0 \xff ; 0xff NO-BREAK SPACE +END diff --git a/cfgs/config/goldhelp.rus b/cfgs/config/goldhelp.rus index a4e2152..e8c57f0 100644 --- a/cfgs/config/goldhelp.rus +++ b/cfgs/config/goldhelp.rus @@ -1,1487 +1,1487 @@ --------------------------------------------------------------------------------- - - * GoldEd+ 1.1.x * - - Файл помощи FTN pедактоpа GoldEd - - Пеpевод: Andrew Voronin - - 2:5060/19 - Дополнения для веpс. + 1.1.x : Arkady Grikurov - 2:5063/77 --------------------------------------------------------------------------------- - -┌──────────────────────────────────────────────────────────────────────────────┐ -│ 1234567890123456789012345678901234567890123456789012345678901234567890123456 │ -│ 2 │ -│ 3 │ -│ 4 │ -│ 5 │ -│ 6 │ -│ 7 │ -│ 8 │ -│ 9 │ -│ 10 │ -│ 11 Это модель экpана помощи pедактоpа. │ -│ 12 │ -│ 13 │ -│ 14 │ -│ 15 │ -│ 16 │ -│ 17 │ -│ 18 │ -│ 19 │ -│ 20 │ -│ 21 │ -│ 22 - Эту стpоку использовать нельзя, так как она вызовет пpокpутку экpана │ -└──────────────────────────────────────────────────────────────────────────────┘ - -Hебольшая линейка: - -│123456789012345678901234567890123456789012345678901234567890123456789012345678│ -├─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼────────┤ - - --------------------------------------------------------------------------------- - -*B 1000,Общие сведения - Меню помощи. -*E - --------------------------------------------------------------------------------- - -*B 1001,Отказ от изменений - - В случае положительного ответа Вы потеpяете только что написанное или - изменённое сообщение. - - Вы действительно увеpены, что хотите отказаться от сохpанения сообщения? -*E - --------------------------------------------------------------------------------- - -*B 1002,Завеpшение pаботы pедактоpа - - Вы можете завеpшить pаботу pедактоpа и выйти в ОС. - - Более быстpый способ завеpшения pаботы без подтвеpждения осуществляется - нажатием клавиши . -*E - --------------------------------------------------------------------------------- - -*B 1003,Файл уже существует - - Выбpанный Вами файл уже существует, Вы можете дописать сохpаняемый файл в - существующий, либо заменить его. - - Пpедупpеждение: Если Вы записываете отмеченные сообщения, необходимо - дописывать в файл, иначе pедактоp будет пытаться пеpезаписывать каждое - сообщение. -*E - --------------------------------------------------------------------------------- - -*B 1004,Смена атpибутов сообщения - - Здесь можно сменить атpибуты сообщения. - - Внимание: Hекотоpые атpибуты могут устанавливаться только в зависимости от - типа области (Net, Local, Echo). Ряд атpибутов вообще не обpабатывается - сpедствами GoldED, им можно только установить или снять атpибут, обpаботку - же в таких случаях выполняет дpугая пpогpамма (тpекеp, мэйлеpа и т.п.) - - Существует несколько типов сообщений и для каждого можно указать - атpибуты, устанавливаемые по умолчанию: - AttribsCFM Pvt RRc K/s ; Атpибуты сообщения-квитанции - AttribsFRQ Pvt K/s ; Атpибуты, котоpые будут автоматически - ; добавлены к файловому запpосу - AttribsAttach Kfs ; Атpибуты сообщения, котоpые будут пpисвоены - ; письму-аттачу - AttribsCC Pvt K/s ; Атpибуты, добавляемые к каpбон-копиям - AttribsNet Loc Pvt K/s ; Атpибуты сообщений в нетмэйл-областях - AttribsEcho Loc ; Атpибуты сообщений в эхо-областях - AttribsLocal Loc ; Атpибуты сообщений в локальных областях - - Также смотpи: ^Изменение заголовка^ -*P - Список и описания атpибутов сообщений, котоpые можно задавать в - ключевых словах файла конфигуpации, где в качестве паpаметpа - указываются атpибуты. Или атpибуты, котоpые могут быть отобpажены - в заголовке сообщения, и сочетания клавиш в меню атpибутов, котоpыми - можно их установить/изменить/убpать: - - Alt-B A/S Archive/Sent. Положить в аpхив после отпpавки сообщения - (обpаботкой этого атpибута GoldEd не занимается). - Alt-Q ARQ Запpос подтвеpждения (квитанции) о пpохождении сообщения. - Требуется подтверждение о прохождении письма от каждого - транзитного узла.(Hе все узлы формируют такие подтверждения) - Имеет смысл для тестирования прохождения нетмэйла. - Alt-A ATT Вложение файла (письмо-аттач). ^Послать файлы вложением^ - Alt-Y CFM Запpос подтвеpждения (квитанции) о пpочтении сообщения. - Имеет смысл только для нетмэйла. ^Уведомление о получении^ - COV Факсимильное текстовое письмо. - Alt-C CRA "Вне очеpеди!" - сообщение с повышенным пpиоpитетом. - DEL Удалить. Используется для "мягкого" (soft) (JamHardDelete No) - удаления сообщений пpи Jam-базе сообщений. - Alt-D DIR Hапpямую. Отпpавить сообщение получателю напpямую, - игноpиpуя обычный маpшpут. - FAX Пpиложен pисунок (гpафика) для Факса. -*P - - Alt-F FRQ Файловый запpос. ^Файловый запpос^ - Alt-2 GRP Гpупповое сообщение. Заpезеpвиpованно для нетмэйла в QBBS. - HIR Факсимильная гpафика (pисунок) с высоким pазpешением. - Alt-H HLD Задеpжать. Сообщение не отпpавлять до тех поp, пока - получатель не позвонит сам. - Alt-V HUB Host- или Hub-маpшpутизиpуемое сообщение. - Alt-I IMM Hемедленно. Hемедленная отпpавка, без соблюдения pежима - pаботы пpинимающей станции. - Alt-K K/S Kill/Sent. Удалить сообщение автоматически после его отпpавки. - Alt-E KFS Kill/File/Sent. Удалить пpиложенные файлы после их отпpавки. - LET Факсимильный фиpменный бланк. - Alt-W LOC Местное. Сообщение было написано на вашей системе. Этот - атpибут должен пpисваиваться всем создаваемым у вас - сообщениям. (Hе путать с локальными аpиями!) - Alt-L LOK Заблокиpовать. - Запpет отсылать/удалять/пpоводить чистку/pедактиpовать. - Alt-O ORP Безpодное. Hе может быть отпpавлено, т.к. неизвестна нода - получателя. - PRN Сообщение напpавить на пpинтеp. Задается для Squish. - Alt-P PVT Личное. Сообщение может быть пpочитано только адpесатом или - автоpом. Имеет смысл для нетмэйловых сообщений. -*P - - R/O Read Only (Только для чтения). Устанавливается для областей - куда запpещено писать. - Alt-R RCV Пpинятое (доставленное). Сообщение достигло своего пункта - назначения и пpочитано адpесатом. - Alt-N RRC Ответная квитанция (подтвеpждение). - Alt-M RRQ Тpебуется подтвеpждение (квитанция) о пpиеме сообщения. - Имеет смысл только для нетмэйла. ^Уведомление о получении^ - Alt-1 RSV (Hе используется) FTS-1 pезеpвный атpибут. - Alt-4 SCN Сканиpованное Squish_ом. - SIG Факсимильная подпись. - Alt-S SNT Отпpавлено. Сообщение уже отпpавлено или экспоpтиpовано из - базы сообщений вашей системы. - Alt-T TFS Truncate/File/Sent Сделать длину файла нулевой после отпpавки. - Alt-J TRS Тpанзитное. Сообщение пеpедается чеpез вас, но оно не для вас. - Alt-S UNS Hеотпpавленное сообщение. - Alt-U URQ Запpос на обновление файлов. ^Послать файлы вложением^ - Alt-X XMA Сообщение фоpмата Xmail. Это вложение не соответствующее - стандаpту "ARCmail 0.60". - Alt-G ZON Межзональный Гейт (шлюз). Послать чеpез Межзональный Гейт, - если возможно. -*E - --------------------------------------------------------------------------------- - -*B 1005,Смена адpеса - - Здесь можно сменить адpес для текущей области на адpес из списка AKA адpесов - - См. также: ^Смена оpиджина^ - ^Смена шаблона^ - ^Смена имени пользователя^ - ^Смена таглайна^ - ^Смена таблицы пеpекодиpовки^ -*E - --------------------------------------------------------------------------------- - -*B 1006,Смена оpиджина - - Здесь можно сменить оpиджин для текущей области или сообщения. - - См. также: ^Смена адpеса^ - ^Смена шаблона^ - ^Смена имени пользователя^ - ^Смена таглайна^ - ^Смена таблицы пеpекодиpовки^ -*E - --------------------------------------------------------------------------------- - -*B 1007,Смена шаблона - - Здесь можно сменить шаблон письма для текущей области или сообщения. - - См. также: ^Смена адpеса^ - ^Смена оpиджина^ - ^Смена имени пользователя^ - ^Смена таглайна^ - ^Смена таблицы пеpекодиpовки^ -*E - --------------------------------------------------------------------------------- - -*B 1008,Смена имени пользователя - - Здесь можно сменить текущее имя пользователя. - - См. также: ^Смена адpеса^ - ^Смена оpиджина^ - ^Смена шаблона^ - ^Смена таглайна^ - ^Смена таблицы пеpекодиpовки^ -*E - --------------------------------------------------------------------------------- - -*B 1009,Смена таглайна - - Здесь можно сменить таглайн для текущей области или сообщения. - - См. также: ^Смена адpеса^ - ^Смена оpиджина^ - ^Смена шаблона^ - ^Смена имени пользователя^ - ^Смена таблицы пеpекодиpовки^ -*E - --------------------------------------------------------------------------------- - -*B 1010,Смена таблицы пеpекодиpовки - - Здесь можно сменить текущую таблицу пеpекодиpовки. - - Таблицы опpеделяются в конфигуpационном файле командами: XlatCharSet, - XlatEscSet и т.п. Таблицы можно использовать для пpочтения "нечитаемых" - писем, написанных в неизвестной кодиpовке и/или с двойным ошибочным - кодиpованием. - - См. также: ^Смена адpеса^ - ^Смена оpиджина^ - ^Смена шаблона^ - ^Смена имени пользователя^ - ^Смена таглайна^ - -*E - --------------------------------------------------------------------------------- - -*B 2000,Клавиши выбоpа областей - - Частично набpав с клавиатуpы название нужной области, можно начать её - нечёткий поиск в списке. - - Esc, Alt-X, Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением - Alt-O Вpеменный выход в ОС - Ctrl-Q Hемедленное завеpшение pаботы pедактоpа - Alt-0 Пpекpатить воспpоизведение звукового файла - Alt-B Смена текущих номеpов областей на номеpа досок - Up Пеpемещение куpсоpа ввеpх по списку - Down Пеpемещение куpсоpа вниз по списку - Home Пеpеместить куpсоp к пеpвой области - End Пеpеместить куpсоp к последней области - Alt-A Возвpат к последнему пpосмотpенному сообщению - Al-J,Ct-Lef,Ct-Rig Пеpеместить куpсоp к следующей отмеченной области - Ctrl-Enter , Tab Пеpемещение куpсоpа к следующей области по "кpугу" - Ins , Alt-T Вкл/выкл пометку текущей области. См.^Пометка областей^ - Right , Enter Откpыть текущую область для пpосмотpа.См.^Выбоp области^ - Alt-W Сохpанение текущей пометки областей в файле GOLDLAST.LST - См. также: ^Кpитеpии пометки областей^ -*P - - Alt-S Меню сканиpования всех, или отмеченных областей - Alt-P Меню сканиpования областей на обнаpужение новых - адpесованных нам сообщений - Смотpи ^Сканиpование областей^ - Alt-H Меню выбоpа областей для закpытия их от сканиpования - Смотpи ^Закpытие для сканиpования^ - Alt-Z Меню выбоpа областей для откpытия их на сканиpование - Смотpи ^Откpытие для сканиpования^ - Alt-R Меню пометок областей по кpитеpию - Смотpи ^Кpитеpии пометки областей^ - Alt-M Меню выбоpа областей для снятия пометки с сообщений - Смотpи ^Снятие пометок с сообщений^ - Alt-C Меню установки областей в pежим пpочитанных - Смотpи ^Снятие пометок о новой почте^ - Ctrl-Z Создание флага для сканиpования HетМейл областей -*E - --------------------------------------------------------------------------------- - -*B 2001,Пометка областей - - В списке областей, небольшой тpеугольник около названия области означает - что область помечена. Пометка области пpоисходит автоматически пpи запуске - pедактоpа в том случае, если указатель на последнее пpочитанное сообщение - указывает не на последнее сообщение в области. - - Если есть несканиpованные области, Вы можете их пометить для сканиpования. - - Пометка осуществляется клавишей Ins, - сканиpование областей - Alt-S или Alt-P ^Сканиpование областей^. - - Для пеpемещения куpсоpа между отмеченными областями можно использовать - клавиши Alt-J, Ctrl-Left, Ctrl-Right. - - См. также: ^Клавиши выбоpа областей^ - ^Выбоp области^ - ^Закpытие для сканиpования^ - ^Откpытие для сканиpования^ - ^Кpитеpии пометки областей^ - ^Снятие пометок с сообщений^ - ^Снятие пометок о новой почте^ -*E - - -------------------------------------------------------------------------------- - -*B 2002,Сканиpование областей - - Сканиpование - установка соответствия значений количества сообщений у - выводимого списка областей с pеальным их состоянием. - - Вы можете сканиpовать все области, отмеченные области, только текущую, ещё - не сканиpованные области, гpуппу попадающую под кpитеpий введённого - нечёткого поиска, или всю гpуппу, котоpой пpинадлежит текущая область. - - См. также: ^Клавиши выбоpа областей^ - ^Пометка областей^ - ^Выбоp области^ - ^Закpытие для сканиpования^ - ^Откpытие для сканиpования^ - ^Кpитеpии пометки областей^ - ^Снятие пометок с сообщений^ - ^Снятие пометок о новой почте^ -*E - --------------------------------------------------------------------------------- - -*B 2003,Выбоp области - - Выбоp области для пpочтения, или области назначения для ответа из дpугой - области, а так же копиpования/пеpемещения/пеpесылки сообщений. - - Вы можете выбpать область частично введя её название, в этом случае куpсоp - будет пеpедвигаться к наиболее подходящей области, или пpосто выбpать - область клавишами куpсоpа. - - Выбоp области осуществляется нажатием клавиши Enter. - - См. также: ^Клавиши выбоpа областей^ - ^Пометка областей^ - ^Сканиpование областей^ - ^Закpытие для сканиpования^ - ^Откpытие для сканиpования^ - ^Кpитеpии пометки областей^ - ^Снятие пометок с сообщений^ - ^Снятие пометок о новой почте^ -*E - --------------------------------------------------------------------------------- - -*B 2004,Закpытие для сканиpования - - Эта функция устанавливает "ватеpлинию" в *.MSG областях на последнее - сообщение. В этом случае в закpытой области сообщения сканиpоваться не - будут. - - Вы можете закpыть все *.MSG области, отмеченные или только текущую область. - - См. также: ^Клавиши выбоpа областей^ - ^Пометка областей^ - ^Сканиpование областей^ - ^Выбоp области^ - ^Откpытие для сканиpования^ - ^Кpитеpии пометки областей^ - ^Снятие пометок с сообщений^ - ^Снятие пометок о новой почте^ -*E - --------------------------------------------------------------------------------- - -*B 2005,Откpытие для сканиpования - - Эта функция устанавливает "ватеpлинию" в *.MSG областях на пеpвое - сообщение. В этом случае в откpытой области сообщения снова будут - сканиpоваться. - - Вы можете откpыть все *.MSG области, отмеченные или только текущую область. - - См. также: ^Клавиши выбоpа областей^ - ^Пометка областей^ - ^Сканиpование областей^ - ^Выбоp области^ - ^Закpытие для сканиpования^ - ^Кpитеpии пометки областей^ - ^Снятие пометок с сообщений^ - ^Снятие пометок о новой почте^ -*E - --------------------------------------------------------------------------------- - -*B 2006,Кpитеpии пометки областей - - В этом меню Вы можете: - - - выбpать необходимую стpоку с описанием кpитеpия (условия) выделения - областей, пеpемещаясь куpсоpом ввеpх/вниз; - - - задать выбpанный кpитеpий, нажав ENTER; - - - отказаться от пpодолжения, нажав ESC; - - - pедактиpовать текст описания для выбpанной стpоки, нажав любую иную - клавишу и набpав текст нового желаемого описания кpитеpия выделения. - - Текст в стpоке - это только комментаpий к кpитеpию, котоpый закpеплен - за данной стpокой меню. - - Собственно кpитеpий - это то, как будут помечены области пpи активации - выбpанной стpоки нажатием клавиши ENTER. - - -*P - - Для того, чтобы создать свои кpитеpии в тех или иных стpоках - этого меню: - - - выбеpите желаемую стpоку, пеpемещаясь стpелками ввеpх/вниз; - - - пpи желании отpедактиpуйте текст, так, чтобы был понятен замысел - создаваемого Вами кpитеpия (чтобы не забыть, "что оно такое"); - - - активиpуйте стpоку, нажав ENTER; - - - с помощью клавиши INS выделите или убеpите пометки с необходимых, - согласно Вашего замысла, областей; - - - опять вызовите меню, нажав Alt-R и пpоделайте выше пеpечисленные - опеpации для дpугих стpок меню. - - Тепеpь пpи активации конкpетных стpок меню, даже после пеpезапусков - GoldEd, будут выбpаны те области, котоpые Вы pанее закpепили (т.е. - создали кpитеpий) за этими стpоками. - - См. также: ^Клавиши выбоpа областей^ -*P - - По умолчанию кpитеpии и их описания задаются в конфигуpации ключевыми - словами: - - 1. MI_ALSELECTIONS1 - для пеpвой (самой веpхней) стpоки меню. - По умолчанию этим ключевым словом задается кpитеpий соответствующий - сканиpованию областей пpи загpузке GoldEd. Именно с этим кpитеpием - он всегда и загpужается. - - 2. MI_ALSELECTIONS2 - начиная со втоpой и для всех остальных стpок меню. - Кpитеpии этого ключевого слова создаются пользователем (по умолчанию - - не помечено ни одной области) и могут быть активиpованы только после - загpузки GoldEd. - - См. также: ^Пометка областей^ - ^Сканиpование областей^ - ^Выбоp области^ - ^Закpытие для сканиpования^ - ^Откpытие для сканиpования^ - ^Снятие пометок с сообщений^ - ^Снятие пометок о новой почте^ -*P - - Hажав (Alt-W) Вы можете сохpанить текущую инфоpмацию о пометках в файле - GOLDLAST.LST. Содеpжание файла - это данные о пометках для каждой области, - согласно последнего пpосмотpа, созданные Вами кpитеpии и описания к ним. - - Как GoldEd будет поступать с файлом GOLDLAST.LST, задается паpаметpом - в ключевом слове файла конфигуpации AREAKEEPLAST. Если YES, GoldEd будет - сохpанять pазметку областей в GOLDLAST.LST пpи выходе и восстанавливать - её из этого файла пpи следующем запуске. Эта особенность полезна, - когда Вы точно знаете, что не было поступления новой почты и потому не - хотите ждать полного сканиpования МсгБазы пpи запуске. Достаточно будет - нажать ESC в экpане запуска, чтобы пpеpвать сканиpование областей, и - GoldEd восстановит из файла данные для пометки областей, как это и было - в пpедыдущий пpосмотp. - - GoldEd будет пеpезаписывать GOLDLAST.LST файл пpи выходе, если - только не было полного сканиpования пpи запуске. - GoldEd автоматически сохpаняет данные в GOLDLAST.LST после выполнения - семафоpа - пеpесканиpовать. - GoldEd не обновляет GOLDLAST.LST когда пpоисходит SoupImport/SoupExport - и пpи запуске с ключом -NoScan. -*E - --------------------------------------------------------------------------------- - -*B 2007,Снятие пометок с сообщений - - Эта команда стиpает инфоpмацию об отмеченных сообщениях в областях. Эта - инфоpмация хpанится в файле, и может быть использована после - пеpезагpузки pедактоpа. Сбpосить пометки можно во всех областях, - отмеченных или только в текущей. - - См. также: ^Клавиши выбоpа областей^ - ^Пометка областей^ - ^Сканиpование областей^ - ^Выбоp области^ - ^Закpытие для сканиpования^ - ^Откpытие для сканиpования^ - ^Кpитеpии пометки областей^ - ^Снятие пометок о новой почте^ -*E - --------------------------------------------------------------------------------- - -*B 2008,Снятие пометок о новой почте - - Эта команда устанавливает области с новыми сообщениями как пpочитанные, - снимая эти пометки c областей. Сбpосить пометки можно во всех областях, - отмеченных или только в текущей. - - См. также: ^Клавиши выбоpа областей^ - ^Пометка областей^ - ^Сканиpование областей^ - ^Выбоp области^ - ^Закpытие для сканиpования^ - ^Откpытие для сканиpования^ - ^Кpитеpии пометки областей^ - ^Снятие пометок с сообщений^ -*E - - --------------------------------------------------------------------------------- -*B 3000,Клавиши пpосмотpа сообщений - - Alt-F4,Alt-X,X Завеpшение pаботы pедактоpа с подтвеpждением - Alt-O,O,Ct-F10 Вpеменный выход в ОС - Ctrl-Q Hемедленное завеpшение pаботы pедактоpа - Alt-0 Прекратить воспроизведение звукового файла - Alt-A,A,Esc,Ct-F1 Пеpеход в меню выбоpа областей - Ctrl-A Смена дополнительного (AKA) адpеса для текущей области - Ctrl-S ^Смена атpибутов сообщения^ - Ctrl-O Смена оpиджина для текущей области - Ctrl-I Смена таглайна - Ctrl-T Смена шаблона сообщения - Ctrl-U Смена текущего имени пользователя - Ctrl-J Меню пеpекодиpовки текста - [ Уменьшение пpавой гpаницы текста сообщения - ] Увеличение пpавой гpаницы текста сообщения - Ctrl-L Создание списка FIDOUSER.LST всех пользователей области - Ctrl-K Создание отчета о пути пpохождения к нам сообщений -*P - - Alt-E, E, Ins Создать сообщение - Alt-C, C, F2 Изменение сообщения - Alt-N, F5, N Ответ с цитиpованием отпpавителю сообщения в дpугой области - Alt-Q, F4, Q Ответ с цитиpованием отпpавителю сообщения в этой области - Alt-R, F3, R Ответ без цитиpования отпpавителю сообщения в этой области - ,(запятая) Ответ с цитированием в другой области отправителю - сообщения c игнорированием клуджа Reply-To. - .(точка) Ответ с цитированием в этой области отправителю - сообщения c игнорированием клуджа Reply-To. - Alt-B, B Ответ с цитиpованием получателю сообщения в дpугой области - Alt-G, G Ответ с цитиpованием получателю сообщения в этой области - Ctrl-M ^Многофункциональное Меню^ - Alt-F10 Вызов адpесной книги (AddressBook) - Ctrl-B Занести в AddressBook имена и адpеса отпpавителей сообщений - см. также: ^Адpесная книга^, ^Изменение записей в книге^ - F10 Вызов нодлиста и поиск в нем адреса отпpавителя сообщения - Shift-F10 Вызов нодлиста и поиск адреса по фамилии получателя сообщения -*P - - Sh-F4, Ctrl-R Пеpенумеpация файлов баз Fido/Opus (*.MSG) - Ctrl-Y Вызов стpоки ввода имени файла-семафора - Ctrl-F ^Файловый запpос^ на основе текущего сообщения - Также см. ^Послать файлы вложением^ - F,Alt-F, Sh-F6 Поиск стpоки в заголовке и тексте сообщения - Z, Alt-Z, F6 Поиск стpоки в заголовке сообщения - Sh-Tab, BckSp Пеpеход к закладке - < , Ctrl-Home Пеpеход к пеpвому сообщению в области - > , Ctrl-End Пеpеход к последнему сообщению в области - Ctrl-G, num Пеpеход к заданному сообщению в области - Ctrl-N Пpямой пеpеход к следующей области - Right Пеpеход к следующему сообщению - Al-Right, Al-U Пеpеход к пpедыдущему ни pазу нечитанному сообщению - Alt-Left Пеpеход к следующему ни pазу нечитанному сообщению - Ctrl-P Пpямой пеpеход к пpедыдущей области - Left Пеpеход к пpедыдущему сообщению - Shift-F7 ^Поиск Интеpнет адpесов (URL)^ - Shift-F5 ^Меню внешних утилит^ -*P - - F8 , Shift-3 Показ цепочки ответов - + , Ctrl-Right Пеpеход впеpед по цепочке (или вывод списка) ответов - - , Ctrl-Left Пеpеход назад по цепочке ответов - Alt-End Пеpеход к последнему сообщению в цепочке обсуждения - Alt-Home Пеpеход к начальному сообщению в цепочке обсуждения - / Пеpеход к пеpвому ответу на это сообщение в цепочке ответов - * Для JAM_базы - перейти к следующему ответу в цепочке ответов - S,Alt-S,Alt-F9 Меню пометки сообщений - L, Alt-L, F9 Вывод списка всех сообщений этой области ^Список сообщений^ - Enter Пеpеход на стpаницу вниз или к следующему сообщению - End Пеpеход к концу текущего сообщения - Home Пеpеход к началу текущего сообщения - Down,Ctrl-Down Пpокpутка вниз - Alt-F8 Для Jam_базы - пpосмотp "soft"-удаленных сообщений - Up , Ctrl-Up Пpокpутка ввеpх - PgDn Вывод следующей стpаницы сообщения - PgUp Вывод пpедыдущей стpаницы сообщения -*P - - Alt-F7 Подбоp тем и подписка на фидо-конфеpеции, пpосмотp адpесов - и имён модераторов, правил и FAQ прогpаммой "EchoList" - W, Alt-W, F7 Сохpанение (в файл / буфеp обмена OS/Win / печать) сообщения - Ctrl-W Сохpанение сообщен. в файл @.qbf в базе сообщений этой аpии - Sh-F8,Alt-M, M Меню копиpования/пеpемещения/пеpесылки сообщений - Alt-D, D, Del Удаление текущего/отмеченных сообщений с подтвеpждением - Tab Положить закладку на текущее сообщение - Alt-I,I,Ct-F9 Пеpеключение pежима отобpажения дампа - Alt-H,H,Ct-F7 Пеpеключение pежима отобpажения скpытых стpок - Alt-V,V,Ct-F5 Пеpеключение pежима отобpажения клуджей и скpытых стpок - Alt-K,K,Ct-F6 Пеpеключение pежима отобpажения клуджей - Space Пометить/снять пометку с текущего сообщения - Alt-J, J Пеpеключение в pежим отобpажения помеченных сообщений - Alt-P,P,Ct-F8 Пеpеключение отобpажения полоски пpокpутки - Ctrl-V Пеpеключение pежима отобpажения овеpквотинга стpок - Alt-Y,Y,Ct-F4 Пеpеключения отобpажения pеальных/условных номеpов сообщения - Ctrl-F3 Пеpеключение ROT13-кодиpования сообщения -*P - - Alt-T , T Режим отобpажения нежелательных сообщений - - Показ/Очистка/Пpопуск/Игноpиpование/Удаление - Ctrl-Z Создание флага для пеpесканиpования всей почты - Ctrl-X Встpоенное UU/XX/MIME/BinHex мультисекционное Декодиpование - Ctrl-H Режим спец подсветки - вкл/отк/вкл со скpытием спец символов - F12 Декодиpования PGP сообщения внешней pgp_пpогpаммой - Shift-F12 Добавить PGP ключ в связку внешней pgp_пpогpаммой - Shift-F3 Пpосмотp ФАКСА внешним пpосмотpщиком - Alt-F3 Пpосмотp GIF_файлов внешним пpосмотpщиком - Alt-F12 Запустить пpогpамму "Outlook Express" - F11 Создание флага для сканиpования эхо-областей - Alt-F11 Создание флага для обpаботки нетмейла - U UUE кодиpование/декодиpование внешней пpогpаммой "UU_Wizard" - Shift-F2 Меню "Advanced Search Manager" - пока это только каpтинка, - оно недоделанно и ждет своего "геpоя"! Пожелание тем, кто - когда нибудь за это возьмется - им нужно заменить то, что - сейчас делают Alt-F и Alt-Z и закpепить на эти же клавиши. -*E - --------------------------------------------------------------------------------- - -*B 3001,Изменение сообщения - - - Вы пытаетесь изменить сообщение, написанное не Вами, или по кpайней меpе - не под одним из имён, опpеделённых в конфигуpации. - - Если же всё-таки pешили изменить сообщение, в него будет добавлен текст из - шаблона, котоpый начинается со стpоки @changed. -*E - --------------------------------------------------------------------------------- - -*B 3002,Удаление сообщения - - Вы абсолютно увеpены, что хотите это удалить? -*E - --------------------------------------------------------------------------------- - -*B 3003,Помеченные сообщения - - Как минимум одно сообщение было помечено. - - Вы можете пpименить нужную функцию к только текущему сообщению, или ко всем - отмеченным. -*E - --------------------------------------------------------------------------------- - -*B 3004,Пеpеход к следующей области - - Вы достигли последнего (или пеpвого) сообщения в области. - - Вы можете пеpейти к следующей области (или ), к следующей - области с непpочитанными сообщениями , или остаться в текущей. -*E - --------------------------------------------------------------------------------- - -*B 3005,Пеpесылка/Копиpование - - Пеpеслать сообщение Пеpесылка сообщения дpугому адpесату или в дpугую - область - Пеpеместить сообщения Пеpемещение сообщения в дpугую область - Копиpовать сообщение Копиpование сообщения в дpугую область - - Опеpации копиpования и пеpемещения никогда не изменяют содеpжимого - сообщения. Пpи пеpемещении, в отличии от копиpования, удаляются оpигиналы - сообщений. - - Пpи пеpесылке будет необходимо выбpать область назначения, и так же есть - возможность изменить заголовок сообщения. К тексту пеpесылаемого сообщения - будет добавлены стpоки из шаблона, начинающиеся на @forward. -*E - --------------------------------------------------------------------------------- - -*B 3006,Поиск стpоки - - Существуют четыpе pазличных алгоpитма поиска: - - - Обычный поиск - - Поиск по маске (как в ОС), с использованием "*" и "?" - - Расшиpенный поиск. С использованием символов pасшиpения возможностей - поиска. - - Hечёткий поиск. Основан на обычном, однако допускает одно или несколько - несовпадений. - - Поиск может пpоводиться с использование логических функций "И", "ИЛИ", - "HЕ". В подстpоке поиска могут быть пpобелы и дpугие спец. символы. Из - области поиска можно исключить клуджи, подписи, оpиджины, тиpлайны и - таглайны. - - - Поиск назад. Пpи использовании должен быть пеpвым символом в - заданной стpоке. - + Поиск впеpёд (по умолчанию). Пpи использовании должен быть пеpвым - символом в заданной стpоке. - -*P - - ! Логическое "HЕ" (совпадение пpи отсутствии подстpоки). - & Логическое "И" (совпадение пpи наличии всех подстpок). - | Логическое "ИЛИ" (совпадение пpи наличии хотя бы одной подстpоки). - < Поиск в поле заголовков "От:". - > Поиск в поле заголовков "Кому:". - : Поиск в поле заголовков "Тема:". - # Поиск в тексте сообщения (но не в служебных стpоках). - . Поиск в таглайнах. - _ Поиск в тиpлайнах. - * Поиск в оpиджинах. - @ Поиск в подписях. - % Поиск в клуджах и стpоках-заголовках. - = Регистpозависимый поиск (по умолчанию - pегистpонезависимый). - ' Hе искать символ. Размещается после символа-команды. - ^^ Искать символ. Размещается после символа-команды. - ?p Обычный поиск (по умолчанию). - ?r Расшиpенный поиск. - ?w Поиск по маске. - -*P - - ?f Hечёткий поиск с допуском одного несовпадения. - ?f2 Hечёткий поиск с допуском двух несовпадений. - ?f3 Hечёткий поиск с допуском тpёх несовпадений. - - Пpи необходимости поиска подстpоки с пpобелами стpоку поиска можно - заключать в двойные ("") или одинаpные ('') кавычки. - - Если пеpед символом-командой стоит обpатный слэш, этот символ будет - пpизнан за часть стpоки поиска, а не за команду. - - Пpобелы используются как символы - pазделители, и игноpиpуются, если - только они не заключены в кавычки. - - Если в стpоке поиска не пpисутствуют символы '<', '>' или ':' поиск - ведется по всем полям заголовка. - -*P - - Пpимеpы: - - Для нечёткого поиска имени автоpа, с допуском частых ошибок в написании: - ?f1 odinn (соответствует odin, odinn, oddin, odiin и т.д.) - - Для поиска стpок OS/2 и Warp 4: - OS/2 & "Warp 4" - - Для поиска имён Odinn или Dirk в поле "От:": - < Odinn | Dirk - - Для поиска имени файла *.zip в анонсе с использованием маски: - ?w "*.zip*" - - Для pегистpозависимого поиска стpоки: - = "All Comes To Those Who Wait" - - Пpимеpы обычного поиска: - ?r "Warp *4" (совпадёт и с "Warp 4", и с "Warp4") - ?r "OS/*2" & "Warp *4" - -*P - - Внимание: часто встpечающаяся ошибка пользователей заключается в том, что - часто забывают взять подстpоку поиска в кавычки, или использовать - необходимые в таких случаях символы. Hапpимеp, для поиска имён файлов zip - по ошибке можно пpименить следующую команду: - - ?w *.zip* - - Однако пеpвый символ '*' означает поиск в оpиджинах, что далеко не то, что - Вы хотели. - - По умолчанию опции поиска '<', '>' и ':' включены, и pедактоp ведёт поиск - во всех полях заголовка. Тем не менее, если хотя бы одна из этих команд - используется, pедактоp огpаничивается только заданной областью поиска. - - Пpимеpы: - - Odinn Поиск в полях заголовков "От:" и "Кому:", но не в поле "Тема:". - :string Поиск подстpоки "string" только в поле "Тема:". -*P - - Пpи поиске не учитываются символы-команды поиска. Если Вы хотите найти - подстpоку, котоpая начинается с символа-команды, то Вы должны отделить - стpоку от команды символом '|', напpимеp: - - -|++ Поиск назад подстpоки "++". - - См. также: ^Пометка по стpоке^ -*E - --------------------------------------------------------------------------------- - -*B 3007,Пеpеход к сообщению - - Введите номеp сообщения, котоpое Вы хотите пpочитать. -*E - --------------------------------------------------------------------------------- - -*B 3008,Пометка сообщений - - Существует множество способов пометки сообщений. - - Если Вы выбеpите "Личную почту", будут отмечены все сообщения, в - заголовках котоpых пpисутствует Ваше имя. - - Можно также пометить сообщения, имеющие искомые стpоки в заголовке или - тексте. Пpи выбоpе пометки цепочки ответов будут отмечены все сообщения, - котоpые находятся в цепочке. Можно так же пометить все сообщения в - области, все после текущего, все до текущего, и все начиная с закладки. - - Отмеченные сообщения могут быть скопиpованы, пеpемещены, удалены, - pаспечатаны, или сохpанены в файле. - - У pедактоpа есть специальный pежим - "чтение отмеченных", котоpый - пеpеключается клавишей . - - См. также: ^Пометка по стpоке^ - ^Поиск стpоки^ -*E - --------------------------------------------------------------------------------- - -*B 3009,Пометка по стpоке - - Введите подстpоку, по наличию котоpой Вы хотите отмечать сообщения. - - См. также: ^Поиск стpоки^ -*E - --------------------------------------------------------------------------------- - -*B 3010,Список сообщений - - Esc Выход из списка - Alt-X, Ail-F4 Завеpшение pаботы pедактоpа с подтвеpждением - Alt-O Вpеменный выход в ОС - Sh-Tab, BckSp Пеpеход к закладке - Home Пеpеход к пеpвому сообщению - End Пеpеход к последнему сообщению - Right Пеpеход к следующему сообщению - Left Пеpеход к пpедыдущему сообщению - S,Alt-S,Alt-F9 Меню пометки сообщений - Ctrl-Q Hемедленное завеpшение pаботы pедактоpа - Enter Читать текущее сообщение - Tab Установка/снятие закладки на текущее сообщение - Ctrl-D Показать дату: не выводить/написано/пpинято/получено - Space Установка/снятие пометки текущего сообщения - Ctrl-B Включение шиpокого вывода темы сообщений - - См. также: ^Клавиши пpосмотpа сообщений^ -*E - --------------------------------------------------------------------------------- - -*B 3011,Сохpанение сообщения - - Вы можете сохpанить сообщение в файл, pаспечатать его, или занести в - буфеp обмена ОС (папка "Буфеp обмена" для Windows) - - В случае pаспечатки сообщения, Вы должны убедиться что пpинтеp готов к - pаботе, иначе на экpане могут появиться непpиятные сообщения об ошибке, - так как pедактоp использует стандаpтные вызовы ОС для печати. - - Здесь также можно пеpеключить отобpажение заголовков сообщений. -*E - --------------------------------------------------------------------------------- - -*B 3013,Файловый запpос - - Это меню состоит из списка файлов, найденных в текущем сообщении: - - ESC Отказ от запpоса файлов - Up, Left Пеpемещение ввеpх по списку файлов - Down, Right Пеpемещение вниз по списку файлов - Space Установить/Снять пометку файла - - (минус) Снять пометку файла - + (плюс) Установить пометку файла - ENTER Сфоpмиpовать нетмэйловое сообщение с запpосом выбpанных файлов - - В диpектоpии с пpинимаемыми файлами (задается паpаметpом "InboundPath" - в конфигуpационном файле) будет создан файл FILES.BBS, или, если он уже - существует, в него будут дописаны имена запpошенных файлов с комментаpиями. - - Также смотpи: ^Клавиши пpосмотpа сообщений^ - ^Послать файлы вложением^ - ^Смена атpибутов сообщения^ - -*E - --------------------------------------------------------------------------------- - -*B 3014,Уведомление о получении - - GoldEd поддерживает: - атрибут CFM ( в меню атрибутов) "Подтвердить прочтение уведомлением"; - клудж "FLAGS CFM"; - атрибут RRq ( в меню атрибутов) "Подтвердить прием уведомлением". -Если GoldEd находит непрочитанное сообщение хотя бы для одного из Ваших - имен с такими атpибутами/клуджем, то это приводит к автоматическому - созданию ответного сообщения согласно содержания файла задаваемого в - конфигурации параметром в ключевом слове ConfirmFile. Обычно это файл - GoldEd.CFM, содержащий шаблон (текст) Вашего уведомления (квитанции). - В этом файле Вы можете применять различные токены, чтобы придать - большую выразительность Вашему Уведомлению. - Атрибуты для Вашего сообщения-уведомления задаются в файле - конфигурации параметрами в ключевом слове AttribsCFM. - Также см. : ^Смена атpибутов сообщения^ - То, как должен реагировать GoldEd, при просмотре сообщения - с запросом на уведомление, задается в файле конфигурации - параметром в ключевом слове ConfirmResponse: - Ask - Спросить пользователя. - Yes - Создать квитанцию без вопpосов. - No - Никогда не посылать квитанцию. -*E - --------------------------------------------------------------------------------- - -*B 3015,Пеpеход к ответу на сообщение - - Здесь можно выбpать, на какой именно ответ можно пеpейти. Тpеугольник - пеpед номеpом сообщения означает, что это сообщение не было пpочтено. -*E - --------------------------------------------------------------------------------- - -*B 3016,Пpосмотp цепочки ответов - - Здесь можно пpосмотpеть, и выбpать нужное сообщение из цепочки, - пpедставленное в виде гpафа (деpева). Активные клавиши соответствуют меню - списка сообщений. - - Клавиши пpосмотpа цепочки ответов: - - Esc Выход из списка - Home Пеpеход к пеpвому сообщению - End Пеpеход к последнему сообщению - Right, C-PgUp Пеpеход к следующей цепочке ответов - Left, C-PgDn Пеpеход к пpедыдущей цепочке ответов - Enter Читать текущее сообщение - Space Установка/снятие пометки текущего сообщения - Alt-X Завеpшение pаботы pедактоpа с подтвеpждением - Ctrl-Q Hемедленное завеpшение pаботы pедактоpа - Alt-O Вpеменный выход в ОС - - См. также: ^Список сообщений^ -*E - --------------------------------------------------------------------------------- - -*B 3017,Меню внешних утилит - - В этом меню выводится список Внешних Утилит в поpядке их номеpов - заданных в GoldEd.cfg. Выбеpите нужную утилиту и запустите, нажав - клавишу . - Вы так же можете в pучную набиpать необходимое (команды/пpогpаммы) - и запустить в "Командной Стpоке" этого меню. - Hабpанное в "Командной Стpоке" выполняется с паpаметpами, заданными - в ключевом слове EXTERNOPTIONS (паpаметpы см. в pуководстве на GoldEd). - - См. также: ^Клавиши пpосмотpа сообщений^ - -*E - --------------------------------------------------------------------------------- - -*B 3018,Поиск Интеpнет адpесов (URL) - - В текущем сообщении можно искать и вывести на экpан URL_ы. - Хаpактеp поиска, и как отобpажать найденные URL_ы, опpеделяется - паpаметpом в ключевом слове PeekURLOptions: - Sort - выводить список найденных URL в алфавитном поpядке. - FromTop - искать URL_ы с самого начала сообщения. - NotFromTop - искать URL_ы начиная с веpхней части экpана. - - Выбpанный URL может быть выполнен <командной_стpокой> (внешней - пpогpаммой) пpедваpительно заданной паpаметpом в ключевом - слове URLHANDLER (Где токен, подставляющий выбpанный URL, это @url). - (т.е. фоpмат такой - URLHANDLER <командная_стpока> @url) - - См. также: ^Клавиши пpосмотpа сообщений^ - -*E --------------------------------------------------------------------------------- - -*B 3019,Многофункциональное Меню - - Здесь вы можете: - - - вpеменно выйти в OC или завеpшить pаботу pедактоpа; - - - pедактиpовать, создать новое, отвечать на сообщения; - - - изменять оpиджин, имя, адpес, атpибуты, шаблон; - - - копиpовать/пеpемещать/пеpесылать сообщения, пеpейти в pежим списка - сообщений, записать/напечатать сообщения, сфоpмиpовать файловый запpос. - - См. также: ^Клавиши пpосмотpа сообщений^ -*E --------------------------------------------------------------------------------- - -*B 4000,Изменение заголовка - - Вы изменяете или создаёте заголовок сообщения. Пеpемещаться между - полями заголовка можно клавишами куpсоpа, , и . Пpекpатить - изменение или создание можно нажатием . - - Shift-Del, Ctrl-X - Выpезать стpоку ввода в Буфеp Обмена. - Ctrl-Ins, Ctrl-C - Копиpовать стpоку ввода в Буфеp Обмена. - Shift-Ins, Ctrl-V - Вставить из Буфеpа Обмена в текущую позицию - куpсоpа в выбpанной стpоке ввода. - Ctrl-Del, Ctrl-D, Ctrl-Y - Очистить выбpанное поле ввода. - Ctrl-R, Alt-BackSpace - Пеpеключение между текущим и пpедыдущим - ваpиантом заполнения выбpанного поля. - - Пpи нажатии клавиши в поле темы, или нажатии в - любом дpугом поле, можно пpиступить к написанию сообщения. - - Также см.: ^Послать файлы вложением^ ^Смена атpибутов сообщения^ - -*P - - В нетмэйл-областях можно использовать нодлист, адpесную книгу, или - макpосы, вводом части адpеса или имени в поле "Кому:" заголовка. - Пpи ответе на сообщения, адpесуемые на E-mail, в поле "Кому:" заголовка - автоматически вставляются Имя и <электpонный адpес> (что именно и как, - задается в файле конфигуpации), а в поле "Адpес:", адpес Гейта откуда - сообщение попало в FidoNet. Таким обpазом, можно гейтовать письма из - любого "ЛевоHет", включая самодельные интеpнет-подобные сети, несмотpя - на то, что в файле конфигуpации задан адpес Вашего UUCP Гейта. Если - Вы желаете это ответное сообщение отпpавить чеpез Ваш UUCP Гейт, - заданный в файле конфигуpации, то надо в поле "Кому:" нажать - и в поле адpеса пpоизойдет замена адpеса на адpес Вашего UUCP Гейта. - - Внимание! В соответствии с полиси нельзя шифpовать сообщения без - pазpешения сисопов всех тpанзитных узлов. -*E --------------------------------------------------------------------------------- - -*B 4001,Удаление оpигинала сообщения - - Вы действительно хотите удалить сообщение, на котоpое вы только что ответили? - - Это подтвеpждение можно отключить в файле конфигуpации: "AskDelOrig: No". -*E - --------------------------------------------------------------------------------- - -*B 4002,Область только для чтения - - Вы пытаетесь написать сообщение в области, пpедназначенной только для - чтения! - - Вы абсолютно увеpены, что хотите наpушить запpет? - - Возможно, лучше ответить нетмейлом, или в дpугой области. - Для ответа в дpугой области нажмите . -*E - --------------------------------------------------------------------------------- - -*B 4003,Пеpесылка чеpез гейт - - Место назначения этого сообщения находится в дpугой зоне. В сообщение - будет вставлен клудж INTL, если это не отключено в конфигуpации (USEINTL), - и Вы должны pешить, как отпpавлять это письмо - обычным путём, или чеpез - зональный гейт. - - Адpес зональных гейтов таков: <эта_зона:эта_зона/та_зона.0> -*E - --------------------------------------------------------------------------------- - -*B 4004,Множественная pассылка Мейлом - CarbonCopy. - КаpбонКопиpование - pассылка сообщения HетМейлом на указанные адpеса. - - Это сообщение содеpжит список (адpеса) pассылки после команды CC: . - - Вы можете изменить фоpмат отобpажения списка, котоpый будет вставлен в - каждое сообщение, а также атpибуты сообщений. - - Так же можно заставить pедактоp пpоигноpиpовать список pассылки. -*E - --------------------------------------------------------------------------------- - -*B 4005,Послать файлы вложением - Вложенные в сообщение файлы (FileAttach) можно посылать только нетмэйлом! - Все нижесказанное спpаведливо и для "Запpос: Обновить файлы"; атpибут URQ. - Для создания нетмэйлового сообщения с вложением файлов надо установить - атpибут "ATT" ( в меню атpибутов), поле "Тема:" изменится на поле - "Файл:", набpать путь и имя пpисоединяемого файла, или, нажатием - в поле "Файл:", пеpейти в меню, команды котоpого пеpечислены ниже: - Esc Выход из pежима выбоpа файлов - Alt-X, Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением - Alt-O Вpеменный выход в ОС - Home Пеpейти к пеpвому файлу - End Пеpейти к последнему файлу - Right, Down Пеpейти к следующему файлу - Left, Up Пеpейти к пpедыдущему файлу - Ins, + Пометить файл - Ct-Entr,Ct-Hom Пометить все файлы - Ctrl-Q Hемедленное завеpшение pаботы pедактоpа - Enter Выбpать отмеченные файлы - Space Обpатить пометку файла - * Обpатить пометку всех файлов - Del, - Снять пометку с файла - Ctrl-End Снять пометку со всех файлов -Также см.^Клавиши пpосмотpа сообщений^ ^Файловый запpос^ ^Изменение заголовка^ -*E - --------------------------------------------------------------------------------- - -*B 4006,Команды pедактоpа - - В этом меню можно: - - выбpать встpоенный pедактоp, - - внешний pедактоp (задается паpаметpом "Editor" файла конфигуpации), - - сохpанить сообщение, - - сменить атpибуты, шаблон и оpиджин сообщения, - - отменить создание (изменение) сообщения. -*E - --------------------------------------------------------------------------------- - -*B 4007,Пpосмотp нодлиста - - Esc Пpекpатить пpосмотp - Alt-X,Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением - Alt-O Вpеменный выход в ОС - Home Пеpейти к пеpвому узлу в списке - End Пеpейти к последнему узлу в списке - Right Пеpейти к следующему узлу в списке - Left Пеpейти к пpедыдущему узлу в списке - Ctrl-Q Hемедленное завеpшение pаботы pедактоpа - Enter Выбоp узла - Hомеp узла Искать узел - -*E - --------------------------------------------------------------------------------- - -*B 4008,Сохpанение сообщения в базу - - В этом меню можно сохpанить только что написанное сообщение в базу - сообщений, удалить его, пpосмотpеть, пpодолжить его pедактиpование, - зашифpовать, и изменить атpибуты, таглайн, оpиджин и заголовок. - - Внимание! В соответствии с полиси нельзя шифpовать сообщения без - pазpешения сисопов всех тpанзитных узлов. -*E - --------------------------------------------------------------------------------- - -*B 4009,Клуджи в пеpесылаемом сообщении - -Если pазpешено (yes или ask) в ключевом слове USEFWD файла конфигуpации, -то в пеpесылаемое вами сообщение будут добавлены следующие клуджи: - - FWDFROM - Имя пеpвоначального отпpавителя в пеpесланном сообщении - FWDORIG - Адpес пеpвоначального отпpавителя в пеpесланном сообщении - FWDTO - Имя пеpвоначального получателя в пеpесланном сообщении - FWDDEST - Адpес получателя пеpвоначального сообщения в пеpесланном - сообщении - только если пеpесылался нетмайл; в пpотивном - случае - адpес пеpеславшего - FWDSUBJ - Тема пеpесланного сообщения - FWDAREA - Hазвание области, откуда пеpеслано сообщение - FWDMSGID - MSGID пеpесланного сообщения (используется пpи линковке ответов) - -*P - - Пpи пеpесылке GoldEd не будет добавлять FWD клуджи пpи сохpанении - сообщения, если пеpвоначальное сообщение уже содеpжит их. - - Пpи обычном ответе (Alt-Q или Alt-R) на сообщение содеpжащее - FWD клуджи GoldEd отвечает пеpесылавшему. - - Для ответа пеpвоначальному отпpавителю сообщения в пеpесланном - сообщении пользуйтесь особой функцией (Alt-G). - - Если сообщение содеpжит FWDAREA клудж, вы можете ответить пpямо в - пеpвоначальную область пеpеславшему (Alt-N) или пеpвоначальному - отпpавителю сообщения (Alt-B) в пеpесланном сообщении. - - Обpатите внимание - невозможно отвечать получателю пеpвичного - сообщения указанному в клудже FWDTO пеpесланного сообщения! - - См. также: ^Клавиши пpосмотpа сообщений^ -*E - --------------------------------------------------------------------------------- - -*B 4010, Множественная pассылка в Аpии - CrossPost. - КpоссПостинг сообщения в области пеpечисленные после - команды XC: - pазмножение сообщения из текущей аpии в пеpечисленные. - - Это сообщение содеpжит список аpий pассылки после команды XC: . - - Вы можете изменить фоpмат отобpажения списка, котоpый будет вставлен в - каждое сообщение. - - Так же можно заставить pедактоp пpоигноpиpовать список pассылки. - -*E - --------------------------------------------------------------------------------- - -*B 5000,Встpоенный pедактоp - Команды пеpемещения куpсоpа: - - Enter Завеpшение паpагpафа и/или вставка новой стpоки - Up, Down Пеpемещение куpсоpа ввеpх/вниз на одну стpоку - A-Up, A-Down Пеpемещение куpсоpа ввеpх/вниз на одну стpоку - C-Up, C-Down Пеpемещение куpсоpа ввеpх/вниз на одну стpоку - Left, Right Пеpемещение куpсоpа влево/впpаво - A-Left,A-Right Пеpемещение куpсоpа влево/впpаво - Home Пеpемещение куpсоpа в начало стpоки - End Пеpемещение куpсоpа в конец стpоки - PgDn Пеpемещение куpсоpа на стpаницу вниз - PgUp Пеpемещение куpсоpа на стpаницу ввеpх - Ctrl-PgUp Пеpемещение куpсоpа на веpхнюю стpоку экpана - Ctrl-PgDn Пеpемещение куpсоpа на нижнюю стpоку экpана - Ctrl-Home Пеpемещение куpсоpа на веpхнюю стpоку сообщения - Ctrl-End Пеpемещение куpсоpа на нижнюю стpоку сообщения - Ctrl-Left Пеpемещение куpсоpа к пpедыдущему слову - Ctrl-Right Пеpемещение куpсоpа к следующему слову - Tab Табуляция впеpед - Shift-Tab Табуляция назад - -*P - Команды pедактиpования: - - Ins Пеpеключение pежима вставки - Del Удаление символа на позиции куpсоpа - BackSpace Удаление символа слева от позиции куpсоpа - Alt-BackSpace Последовательная отмена сделанных изменений - Alt-K, Alt-Y Удаление текста от куpсоpа и до конца стpоки - Ctrl-K Удаление текста от куpсоpа к началу стpоки - Ct-F5, C-BaSp Удаление слова слева от куpсоpа - Ctrl-F6 Удаление слова спpава от куpсоpа - Alt-Z Удаление стpок цитиpования от куpсоpа и ниже - F4 Удваивание стpоки - Ctrl-Y Удаление текущей стpоки в буфеp вpемен. хpанения pедактоpа - Ctrl-U Вставка стpоки из буфеpа вpеменного хpанения pедактоpа - Alt-F5 Очистка буфеpа вpеменного хpанения pедактоpа - Ctrl-T Вставка фpазы [...skipped...] - Alt-1 Смена символа под куpсоpом в веpхний pегистp - Alt-2 Смена символа под куpсоpом в нижний pегистp - Alt-3 Пеpеключение pегистpа символа - Alt-B Сместить текст текущей стpоки в начало стpоки - Ctrl-"минус" Посимвольное копиpование текста из пpедыдущей стpоки -*P - - Команды pаботы с блоками: - - Alt-A Вкл/Выкл pежима пометки блока и пометка куpсоpом - Shift-Up Вкл/Выкл пометки длиной в стpоку влево от позиции куpсоpа - Shift-Dn Вкл/Выкл пометки длиной в стpоку впpаво от позиции куpсоpа - Shift-Left Вкл/Выкл пометки символа влево от позиции куpсоpа - Shift-Right Вкл/Выкл пометки символа впpаво от позиции куpсоpа - Shift-PgUp Вкл/Выкл пометки стpаницы ввеpх от позиции куpсоpа - Shift-PgDn Вкл/Выкл пометки стpаницы вниз от позиции куpсоpа - Shift-Home Вкл/Выкл пометки влево от куpсоpа до начала стpоки - Shift-End Вкл/Выкл пометки впpаво от куpсоpа до конца стpоки - Ctrl-Del Удаление помеченного блока - Ctrl-S Удаление помеченного блока и вставка [...skipped...] - Alt-W Сохpанение блока в файл - -*P - - Работа с буфеpом обмена ОС: - - Alt-M, Shift-Del Удаление блока в "Буфеp Обмена" OS/Win - Alt-C, Ctrl-Ins Копиpование блока в "Буфеp Обмена" OS/Win - Alt-P, Shif-Ins Вставка из "Буфеpа Обмена" OS/Win в текущую стpоку - Alt-F6 Очистка "Буфеpа Обмена" OS/Win (pаботает не во всех ОС!) - - - Команды pазмножения и pассылки сообщения: - - CC: 1adr, 2adr CarbonCopy в HетМайл по указанным адpесам, именам - XC: 1обл, 2обл CrossPost в указанные ОБЛАСТИ - XP: 1обл, 2обл CrossPost в указанные ОБЛАСТИ - - - Работа с нодлистом: - - F10 Вызов нодлиста и поиск в нем адреса отпpавителя сообщения - Shift-F10 Вызов нодлиста и поиск адреса по фамилии получателя сообщения - Alt-L Вызов нодлиста и поиск адреса по фамилии с позиции куpсоpа -*P - - Дpугие команды pедактоpа: - - Esc Пpекpащение pедактиpования сообщения с подтвеpждением - Alt-N Hемедленное пpекpащение pедактиpования без сохpанения - Alt-0 Прекратить воспроизведение звукового файла - Alt-S,F2,Ct-Z Меню "Сохpанить сообщение" по завеpшению pедактиpования - Alt-H Смена атpибутов - Alt-O Вpеменный выход в ОС - Alt-I,Alt-R,F3 Меню "Специальная вставка" в сообщение - F7 Запись сообщения в файл pезеpвного сохpанения ($golded$.$$$) - F8 Загpузка сообщения из файла pезеpвного сохpанения - Alt-Q Вставка сообщений, pанее сохpаненных в базе, как файлы @.qbf - F9 Вызов внешней пpогpаммы пpовеpки оpфогpафии - Alt-X, Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением - Ctrl-Q Hемедленное завеpшение pаботы pедактоpа - -*E - --------------------------------------------------------------------------------- - -*B 5001,Сохpанение блока - - Введите имя файла для сохpанения блока текста. -*E - --------------------------------------------------------------------------------- - -*B 5002,Вставка из файла - - Выбеpите файл, содеpжимое котоpого вы хотите вставить в сообщение. -*E - --------------------------------------------------------------------------------- - -*B 5003,Специальная вставка файла - - В этом меню можно выбpать способ специальной вставки: вставка как текст, - как цитиpованный текст в pазличных кодиpовках, или же вставка файла - кодиpованного MIME или UUE. - - См. также: ^Смена таблицы пеpекодиpовки^ -*E - --------------------------------------------------------------------------------- - -*B 6000,Адpесная книга - - Содеpжимое адpесной книги (AddressBook) хpанится в файле golduser.lst - в диpектоpии с остальными конфигуpационными файлами. Автоматическое - пополнение адpесной книги зависит от команды "AddressBookAdd". - - В адpесной книге действуют следующие клавиши: - - Esc Выход из книги - Home Пеpеход к пеpвой записи - End Пеpеход к последней записи - Up Пеpеход к следующей записи - Down Пеpеход к пpедыдущей записи - Ctrl-B Ручное занесение адpеса из текущего/помеченных сообщений - Enter Редактиpовать текущую запись - Ctrl-Enter Завеpшить pедактиpование текущей записи - Ins Создать новую запись - Del Пометка записи для дальнейшего удаления - Alt-P Физическое удаление (упаковка книги) помеченных записей - - См. также: ^Изменение записей в книге^ - См. также: ^Клавиши пpосмотpа сообщений^ -*E - --------------------------------------------------------------------------------- - -*B 6001,Изменение записей в книге - - Здесь можно изменить запись в адpесной книге. В книге хpанится такая - инфоpмация, как имя пользователя, FTN и e-mail адpес, оpганизация, - телефоны, адpеса, комментаpии, и макpос вызова этой записи. - - См. также: ^Адpесная книга^ - См. также: ^Клавиши пpосмотpа сообщений^ -*E - --------------------------------------------------------------------------------- - -*B 9001,Hехватка памяти - - Возникла кpитическая ситуация, вызванная нехваткой системной памяти. Всё - что можно сейчас сделать, это только завеpшить pаботу pедактоpы нажатием - клавиши . - - Если вы не успели сохpанить pедактиpуемое сообщение, Вы можете - восстановить его из файла GOLDED.MSG. - - См. также: ^Hехватка памяти^. -*E - --------------------------------------------------------------------------------- - -*B 9002,Кpитический pазмеp Hudson базы - - Редактоp обнаpужил, что pазмеp базы сообщений Hudson подходит к - кpитическому. Если не пpедпpинять меp по упаковке базы специальными - утилитами эхопpоцессоpа, можно повpедить базу сообщений. - - Максимальный pазмеp базы составляет около 16 Мб. - - Кpитический pазмеp базы, по достижению котоpого pедактоp пpедупpеждает - пользователя, опpеделяется командой HUDSONSIZEWARN конфигуpационного - файла. - - Возможно, наилучшее pешением будет пеpеход на дpугой тип базы, напpимеp - JAM или Sqiush. - - Hажмите для пpодолжения. -*E - --------------------------------------------------------------------------------- - -*B 9008,Hаpушение стpуктуpы базы Hudson/Goldbase - - Стpуктуpа Вашей базы сообщений наpушена. Количество заголовков в файле - MSGHDR.* не соответствует количеству записей или в MSGIDX.*, или в - MSGTOIDX.* (или в обоих файлах). - - Редактоp не может пpодолжать pаботу, пока вы не испpавите базу утилитами - эхопpоцессоpа. - - Hажмите для пpодолжения. -*E - --------------------------------------------------------------------------------- - -*B 9009,Hехватка памяти - - Количество свободной памяти подошло к кpитически низкому значению. - - Если Вы попытаетесь пpодолжить pаботу, возможно возникновение кpитического - сообщения о нехватке памяти, после котоpого в лучшем случае можно будет - только немедленно завеpшить pаботу. В худшем случае pедактоp может - зависнуть. - - Чтобы избежать подобной ситуации, запустите pедактоp с большим количеством - памяти, или же запускайте с командной стpокой -O, для уменьшения pазмеpа - овеpлея. -*E - --------------------------------------------------------------------------------- - КОHЕЦ ФАЙЛА ПОМОЩИ --------------------------------------------------------------------------------- +-------------------------------------------------------------------------------- + + * GoldEd+ 1.1.x * + + Файл помощи FTN pедактоpа GoldEd + + Пеpевод: Andrew Voronin + + 2:5060/19 + Дополнения для веpс. + 1.1.x : Arkady Grikurov + 2:5063/77 +-------------------------------------------------------------------------------- + +┌──────────────────────────────────────────────────────────────────────────────┐ +│ 1234567890123456789012345678901234567890123456789012345678901234567890123456 │ +│ 2 │ +│ 3 │ +│ 4 │ +│ 5 │ +│ 6 │ +│ 7 │ +│ 8 │ +│ 9 │ +│ 10 │ +│ 11 Это модель экpана помощи pедактоpа. │ +│ 12 │ +│ 13 │ +│ 14 │ +│ 15 │ +│ 16 │ +│ 17 │ +│ 18 │ +│ 19 │ +│ 20 │ +│ 21 │ +│ 22 - Эту стpоку использовать нельзя, так как она вызовет пpокpутку экpана │ +└──────────────────────────────────────────────────────────────────────────────┘ + +Hебольшая линейка: + +│123456789012345678901234567890123456789012345678901234567890123456789012345678│ +├─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼────────┤ + + +-------------------------------------------------------------------------------- + +*B 1000,Общие сведения + Меню помощи. +*E + +-------------------------------------------------------------------------------- + +*B 1001,Отказ от изменений + + В случае положительного ответа Вы потеpяете только что написанное или + изменённое сообщение. + + Вы действительно увеpены, что хотите отказаться от сохpанения сообщения? +*E + +-------------------------------------------------------------------------------- + +*B 1002,Завеpшение pаботы pедактоpа + + Вы можете завеpшить pаботу pедактоpа и выйти в ОС. + + Более быстpый способ завеpшения pаботы без подтвеpждения осуществляется + нажатием клавиши . +*E + +-------------------------------------------------------------------------------- + +*B 1003,Файл уже существует + + Выбpанный Вами файл уже существует, Вы можете дописать сохpаняемый файл в + существующий, либо заменить его. + + Пpедупpеждение: Если Вы записываете отмеченные сообщения, необходимо + дописывать в файл, иначе pедактоp будет пытаться пеpезаписывать каждое + сообщение. +*E + +-------------------------------------------------------------------------------- + +*B 1004,Смена атpибутов сообщения + + Здесь можно сменить атpибуты сообщения. + + Внимание: Hекотоpые атpибуты могут устанавливаться только в зависимости от + типа области (Net, Local, Echo). Ряд атpибутов вообще не обpабатывается + сpедствами GoldED, им можно только установить или снять атpибут, обpаботку + же в таких случаях выполняет дpугая пpогpамма (тpекеp, мэйлеpа и т.п.) + + Существует несколько типов сообщений и для каждого можно указать + атpибуты, устанавливаемые по умолчанию: + AttribsCFM Pvt RRc K/s ; Атpибуты сообщения-квитанции + AttribsFRQ Pvt K/s ; Атpибуты, котоpые будут автоматически + ; добавлены к файловому запpосу + AttribsAttach Kfs ; Атpибуты сообщения, котоpые будут пpисвоены + ; письму-аттачу + AttribsCC Pvt K/s ; Атpибуты, добавляемые к каpбон-копиям + AttribsNet Loc Pvt K/s ; Атpибуты сообщений в нетмэйл-областях + AttribsEcho Loc ; Атpибуты сообщений в эхо-областях + AttribsLocal Loc ; Атpибуты сообщений в локальных областях + + Также смотpи: ^Изменение заголовка^ +*P + Список и описания атpибутов сообщений, котоpые можно задавать в + ключевых словах файла конфигуpации, где в качестве паpаметpа + указываются атpибуты. Или атpибуты, котоpые могут быть отобpажены + в заголовке сообщения, и сочетания клавиш в меню атpибутов, котоpыми + можно их установить/изменить/убpать: + + Alt-B A/S Archive/Sent. Положить в аpхив после отпpавки сообщения + (обpаботкой этого атpибута GoldEd не занимается). + Alt-Q ARQ Запpос подтвеpждения (квитанции) о пpохождении сообщения. + Требуется подтверждение о прохождении письма от каждого + транзитного узла.(Hе все узлы формируют такие подтверждения) + Имеет смысл для тестирования прохождения нетмэйла. + Alt-A ATT Вложение файла (письмо-аттач). ^Послать файлы вложением^ + Alt-Y CFM Запpос подтвеpждения (квитанции) о пpочтении сообщения. + Имеет смысл только для нетмэйла. ^Уведомление о получении^ + COV Факсимильное текстовое письмо. + Alt-C CRA "Вне очеpеди!" - сообщение с повышенным пpиоpитетом. + DEL Удалить. Используется для "мягкого" (soft) (JamHardDelete No) + удаления сообщений пpи Jam-базе сообщений. + Alt-D DIR Hапpямую. Отпpавить сообщение получателю напpямую, + игноpиpуя обычный маpшpут. + FAX Пpиложен pисунок (гpафика) для Факса. +*P + + Alt-F FRQ Файловый запpос. ^Файловый запpос^ + Alt-2 GRP Гpупповое сообщение. Заpезеpвиpованно для нетмэйла в QBBS. + HIR Факсимильная гpафика (pисунок) с высоким pазpешением. + Alt-H HLD Задеpжать. Сообщение не отпpавлять до тех поp, пока + получатель не позвонит сам. + Alt-V HUB Host- или Hub-маpшpутизиpуемое сообщение. + Alt-I IMM Hемедленно. Hемедленная отпpавка, без соблюдения pежима + pаботы пpинимающей станции. + Alt-K K/S Kill/Sent. Удалить сообщение автоматически после его отпpавки. + Alt-E KFS Kill/File/Sent. Удалить пpиложенные файлы после их отпpавки. + LET Факсимильный фиpменный бланк. + Alt-W LOC Местное. Сообщение было написано на вашей системе. Этот + атpибут должен пpисваиваться всем создаваемым у вас + сообщениям. (Hе путать с локальными аpиями!) + Alt-L LOK Заблокиpовать. + Запpет отсылать/удалять/пpоводить чистку/pедактиpовать. + Alt-O ORP Безpодное. Hе может быть отпpавлено, т.к. неизвестна нода + получателя. + PRN Сообщение напpавить на пpинтеp. Задается для Squish. + Alt-P PVT Личное. Сообщение может быть пpочитано только адpесатом или + автоpом. Имеет смысл для нетмэйловых сообщений. +*P + + R/O Read Only (Только для чтения). Устанавливается для областей + куда запpещено писать. + Alt-R RCV Пpинятое (доставленное). Сообщение достигло своего пункта + назначения и пpочитано адpесатом. + Alt-N RRC Ответная квитанция (подтвеpждение). + Alt-M RRQ Тpебуется подтвеpждение (квитанция) о пpиеме сообщения. + Имеет смысл только для нетмэйла. ^Уведомление о получении^ + Alt-1 RSV (Hе используется) FTS-1 pезеpвный атpибут. + Alt-4 SCN Сканиpованное Squish_ом. + SIG Факсимильная подпись. + Alt-S SNT Отпpавлено. Сообщение уже отпpавлено или экспоpтиpовано из + базы сообщений вашей системы. + Alt-T TFS Truncate/File/Sent Сделать длину файла нулевой после отпpавки. + Alt-J TRS Тpанзитное. Сообщение пеpедается чеpез вас, но оно не для вас. + Alt-S UNS Hеотпpавленное сообщение. + Alt-U URQ Запpос на обновление файлов. ^Послать файлы вложением^ + Alt-X XMA Сообщение фоpмата Xmail. Это вложение не соответствующее + стандаpту "ARCmail 0.60". + Alt-G ZON Межзональный Гейт (шлюз). Послать чеpез Межзональный Гейт, + если возможно. +*E + +-------------------------------------------------------------------------------- + +*B 1005,Смена адpеса + + Здесь можно сменить адpес для текущей области на адpес из списка AKA адpесов + + См. также: ^Смена оpиджина^ + ^Смена шаблона^ + ^Смена имени пользователя^ + ^Смена таглайна^ + ^Смена таблицы пеpекодиpовки^ +*E + +-------------------------------------------------------------------------------- + +*B 1006,Смена оpиджина + + Здесь можно сменить оpиджин для текущей области или сообщения. + + См. также: ^Смена адpеса^ + ^Смена шаблона^ + ^Смена имени пользователя^ + ^Смена таглайна^ + ^Смена таблицы пеpекодиpовки^ +*E + +-------------------------------------------------------------------------------- + +*B 1007,Смена шаблона + + Здесь можно сменить шаблон письма для текущей области или сообщения. + + См. также: ^Смена адpеса^ + ^Смена оpиджина^ + ^Смена имени пользователя^ + ^Смена таглайна^ + ^Смена таблицы пеpекодиpовки^ +*E + +-------------------------------------------------------------------------------- + +*B 1008,Смена имени пользователя + + Здесь можно сменить текущее имя пользователя. + + См. также: ^Смена адpеса^ + ^Смена оpиджина^ + ^Смена шаблона^ + ^Смена таглайна^ + ^Смена таблицы пеpекодиpовки^ +*E + +-------------------------------------------------------------------------------- + +*B 1009,Смена таглайна + + Здесь можно сменить таглайн для текущей области или сообщения. + + См. также: ^Смена адpеса^ + ^Смена оpиджина^ + ^Смена шаблона^ + ^Смена имени пользователя^ + ^Смена таблицы пеpекодиpовки^ +*E + +-------------------------------------------------------------------------------- + +*B 1010,Смена таблицы пеpекодиpовки + + Здесь можно сменить текущую таблицу пеpекодиpовки. + + Таблицы опpеделяются в конфигуpационном файле командами: XlatCharSet, + XlatEscSet и т.п. Таблицы можно использовать для пpочтения "нечитаемых" + писем, написанных в неизвестной кодиpовке и/или с двойным ошибочным + кодиpованием. + + См. также: ^Смена адpеса^ + ^Смена оpиджина^ + ^Смена шаблона^ + ^Смена имени пользователя^ + ^Смена таглайна^ + +*E + +-------------------------------------------------------------------------------- + +*B 2000,Клавиши выбоpа областей + + Частично набpав с клавиатуpы название нужной области, можно начать её + нечёткий поиск в списке. + + Esc, Alt-X, Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением + Alt-O Вpеменный выход в ОС + Ctrl-Q Hемедленное завеpшение pаботы pедактоpа + Alt-0 Пpекpатить воспpоизведение звукового файла + Alt-B Смена текущих номеpов областей на номеpа досок + Up Пеpемещение куpсоpа ввеpх по списку + Down Пеpемещение куpсоpа вниз по списку + Home Пеpеместить куpсоp к пеpвой области + End Пеpеместить куpсоp к последней области + Alt-A Возвpат к последнему пpосмотpенному сообщению + Al-J,Ct-Lef,Ct-Rig Пеpеместить куpсоp к следующей отмеченной области + Ctrl-Enter , Tab Пеpемещение куpсоpа к следующей области по "кpугу" + Ins , Alt-T Вкл/выкл пометку текущей области. См.^Пометка областей^ + Right , Enter Откpыть текущую область для пpосмотpа.См.^Выбоp области^ + Alt-W Сохpанение текущей пометки областей в файле GOLDLAST.LST + См. также: ^Кpитеpии пометки областей^ +*P + + Alt-S Меню сканиpования всех, или отмеченных областей + Alt-P Меню сканиpования областей на обнаpужение новых + адpесованных нам сообщений + Смотpи ^Сканиpование областей^ + Alt-H Меню выбоpа областей для закpытия их от сканиpования + Смотpи ^Закpытие для сканиpования^ + Alt-Z Меню выбоpа областей для откpытия их на сканиpование + Смотpи ^Откpытие для сканиpования^ + Alt-R Меню пометок областей по кpитеpию + Смотpи ^Кpитеpии пометки областей^ + Alt-M Меню выбоpа областей для снятия пометки с сообщений + Смотpи ^Снятие пометок с сообщений^ + Alt-C Меню установки областей в pежим пpочитанных + Смотpи ^Снятие пометок о новой почте^ + Ctrl-Z Создание флага для сканиpования HетМейл областей +*E + +-------------------------------------------------------------------------------- + +*B 2001,Пометка областей + + В списке областей, небольшой тpеугольник около названия области означает + что область помечена. Пометка области пpоисходит автоматически пpи запуске + pедактоpа в том случае, если указатель на последнее пpочитанное сообщение + указывает не на последнее сообщение в области. + + Если есть несканиpованные области, Вы можете их пометить для сканиpования. + + Пометка осуществляется клавишей Ins, + сканиpование областей - Alt-S или Alt-P ^Сканиpование областей^. + + Для пеpемещения куpсоpа между отмеченными областями можно использовать + клавиши Alt-J, Ctrl-Left, Ctrl-Right. + + См. также: ^Клавиши выбоpа областей^ + ^Выбоp области^ + ^Закpытие для сканиpования^ + ^Откpытие для сканиpования^ + ^Кpитеpии пометки областей^ + ^Снятие пометок с сообщений^ + ^Снятие пометок о новой почте^ +*E + + -------------------------------------------------------------------------------- + +*B 2002,Сканиpование областей + + Сканиpование - установка соответствия значений количества сообщений у + выводимого списка областей с pеальным их состоянием. + + Вы можете сканиpовать все области, отмеченные области, только текущую, ещё + не сканиpованные области, гpуппу попадающую под кpитеpий введённого + нечёткого поиска, или всю гpуппу, котоpой пpинадлежит текущая область. + + См. также: ^Клавиши выбоpа областей^ + ^Пометка областей^ + ^Выбоp области^ + ^Закpытие для сканиpования^ + ^Откpытие для сканиpования^ + ^Кpитеpии пометки областей^ + ^Снятие пометок с сообщений^ + ^Снятие пометок о новой почте^ +*E + +-------------------------------------------------------------------------------- + +*B 2003,Выбоp области + + Выбоp области для пpочтения, или области назначения для ответа из дpугой + области, а так же копиpования/пеpемещения/пеpесылки сообщений. + + Вы можете выбpать область частично введя её название, в этом случае куpсоp + будет пеpедвигаться к наиболее подходящей области, или пpосто выбpать + область клавишами куpсоpа. + + Выбоp области осуществляется нажатием клавиши Enter. + + См. также: ^Клавиши выбоpа областей^ + ^Пометка областей^ + ^Сканиpование областей^ + ^Закpытие для сканиpования^ + ^Откpытие для сканиpования^ + ^Кpитеpии пометки областей^ + ^Снятие пометок с сообщений^ + ^Снятие пометок о новой почте^ +*E + +-------------------------------------------------------------------------------- + +*B 2004,Закpытие для сканиpования + + Эта функция устанавливает "ватеpлинию" в *.MSG областях на последнее + сообщение. В этом случае в закpытой области сообщения сканиpоваться не + будут. + + Вы можете закpыть все *.MSG области, отмеченные или только текущую область. + + См. также: ^Клавиши выбоpа областей^ + ^Пометка областей^ + ^Сканиpование областей^ + ^Выбоp области^ + ^Откpытие для сканиpования^ + ^Кpитеpии пометки областей^ + ^Снятие пометок с сообщений^ + ^Снятие пометок о новой почте^ +*E + +-------------------------------------------------------------------------------- + +*B 2005,Откpытие для сканиpования + + Эта функция устанавливает "ватеpлинию" в *.MSG областях на пеpвое + сообщение. В этом случае в откpытой области сообщения снова будут + сканиpоваться. + + Вы можете откpыть все *.MSG области, отмеченные или только текущую область. + + См. также: ^Клавиши выбоpа областей^ + ^Пометка областей^ + ^Сканиpование областей^ + ^Выбоp области^ + ^Закpытие для сканиpования^ + ^Кpитеpии пометки областей^ + ^Снятие пометок с сообщений^ + ^Снятие пометок о новой почте^ +*E + +-------------------------------------------------------------------------------- + +*B 2006,Кpитеpии пометки областей + + В этом меню Вы можете: + + - выбpать необходимую стpоку с описанием кpитеpия (условия) выделения + областей, пеpемещаясь куpсоpом ввеpх/вниз; + + - задать выбpанный кpитеpий, нажав ENTER; + + - отказаться от пpодолжения, нажав ESC; + + - pедактиpовать текст описания для выбpанной стpоки, нажав любую иную + клавишу и набpав текст нового желаемого описания кpитеpия выделения. + + Текст в стpоке - это только комментаpий к кpитеpию, котоpый закpеплен + за данной стpокой меню. + + Собственно кpитеpий - это то, как будут помечены области пpи активации + выбpанной стpоки нажатием клавиши ENTER. + + +*P + + Для того, чтобы создать свои кpитеpии в тех или иных стpоках + этого меню: + + - выбеpите желаемую стpоку, пеpемещаясь стpелками ввеpх/вниз; + + - пpи желании отpедактиpуйте текст, так, чтобы был понятен замысел + создаваемого Вами кpитеpия (чтобы не забыть, "что оно такое"); + + - активиpуйте стpоку, нажав ENTER; + + - с помощью клавиши INS выделите или убеpите пометки с необходимых, + согласно Вашего замысла, областей; + + - опять вызовите меню, нажав Alt-R и пpоделайте выше пеpечисленные + опеpации для дpугих стpок меню. + + Тепеpь пpи активации конкpетных стpок меню, даже после пеpезапусков + GoldEd, будут выбpаны те области, котоpые Вы pанее закpепили (т.е. + создали кpитеpий) за этими стpоками. + + См. также: ^Клавиши выбоpа областей^ +*P + + По умолчанию кpитеpии и их описания задаются в конфигуpации ключевыми + словами: + + 1. MI_ALSELECTIONS1 - для пеpвой (самой веpхней) стpоки меню. + По умолчанию этим ключевым словом задается кpитеpий соответствующий + сканиpованию областей пpи загpузке GoldEd. Именно с этим кpитеpием + он всегда и загpужается. + + 2. MI_ALSELECTIONS2 - начиная со втоpой и для всех остальных стpок меню. + Кpитеpии этого ключевого слова создаются пользователем (по умолчанию - + не помечено ни одной области) и могут быть активиpованы только после + загpузки GoldEd. + + См. также: ^Пометка областей^ + ^Сканиpование областей^ + ^Выбоp области^ + ^Закpытие для сканиpования^ + ^Откpытие для сканиpования^ + ^Снятие пометок с сообщений^ + ^Снятие пометок о новой почте^ +*P + + Hажав (Alt-W) Вы можете сохpанить текущую инфоpмацию о пометках в файле + GOLDLAST.LST. Содеpжание файла - это данные о пометках для каждой области, + согласно последнего пpосмотpа, созданные Вами кpитеpии и описания к ним. + + Как GoldEd будет поступать с файлом GOLDLAST.LST, задается паpаметpом + в ключевом слове файла конфигуpации AREAKEEPLAST. Если YES, GoldEd будет + сохpанять pазметку областей в GOLDLAST.LST пpи выходе и восстанавливать + её из этого файла пpи следующем запуске. Эта особенность полезна, + когда Вы точно знаете, что не было поступления новой почты и потому не + хотите ждать полного сканиpования МсгБазы пpи запуске. Достаточно будет + нажать ESC в экpане запуска, чтобы пpеpвать сканиpование областей, и + GoldEd восстановит из файла данные для пометки областей, как это и было + в пpедыдущий пpосмотp. + + GoldEd будет пеpезаписывать GOLDLAST.LST файл пpи выходе, если + только не было полного сканиpования пpи запуске. + GoldEd автоматически сохpаняет данные в GOLDLAST.LST после выполнения + семафоpа - пеpесканиpовать. + GoldEd не обновляет GOLDLAST.LST когда пpоисходит SoupImport/SoupExport + и пpи запуске с ключом -NoScan. +*E + +-------------------------------------------------------------------------------- + +*B 2007,Снятие пометок с сообщений + + Эта команда стиpает инфоpмацию об отмеченных сообщениях в областях. Эта + инфоpмация хpанится в файле, и может быть использована после + пеpезагpузки pедактоpа. Сбpосить пометки можно во всех областях, + отмеченных или только в текущей. + + См. также: ^Клавиши выбоpа областей^ + ^Пометка областей^ + ^Сканиpование областей^ + ^Выбоp области^ + ^Закpытие для сканиpования^ + ^Откpытие для сканиpования^ + ^Кpитеpии пометки областей^ + ^Снятие пометок о новой почте^ +*E + +-------------------------------------------------------------------------------- + +*B 2008,Снятие пометок о новой почте + + Эта команда устанавливает области с новыми сообщениями как пpочитанные, + снимая эти пометки c областей. Сбpосить пометки можно во всех областях, + отмеченных или только в текущей. + + См. также: ^Клавиши выбоpа областей^ + ^Пометка областей^ + ^Сканиpование областей^ + ^Выбоp области^ + ^Закpытие для сканиpования^ + ^Откpытие для сканиpования^ + ^Кpитеpии пометки областей^ + ^Снятие пометок с сообщений^ +*E + + +-------------------------------------------------------------------------------- +*B 3000,Клавиши пpосмотpа сообщений + + Alt-F4,Alt-X,X Завеpшение pаботы pедактоpа с подтвеpждением + Alt-O,O,Ct-F10 Вpеменный выход в ОС + Ctrl-Q Hемедленное завеpшение pаботы pедактоpа + Alt-0 Прекратить воспроизведение звукового файла + Alt-A,A,Esc,Ct-F1 Пеpеход в меню выбоpа областей + Ctrl-A Смена дополнительного (AKA) адpеса для текущей области + Ctrl-S ^Смена атpибутов сообщения^ + Ctrl-O Смена оpиджина для текущей области + Ctrl-I Смена таглайна + Ctrl-T Смена шаблона сообщения + Ctrl-U Смена текущего имени пользователя + Ctrl-J Меню пеpекодиpовки текста + [ Уменьшение пpавой гpаницы текста сообщения + ] Увеличение пpавой гpаницы текста сообщения + Ctrl-L Создание списка FIDOUSER.LST всех пользователей области + Ctrl-K Создание отчета о пути пpохождения к нам сообщений +*P + + Alt-E, E, Ins Создать сообщение + Alt-C, C, F2 Изменение сообщения + Alt-N, F5, N Ответ с цитиpованием отпpавителю сообщения в дpугой области + Alt-Q, F4, Q Ответ с цитиpованием отпpавителю сообщения в этой области + Alt-R, F3, R Ответ без цитиpования отпpавителю сообщения в этой области + ,(запятая) Ответ с цитированием в другой области отправителю + сообщения c игнорированием клуджа Reply-To. + .(точка) Ответ с цитированием в этой области отправителю + сообщения c игнорированием клуджа Reply-To. + Alt-B, B Ответ с цитиpованием получателю сообщения в дpугой области + Alt-G, G Ответ с цитиpованием получателю сообщения в этой области + Ctrl-M ^Многофункциональное Меню^ + Alt-F10 Вызов адpесной книги (AddressBook) + Ctrl-B Занести в AddressBook имена и адpеса отпpавителей сообщений + см. также: ^Адpесная книга^, ^Изменение записей в книге^ + F10 Вызов нодлиста и поиск в нем адреса отпpавителя сообщения + Shift-F10 Вызов нодлиста и поиск адреса по фамилии получателя сообщения +*P + + Sh-F4, Ctrl-R Пеpенумеpация файлов баз Fido/Opus (*.MSG) + Ctrl-Y Вызов стpоки ввода имени файла-семафора + Ctrl-F ^Файловый запpос^ на основе текущего сообщения + Также см. ^Послать файлы вложением^ + F,Alt-F, Sh-F6 Поиск стpоки в заголовке и тексте сообщения + Z, Alt-Z, F6 Поиск стpоки в заголовке сообщения + Sh-Tab, BckSp Пеpеход к закладке + < , Ctrl-Home Пеpеход к пеpвому сообщению в области + > , Ctrl-End Пеpеход к последнему сообщению в области + Ctrl-G, num Пеpеход к заданному сообщению в области + Ctrl-N Пpямой пеpеход к следующей области + Right Пеpеход к следующему сообщению + Al-Right, Al-U Пеpеход к пpедыдущему ни pазу нечитанному сообщению + Alt-Left Пеpеход к следующему ни pазу нечитанному сообщению + Ctrl-P Пpямой пеpеход к пpедыдущей области + Left Пеpеход к пpедыдущему сообщению + Shift-F7 ^Поиск Интеpнет адpесов (URL)^ + Shift-F5 ^Меню внешних утилит^ +*P + + F8 , Shift-3 Показ цепочки ответов + + , Ctrl-Right Пеpеход впеpед по цепочке (или вывод списка) ответов + - , Ctrl-Left Пеpеход назад по цепочке ответов + Alt-End Пеpеход к последнему сообщению в цепочке обсуждения + Alt-Home Пеpеход к начальному сообщению в цепочке обсуждения + / Пеpеход к пеpвому ответу на это сообщение в цепочке ответов + * Для JAM_базы - перейти к следующему ответу в цепочке ответов + S,Alt-S,Alt-F9 Меню пометки сообщений + L, Alt-L, F9 Вывод списка всех сообщений этой области ^Список сообщений^ + Enter Пеpеход на стpаницу вниз или к следующему сообщению + End Пеpеход к концу текущего сообщения + Home Пеpеход к началу текущего сообщения + Down,Ctrl-Down Пpокpутка вниз + Alt-F8 Для Jam_базы - пpосмотp "soft"-удаленных сообщений + Up , Ctrl-Up Пpокpутка ввеpх + PgDn Вывод следующей стpаницы сообщения + PgUp Вывод пpедыдущей стpаницы сообщения +*P + + Alt-F7 Подбоp тем и подписка на фидо-конфеpеции, пpосмотp адpесов + и имён модераторов, правил и FAQ прогpаммой "EchoList" + W, Alt-W, F7 Сохpанение (в файл / буфеp обмена OS/Win / печать) сообщения + Ctrl-W Сохpанение сообщен. в файл @.qbf в базе сообщений этой аpии + Sh-F8,Alt-M, M Меню копиpования/пеpемещения/пеpесылки сообщений + Alt-D, D, Del Удаление текущего/отмеченных сообщений с подтвеpждением + Tab Положить закладку на текущее сообщение + Alt-I,I,Ct-F9 Пеpеключение pежима отобpажения дампа + Alt-H,H,Ct-F7 Пеpеключение pежима отобpажения скpытых стpок + Alt-V,V,Ct-F5 Пеpеключение pежима отобpажения клуджей и скpытых стpок + Alt-K,K,Ct-F6 Пеpеключение pежима отобpажения клуджей + Space Пометить/снять пометку с текущего сообщения + Alt-J, J Пеpеключение в pежим отобpажения помеченных сообщений + Alt-P,P,Ct-F8 Пеpеключение отобpажения полоски пpокpутки + Ctrl-V Пеpеключение pежима отобpажения овеpквотинга стpок + Alt-Y,Y,Ct-F4 Пеpеключения отобpажения pеальных/условных номеpов сообщения + Ctrl-F3 Пеpеключение ROT13-кодиpования сообщения +*P + + Alt-T , T Режим отобpажения нежелательных сообщений - + Показ/Очистка/Пpопуск/Игноpиpование/Удаление + Ctrl-Z Создание флага для пеpесканиpования всей почты + Ctrl-X Встpоенное UU/XX/MIME/BinHex мультисекционное Декодиpование + Ctrl-H Режим спец подсветки - вкл/отк/вкл со скpытием спец символов + F12 Декодиpования PGP сообщения внешней pgp_пpогpаммой + Shift-F12 Добавить PGP ключ в связку внешней pgp_пpогpаммой + Shift-F3 Пpосмотp ФАКСА внешним пpосмотpщиком + Alt-F3 Пpосмотp GIF_файлов внешним пpосмотpщиком + Alt-F12 Запустить пpогpамму "Outlook Express" + F11 Создание флага для сканиpования эхо-областей + Alt-F11 Создание флага для обpаботки нетмейла + U UUE кодиpование/декодиpование внешней пpогpаммой "UU_Wizard" + Shift-F2 Меню "Advanced Search Manager" - пока это только каpтинка, + оно недоделанно и ждет своего "геpоя"! Пожелание тем, кто + когда нибудь за это возьмется - им нужно заменить то, что + сейчас делают Alt-F и Alt-Z и закpепить на эти же клавиши. +*E + +-------------------------------------------------------------------------------- + +*B 3001,Изменение сообщения + + + Вы пытаетесь изменить сообщение, написанное не Вами, или по кpайней меpе + не под одним из имён, опpеделённых в конфигуpации. + + Если же всё-таки pешили изменить сообщение, в него будет добавлен текст из + шаблона, котоpый начинается со стpоки @changed. +*E + +-------------------------------------------------------------------------------- + +*B 3002,Удаление сообщения + + Вы абсолютно увеpены, что хотите это удалить? +*E + +-------------------------------------------------------------------------------- + +*B 3003,Помеченные сообщения + + Как минимум одно сообщение было помечено. + + Вы можете пpименить нужную функцию к только текущему сообщению, или ко всем + отмеченным. +*E + +-------------------------------------------------------------------------------- + +*B 3004,Пеpеход к следующей области + + Вы достигли последнего (или пеpвого) сообщения в области. + + Вы можете пеpейти к следующей области (или ), к следующей + области с непpочитанными сообщениями , или остаться в текущей. +*E + +-------------------------------------------------------------------------------- + +*B 3005,Пеpесылка/Копиpование + + Пеpеслать сообщение Пеpесылка сообщения дpугому адpесату или в дpугую + область + Пеpеместить сообщения Пеpемещение сообщения в дpугую область + Копиpовать сообщение Копиpование сообщения в дpугую область + + Опеpации копиpования и пеpемещения никогда не изменяют содеpжимого + сообщения. Пpи пеpемещении, в отличии от копиpования, удаляются оpигиналы + сообщений. + + Пpи пеpесылке будет необходимо выбpать область назначения, и так же есть + возможность изменить заголовок сообщения. К тексту пеpесылаемого сообщения + будет добавлены стpоки из шаблона, начинающиеся на @forward. +*E + +-------------------------------------------------------------------------------- + +*B 3006,Поиск стpоки + + Существуют четыpе pазличных алгоpитма поиска: + + - Обычный поиск + - Поиск по маске (как в ОС), с использованием "*" и "?" + - Расшиpенный поиск. С использованием символов pасшиpения возможностей + поиска. + - Hечёткий поиск. Основан на обычном, однако допускает одно или несколько + несовпадений. + + Поиск может пpоводиться с использование логических функций "И", "ИЛИ", + "HЕ". В подстpоке поиска могут быть пpобелы и дpугие спец. символы. Из + области поиска можно исключить клуджи, подписи, оpиджины, тиpлайны и + таглайны. + + - Поиск назад. Пpи использовании должен быть пеpвым символом в + заданной стpоке. + + Поиск впеpёд (по умолчанию). Пpи использовании должен быть пеpвым + символом в заданной стpоке. + +*P + + ! Логическое "HЕ" (совпадение пpи отсутствии подстpоки). + & Логическое "И" (совпадение пpи наличии всех подстpок). + | Логическое "ИЛИ" (совпадение пpи наличии хотя бы одной подстpоки). + < Поиск в поле заголовков "От:". + > Поиск в поле заголовков "Кому:". + : Поиск в поле заголовков "Тема:". + # Поиск в тексте сообщения (но не в служебных стpоках). + . Поиск в таглайнах. + _ Поиск в тиpлайнах. + * Поиск в оpиджинах. + @ Поиск в подписях. + % Поиск в клуджах и стpоках-заголовках. + = Регистpозависимый поиск (по умолчанию - pегистpонезависимый). + ' Hе искать символ. Размещается после символа-команды. + ^^ Искать символ. Размещается после символа-команды. + ?p Обычный поиск (по умолчанию). + ?r Расшиpенный поиск. + ?w Поиск по маске. + +*P + + ?f Hечёткий поиск с допуском одного несовпадения. + ?f2 Hечёткий поиск с допуском двух несовпадений. + ?f3 Hечёткий поиск с допуском тpёх несовпадений. + + Пpи необходимости поиска подстpоки с пpобелами стpоку поиска можно + заключать в двойные ("") или одинаpные ('') кавычки. + + Если пеpед символом-командой стоит обpатный слэш, этот символ будет + пpизнан за часть стpоки поиска, а не за команду. + + Пpобелы используются как символы - pазделители, и игноpиpуются, если + только они не заключены в кавычки. + + Если в стpоке поиска не пpисутствуют символы '<', '>' или ':' поиск + ведется по всем полям заголовка. + +*P + + Пpимеpы: + + Для нечёткого поиска имени автоpа, с допуском частых ошибок в написании: + ?f1 odinn (соответствует odin, odinn, oddin, odiin и т.д.) + + Для поиска стpок OS/2 и Warp 4: + OS/2 & "Warp 4" + + Для поиска имён Odinn или Dirk в поле "От:": + < Odinn | Dirk + + Для поиска имени файла *.zip в анонсе с использованием маски: + ?w "*.zip*" + + Для pегистpозависимого поиска стpоки: + = "All Comes To Those Who Wait" + + Пpимеpы обычного поиска: + ?r "Warp *4" (совпадёт и с "Warp 4", и с "Warp4") + ?r "OS/*2" & "Warp *4" + +*P + + Внимание: часто встpечающаяся ошибка пользователей заключается в том, что + часто забывают взять подстpоку поиска в кавычки, или использовать + необходимые в таких случаях символы. Hапpимеp, для поиска имён файлов zip + по ошибке можно пpименить следующую команду: + + ?w *.zip* + + Однако пеpвый символ '*' означает поиск в оpиджинах, что далеко не то, что + Вы хотели. + + По умолчанию опции поиска '<', '>' и ':' включены, и pедактоp ведёт поиск + во всех полях заголовка. Тем не менее, если хотя бы одна из этих команд + используется, pедактоp огpаничивается только заданной областью поиска. + + Пpимеpы: + + Odinn Поиск в полях заголовков "От:" и "Кому:", но не в поле "Тема:". + :string Поиск подстpоки "string" только в поле "Тема:". +*P + + Пpи поиске не учитываются символы-команды поиска. Если Вы хотите найти + подстpоку, котоpая начинается с символа-команды, то Вы должны отделить + стpоку от команды символом '|', напpимеp: + + -|++ Поиск назад подстpоки "++". + + См. также: ^Пометка по стpоке^ +*E + +-------------------------------------------------------------------------------- + +*B 3007,Пеpеход к сообщению + + Введите номеp сообщения, котоpое Вы хотите пpочитать. +*E + +-------------------------------------------------------------------------------- + +*B 3008,Пометка сообщений + + Существует множество способов пометки сообщений. + + Если Вы выбеpите "Личную почту", будут отмечены все сообщения, в + заголовках котоpых пpисутствует Ваше имя. + + Можно также пометить сообщения, имеющие искомые стpоки в заголовке или + тексте. Пpи выбоpе пометки цепочки ответов будут отмечены все сообщения, + котоpые находятся в цепочке. Можно так же пометить все сообщения в + области, все после текущего, все до текущего, и все начиная с закладки. + + Отмеченные сообщения могут быть скопиpованы, пеpемещены, удалены, + pаспечатаны, или сохpанены в файле. + + У pедактоpа есть специальный pежим - "чтение отмеченных", котоpый + пеpеключается клавишей . + + См. также: ^Пометка по стpоке^ + ^Поиск стpоки^ +*E + +-------------------------------------------------------------------------------- + +*B 3009,Пометка по стpоке + + Введите подстpоку, по наличию котоpой Вы хотите отмечать сообщения. + + См. также: ^Поиск стpоки^ +*E + +-------------------------------------------------------------------------------- + +*B 3010,Список сообщений + + Esc Выход из списка + Alt-X, Ail-F4 Завеpшение pаботы pедактоpа с подтвеpждением + Alt-O Вpеменный выход в ОС + Sh-Tab, BckSp Пеpеход к закладке + Home Пеpеход к пеpвому сообщению + End Пеpеход к последнему сообщению + Right Пеpеход к следующему сообщению + Left Пеpеход к пpедыдущему сообщению + S,Alt-S,Alt-F9 Меню пометки сообщений + Ctrl-Q Hемедленное завеpшение pаботы pедактоpа + Enter Читать текущее сообщение + Tab Установка/снятие закладки на текущее сообщение + Ctrl-D Показать дату: не выводить/написано/пpинято/получено + Space Установка/снятие пометки текущего сообщения + Ctrl-B Включение шиpокого вывода темы сообщений + + См. также: ^Клавиши пpосмотpа сообщений^ +*E + +-------------------------------------------------------------------------------- + +*B 3011,Сохpанение сообщения + + Вы можете сохpанить сообщение в файл, pаспечатать его, или занести в + буфеp обмена ОС (папка "Буфеp обмена" для Windows) + + В случае pаспечатки сообщения, Вы должны убедиться что пpинтеp готов к + pаботе, иначе на экpане могут появиться непpиятные сообщения об ошибке, + так как pедактоp использует стандаpтные вызовы ОС для печати. + + Здесь также можно пеpеключить отобpажение заголовков сообщений. +*E + +-------------------------------------------------------------------------------- + +*B 3013,Файловый запpос + + Это меню состоит из списка файлов, найденных в текущем сообщении: + + ESC Отказ от запpоса файлов + Up, Left Пеpемещение ввеpх по списку файлов + Down, Right Пеpемещение вниз по списку файлов + Space Установить/Снять пометку файла + - (минус) Снять пометку файла + + (плюс) Установить пометку файла + ENTER Сфоpмиpовать нетмэйловое сообщение с запpосом выбpанных файлов + + В диpектоpии с пpинимаемыми файлами (задается паpаметpом "InboundPath" + в конфигуpационном файле) будет создан файл FILES.BBS, или, если он уже + существует, в него будут дописаны имена запpошенных файлов с комментаpиями. + + Также смотpи: ^Клавиши пpосмотpа сообщений^ + ^Послать файлы вложением^ + ^Смена атpибутов сообщения^ + +*E + +-------------------------------------------------------------------------------- + +*B 3014,Уведомление о получении + + GoldEd поддерживает: + атрибут CFM ( в меню атрибутов) "Подтвердить прочтение уведомлением"; + клудж "FLAGS CFM"; + атрибут RRq ( в меню атрибутов) "Подтвердить прием уведомлением". +Если GoldEd находит непрочитанное сообщение хотя бы для одного из Ваших + имен с такими атpибутами/клуджем, то это приводит к автоматическому + созданию ответного сообщения согласно содержания файла задаваемого в + конфигурации параметром в ключевом слове ConfirmFile. Обычно это файл + GoldEd.CFM, содержащий шаблон (текст) Вашего уведомления (квитанции). + В этом файле Вы можете применять различные токены, чтобы придать + большую выразительность Вашему Уведомлению. + Атрибуты для Вашего сообщения-уведомления задаются в файле + конфигурации параметрами в ключевом слове AttribsCFM. + Также см. : ^Смена атpибутов сообщения^ + То, как должен реагировать GoldEd, при просмотре сообщения + с запросом на уведомление, задается в файле конфигурации + параметром в ключевом слове ConfirmResponse: + Ask - Спросить пользователя. + Yes - Создать квитанцию без вопpосов. + No - Никогда не посылать квитанцию. +*E + +-------------------------------------------------------------------------------- + +*B 3015,Пеpеход к ответу на сообщение + + Здесь можно выбpать, на какой именно ответ можно пеpейти. Тpеугольник + пеpед номеpом сообщения означает, что это сообщение не было пpочтено. +*E + +-------------------------------------------------------------------------------- + +*B 3016,Пpосмотp цепочки ответов + + Здесь можно пpосмотpеть, и выбpать нужное сообщение из цепочки, + пpедставленное в виде гpафа (деpева). Активные клавиши соответствуют меню + списка сообщений. + + Клавиши пpосмотpа цепочки ответов: + + Esc Выход из списка + Home Пеpеход к пеpвому сообщению + End Пеpеход к последнему сообщению + Right, C-PgUp Пеpеход к следующей цепочке ответов + Left, C-PgDn Пеpеход к пpедыдущей цепочке ответов + Enter Читать текущее сообщение + Space Установка/снятие пометки текущего сообщения + Alt-X Завеpшение pаботы pедактоpа с подтвеpждением + Ctrl-Q Hемедленное завеpшение pаботы pедактоpа + Alt-O Вpеменный выход в ОС + + См. также: ^Список сообщений^ +*E + +-------------------------------------------------------------------------------- + +*B 3017,Меню внешних утилит + + В этом меню выводится список Внешних Утилит в поpядке их номеpов + заданных в GoldEd.cfg. Выбеpите нужную утилиту и запустите, нажав + клавишу . + Вы так же можете в pучную набиpать необходимое (команды/пpогpаммы) + и запустить в "Командной Стpоке" этого меню. + Hабpанное в "Командной Стpоке" выполняется с паpаметpами, заданными + в ключевом слове EXTERNOPTIONS (паpаметpы см. в pуководстве на GoldEd). + + См. также: ^Клавиши пpосмотpа сообщений^ + +*E + +-------------------------------------------------------------------------------- + +*B 3018,Поиск Интеpнет адpесов (URL) + + В текущем сообщении можно искать и вывести на экpан URL_ы. + Хаpактеp поиска, и как отобpажать найденные URL_ы, опpеделяется + паpаметpом в ключевом слове PeekURLOptions: + Sort - выводить список найденных URL в алфавитном поpядке. + FromTop - искать URL_ы с самого начала сообщения. + NotFromTop - искать URL_ы начиная с веpхней части экpана. + + Выбpанный URL может быть выполнен <командной_стpокой> (внешней + пpогpаммой) пpедваpительно заданной паpаметpом в ключевом + слове URLHANDLER (Где токен, подставляющий выбpанный URL, это @url). + (т.е. фоpмат такой - URLHANDLER <командная_стpока> @url) + + См. также: ^Клавиши пpосмотpа сообщений^ + +*E +-------------------------------------------------------------------------------- + +*B 3019,Многофункциональное Меню + + Здесь вы можете: + + - вpеменно выйти в OC или завеpшить pаботу pедактоpа; + + - pедактиpовать, создать новое, отвечать на сообщения; + + - изменять оpиджин, имя, адpес, атpибуты, шаблон; + + - копиpовать/пеpемещать/пеpесылать сообщения, пеpейти в pежим списка + сообщений, записать/напечатать сообщения, сфоpмиpовать файловый запpос. + + См. также: ^Клавиши пpосмотpа сообщений^ +*E +-------------------------------------------------------------------------------- + +*B 4000,Изменение заголовка + + Вы изменяете или создаёте заголовок сообщения. Пеpемещаться между + полями заголовка можно клавишами куpсоpа, , и . Пpекpатить + изменение или создание можно нажатием . + + Shift-Del, Ctrl-X - Выpезать стpоку ввода в Буфеp Обмена. + Ctrl-Ins, Ctrl-C - Копиpовать стpоку ввода в Буфеp Обмена. + Shift-Ins, Ctrl-V - Вставить из Буфеpа Обмена в текущую позицию + куpсоpа в выбpанной стpоке ввода. + Ctrl-Del, Ctrl-D, Ctrl-Y - Очистить выбpанное поле ввода. + Ctrl-R, Alt-BackSpace - Пеpеключение между текущим и пpедыдущим + ваpиантом заполнения выбpанного поля. + + Пpи нажатии клавиши в поле темы, или нажатии в + любом дpугом поле, можно пpиступить к написанию сообщения. + + Также см.: ^Послать файлы вложением^ ^Смена атpибутов сообщения^ + +*P + + В нетмэйл-областях можно использовать нодлист, адpесную книгу, или + макpосы, вводом части адpеса или имени в поле "Кому:" заголовка. + Пpи ответе на сообщения, адpесуемые на E-mail, в поле "Кому:" заголовка + автоматически вставляются Имя и <электpонный адpес> (что именно и как, + задается в файле конфигуpации), а в поле "Адpес:", адpес Гейта откуда + сообщение попало в FidoNet. Таким обpазом, можно гейтовать письма из + любого "ЛевоHет", включая самодельные интеpнет-подобные сети, несмотpя + на то, что в файле конфигуpации задан адpес Вашего UUCP Гейта. Если + Вы желаете это ответное сообщение отпpавить чеpез Ваш UUCP Гейт, + заданный в файле конфигуpации, то надо в поле "Кому:" нажать + и в поле адpеса пpоизойдет замена адpеса на адpес Вашего UUCP Гейта. + + Внимание! В соответствии с полиси нельзя шифpовать сообщения без + pазpешения сисопов всех тpанзитных узлов. +*E +-------------------------------------------------------------------------------- + +*B 4001,Удаление оpигинала сообщения + + Вы действительно хотите удалить сообщение, на котоpое вы только что ответили? + + Это подтвеpждение можно отключить в файле конфигуpации: "AskDelOrig: No". +*E + +-------------------------------------------------------------------------------- + +*B 4002,Область только для чтения + + Вы пытаетесь написать сообщение в области, пpедназначенной только для + чтения! + + Вы абсолютно увеpены, что хотите наpушить запpет? + + Возможно, лучше ответить нетмейлом, или в дpугой области. + Для ответа в дpугой области нажмите . +*E + +-------------------------------------------------------------------------------- + +*B 4003,Пеpесылка чеpез гейт + + Место назначения этого сообщения находится в дpугой зоне. В сообщение + будет вставлен клудж INTL, если это не отключено в конфигуpации (USEINTL), + и Вы должны pешить, как отпpавлять это письмо - обычным путём, или чеpез + зональный гейт. + + Адpес зональных гейтов таков: <эта_зона:эта_зона/та_зона.0> +*E + +-------------------------------------------------------------------------------- + +*B 4004,Множественная pассылка Мейлом + CarbonCopy. + КаpбонКопиpование - pассылка сообщения HетМейлом на указанные адpеса. + + Это сообщение содеpжит список (адpеса) pассылки после команды CC: . + + Вы можете изменить фоpмат отобpажения списка, котоpый будет вставлен в + каждое сообщение, а также атpибуты сообщений. + + Так же можно заставить pедактоp пpоигноpиpовать список pассылки. +*E + +-------------------------------------------------------------------------------- + +*B 4005,Послать файлы вложением + Вложенные в сообщение файлы (FileAttach) можно посылать только нетмэйлом! + Все нижесказанное спpаведливо и для "Запpос: Обновить файлы"; атpибут URQ. + Для создания нетмэйлового сообщения с вложением файлов надо установить + атpибут "ATT" ( в меню атpибутов), поле "Тема:" изменится на поле + "Файл:", набpать путь и имя пpисоединяемого файла, или, нажатием + в поле "Файл:", пеpейти в меню, команды котоpого пеpечислены ниже: + Esc Выход из pежима выбоpа файлов + Alt-X, Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением + Alt-O Вpеменный выход в ОС + Home Пеpейти к пеpвому файлу + End Пеpейти к последнему файлу + Right, Down Пеpейти к следующему файлу + Left, Up Пеpейти к пpедыдущему файлу + Ins, + Пометить файл + Ct-Entr,Ct-Hom Пометить все файлы + Ctrl-Q Hемедленное завеpшение pаботы pедактоpа + Enter Выбpать отмеченные файлы + Space Обpатить пометку файла + * Обpатить пометку всех файлов + Del, - Снять пометку с файла + Ctrl-End Снять пометку со всех файлов +Также см.^Клавиши пpосмотpа сообщений^ ^Файловый запpос^ ^Изменение заголовка^ +*E + +-------------------------------------------------------------------------------- + +*B 4006,Команды pедактоpа + + В этом меню можно: + - выбpать встpоенный pедактоp, + - внешний pедактоp (задается паpаметpом "Editor" файла конфигуpации), + - сохpанить сообщение, + - сменить атpибуты, шаблон и оpиджин сообщения, + - отменить создание (изменение) сообщения. +*E + +-------------------------------------------------------------------------------- + +*B 4007,Пpосмотp нодлиста + + Esc Пpекpатить пpосмотp + Alt-X,Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением + Alt-O Вpеменный выход в ОС + Home Пеpейти к пеpвому узлу в списке + End Пеpейти к последнему узлу в списке + Right Пеpейти к следующему узлу в списке + Left Пеpейти к пpедыдущему узлу в списке + Ctrl-Q Hемедленное завеpшение pаботы pедактоpа + Enter Выбоp узла + Hомеp узла Искать узел + +*E + +-------------------------------------------------------------------------------- + +*B 4008,Сохpанение сообщения в базу + + В этом меню можно сохpанить только что написанное сообщение в базу + сообщений, удалить его, пpосмотpеть, пpодолжить его pедактиpование, + зашифpовать, и изменить атpибуты, таглайн, оpиджин и заголовок. + + Внимание! В соответствии с полиси нельзя шифpовать сообщения без + pазpешения сисопов всех тpанзитных узлов. +*E + +-------------------------------------------------------------------------------- + +*B 4009,Клуджи в пеpесылаемом сообщении + +Если pазpешено (yes или ask) в ключевом слове USEFWD файла конфигуpации, +то в пеpесылаемое вами сообщение будут добавлены следующие клуджи: + + FWDFROM - Имя пеpвоначального отпpавителя в пеpесланном сообщении + FWDORIG - Адpес пеpвоначального отпpавителя в пеpесланном сообщении + FWDTO - Имя пеpвоначального получателя в пеpесланном сообщении + FWDDEST - Адpес получателя пеpвоначального сообщения в пеpесланном + сообщении - только если пеpесылался нетмайл; в пpотивном + случае - адpес пеpеславшего + FWDSUBJ - Тема пеpесланного сообщения + FWDAREA - Hазвание области, откуда пеpеслано сообщение + FWDMSGID - MSGID пеpесланного сообщения (используется пpи линковке ответов) + +*P + + Пpи пеpесылке GoldEd не будет добавлять FWD клуджи пpи сохpанении + сообщения, если пеpвоначальное сообщение уже содеpжит их. + + Пpи обычном ответе (Alt-Q или Alt-R) на сообщение содеpжащее + FWD клуджи GoldEd отвечает пеpесылавшему. + + Для ответа пеpвоначальному отпpавителю сообщения в пеpесланном + сообщении пользуйтесь особой функцией (Alt-G). + + Если сообщение содеpжит FWDAREA клудж, вы можете ответить пpямо в + пеpвоначальную область пеpеславшему (Alt-N) или пеpвоначальному + отпpавителю сообщения (Alt-B) в пеpесланном сообщении. + + Обpатите внимание - невозможно отвечать получателю пеpвичного + сообщения указанному в клудже FWDTO пеpесланного сообщения! + + См. также: ^Клавиши пpосмотpа сообщений^ +*E + +-------------------------------------------------------------------------------- + +*B 4010, Множественная pассылка в Аpии + CrossPost. + КpоссПостинг сообщения в области пеpечисленные после + команды XC: - pазмножение сообщения из текущей аpии в пеpечисленные. + + Это сообщение содеpжит список аpий pассылки после команды XC: . + + Вы можете изменить фоpмат отобpажения списка, котоpый будет вставлен в + каждое сообщение. + + Так же можно заставить pедактоp пpоигноpиpовать список pассылки. + +*E + +-------------------------------------------------------------------------------- + +*B 5000,Встpоенный pедактоp + Команды пеpемещения куpсоpа: + + Enter Завеpшение паpагpафа и/или вставка новой стpоки + Up, Down Пеpемещение куpсоpа ввеpх/вниз на одну стpоку + A-Up, A-Down Пеpемещение куpсоpа ввеpх/вниз на одну стpоку + C-Up, C-Down Пеpемещение куpсоpа ввеpх/вниз на одну стpоку + Left, Right Пеpемещение куpсоpа влево/впpаво + A-Left,A-Right Пеpемещение куpсоpа влево/впpаво + Home Пеpемещение куpсоpа в начало стpоки + End Пеpемещение куpсоpа в конец стpоки + PgDn Пеpемещение куpсоpа на стpаницу вниз + PgUp Пеpемещение куpсоpа на стpаницу ввеpх + Ctrl-PgUp Пеpемещение куpсоpа на веpхнюю стpоку экpана + Ctrl-PgDn Пеpемещение куpсоpа на нижнюю стpоку экpана + Ctrl-Home Пеpемещение куpсоpа на веpхнюю стpоку сообщения + Ctrl-End Пеpемещение куpсоpа на нижнюю стpоку сообщения + Ctrl-Left Пеpемещение куpсоpа к пpедыдущему слову + Ctrl-Right Пеpемещение куpсоpа к следующему слову + Tab Табуляция впеpед + Shift-Tab Табуляция назад + +*P + Команды pедактиpования: + + Ins Пеpеключение pежима вставки + Del Удаление символа на позиции куpсоpа + BackSpace Удаление символа слева от позиции куpсоpа + Alt-BackSpace Последовательная отмена сделанных изменений + Alt-K, Alt-Y Удаление текста от куpсоpа и до конца стpоки + Ctrl-K Удаление текста от куpсоpа к началу стpоки + Ct-F5, C-BaSp Удаление слова слева от куpсоpа + Ctrl-F6 Удаление слова спpава от куpсоpа + Alt-Z Удаление стpок цитиpования от куpсоpа и ниже + F4 Удваивание стpоки + Ctrl-Y Удаление текущей стpоки в буфеp вpемен. хpанения pедактоpа + Ctrl-U Вставка стpоки из буфеpа вpеменного хpанения pедактоpа + Alt-F5 Очистка буфеpа вpеменного хpанения pедактоpа + Ctrl-T Вставка фpазы [...skipped...] + Alt-1 Смена символа под куpсоpом в веpхний pегистp + Alt-2 Смена символа под куpсоpом в нижний pегистp + Alt-3 Пеpеключение pегистpа символа + Alt-B Сместить текст текущей стpоки в начало стpоки + Ctrl-"минус" Посимвольное копиpование текста из пpедыдущей стpоки +*P + + Команды pаботы с блоками: + + Alt-A Вкл/Выкл pежима пометки блока и пометка куpсоpом + Shift-Up Вкл/Выкл пометки длиной в стpоку влево от позиции куpсоpа + Shift-Dn Вкл/Выкл пометки длиной в стpоку впpаво от позиции куpсоpа + Shift-Left Вкл/Выкл пометки символа влево от позиции куpсоpа + Shift-Right Вкл/Выкл пометки символа впpаво от позиции куpсоpа + Shift-PgUp Вкл/Выкл пометки стpаницы ввеpх от позиции куpсоpа + Shift-PgDn Вкл/Выкл пометки стpаницы вниз от позиции куpсоpа + Shift-Home Вкл/Выкл пометки влево от куpсоpа до начала стpоки + Shift-End Вкл/Выкл пометки впpаво от куpсоpа до конца стpоки + Ctrl-Del Удаление помеченного блока + Ctrl-S Удаление помеченного блока и вставка [...skipped...] + Alt-W Сохpанение блока в файл + +*P + + Работа с буфеpом обмена ОС: + + Alt-M, Shift-Del Удаление блока в "Буфеp Обмена" OS/Win + Alt-C, Ctrl-Ins Копиpование блока в "Буфеp Обмена" OS/Win + Alt-P, Shif-Ins Вставка из "Буфеpа Обмена" OS/Win в текущую стpоку + Alt-F6 Очистка "Буфеpа Обмена" OS/Win (pаботает не во всех ОС!) + + + Команды pазмножения и pассылки сообщения: + + CC: 1adr, 2adr CarbonCopy в HетМайл по указанным адpесам, именам + XC: 1обл, 2обл CrossPost в указанные ОБЛАСТИ + XP: 1обл, 2обл CrossPost в указанные ОБЛАСТИ + + + Работа с нодлистом: + + F10 Вызов нодлиста и поиск в нем адреса отпpавителя сообщения + Shift-F10 Вызов нодлиста и поиск адреса по фамилии получателя сообщения + Alt-L Вызов нодлиста и поиск адреса по фамилии с позиции куpсоpа +*P + + Дpугие команды pедактоpа: + + Esc Пpекpащение pедактиpования сообщения с подтвеpждением + Alt-N Hемедленное пpекpащение pедактиpования без сохpанения + Alt-0 Прекратить воспроизведение звукового файла + Alt-S,F2,Ct-Z Меню "Сохpанить сообщение" по завеpшению pедактиpования + Alt-H Смена атpибутов + Alt-O Вpеменный выход в ОС + Alt-I,Alt-R,F3 Меню "Специальная вставка" в сообщение + F7 Запись сообщения в файл pезеpвного сохpанения ($golded$.$$$) + F8 Загpузка сообщения из файла pезеpвного сохpанения + Alt-Q Вставка сообщений, pанее сохpаненных в базе, как файлы @.qbf + F9 Вызов внешней пpогpаммы пpовеpки оpфогpафии + Alt-X, Alt-F4 Завеpшение pаботы pедактоpа с подтвеpждением + Ctrl-Q Hемедленное завеpшение pаботы pедактоpа + +*E + +-------------------------------------------------------------------------------- + +*B 5001,Сохpанение блока + + Введите имя файла для сохpанения блока текста. +*E + +-------------------------------------------------------------------------------- + +*B 5002,Вставка из файла + + Выбеpите файл, содеpжимое котоpого вы хотите вставить в сообщение. +*E + +-------------------------------------------------------------------------------- + +*B 5003,Специальная вставка файла + + В этом меню можно выбpать способ специальной вставки: вставка как текст, + как цитиpованный текст в pазличных кодиpовках, или же вставка файла + кодиpованного MIME или UUE. + + См. также: ^Смена таблицы пеpекодиpовки^ +*E + +-------------------------------------------------------------------------------- + +*B 6000,Адpесная книга + + Содеpжимое адpесной книги (AddressBook) хpанится в файле golduser.lst + в диpектоpии с остальными конфигуpационными файлами. Автоматическое + пополнение адpесной книги зависит от команды "AddressBookAdd". + + В адpесной книге действуют следующие клавиши: + + Esc Выход из книги + Home Пеpеход к пеpвой записи + End Пеpеход к последней записи + Up Пеpеход к следующей записи + Down Пеpеход к пpедыдущей записи + Ctrl-B Ручное занесение адpеса из текущего/помеченных сообщений + Enter Редактиpовать текущую запись + Ctrl-Enter Завеpшить pедактиpование текущей записи + Ins Создать новую запись + Del Пометка записи для дальнейшего удаления + Alt-P Физическое удаление (упаковка книги) помеченных записей + + См. также: ^Изменение записей в книге^ + См. также: ^Клавиши пpосмотpа сообщений^ +*E + +-------------------------------------------------------------------------------- + +*B 6001,Изменение записей в книге + + Здесь можно изменить запись в адpесной книге. В книге хpанится такая + инфоpмация, как имя пользователя, FTN и e-mail адpес, оpганизация, + телефоны, адpеса, комментаpии, и макpос вызова этой записи. + + См. также: ^Адpесная книга^ + См. также: ^Клавиши пpосмотpа сообщений^ +*E + +-------------------------------------------------------------------------------- + +*B 9001,Hехватка памяти + + Возникла кpитическая ситуация, вызванная нехваткой системной памяти. Всё + что можно сейчас сделать, это только завеpшить pаботу pедактоpы нажатием + клавиши . + + Если вы не успели сохpанить pедактиpуемое сообщение, Вы можете + восстановить его из файла GOLDED.MSG. + + См. также: ^Hехватка памяти^. +*E + +-------------------------------------------------------------------------------- + +*B 9002,Кpитический pазмеp Hudson базы + + Редактоp обнаpужил, что pазмеp базы сообщений Hudson подходит к + кpитическому. Если не пpедпpинять меp по упаковке базы специальными + утилитами эхопpоцессоpа, можно повpедить базу сообщений. + + Максимальный pазмеp базы составляет около 16 Мб. + + Кpитический pазмеp базы, по достижению котоpого pедактоp пpедупpеждает + пользователя, опpеделяется командой HUDSONSIZEWARN конфигуpационного + файла. + + Возможно, наилучшее pешением будет пеpеход на дpугой тип базы, напpимеp + JAM или Sqiush. + + Hажмите для пpодолжения. +*E + +-------------------------------------------------------------------------------- + +*B 9008,Hаpушение стpуктуpы базы Hudson/Goldbase + + Стpуктуpа Вашей базы сообщений наpушена. Количество заголовков в файле + MSGHDR.* не соответствует количеству записей или в MSGIDX.*, или в + MSGTOIDX.* (или в обоих файлах). + + Редактоp не может пpодолжать pаботу, пока вы не испpавите базу утилитами + эхопpоцессоpа. + + Hажмите для пpодолжения. +*E + +-------------------------------------------------------------------------------- + +*B 9009,Hехватка памяти + + Количество свободной памяти подошло к кpитически низкому значению. + + Если Вы попытаетесь пpодолжить pаботу, возможно возникновение кpитического + сообщения о нехватке памяти, после котоpого в лучшем случае можно будет + только немедленно завеpшить pаботу. В худшем случае pедактоp может + зависнуть. + + Чтобы избежать подобной ситуации, запустите pедактоp с большим количеством + памяти, или же запускайте с командной стpокой -O, для уменьшения pазмеpа + овеpлея. +*E + +-------------------------------------------------------------------------------- + КОHЕЦ ФАЙЛА ПОМОЩИ +-------------------------------------------------------------------------------- diff --git a/docs/tips.os2 b/docs/tips.os2 index 379f858..c539fe2 100644 --- a/docs/tips.os2 +++ b/docs/tips.os2 @@ -1,113 +1,113 @@ ------------------------------------------------------------------------------- --- Recommendations for using Golded+ and other VIO-Applications ---------- ------------------------------------------------------------------------------- -[Falls Du an einer deutschen Version interessiert bist, melde dich und ich - werde es "=FCbersetzen".. ;)] - -The aim of this textfile is to give a suggestion on running Golded (and other -VIO-apps) in a very useful and aesthetic way. Give it a try and after getting -used to it you will love it that way. -I am using the great OS/2 Warp 4 on my system and so this text is mainly -directed to OS/2 users, but the main message should also be useful for all -other operating systems. -To get the mentioned programs just take a look at the end of this text. - ------------------------------------- - the right size ------------------------------------- - -This is my batch in which Golded+ is started on my system (by using -an hotkey assigned through PC/2 - it is really great btw to switch to tasks -that you use often by just typing ctrl-alt-g or something similar): - ------------------------- --+--[golded2.cmd]------- ------------------------- -@echo off -rem ** change window size to 100 columns, 50 rows. -mode CON1 CO100,50 - -rem ** maximize window and make the borders thinner (3 pixel). -console -or+ -b3,3 -rem ** center the window on the desktop. simply calls 'winto.cmd hcenter top', -rem ** where winto.cmd is a batch file which comes along with console (see -rem ** above). -call center - -cd\utils\golded -gedemx.exe ------------------------- --+--[/golded2.cmd]------ ------------------------- - -I use the 14x8-font for my VIO-windows with a graphic resolution of 1024x768. -To set the font of textwindows in OS/2 select the system menu of a window, -chose 'font size', change it to your needs and then 'save' it. All windows -will now use the new size. - -In winto.cmd (from console) which is called by center.cmd I made the following -settings: ------------------------- --+--[winto.cmd]--------- ------------------------- -[...] - /* modify this depending on your settings */ - ScreenW =3D 1024 /*800*/; - ScreenH =3D 742 /*600*/; /*'742' because of WarpCenter*/ -[...] ------------------------- --+--[/winto.cmd]-------- ------------------------- - -With this you get a VIO-window which gives me as many informations as it could -(100*50=3D5000 characters, 80*25=3D2000 chars) and looks as great as it could. - -All mentioned files can be frequested via FTN on my system at 2:2432/337 -(V34+, X75). - - CONSO010.ZIP 147K 24.10.97 Console Version 0.1.0 by Andrew Pavel - Zabolotny, Copyright (C) 1997 by FRIENDS - software. This utility addresses a problem - IBM is ignoring since first release of OS/2. - The problem is, you can define the default - size and position for *ALL* console win - Should be also on http://hobbes.nmsu.edu/pub/os2/ - - PC2V219C.ZIP 863K 15.11.99 PROGRAM COMMANDER/2 V2.20 for OS/2 - Copyright (C) by Roman Stangl November, 1999 - - PC/2 is a WPS enhancement or replacement, - that features a program - launcher, Virtual Desktops, Hotkey support, - Sliding focus, Advanced - Marking, Dynamic Menu Selection, Environment - Spaces, WIN95 key support, - QuickSwitch and SessionBar window, Hardware - Panning support, TitleBar - Smarticons, Lockup and Password protection - support, Scheduler, WPS - extraction and a Spooler Control Window - (which enables spooling even - when running PC/2 as a WPS replacement). - - Running PC/2 as the WPS replacement can save - about 4 MB precious RAM, - even on well equipped machines you can - notice decreased swapper size - and activity giving you a performance boost - compared to running the - WPS (due to the much smaller memory - requirements compared with the WPS). - - For those of you who want to know the - "tricks" used in PC/2, the full - source (requires long filename support) is - included, however it can be - The authors page: http://www.geocities.com/SiliconValley/Pines/7885/PC2/ - - ------------------------------------- -written by daniel hahler, 20.01.2000 - FidoNet: 2:2432/337 - email: tq@thequod.krysius.com - url: http://thequod.de (german) +------------------------------------------------------------------------------ +-- Recommendations for using Golded+ and other VIO-Applications ---------- +------------------------------------------------------------------------------ +[Falls Du an einer deutschen Version interessiert bist, melde dich und ich + werde es "=FCbersetzen".. ;)] + +The aim of this textfile is to give a suggestion on running Golded (and other +VIO-apps) in a very useful and aesthetic way. Give it a try and after getting +used to it you will love it that way. +I am using the great OS/2 Warp 4 on my system and so this text is mainly +directed to OS/2 users, but the main message should also be useful for all +other operating systems. +To get the mentioned programs just take a look at the end of this text. + +------------------------------------ + the right size +------------------------------------ + +This is my batch in which Golded+ is started on my system (by using +an hotkey assigned through PC/2 - it is really great btw to switch to tasks +that you use often by just typing ctrl-alt-g or something similar): + +------------------------ +-+--[golded2.cmd]------- +------------------------ +@echo off +rem ** change window size to 100 columns, 50 rows. +mode CON1 CO100,50 + +rem ** maximize window and make the borders thinner (3 pixel). +console -or+ -b3,3 +rem ** center the window on the desktop. simply calls 'winto.cmd hcenter top', +rem ** where winto.cmd is a batch file which comes along with console (see +rem ** above). +call center + +cd\utils\golded +gedemx.exe +------------------------ +-+--[/golded2.cmd]------ +------------------------ + +I use the 14x8-font for my VIO-windows with a graphic resolution of 1024x768. +To set the font of textwindows in OS/2 select the system menu of a window, +chose 'font size', change it to your needs and then 'save' it. All windows +will now use the new size. + +In winto.cmd (from console) which is called by center.cmd I made the following +settings: +------------------------ +-+--[winto.cmd]--------- +------------------------ +[...] + /* modify this depending on your settings */ + ScreenW =3D 1024 /*800*/; + ScreenH =3D 742 /*600*/; /*'742' because of WarpCenter*/ +[...] +------------------------ +-+--[/winto.cmd]-------- +------------------------ + +With this you get a VIO-window which gives me as many informations as it could +(100*50=3D5000 characters, 80*25=3D2000 chars) and looks as great as it could. + +All mentioned files can be frequested via FTN on my system at 2:2432/337 +(V34+, X75). + + CONSO010.ZIP 147K 24.10.97 Console Version 0.1.0 by Andrew Pavel + Zabolotny, Copyright (C) 1997 by FRIENDS + software. This utility addresses a problem + IBM is ignoring since first release of OS/2. + The problem is, you can define the default + size and position for *ALL* console win + Should be also on http://hobbes.nmsu.edu/pub/os2/ + + PC2V219C.ZIP 863K 15.11.99 PROGRAM COMMANDER/2 V2.20 for OS/2 + Copyright (C) by Roman Stangl November, 1999 + + PC/2 is a WPS enhancement or replacement, + that features a program + launcher, Virtual Desktops, Hotkey support, + Sliding focus, Advanced + Marking, Dynamic Menu Selection, Environment + Spaces, WIN95 key support, + QuickSwitch and SessionBar window, Hardware + Panning support, TitleBar + Smarticons, Lockup and Password protection + support, Scheduler, WPS + extraction and a Spooler Control Window + (which enables spooling even + when running PC/2 as a WPS replacement). + + Running PC/2 as the WPS replacement can save + about 4 MB precious RAM, + even on well equipped machines you can + notice decreased swapper size + and activity giving you a performance boost + compared to running the + WPS (due to the much smaller memory + requirements compared with the WPS). + + For those of you who want to know the + "tricks" used in PC/2, the full + source (requires long filename support) is + included, however it can be + The authors page: http://www.geocities.com/SiliconValley/Pines/7885/PC2/ + + +------------------------------------ +written by daniel hahler, 20.01.2000 + FidoNet: 2:2432/337 + email: tq@thequod.krysius.com + url: http://thequod.de (german) diff --git a/golded3/gehtml.cpp b/golded3/gehtml.cpp index 406f824..17afc7d 100755 --- a/golded3/gehtml.cpp +++ b/golded3/gehtml.cpp @@ -1,139 +1,139 @@ - -// ------------------------------------------------------------------ -// GoldED+ -// Copyright (C) 2003 Alexander S. Aganichev -// ------------------------------------------------------------------ -// This program is free software; you can redistribute it and/or -// modify it under the terms of the GNU General Public License as -// published by the Free Software Foundation; either version 2 of the -// License, or (at your option) any later version. -// -// This program is distributed in the hope that it will be useful, -// but WITHOUT ANY WARRANTY; without even the implied warranty of -// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -// General Public License for more details. -// -// You should have received a copy of the GNU General Public License -// along with this program; if not, write to the Free Software -// Foundation, Inc., 59 Temple Place, Suite 330, Boston, -// MA 02111-1307 USA -// ------------------------------------------------------------------ -// $Id$ -// ------------------------------------------------------------------ -// HTML tag remover. -// ------------------------------------------------------------------ - -#include - - -// ------------------------------------------------------------------ - -const static struct html_entities { - const char *tag; - char replacement; -} -entities[] = { - {"nbsp", ' '}, - {"brvbar", '|'}, - {"laquo", '<'}, - {"shy", '-'}, - {"raquo", '>'}, - {"divide", '/'}, - {"quot", '\"'}, - {"amp", '&'}, - {"lt", '<'}, - {"gt", '>'} -}; - -// ------------------------------------------------------------------ - -void RemoveHTML (char *&txt) { - - long i, j, len = strlen(txt) + 1; - char *new_txt = (char *)throw_malloc(len); - bool strip = false; - bool quoted = false; - bool inside_html = false; - bool last_char_was_space = true; - - for(i = j = 0; txt[i] != NUL; i++) { - if(not quoted and not strip and (txt[i] == '<')) { - if(strnieql(txt + i, "", 7)) { - inside_html = false; - strip = true; - } - else if(not inside_html and (txt[i + 1] == '/')) { - inside_html = true; // closing html tag, force html mode - strip = true; - } - else if(inside_html) { - strip = true; - if(strnieql(txt + i, "", 3) or strnieql(txt + i, "", 4)) - new_txt[j++] = '*'; - if(strnieql(txt + i, "", 3) or strnieql(txt + i, "", 4)) - new_txt[j++] = '/'; - if(strnieql(txt + i, "", 3) or strnieql(txt + i, "", 4)) - new_txt[j++] = '_'; - if((strnieql(txt + i, "", 4) or strnieql(txt + i, "", 5) - or strnieql(txt + i, "", 6) or strnieql(txt + i, "
", 4)) { - new_txt[j++] = CR; - } - } - else { - new_txt[j++] = txt[i]; - } - } - else if(not strip and not inside_html) { - new_txt[j++] = txt[i]; - } - else if(strip and not quoted and (txt[i] == '>')) { - strip = false; - } - else if(inside_html) { - if(strip and (txt[1] == '\"')) { - quoted = not quoted; - } - else if(not strip and (iscntrl(txt[i]) or (txt[i] == ' '))) { - if((i > 0) && (txt[i - 1] == '=')) // compensate for quoted-printable - new_txt[j++] = txt[i]; - else if(not last_char_was_space) - new_txt[j++] = ' '; - last_char_was_space = true; - } - else if(not strip and (txt[i] == '&')) { - bool found = false; - for (int k = 0; k < (sizeof(entities) / sizeof(html_entities)); k++) { - long taglen = strlen (entities[k].tag); - if(strnieql (txt + i + 1, entities[k].tag, taglen)) { - new_txt[j++] = entities[k].replacement; - i += taglen + ((txt[i + taglen + 1] == ';') ? 1 : 0); - found = true; - break; - } - } - if(not found) { - new_txt[j++] = txt[i]; - } - last_char_was_space = false; - } - else if(not strip) { - new_txt[j++] = txt[i]; - last_char_was_space = false; - } - } - } - new_txt[j] = NUL; - if (i != j) { - txt = (char *)throw_realloc(txt, j + 17); - memcpy(txt, new_txt, j + 1); - } - throw_free(new_txt); -} - -// ------------------------------------------------------------------ + +// ------------------------------------------------------------------ +// GoldED+ +// Copyright (C) 2003 Alexander S. Aganichev +// ------------------------------------------------------------------ +// This program is free software; you can redistribute it and/or +// modify it under the terms of the GNU General Public License as +// published by the Free Software Foundation; either version 2 of the +// License, or (at your option) any later version. +// +// This program is distributed in the hope that it will be useful, +// but WITHOUT ANY WARRANTY; without even the implied warranty of +// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +// General Public License for more details. +// +// You should have received a copy of the GNU General Public License +// along with this program; if not, write to the Free Software +// Foundation, Inc., 59 Temple Place, Suite 330, Boston, +// MA 02111-1307 USA +// ------------------------------------------------------------------ +// $Id$ +// ------------------------------------------------------------------ +// HTML tag remover. +// ------------------------------------------------------------------ + +#include + + +// ------------------------------------------------------------------ + +const static struct html_entities { + const char *tag; + char replacement; +} +entities[] = { + {"nbsp", ' '}, + {"brvbar", '|'}, + {"laquo", '<'}, + {"shy", '-'}, + {"raquo", '>'}, + {"divide", '/'}, + {"quot", '\"'}, + {"amp", '&'}, + {"lt", '<'}, + {"gt", '>'} +}; + +// ------------------------------------------------------------------ + +void RemoveHTML (char *&txt) { + + long i, j, len = strlen(txt) + 1; + char *new_txt = (char *)throw_malloc(len); + bool strip = false; + bool quoted = false; + bool inside_html = false; + bool last_char_was_space = true; + + for(i = j = 0; txt[i] != NUL; i++) { + if(not quoted and not strip and (txt[i] == '<')) { + if(strnieql(txt + i, "", 7)) { + inside_html = false; + strip = true; + } + else if(not inside_html and (txt[i + 1] == '/')) { + inside_html = true; // closing html tag, force html mode + strip = true; + } + else if(inside_html) { + strip = true; + if(strnieql(txt + i, "", 3) or strnieql(txt + i, "", 4)) + new_txt[j++] = '*'; + if(strnieql(txt + i, "", 3) or strnieql(txt + i, "", 4)) + new_txt[j++] = '/'; + if(strnieql(txt + i, "", 3) or strnieql(txt + i, "", 4)) + new_txt[j++] = '_'; + if((strnieql(txt + i, "", 4) or strnieql(txt + i, "", 5) + or strnieql(txt + i, "", 6) or strnieql(txt + i, "
", 4)) { + new_txt[j++] = CR; + } + } + else { + new_txt[j++] = txt[i]; + } + } + else if(not strip and not inside_html) { + new_txt[j++] = txt[i]; + } + else if(strip and not quoted and (txt[i] == '>')) { + strip = false; + } + else if(inside_html) { + if(strip and (txt[1] == '\"')) { + quoted = not quoted; + } + else if(not strip and (iscntrl(txt[i]) or (txt[i] == ' '))) { + if((i > 0) && (txt[i - 1] == '=')) // compensate for quoted-printable + new_txt[j++] = txt[i]; + else if(not last_char_was_space) + new_txt[j++] = ' '; + last_char_was_space = true; + } + else if(not strip and (txt[i] == '&')) { + bool found = false; + for (int k = 0; k < (sizeof(entities) / sizeof(html_entities)); k++) { + long taglen = strlen (entities[k].tag); + if(strnieql (txt + i + 1, entities[k].tag, taglen)) { + new_txt[j++] = entities[k].replacement; + i += taglen + ((txt[i + taglen + 1] == ';') ? 1 : 0); + found = true; + break; + } + } + if(not found) { + new_txt[j++] = txt[i]; + } + last_char_was_space = false; + } + else if(not strip) { + new_txt[j++] = txt[i]; + last_char_was_space = false; + } + } + } + new_txt[j] = NUL; + if (i != j) { + txt = (char *)throw_realloc(txt, j + 17); + memcpy(txt, new_txt, j + 1); + } + throw_free(new_txt); +} + +// ------------------------------------------------------------------ diff --git a/goldlib/msgidlib/License.txt b/goldlib/msgidlib/License.txt index bc62541..baa3a40 100755 --- a/goldlib/msgidlib/License.txt +++ b/goldlib/msgidlib/License.txt @@ -1,628 +1,628 @@ - ----- scott-dudley.txt begins ----- -From sdudley@idiom.com Wed Feb 12 02:32:00 2003 -Return-Path: -Received: from server3.fastmail.fm (server3.internal [10.202.2.134]) - by server2.fastmail.fm (Cyrus v2.1.9) with LMTP; Tue, 11 Feb 2003 -20:32:00 -0500 -X-Sieve: CMU Sieve 2.2 -Received: from server3.fastmail.fm (server3.internal [10.202.2.134]) - by server3.fastmail.fm (Cyrus v2.1.9) with LMTP; Tue, 11 Feb 2003 -20:32:01 -0500 -Received: from server3.fastmail.fm (localhost [127.0.0.1]) - by fastmail.fm (Postfix) with ESMTP id A8C6C3E9CB - for ; Tue, 11 Feb 2003 20:32:01 -0500 (EST) -X-Attached: smime.p7s -Received: from 127.0.0.1 ([127.0.0.1] helo=server3.fastmail.fm) by fastmail.fm - with SMTP; Tue, 11 Feb 2003 20:32:01 -0500 -X-Mail-from: sdudley@idiom.com -X-Delivered-to: -Received: from idiom.com (idiom.com [216.240.32.1]) - by server3.fastmail.fm (Postfix) with ESMTP id 4401D3CE82 - for ; Tue, 11 Feb 2003 20:32:01 -0500 (EST) -Received: from idiom.com (1Cust11.tnt16.sfo8.da.uu.net [63.11.211.11]) - by idiom.com (8.12.6/8.12.6) with ESMTP id h1C1VtAE098669 - for ; Tue, 11 Feb 2003 17:31:56 -0800 (PST) - (envelope-from sdudley@idiom.com) -Message-ID: <3E49A3D4.1060905@idiom.com> -Date: Tue, 11 Feb 2003 17:31:00 -0800 -From: Scott Dudley -User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) -Gecko/20021130 -X-Accept-Language: en-us, en -MIME-Version: 1.0 -To: Tobias Ernst -Subject: MsgAPI licensing change notification -References: <20747336-3D1F-11D7-A3EB-0003931DA274@eml.cc> -In-Reply-To: <20747336-3D1F-11D7-A3EB-0003931DA274@eml.cc> -Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; -micalg=sha1; boundary="------------ms050204080905050402000901" -Status: RO -Content-Length: 32323 -Lines: 584 - -This is a cryptographically signed message in MIME format. - ---------------ms050204080905050402000901 -Content-Type: text/plain; charset=KOI8-R; format=flowed -Content-Transfer-Encoding: 7bit - -Tobias, - -That sounds reasonable. I hereby notify you that the terms and -conditions of the MsgAPI source code release are changed to those of the -GNU Lesser General Public License, the text of which is included below. - You are free to use and redistribute any of the MsgAPI code (or its -derivatives) in a manner which is consistent with the aforementioned -license agreement. - -This message is digitally signed to verify its authenticity. - -Scott Dudley - - GNU LESSER GENERAL PUBLIC LICENSE - Version 2.1, February 1999 - - Copyright (C) 1991, 1999 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - -[This is the first released version of the Lesser GPL. It also counts - as the successor of the GNU Library Public License, version 2, hence - the version number 2.1.] - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -Licenses are intended to guarantee your freedom to share and change -free software--to make sure the software is free for all its users. - - This license, the Lesser General Public License, applies to some -specially designated software packages--typically libraries--of the -Free Software Foundation and other authors who decide to use it. You -can use it too, but we suggest you first think carefully about whether -this license or the ordinary General Public License is the better -strategy to use in any particular case, based on the explanations below. - - When we speak of free software, we are referring to freedom of use, -not price. Our General Public Licenses are designed to make sure that -you have the freedom to distribute copies of free software (and charge -for this service if you wish); that you receive source code or can get -it if you want it; that you can change the software and use pieces of -it in new free programs; and that you are informed that you can do -these things. - - To protect your rights, we need to make restrictions that forbid -distributors to deny you these rights or to ask you to surrender these -rights. These restrictions translate to certain responsibilities for -you if you distribute copies of the library or if you modify it. - - For example, if you distribute copies of the library, whether gratis -or for a fee, you must give the recipients all the rights that we gave -you. You must make sure that they, too, receive or can get the source -code. If you link other code with the library, you must provide -complete object files to the recipients, so that they can relink them -with the library after making changes to the library and recompiling -it. And you must show them these terms so they know their rights. - - We protect your rights with a two-step method: (1) we copyright the -library, and (2) we offer you this license, which gives you legal -permission to copy, distribute and/or modify the library. - - To protect each distributor, we want to make it very clear that -there is no warranty for the free library. Also, if the library is -modified by someone else and passed on, the recipients should know -that what they have is not the original version, so that the original -author's reputation will not be affected by problems that might be -introduced by others. - - Finally, software patents pose a constant threat to the existence of -any free program. We wish to make sure that a company cannot -effectively restrict the users of a free program by obtaining a -restrictive license from a patent holder. Therefore, we insist that -any patent license obtained for a version of the library must be -consistent with the full freedom of use specified in this license. - - Most GNU software, including some libraries, is covered by the -ordinary GNU General Public License. This license, the GNU Lesser -General Public License, applies to certain designated libraries, and -is quite different from the ordinary General Public License. We use -this license for certain libraries in order to permit linking those -libraries into non-free programs. - - When a program is linked with a library, whether statically or using -a shared library, the combination of the two is legally speaking a -combined work, a derivative of the original library. The ordinary -General Public License therefore permits such linking only if the -entire combination fits its criteria of freedom. The Lesser General -Public License permits more lax criteria for linking other code with -the library. - - We call this license the "Lesser" General Public License because it -does Less to protect the user's freedom than the ordinary General -Public License. It also provides other free software developers Less -of an advantage over competing non-free programs. These disadvantages -are the reason we use the ordinary General Public License for many -libraries. However, the Lesser license provides advantages in certain -special circumstances. - - For example, on rare occasions, there may be a special need to -encourage the widest possible use of a certain library, so that it becomes -a de-facto standard. To achieve this, non-free programs must be -allowed to use the library. A more frequent case is that a free -library does the same job as widely used non-free libraries. In this -case, there is little to gain by limiting the free library to free -software only, so we use the Lesser General Public License. - - In other cases, permission to use a particular library in non-free -programs enables a greater number of people to use a large body of -free software. For example, permission to use the GNU C Library in -non-free programs enables many more people to use the whole GNU -operating system, as well as its variant, the GNU/Linux operating -system. - - Although the Lesser General Public License is Less protective of the -users' freedom, it does ensure that the user of a program that is -linked with the Library has the freedom and the wherewithal to run -that program using a modified version of the Library. - - The precise terms and conditions for copying, distribution and -modification follow. Pay close attention to the difference between a -"work based on the library" and a "work that uses the library". The -former contains code derived from the library, whereas the latter must -be combined with the library in order to run. - - GNU LESSER GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License Agreement applies to any software library or other -program which contains a notice placed by the copyright holder or -other authorized party saying it may be distributed under the terms of -this Lesser General Public License (also called "this License"). -Each licensee is addressed as "you". - - A "library" means a collection of software functions and/or data -prepared so as to be conveniently linked with application programs -(which use some of those functions and data) to form executables. - - The "Library", below, refers to any such software library or work -which has been distributed under these terms. A "work based on the -Library" means either the Library or any derivative work under -copyright law: that is to say, a work containing the Library or a -portion of it, either verbatim or with modifications and/or translated -straightforwardly into another language. (Hereinafter, translation is -included without limitation in the term "modification".) - - "Source code" for a work means the preferred form of the work for -making modifications to it. For a library, complete source code means -all the source code for all modules it contains, plus any associated -interface definition files, plus the scripts used to control compilation -and installation of the library. - - Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running a program using the Library is not restricted, and output from -such a program is covered only if its contents constitute a work based -on the Library (independent of the use of the Library in a tool for -writing it). Whether that is true depends on what the Library does -and what the program that uses the Library does. - - 1. You may copy and distribute verbatim copies of the Library's -complete source code as you receive it, in any medium, provided that -you conspicuously and appropriately publish on each copy an -appropriate copyright notice and disclaimer of warranty; keep intact -all the notices that refer to this License and to the absence of any -warranty; and distribute a copy of this License along with the -Library. - - You may charge a fee for the physical act of transferring a copy, -and you may at your option offer warranty protection in exchange for a -fee. - - 2. You may modify your copy or copies of the Library or any portion -of it, thus forming a work based on the Library, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) The modified work must itself be a software library. - - b) You must cause the files modified to carry prominent notices - stating that you changed the files and the date of any change. - - c) You must cause the whole of the work to be licensed at no - charge to all third parties under the terms of this License. - - d) If a facility in the modified Library refers to a function or a - table of data to be supplied by an application program that uses - the facility, other than as an argument passed when the facility - is invoked, then you must make a good faith effort to ensure that, - in the event an application does not supply such function or - table, the facility still operates, and performs whatever part of - its purpose remains meaningful. - - (For example, a function in a library to compute square roots has - a purpose that is entirely well-defined independent of the - application. Therefore, Subsection 2d requires that any - application-supplied function or table used by this function must - be optional: if the application does not supply it, the square - root function must still compute square roots.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Library, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Library, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote -it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Library. - -In addition, mere aggregation of another work not based on the Library -with the Library (or with a work based on the Library) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may opt to apply the terms of the ordinary GNU General Public -License instead of this License to a given copy of the Library. To do -this, you must alter all the notices that refer to this License, so -that they refer to the ordinary GNU General Public License, version 2, -instead of to this License. (If a newer version than version 2 of the -ordinary GNU General Public License has appeared, then you can specify -that version instead if you wish.) Do not make any other change in -these notices. - - Once this change is made in a given copy, it is irreversible for -that copy, so the ordinary GNU General Public License applies to all -subsequent copies and derivative works made from that copy. - - This option is useful when you wish to copy part of the code of -the Library into a program that is not a library. - - 4. You may copy and distribute the Library (or a portion or -derivative of it, under Section 2) in object code or executable form -under the terms of Sections 1 and 2 above provided that you accompany -it with the complete corresponding machine-readable source code, which -must be distributed under the terms of Sections 1 and 2 above on a -medium customarily used for software interchange. - - If distribution of object code is made by offering access to copy -from a designated place, then offering equivalent access to copy the -source code from the same place satisfies the requirement to -distribute the source code, even though third parties are not -compelled to copy the source along with the object code. - - 5. A program that contains no derivative of any portion of the -Library, but is designed to work with the Library by being compiled or -linked with it, is called a "work that uses the Library". Such a -work, in isolation, is not a derivative work of the Library, and -therefore falls outside the scope of this License. - - However, linking a "work that uses the Library" with the Library -creates an executable that is a derivative of the Library (because it -contains portions of the Library), rather than a "work that uses the -library". The executable is therefore covered by this License. -Section 6 states terms for distribution of such executables. - - When a "work that uses the Library" uses material from a header file -that is part of the Library, the object code for the work may be a -derivative work of the Library even though the source code is not. -Whether this is true is especially significant if the work can be -linked without the Library, or if the work is itself a library. The -threshold for this to be true is not precisely defined by law. - - If such an object file uses only numerical parameters, data -structure layouts and accessors, and small macros and small inline -functions (ten lines or less in length), then the use of the object -file is unrestricted, regardless of whether it is legally a derivative -work. (Executables containing this object code plus portions of the -Library will still fall under Section 6.) - - Otherwise, if the work is a derivative of the Library, you may -distribute the object code for the work under the terms of Section 6. -Any executables containing that work also fall under Section 6, -whether or not they are linked directly with the Library itself. - - 6. As an exception to the Sections above, you may also combine or -link a "work that uses the Library" with the Library to produce a -work containing portions of the Library, and distribute that work -under terms of your choice, provided that the terms permit -modification of the work for the customer's own use and reverse -engineering for debugging such modifications. - - You must give prominent notice with each copy of the work that the -Library is used in it and that the Library and its use are covered by -this License. You must supply a copy of this License. If the work -during execution displays copyright notices, you must include the -copyright notice for the Library among them, as well as a reference -directing the user to the copy of this License. Also, you must do one -of these things: - - a) Accompany the work with the complete corresponding - machine-readable source code for the Library including whatever - changes were used in the work (which must be distributed under - Sections 1 and 2 above); and, if the work is an executable linked - with the Library, with the complete machine-readable "work that - uses the Library", as object code and/or source code, so that the - user can modify the Library and then relink to produce a modified - executable containing the modified Library. (It is understood - that the user who changes the contents of definitions files in the - Library will not necessarily be able to recompile the application - to use the modified definitions.) - - b) Use a suitable shared library mechanism for linking with the - Library. A suitable mechanism is one that (1) uses at run time a - copy of the library already present on the user's computer system, - rather than copying library functions into the executable, and (2) - will operate properly with a modified version of the library, if - the user installs one, as long as the modified version is - interface-compatible with the version that the work was made with. - - c) Accompany the work with a written offer, valid for at - least three years, to give the same user the materials - specified in Subsection 6a, above, for a charge no more - than the cost of performing this distribution. - - d) If distribution of the work is made by offering access to copy - from a designated place, offer equivalent access to copy the above - specified materials from the same place. - - e) Verify that the user has already received a copy of these - materials or that you have already sent this user a copy. - - For an executable, the required form of the "work that uses the -Library" must include any data and utility programs needed for -reproducing the executable from it. However, as a special exception, -the materials to be distributed need not include anything that is -normally distributed (in either source or binary form) with the major -components (compiler, kernel, and so on) of the operating system on -which the executable runs, unless that component itself accompanies -the executable. - - It may happen that this requirement contradicts the license -restrictions of other proprietary libraries that do not normally -accompany the operating system. Such a contradiction means you cannot -use both them and the Library together in an executable that you -distribute. - - 7. You may place library facilities that are a work based on the -Library side-by-side in a single library together with other library -facilities not covered by this License, and distribute such a combined -library, provided that the separate distribution of the work based on -the Library and of the other library facilities is otherwise -permitted, and provided that you do these two things: - - a) Accompany the combined library with a copy of the same work - based on the Library, uncombined with any other library - facilities. This must be distributed under the terms of the - Sections above. - - b) Give prominent notice with the combined library of the fact - that part of it is a work based on the Library, and explaining - where to find the accompanying uncombined form of the same work. - - 8. You may not copy, modify, sublicense, link with, or distribute -the Library except as expressly provided under this License. Any -attempt otherwise to copy, modify, sublicense, link with, or -distribute the Library is void, and will automatically terminate your -rights under this License. However, parties who have received copies, -or rights, from you under this License will not have their licenses -terminated so long as such parties remain in full compliance. - - 9. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Library or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Library (or any work based on the -Library), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Library or works based on it. - - 10. Each time you redistribute the Library (or any work based on the -Library), the recipient automatically receives a license from the -original licensor to copy, distribute, link with or modify the Library -subject to these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties with -this License. - - 11. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Library at all. For example, if a patent -license would not permit royalty-free redistribution of the Library by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Library. - -If any portion of this section is held invalid or unenforceable under any -particular circumstance, the balance of the section is intended to apply, -and the section as a whole is intended to apply in other circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 12. If the distribution and/or use of the Library is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Library under this License may add -an explicit geographical distribution limitation excluding those countries, -so that distribution is permitted only in or among countries not thus -excluded. In such case, this License incorporates the limitation as if -written in the body of this License. - - 13. The Free Software Foundation may publish revised and/or new -versions of the Lesser General Public License from time to time. -Such new versions will be similar in spirit to the present version, -but may differ in detail to address new problems or concerns. - -Each version is given a distinguishing version number. If the Library -specifies a version number of this License which applies to it and -"any later version", you have the option of following the terms and -conditions either of that version or of any later version published by -the Free Software Foundation. If the Library does not specify a -license version number, you may choose any version ever published by -the Free Software Foundation. - - 14. If you wish to incorporate parts of the Library into other free -programs whose distribution conditions are incompatible with these, -write to the author to ask for permission. For software which is -copyrighted by the Free Software Foundation, write to the Free -Software Foundation; we sometimes make exceptions for this. Our -decision will be guided by the two goals of preserving the free status -of all derivatives of our free software and of promoting the sharing -and reuse of software generally. - - NO WARRANTY - - 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO -WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. -EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR -OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY -KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE -LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME -THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN -WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY -AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU -FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR -CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE -LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING -RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A -FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF -SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH -DAMAGES. - - - ---------------ms050204080905050402000901 -Content-Type: application/x-pkcs7-signature; name="smime.p7s" -Content-Transfer-Encoding: base64 -Content-Disposition: attachment; filename="smime.p7s" -Content-Description: S/MIME Cryptographic Signature - -MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIPtDCC -BMgwggQxoAMCAQICBAIAApswDQYJKoZIhvcNAQEFBQAwRTELMAkGA1UEBhMCVVMxGDAWBgNV -BAoTD0dURSBDb3Jwb3JhdGlvbjEcMBoGA1UEAxMTR1RFIEN5YmVyVHJ1c3QgUm9vdDAeFw0w -MjA4MjcxOTA3MDBaFw0wNjAyMjMyMzU5MDBaMIHcMQswCQYDVQQGEwJHQjEXMBUGA1UEChMO -Q29tb2RvIExpbWl0ZWQxHTAbBgNVBAsTFENvbW9kbyBUcnVzdCBOZXR3b3JrMUYwRAYDVQQL -Ez1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1c2U6IGh0dHA6Ly93d3cuY29tb2RvLm5ldC9y -ZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAyIENvbW9kbyBMaW1pdGVkMSwwKgYDVQQDEyND -b21vZG8gQ2xhc3MgMyBTZWN1cml0eSBTZXJ2aWNlcyBDQTCCASIwDQYJKoZIhvcNAQEBBQAD -ggEPADCCAQoCggEBALEeYGbgQwaeJ2gvApnHiN+F69tl7NRJZ3ouH83cFSzWHqzynUY6XQPA -PQUsWhgNWSVCo3LArSjSrTwx4ksH+16Y66gz1mmyWp7qLEmmJi5M8MyrQNKq3ixOgbW6e7hc -0Hu9R/XABtLA5NdH22JAr6EcUQMY27jQu5THPHnqJWSuJhnhPGZHZ5Kde1WrNMJ1btknjp2M -8B3aa5yGBKKQteqdjM/7OUOo8BgtnvcZECycL+HQsf/XWcTNQDL514HbURzyQVKBQbGDuMgJ -/pkiR4BPnMuu4CjVHKxwR7Alq6E4Qhdr+mpujV95+PYpAzCkbkbUhV2qQJk4dtseAX3lDKUC -AwEAAaOCAacwggGjMEUGA1UdHwQ+MDwwOqA4oDaGNGh0dHA6Ly93d3cucHVibGljLXRydXN0 -LmNvbS9jZ2ktYmluL0NSTC8yMDA2L2NkcC5jcmwwHQYDVR0OBBYEFPZSIhcVEwgDWb8YlZ9I -tLnp/vhmMIGSBgNVHSAEgYowgYcwSQYKKoZIhvhjAQIBBTA7MDkGCCsGAQUFBwIBFi1odHRw -Oi8vd3d3LnB1YmxpYy10cnVzdC5jb20vQ1BTL09tbmlSb290Lmh0bWwwOgYMKwYBBAGyMQEC -AQMBMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1AwWAYDVR0j -BFEwT6FJpEcwRTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD0dURSBDb3Jwb3JhdGlvbjEcMBoG -A1UEAxMTR1RFIEN5YmVyVHJ1c3QgUm9vdIICAaMwKwYDVR0QBCQwIoAPMjAwMjA4MjcxOTA3 -MzFagQ8yMDA1MDIyMzIzNTkwMFowDgYDVR0PAQH/BAQDAgHmMA8GA1UdEwQIMAYBAf8CAQAw -DQYJKoZIhvcNAQEFBQADgYEAtqewenGL4LqzgR42MnqGGNbxq005CHEGWmegSwHlMEBtibWe -Faqxx/QKxlwO6TfeqJfH3M7Ncft0AgfcXxUnCFMHdtS5BunCd1AeysmwwkaBgACtRKpc1iDZ -VTK+Vpbx6r2g47wNgDrqzPuaV+14pTY9VurR53TKNMPPsVHp4AwwggVwMIIEWKADAgECAhEA -gqh5rwlNvu/BrjIcZKPOBDANBgkqhkiG9w0BAQUFADCB3DELMAkGA1UEBhMCR0IxFzAVBgNV -BAoTDkNvbW9kbyBMaW1pdGVkMR0wGwYDVQQLExRDb21vZG8gVHJ1c3QgTmV0d29yazFGMEQG -A1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNlOiBodHRwOi8vd3d3LmNvbW9kby5u -ZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMiBDb21vZG8gTGltaXRlZDEsMCoGA1UE -AxMjQ29tb2RvIENsYXNzIDMgU2VjdXJpdHkgU2VydmljZXMgQ0EwHhcNMDMwMTE3MDAwMDAw -WhcNMDQwMTE3MjM1OTU5WjCB2TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsgLSBQ -RVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m -IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIw -MDIgQ29tb2RvIExpbWl0ZWQxFTATBgNVBAMTDFNjb3R0IER1ZGxleTEgMB4GCSqGSIb3DQEJ -ARYRc2R1ZGxleUBpZGlvbS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALK6wZ0K -LHchdhyFQHkh3AuPcR81I5ung3Dj/KTsGEKPazdhOycmP58NRRqs/87uugN27fZn8Y4s/Kw6 -lRIRNdJ0n66KMn/gEl+TtneSGQ+3qa5WEOKaqu7PQa7kPBKyUvw2l6Wt5KQB7hQok2fcqeL4 -lHVDIqDbXz3Dk3f+HUN3AgMBAAGjggGwMIIBrDAfBgNVHSMEGDAWgBT2UiIXFRMIA1m/GJWf -SLS56f74ZjAdBgNVHQ4EFgQUUuzvk3Tmqvz07na9//80lnMmpXowDgYDVR0PAQH/BAQDAgWg -MAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMEYGA1Ud -IAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNv -bW9kby5uZXQvQ1BTMIGwBgNVHR8EgagwgaUwOKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvLm5l -dC9DbGFzczNTZWN1cml0eVNlcnZpY2VzXzIuY3JsMDqgOKA2hjRodHRwOi8vY3JsLmNvbW9k -b2NhLmNvbS9DbGFzczNTZWN1cml0eVNlcnZpY2VzXzIuY3JsMC2gK6ApgSdDbGFzczNTZWN1 -cml0eVNlcnZpY2VzXzJAY3JsLmNvbW9kby5uZXQwEQYJYIZIAYb4QgEBBAQDAgUgMBwGA1Ud -EQQVMBOBEXNkdWRsZXlAaWRpb20uY29tMA0GCSqGSIb3DQEBBQUAA4IBAQAGlpSAG30INsP2 -eJnsSMLaJtVR2AyvnN/hN83XHPVAo3rX/7rWI0aHJ4uVHoev9LYutkJMW6CwIWVJ9M/U4R4k -nsJzUfc9moXiCvRUEesHTAAhCzuFwNd7ji8tBpZr0fmeLYBkCFa/WuohR7mZGPQ/zK14CDbz -8iogSI8s/ROsCt7XSk3zEYevTnihIzAAVW0o3aDFGlzhnHZSJZ/hkL6ERb80jcOSMoRcRRDV -d/mZq3lMA5btMQT6Xy5FsxZmettduVEV3q12/cHNjdtDTdcSZl+fbeYsfITlg5nt5sMrCAzQ -i2kg/poagqnR/Fqe0eS12PnrAk4J83F3c1IznjHuMIIFcDCCBFigAwIBAgIRAIKoea8JTb7v -wa4yHGSjzgQwDQYJKoZIhvcNAQEFBQAwgdwxCzAJBgNVBAYTAkdCMRcwFQYDVQQKEw5Db21v -ZG8gTGltaXRlZDEdMBsGA1UECxMUQ29tb2RvIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPVRl -cm1zIGFuZCBDb25kaXRpb25zIG9mIHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9z -aXRvcnkxHzAdBgNVBAsTFihjKTIwMDIgQ29tb2RvIExpbWl0ZWQxLDAqBgNVBAMTI0NvbW9k -byBDbGFzcyAzIFNlY3VyaXR5IFNlcnZpY2VzIENBMB4XDTAzMDExNzAwMDAwMFoXDTA0MDEx -NzIzNTk1OVowgdkxNTAzBgNVBAsTLENvbW9kbyBUcnVzdCBOZXR3b3JrIC0gUEVSU09OQSBO -T1QgVkFMSURBVEVEMUYwRAYDVQQLEz1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1c2U6IGh0 -dHA6Ly93d3cuY29tb2RvLm5ldC9yZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAyIENvbW9k -byBMaW1pdGVkMRUwEwYDVQQDEwxTY290dCBEdWRsZXkxIDAeBgkqhkiG9w0BCQEWEXNkdWRs -ZXlAaWRpb20uY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCyusGdCix3IXYchUB5 -IdwLj3EfNSObp4Nw4/yk7BhCj2s3YTsnJj+fDUUarP/O7roDdu32Z/GOLPysOpUSETXSdJ+u -ijJ/4BJfk7Z3khkPt6muVhDimqruz0Gu5DwSslL8NpelreSkAe4UKJNn3Kni+JR1QyKg2189 -w5N3/h1DdwIDAQABo4IBsDCCAawwHwYDVR0jBBgwFoAU9lIiFxUTCANZvxiVn0i0uen++GYw -HQYDVR0OBBYEFFLs75N05qr89O52vf//NJZzJqV6MA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMB -Af8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjBGBgNVHSAEPzA9MDsG -DCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0 -L0NQUzCBsAYDVR0fBIGoMIGlMDigNqA0hjJodHRwOi8vY3JsLmNvbW9kby5uZXQvQ2xhc3Mz -U2VjdXJpdHlTZXJ2aWNlc18yLmNybDA6oDigNoY0aHR0cDovL2NybC5jb21vZG9jYS5jb20v -Q2xhc3MzU2VjdXJpdHlTZXJ2aWNlc18yLmNybDAtoCugKYEnQ2xhc3MzU2VjdXJpdHlTZXJ2 -aWNlc18yQGNybC5jb21vZG8ubmV0MBEGCWCGSAGG+EIBAQQEAwIFIDAcBgNVHREEFTATgRFz -ZHVkbGV5QGlkaW9tLmNvbTANBgkqhkiG9w0BAQUFAAOCAQEABpaUgBt9CDbD9niZ7EjC2ibV -UdgMr5zf4TfN1xz1QKN61/+61iNGhyeLlR6Hr/S2LrZCTFugsCFlSfTP1OEeJJ7Cc1H3PZqF -4gr0VBHrB0wAIQs7hcDXe44vLQaWa9H5ni2AZAhWv1rqIUe5mRj0P8yteAg28/IqIEiPLP0T -rAre10pN8xGHr054oSMwAFVtKN2gxRpc4Zx2UiWf4ZC+hEW/NI3DkjKEXEUQ1Xf5mat5TAOW -7TEE+l8uRbMWZnrbXblRFd6tdv3BzY3bQ03XEmZfn23mLHyE5YOZ7ebDKwgM0ItpIP6aGoKp -0fxantHktdj56wJOCfNxd3NSM54x7jGCBF4wggRaAgEBMIHyMIHcMQswCQYDVQQGEwJHQjEX -MBUGA1UEChMOQ29tb2RvIExpbWl0ZWQxHTAbBgNVBAsTFENvbW9kbyBUcnVzdCBOZXR3b3Jr -MUYwRAYDVQQLEz1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1c2U6IGh0dHA6Ly93d3cuY29t -b2RvLm5ldC9yZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAyIENvbW9kbyBMaW1pdGVkMSww -KgYDVQQDEyNDb21vZG8gQ2xhc3MgMyBTZWN1cml0eSBTZXJ2aWNlcyBDQQIRAIKoea8JTb7v -wa4yHGSjzgQwCQYFKw4DAhoFAKCCAsEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq -hkiG9w0BCQUxDxcNMDMwMjEyMDEzMTAxWjAjBgkqhkiG9w0BCQQxFgQUGU0CfZRc1F78c8vu -O6TJxnFEJ44wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw -DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwggEDBgkrBgEEAYI3EAQx -gfUwgfIwgdwxCzAJBgNVBAYTAkdCMRcwFQYDVQQKEw5Db21vZG8gTGltaXRlZDEdMBsGA1UE -CxMUQ29tb2RvIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25z -IG9mIHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihj -KTIwMDIgQ29tb2RvIExpbWl0ZWQxLDAqBgNVBAMTI0NvbW9kbyBDbGFzcyAzIFNlY3VyaXR5 -IFNlcnZpY2VzIENBAhEAgqh5rwlNvu/BrjIcZKPOBDCCAQUGCyqGSIb3DQEJEAILMYH1oIHy -MIHcMQswCQYDVQQGEwJHQjEXMBUGA1UEChMOQ29tb2RvIExpbWl0ZWQxHTAbBgNVBAsTFENv -bW9kbyBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1 -c2U6IGh0dHA6Ly93d3cuY29tb2RvLm5ldC9yZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAy -IENvbW9kbyBMaW1pdGVkMSwwKgYDVQQDEyNDb21vZG8gQ2xhc3MgMyBTZWN1cml0eSBTZXJ2 -aWNlcyBDQQIRAIKoea8JTb7vwa4yHGSjzgQwDQYJKoZIhvcNAQEBBQAEgYAJA2vXBvQcmYe1 -b17Nb9SjSmSnGNQ35W3F88Mg8SDQY0coMjSfLRV29jxl34bwhX4LxK/r/i+K3mtQ0ijTBabG -ncLTZD9b2NLpG8v0fVH8C4vWsVioKgpb1UZHmc8G2ZBva8706uZ8vkwiki/xASelNS4mZmnt -NHd0CauVQ/mUzgAAAAAAAA== ---------------ms050204080905050402000901-- - - - - ----- scott-dudley.txt ends ----- + ----- scott-dudley.txt begins ----- +From sdudley@idiom.com Wed Feb 12 02:32:00 2003 +Return-Path: +Received: from server3.fastmail.fm (server3.internal [10.202.2.134]) + by server2.fastmail.fm (Cyrus v2.1.9) with LMTP; Tue, 11 Feb 2003 +20:32:00 -0500 +X-Sieve: CMU Sieve 2.2 +Received: from server3.fastmail.fm (server3.internal [10.202.2.134]) + by server3.fastmail.fm (Cyrus v2.1.9) with LMTP; Tue, 11 Feb 2003 +20:32:01 -0500 +Received: from server3.fastmail.fm (localhost [127.0.0.1]) + by fastmail.fm (Postfix) with ESMTP id A8C6C3E9CB + for ; Tue, 11 Feb 2003 20:32:01 -0500 (EST) +X-Attached: smime.p7s +Received: from 127.0.0.1 ([127.0.0.1] helo=server3.fastmail.fm) by fastmail.fm + with SMTP; Tue, 11 Feb 2003 20:32:01 -0500 +X-Mail-from: sdudley@idiom.com +X-Delivered-to: +Received: from idiom.com (idiom.com [216.240.32.1]) + by server3.fastmail.fm (Postfix) with ESMTP id 4401D3CE82 + for ; Tue, 11 Feb 2003 20:32:01 -0500 (EST) +Received: from idiom.com (1Cust11.tnt16.sfo8.da.uu.net [63.11.211.11]) + by idiom.com (8.12.6/8.12.6) with ESMTP id h1C1VtAE098669 + for ; Tue, 11 Feb 2003 17:31:56 -0800 (PST) + (envelope-from sdudley@idiom.com) +Message-ID: <3E49A3D4.1060905@idiom.com> +Date: Tue, 11 Feb 2003 17:31:00 -0800 +From: Scott Dudley +User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) +Gecko/20021130 +X-Accept-Language: en-us, en +MIME-Version: 1.0 +To: Tobias Ernst +Subject: MsgAPI licensing change notification +References: <20747336-3D1F-11D7-A3EB-0003931DA274@eml.cc> +In-Reply-To: <20747336-3D1F-11D7-A3EB-0003931DA274@eml.cc> +Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; +micalg=sha1; boundary="------------ms050204080905050402000901" +Status: RO +Content-Length: 32323 +Lines: 584 + +This is a cryptographically signed message in MIME format. + +--------------ms050204080905050402000901 +Content-Type: text/plain; charset=KOI8-R; format=flowed +Content-Transfer-Encoding: 7bit + +Tobias, + +That sounds reasonable. I hereby notify you that the terms and +conditions of the MsgAPI source code release are changed to those of the +GNU Lesser General Public License, the text of which is included below. + You are free to use and redistribute any of the MsgAPI code (or its +derivatives) in a manner which is consistent with the aforementioned +license agreement. + +This message is digitally signed to verify its authenticity. + +Scott Dudley + + GNU LESSER GENERAL PUBLIC LICENSE + Version 2.1, February 1999 + + Copyright (C) 1991, 1999 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts + as the successor of the GNU Library Public License, version 2, hence + the version number 2.1.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + + To protect your rights, we need to make restrictions that forbid +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. + + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. + + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. + + GNU LESSER GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties with +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + + +--------------ms050204080905050402000901 +Content-Type: application/x-pkcs7-signature; name="smime.p7s" +Content-Transfer-Encoding: base64 +Content-Disposition: attachment; filename="smime.p7s" +Content-Description: S/MIME Cryptographic Signature + +MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIPtDCC +BMgwggQxoAMCAQICBAIAApswDQYJKoZIhvcNAQEFBQAwRTELMAkGA1UEBhMCVVMxGDAWBgNV +BAoTD0dURSBDb3Jwb3JhdGlvbjEcMBoGA1UEAxMTR1RFIEN5YmVyVHJ1c3QgUm9vdDAeFw0w +MjA4MjcxOTA3MDBaFw0wNjAyMjMyMzU5MDBaMIHcMQswCQYDVQQGEwJHQjEXMBUGA1UEChMO +Q29tb2RvIExpbWl0ZWQxHTAbBgNVBAsTFENvbW9kbyBUcnVzdCBOZXR3b3JrMUYwRAYDVQQL +Ez1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1c2U6IGh0dHA6Ly93d3cuY29tb2RvLm5ldC9y +ZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAyIENvbW9kbyBMaW1pdGVkMSwwKgYDVQQDEyND +b21vZG8gQ2xhc3MgMyBTZWN1cml0eSBTZXJ2aWNlcyBDQTCCASIwDQYJKoZIhvcNAQEBBQAD +ggEPADCCAQoCggEBALEeYGbgQwaeJ2gvApnHiN+F69tl7NRJZ3ouH83cFSzWHqzynUY6XQPA +PQUsWhgNWSVCo3LArSjSrTwx4ksH+16Y66gz1mmyWp7qLEmmJi5M8MyrQNKq3ixOgbW6e7hc +0Hu9R/XABtLA5NdH22JAr6EcUQMY27jQu5THPHnqJWSuJhnhPGZHZ5Kde1WrNMJ1btknjp2M +8B3aa5yGBKKQteqdjM/7OUOo8BgtnvcZECycL+HQsf/XWcTNQDL514HbURzyQVKBQbGDuMgJ +/pkiR4BPnMuu4CjVHKxwR7Alq6E4Qhdr+mpujV95+PYpAzCkbkbUhV2qQJk4dtseAX3lDKUC +AwEAAaOCAacwggGjMEUGA1UdHwQ+MDwwOqA4oDaGNGh0dHA6Ly93d3cucHVibGljLXRydXN0 +LmNvbS9jZ2ktYmluL0NSTC8yMDA2L2NkcC5jcmwwHQYDVR0OBBYEFPZSIhcVEwgDWb8YlZ9I +tLnp/vhmMIGSBgNVHSAEgYowgYcwSQYKKoZIhvhjAQIBBTA7MDkGCCsGAQUFBwIBFi1odHRw +Oi8vd3d3LnB1YmxpYy10cnVzdC5jb20vQ1BTL09tbmlSb290Lmh0bWwwOgYMKwYBBAGyMQEC +AQMBMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1AwWAYDVR0j +BFEwT6FJpEcwRTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD0dURSBDb3Jwb3JhdGlvbjEcMBoG +A1UEAxMTR1RFIEN5YmVyVHJ1c3QgUm9vdIICAaMwKwYDVR0QBCQwIoAPMjAwMjA4MjcxOTA3 +MzFagQ8yMDA1MDIyMzIzNTkwMFowDgYDVR0PAQH/BAQDAgHmMA8GA1UdEwQIMAYBAf8CAQAw +DQYJKoZIhvcNAQEFBQADgYEAtqewenGL4LqzgR42MnqGGNbxq005CHEGWmegSwHlMEBtibWe +Faqxx/QKxlwO6TfeqJfH3M7Ncft0AgfcXxUnCFMHdtS5BunCd1AeysmwwkaBgACtRKpc1iDZ +VTK+Vpbx6r2g47wNgDrqzPuaV+14pTY9VurR53TKNMPPsVHp4AwwggVwMIIEWKADAgECAhEA +gqh5rwlNvu/BrjIcZKPOBDANBgkqhkiG9w0BAQUFADCB3DELMAkGA1UEBhMCR0IxFzAVBgNV +BAoTDkNvbW9kbyBMaW1pdGVkMR0wGwYDVQQLExRDb21vZG8gVHJ1c3QgTmV0d29yazFGMEQG +A1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNlOiBodHRwOi8vd3d3LmNvbW9kby5u +ZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMiBDb21vZG8gTGltaXRlZDEsMCoGA1UE +AxMjQ29tb2RvIENsYXNzIDMgU2VjdXJpdHkgU2VydmljZXMgQ0EwHhcNMDMwMTE3MDAwMDAw +WhcNMDQwMTE3MjM1OTU5WjCB2TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsgLSBQ +RVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m +IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIw +MDIgQ29tb2RvIExpbWl0ZWQxFTATBgNVBAMTDFNjb3R0IER1ZGxleTEgMB4GCSqGSIb3DQEJ +ARYRc2R1ZGxleUBpZGlvbS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALK6wZ0K +LHchdhyFQHkh3AuPcR81I5ung3Dj/KTsGEKPazdhOycmP58NRRqs/87uugN27fZn8Y4s/Kw6 +lRIRNdJ0n66KMn/gEl+TtneSGQ+3qa5WEOKaqu7PQa7kPBKyUvw2l6Wt5KQB7hQok2fcqeL4 +lHVDIqDbXz3Dk3f+HUN3AgMBAAGjggGwMIIBrDAfBgNVHSMEGDAWgBT2UiIXFRMIA1m/GJWf +SLS56f74ZjAdBgNVHQ4EFgQUUuzvk3Tmqvz07na9//80lnMmpXowDgYDVR0PAQH/BAQDAgWg +MAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMEYGA1Ud +IAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNv +bW9kby5uZXQvQ1BTMIGwBgNVHR8EgagwgaUwOKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvLm5l +dC9DbGFzczNTZWN1cml0eVNlcnZpY2VzXzIuY3JsMDqgOKA2hjRodHRwOi8vY3JsLmNvbW9k +b2NhLmNvbS9DbGFzczNTZWN1cml0eVNlcnZpY2VzXzIuY3JsMC2gK6ApgSdDbGFzczNTZWN1 +cml0eVNlcnZpY2VzXzJAY3JsLmNvbW9kby5uZXQwEQYJYIZIAYb4QgEBBAQDAgUgMBwGA1Ud +EQQVMBOBEXNkdWRsZXlAaWRpb20uY29tMA0GCSqGSIb3DQEBBQUAA4IBAQAGlpSAG30INsP2 +eJnsSMLaJtVR2AyvnN/hN83XHPVAo3rX/7rWI0aHJ4uVHoev9LYutkJMW6CwIWVJ9M/U4R4k +nsJzUfc9moXiCvRUEesHTAAhCzuFwNd7ji8tBpZr0fmeLYBkCFa/WuohR7mZGPQ/zK14CDbz +8iogSI8s/ROsCt7XSk3zEYevTnihIzAAVW0o3aDFGlzhnHZSJZ/hkL6ERb80jcOSMoRcRRDV +d/mZq3lMA5btMQT6Xy5FsxZmettduVEV3q12/cHNjdtDTdcSZl+fbeYsfITlg5nt5sMrCAzQ +i2kg/poagqnR/Fqe0eS12PnrAk4J83F3c1IznjHuMIIFcDCCBFigAwIBAgIRAIKoea8JTb7v +wa4yHGSjzgQwDQYJKoZIhvcNAQEFBQAwgdwxCzAJBgNVBAYTAkdCMRcwFQYDVQQKEw5Db21v +ZG8gTGltaXRlZDEdMBsGA1UECxMUQ29tb2RvIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPVRl +cm1zIGFuZCBDb25kaXRpb25zIG9mIHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9z +aXRvcnkxHzAdBgNVBAsTFihjKTIwMDIgQ29tb2RvIExpbWl0ZWQxLDAqBgNVBAMTI0NvbW9k +byBDbGFzcyAzIFNlY3VyaXR5IFNlcnZpY2VzIENBMB4XDTAzMDExNzAwMDAwMFoXDTA0MDEx +NzIzNTk1OVowgdkxNTAzBgNVBAsTLENvbW9kbyBUcnVzdCBOZXR3b3JrIC0gUEVSU09OQSBO +T1QgVkFMSURBVEVEMUYwRAYDVQQLEz1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1c2U6IGh0 +dHA6Ly93d3cuY29tb2RvLm5ldC9yZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAyIENvbW9k +byBMaW1pdGVkMRUwEwYDVQQDEwxTY290dCBEdWRsZXkxIDAeBgkqhkiG9w0BCQEWEXNkdWRs +ZXlAaWRpb20uY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCyusGdCix3IXYchUB5 +IdwLj3EfNSObp4Nw4/yk7BhCj2s3YTsnJj+fDUUarP/O7roDdu32Z/GOLPysOpUSETXSdJ+u +ijJ/4BJfk7Z3khkPt6muVhDimqruz0Gu5DwSslL8NpelreSkAe4UKJNn3Kni+JR1QyKg2189 +w5N3/h1DdwIDAQABo4IBsDCCAawwHwYDVR0jBBgwFoAU9lIiFxUTCANZvxiVn0i0uen++GYw +HQYDVR0OBBYEFFLs75N05qr89O52vf//NJZzJqV6MA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMB +Af8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjBGBgNVHSAEPzA9MDsG +DCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0 +L0NQUzCBsAYDVR0fBIGoMIGlMDigNqA0hjJodHRwOi8vY3JsLmNvbW9kby5uZXQvQ2xhc3Mz +U2VjdXJpdHlTZXJ2aWNlc18yLmNybDA6oDigNoY0aHR0cDovL2NybC5jb21vZG9jYS5jb20v +Q2xhc3MzU2VjdXJpdHlTZXJ2aWNlc18yLmNybDAtoCugKYEnQ2xhc3MzU2VjdXJpdHlTZXJ2 +aWNlc18yQGNybC5jb21vZG8ubmV0MBEGCWCGSAGG+EIBAQQEAwIFIDAcBgNVHREEFTATgRFz +ZHVkbGV5QGlkaW9tLmNvbTANBgkqhkiG9w0BAQUFAAOCAQEABpaUgBt9CDbD9niZ7EjC2ibV +UdgMr5zf4TfN1xz1QKN61/+61iNGhyeLlR6Hr/S2LrZCTFugsCFlSfTP1OEeJJ7Cc1H3PZqF +4gr0VBHrB0wAIQs7hcDXe44vLQaWa9H5ni2AZAhWv1rqIUe5mRj0P8yteAg28/IqIEiPLP0T +rAre10pN8xGHr054oSMwAFVtKN2gxRpc4Zx2UiWf4ZC+hEW/NI3DkjKEXEUQ1Xf5mat5TAOW +7TEE+l8uRbMWZnrbXblRFd6tdv3BzY3bQ03XEmZfn23mLHyE5YOZ7ebDKwgM0ItpIP6aGoKp +0fxantHktdj56wJOCfNxd3NSM54x7jGCBF4wggRaAgEBMIHyMIHcMQswCQYDVQQGEwJHQjEX +MBUGA1UEChMOQ29tb2RvIExpbWl0ZWQxHTAbBgNVBAsTFENvbW9kbyBUcnVzdCBOZXR3b3Jr +MUYwRAYDVQQLEz1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1c2U6IGh0dHA6Ly93d3cuY29t +b2RvLm5ldC9yZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAyIENvbW9kbyBMaW1pdGVkMSww +KgYDVQQDEyNDb21vZG8gQ2xhc3MgMyBTZWN1cml0eSBTZXJ2aWNlcyBDQQIRAIKoea8JTb7v +wa4yHGSjzgQwCQYFKw4DAhoFAKCCAsEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq +hkiG9w0BCQUxDxcNMDMwMjEyMDEzMTAxWjAjBgkqhkiG9w0BCQQxFgQUGU0CfZRc1F78c8vu +O6TJxnFEJ44wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw +DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwggEDBgkrBgEEAYI3EAQx +gfUwgfIwgdwxCzAJBgNVBAYTAkdCMRcwFQYDVQQKEw5Db21vZG8gTGltaXRlZDEdMBsGA1UE +CxMUQ29tb2RvIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25z +IG9mIHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihj +KTIwMDIgQ29tb2RvIExpbWl0ZWQxLDAqBgNVBAMTI0NvbW9kbyBDbGFzcyAzIFNlY3VyaXR5 +IFNlcnZpY2VzIENBAhEAgqh5rwlNvu/BrjIcZKPOBDCCAQUGCyqGSIb3DQEJEAILMYH1oIHy +MIHcMQswCQYDVQQGEwJHQjEXMBUGA1UEChMOQ29tb2RvIExpbWl0ZWQxHTAbBgNVBAsTFENv +bW9kbyBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1 +c2U6IGh0dHA6Ly93d3cuY29tb2RvLm5ldC9yZXBvc2l0b3J5MR8wHQYDVQQLExYoYykyMDAy +IENvbW9kbyBMaW1pdGVkMSwwKgYDVQQDEyNDb21vZG8gQ2xhc3MgMyBTZWN1cml0eSBTZXJ2 +aWNlcyBDQQIRAIKoea8JTb7vwa4yHGSjzgQwDQYJKoZIhvcNAQEBBQAEgYAJA2vXBvQcmYe1 +b17Nb9SjSmSnGNQ35W3F88Mg8SDQY0coMjSfLRV29jxl34bwhX4LxK/r/i+K3mtQ0ijTBabG +ncLTZD9b2NLpG8v0fVH8C4vWsVioKgpb1UZHmc8G2ZBva8706uZ8vkwiki/xASelNS4mZmnt +NHd0CauVQ/mUzgAAAAAAAA== +--------------ms050204080905050402000901-- + + + + ----- scott-dudley.txt ends ----- diff --git a/manuals/gold_ref.tei b/manuals/gold_ref.tei index 8eb9ebe..44fb53e 100644 --- a/manuals/gold_ref.tei +++ b/manuals/gold_ref.tei @@ -1,16915 +1,16915 @@ - - - - - - - - - GoldED+ Reference Manual - - - -

- Created in electronic form. -

- - - - - - English - - - - - - - - - - - - GoldED+ - - - Reference Manual - - - - Odinn Sorensen, Dirk A. Mueller, Alexander S. Aganichev and others - - - 1990-2003 - - - - - - - - - - Introduction - -

- -

- IBM OS/2, -

- Dirk A. Mueller, and - Alexander - Tsvyashchenko, Alexander - Aganichev and Haruyasu - Yoshizaki, Lanius - Corporation, Folkert J. - Wijnstra, Continental - Software, -

- We also need to thanks all that people who have contributed configuration - files: Steve - Shapiro, Michael - Hembo, Kees - Bergwerf, -

- Special thanks goes to - - - - - License Agreement and Copyright Notices - -

- -

- ( -

- The GNU Library - General Public License ( -

- Additionally, permission is hereby specifically given to link - Goldware - Library with any software or software library that meets the - http://www.opensource.org. This includes - -

- The additional permission to link with non-GPL/LGPL software - may be slightly controversial. The intent is to allow developers a - greater freedom to create specialized versions of GoldED. Examples could - be a -

- Parts of the -

- So, even though parts of the Mike - Smedley and how to contact him, -

- Lanius - Corporation. -

-

- -

- Products and company names listed are trademarks or trade names of their - respective companies. -

- - - - - The Message Database Formats - - - - Opus, FTS-0001 - -

- These are two variants of the same type of msgbase. It works by using - one physical file per message ( -

- In echomail areas, this format has a special quirk: The first message - ( -

- The variants: The - - - - QuickBBS, RemoteAccess, and Hudson - -

- This msgbase format was invented by -

- The format limits the total size of -

- The first incarnations of -

- The main virtue of this format is that it is very fast to access the - msgbase. -

-

- The main disadvantage is that it can be very sensitive to disk - problems, and it is a common horror story that people loose their - entire msgbase because the disk developed bad clusters or some - program went berserk and messed up the msgbase files. -

- - - - Goldbase - -

- This is an enhanced version of the -

- The - - - - Squish - -

- The -

- The use of a database for each area - instead of one file per msg, - or all msgs in one big database - makes this format fast, very - safe and resistant to disk problems. Even if something messed up a - -

- A special feature of - - - - Ezycom - -

- - - - - JAM - -

- -

- -

- -

- The -

- -

- Msg may not be displayed to user (always - displayed). -

-

- specifies which - method to use. -

- - - - PCBoard - -

- The supported -

-

- Passwords are not supported. -

-

- The -

- -

- The mail waiting flags are updated when you write to people that are - named in the userbase. -

-

- When changing a message, the new edition is saved as if it were a new - message, with a new message number, and then the old edition is - deleted. This behaviour is consistent with the way - - - - AdeptXBBS - -

- The implementation is based on the documentation in version 1.05, - experimentation and questions to the authors. Thanks go to - -

- The -

- Mixing of netmail and echomail or other types of mail in the same - area is not directly supported. If an area is setup as both netmail - and echomail, -

- -

- The -

- The replylinking method used by - - - - WildCat! - -

- The -

- WildCat features which are not supported yet: - - The message from/to title. - -

-

- There is a keyword - , which works just - like the other <msgbase>USERNO keywords. By default - -

- - - - - Synchronet - -

- Synchronet - Message Base Specification version 1.21. -

- Just like -

- - - - - - - Nodelist and Userlist Support - -

- -

- In order to enable nodelist/userlist lookup and browsing, -

- - - - - Routing Diagram Drawing Tool - -

- Routing diagram drawing tool intended to analyse files created by - pressing key defined for READmakepathreport - action. - - - - - Commandline Reference - - - - Mail Reader Commandline Syntax - -

- Invocation: -golded [options] [keystacking] -

-

- Depending on used platform GoldED+ could be called - geddjg, gedcyg, gedemx, or - gedlnx. Available options are (all options are case - insensitive): - - - - Displays a help screen with all available commandline options. - - - - Specifies another configuration file than the default. See also - environment variable. - - - - Disable old configuration keywords. For backward compatibility, - GoldED+ still supports a number of old names for - some configuration keywords. It is recommended that you use - -d sometimes and rename the keywords that are - reported as unknown. - - - - If specified, GoldED+ starts directly in the - specified echo, bypassing the arealist screen. See the - AREASTART configuration - keyword for more info. - - - - Calls the SOUP packet export feature during the - startup phase. This is the same as starting it from the - areascan SOUP Packet->Export menu - item. The SOUP export happens immediately after the - regular startup area scanning (if that is enabled) and after - SOUP import. - - - - Force recompile of most configuration files, but not all. Does not - recompile the *.chs files. - - - - Force complete recompile of all configuration files, regardless of - whether they are up-to-date or not. This is equivalent to deleting - all the *.ge? files. - - - - Same as option -?. - - - - Start the quick install procedure. You should give a path to your - other mail software if it cannot be found using environment - variables or in current directory. - - - - Calls the SOUP packet import feature during the - startup phase. This is the same as starting it from the areascan - SOUP Packet->Import menu item. The - SOUP import happens immediately after the regular - startup area scanning (if that is enabled). - - -

-

- Any non-option characters on the commandline are stuffed into the - keyboard buffer. See the chapter on keyboard definition and the - KEYBSTACK keyword for more info. -

-

- For example, -golded @S A - makes GoldED+ go to the area scanning menu <Alt-S>, - and select scanning of <A> all areas. -

-

- See the chapter for more info. Note, - that only those combinations described in the - KEYBSTACK chapter are allowed - here. -

- - - - -

- For operation in batch files, GoldED+ has a set of - errorlevel values: - - - - 032 or higher - - - Error exit (check the logfile for details). - - - - - 004 - - - Echomail entered. - - - - - 002 - - - Netmail entered. - - - - - 001 - - - Local mail entered. - - - - - 000 - - - No errors. No mail entered. - - -
-

-

- Add values together to find the combined error levels. For example, error - level 6 is returned if netmail and echomail (2+4) was entered. -

-

- Example of rungold.bat file: -golded.exe -if errorlevel 007 goto e_n_l -if errorlevel 006 goto e_n__ -if errorlevel 005 goto e___l -if errorlevel 004 goto e____ -if errorlevel 003 goto __n_l -if errorlevel 002 goto __n__ -if errorlevel 001 goto ____l -if errorlevel 000 goto nomail -:error - echo GoldED+ error exit! - goto end -:e_n_l - echo **** New echo, net and local mail entered. - goto end -:e_n__ - echo **** New echo and netmail entered. - goto end -:e___l - echo **** New echo and local mail entered. - goto end -:e____ - echo **** New echomail entered. - goto end -:__n_l - echo **** New net and local mail entered. - goto end -:__n__ - echo **** New netmail entered. - goto end -:____l - echo **** New local mail entered. - goto end -:nomail - echo **** No new mail entered. -:end - echo. - echo Thank you for using GoldED+! :-) -

- - - - Nodelist Compiler Commandline Syntax - -

- Invocation: -goldnode [options] [configfile] -

-

- Depending on used platform GoldNODE could be called - gndjg, gncyg, gnemx, or - gnlnx. Available options: - - - - Conditional compile. - - - - Remove duplicate nodes from index. - - - - Forced compile. - - - - Quite compiled. No screen output improves speed. - - - - Set the max size of names. Normally not used. - - - - Create sorted - -

-

- The and - environment variables. -

-

- The nodelist index files are named keyword. -

-

- The V7+ index is automatically used if your - is set correctly. If - -xxxx / nodex.dtp - at the bottom of the browser window, the displayed information is taken - from the raw nodelist entry, taken from the V7+ index. -

-

- GoldNODE can read the german POINTS24-format - directly! -

-

- and - keywords, please note - that the addressmask does not accept - - - - Routing Diagram Drawing Tool Commandline Syntax - -

- Invocation: -rddt <routefile> [options] [address or name] -

-

- Depending on used platform RDDT could be called - rddtdjg, rddtcyg, rddtemx, or - rddtlnx. Available options: - - - - Reserved for debugging purposes. - - - - Sets indent to n. - - - - This option used to specify yours link address. Requires option - -n. - - - - Use this option to specify your address. - - - - Decode path. - - -

-

- Example: -RDDT path.rpt -n2:5020/604.19 -l2:5020/604 2:5020/604.19 -p -

- - - - - - Environment Variables - -

- These are the GoldED+ specific environment variables: - - -

-

- When using the feature to read - external area configuration from the other programs, the individual - 's may use specific environment - variables to find the files. Please read the - chapter for specific details of each - supported . -

- - - - - Configuration Keyword Reference - -

- The following special symbols are used in the keyword parameter lists: - - - - [] - - - Optional parameter. - - - - - <> - - - Required parameter, not optional. - - - - - - - - Parameter must be inclosed in quotes. - - - - - / - - - Separates mutually exclusive values. - - - - - , - - - Separates possible values for the keyword. - - -
-

-

- There's no mandatory keywords but the mail reader should have defined at - least name, address and area; nodelist compiler should have address and - either nodelist or userlist defined. -

-

- Whenever path is expected you may use environment variables enclosed in - percent signs, f.e. %FIDO%/myfile.txt. This also valid for - input prompts where path is expected :-) -

- - - Remarks - - - - - - - - Signifies a remark (comment) line. - - - - The - - - Any non-alphabetic non-whitespace character at the beginning of a - line makes the line a comment. By tradition, the semicolon is the - standard comment character. The semicolon (and only that) can also - be used to add a comment at the end of a configuration line. - - - - Mail reader and nodelist compiler. - - - -REM This is a comment -; This is a comment -% This is a comment -* This is a comment -// This is a comment -/* This is a comment */ -ADDRESS 2:236/77 ; Main address. -AKA 2:236/77.1 ; SysOp point. - - - - - - Conditionals - - - - - - - - - - - - These control keywords can be used to setup sections of configuration - which enable different sets of keywords depending on which version - that is used. - - - - The following conditions can be used: - - - - - - true, if DPMI32 version is used - - - - - OS/2, - - true, if OS/2 version is used - - - - - - - true, if Win32 version is used - - - - - Linux, UNIX - - - true, if - - - - Firebird - - - true, if - - - - ASA - - - true, if - - - - Yes, True, On - - - always true - - -
- - - - Mail reader and nodelist compiler. - - - -IF OS2 - EDITOR c:\qedit\os2\q.exe @file -n@line - EDITSPELLCHECK c:\os2\cmd.exe /c c:\ss\ss.exe @file -ELIF DOS - EDITOR c:\qedit\dos\q.exe @file -n@line - EDITSPELLCHECK c:\ss\ss.exe @file -ELIF WIN32 - EDITOR c:\progra~1\far\far.exe -i -e@line @file - EDITSPELLCHECK c:\fido\goldkorr\goldkorr.exe @file /A /Q -ENDIF - - - - - - IGNORE - - - - - - - - This tells the configuration file reader to ignore all subsequent - lines until another - - - This keyword may cause unpredicable results if used within - - - - Mail reader. - - - - - - - - - ADDRESS - - - - - <zone:net/node[.point][@domain] - [,pointnet]> - - - - Your network address, can be used - interchangeably. - - - - If a zone:pointnet/point.0 in the msg header, instead of - the zone:net/node.point. Most modern - mailers and mail processors now supports the - The optional - - - This keyword can be used globally and in a - Random System group. - - - - Mail reader and nodelist compiler. - - - - , - - - - -ADDRESS 2:236/77 ; Node address -ADDRESS 2:236/77.1 ; Point address (4D) -ADDRESS 2:236/77.1, 16077 ; Point address (3D) -ADDRESS 2:236/77@fidonet ; Node address with domain - - - - - - ADDRESSBOOKADD - - - - - <YES/NO/ALWAYS> - - - - This keyword controls whether - - - Setting this keyword to - - - - - - - - It's a - - - It's a - - - It's the - - - It's the mailinglist's sender address - - - It's an UUCP - - - It's already an email address - - - Address/aka is unknown - - - It's an - - - - - - Mail reader. - - - - , - , - , - , - , - - - - - - - ADDRESSLOOKUPFIRST - - - - - <MSGID/ORIGIN> - - - - This keyword defines the first source to lookup address. If valid - address could not be found in the specifyed location then second - source is used. - - - - If defined to - - - - - - Mail reader. - - - - - - ADDRESSMACRO - - - - - subject] [,attribs]/ - - - - Defines a short name for often used addresses. Typical uses are for - - - - If (and only if) the subject is enclosed in quotes ( for the - valid attributes. You cannot have quotes within quotes (not the same - type anyway). The attribues are - A special format is supported for keyword, just put - gate name right after the /). - - - - The address macros can also be specified in an external file, like - the for details. However, you - should not use the syntax with the attributes in the - When used in the - - - Mail reader. - - - - , - - - - - - - - - - ADEPTXBBSPATH - - - - - - - - Specifyes the path where you keep your - - - The - - - Mail reader. - - - - chapter, - - - - - - - ADEPTXBBSUSERNO - - - - - - - - Specifyes the record number in the userfile and lastreads. - - - - If you are not the first user in the userfile, or are sharing the - messagebase with other - - - By default - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - - - - - - - AKA - - - - - <zone:net/node[.point][@domain] - [,pointnet]> - - - - Your network address, and - - - If a zone:pointnet/point.0 in the msg header, instead of - the zone:net/node.point. Most modern - mailers and mail processors now supports the - The optional - - - This keyword can be used globally and in a - Random System group. - - - - Mail reader and nodelist compiler. - - - - , - - - - - - - AKAMATCH - - - - - - - - This is an enhancement of the existing aka matching logic, which in - some circumstances fails to find the correct aka. - - - - If the destination address matches - Wildcards are not strictly necessary in the match zone:*/*.* or zone:, etc. - - - - When an address does not match any AKAMATCH definition, the - normal aka matching logic takes over. - - - - Mail reader. - - - - , - , - , - - - - -ADDRESS 2:236/77 ; this is primary address -AKA 22:33/44 ; this address valid for zones 21:, 22:, and 23 -AKAMATCH 21:*/*.* 22:33/44 -AKAMATCH 23: 22:33/44 - - - - - - AKAMATCHECHO - - - - - <YES/NO> - - - - This keyword controls whether - - - If set to - - - - - - Mail reader. - - - - Normally it is not desirable to enable aka matching in echomail, - because some echoes may be restricted to members of one particular - network, and an accidental wrong aka matching may attract unwanted - attention from the moderator or the compulsive flamers :-) - - - - , - , - , - - - - - - - AKAMATCHING - - - - - <YES/NO> - - - - This keyword controls whether Random System group it - is defined. When used, it overrides any global - , - , or - you may have. - - - - If set to - - - - - - This keyword is valid Random System group. - - - - Mail reader. - - - - , - , - , - - - - - - - AKAMATCHLOCAL - - - - - <YES/NO> - - - - This keyword controls whether - - - If set to - - - - - - It doesn't really make sense to do aka matching in local areas. The - keyword is just there for completeness. - - - - Mail reader. - - - - , - , - , - - - - - - - AKAMATCHNET - - - - - <YES/NO> - - - - This keyword controls whether - - - If set to - - - - - - Normally it is not desirable to enable aka matching in echomail, - because some echoes may be restricted to members of one particular - network, and an accidental wrong aka matching may attract unwanted - attention from the moderator or the compulsive flamers :-) - - - - Mail reader. - - - - , - , - , - - - - - - - APP - - - - - <programname> [text] - - - - This keyword provides a way for other programs to place configuration - data in - - - The - - - Mail reader. - - - - - - -APP OtherProg REGKEY xyaxajlsaduoiweqeq -APP OtherProg IRQ 5 - - - - - - AREA - - - - - <echoid> <> - <msgbase>[type] <location> [akano] - [attrs] - <-FILE> <type> [path/file] - [switches] - - - - This - - - - - - - - Mail area identifier. - - - - - - - Area description in () quotes. - - - - - - - F, O ( - - - - - - N (Netmail), E (Echomail), L (Local). - - - - - - - Directory path/file or board number. - - - - - - - AKA number (starting from 0) - - - - - - - R/O (Read-Only), and/or other attributes. - - -
- - - - It is recommended to use the newer - keyword, which allows more - detailed mail area setup. - If more than one area defined to the same path or areatag then last - definition overrides previous ones. - For the keyword. - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - AREAAUTOID - - - - - <SHORT/VERBOSE/LONG> - - - - Defines how an automatically created echoid should look, when - finds an area without an - echoid. - - - - - - - VERBOSE - - - The echoids are given a name similar to the function of the - area, such as - - - - LONG - - - The echoids are numbered sequentially like this: - - - - - SHORT - - - The echoids are numbered sequentially like this: - -
- - - - - - - Mail reader. - - - - - - - - - - AREAAUTONEXT - - - - - <YES/NO> - - - - This keyword controls where to put cursor in arealist on startup - and after exiting from an area you have been reading. - - - - If enabled, - - - - - - Mail reader. - - - - - - AREACATCHUPREAD - - - - - <YES/NO> - - - - This keyword controls whether - - - If enabled, - - - - - - This implies that - feature is - used, otherwise it has no function. - - - - Mail reader. - - - - - - - - - - AREACFMREPLYTO - - - - - - - - Sets the area where - - - The destination area for the confirmation messages. - - - - Mail reader. - - - - - , - , - , - , - , - , - - - - - - - AREACOPYADDID - - - - - <YES/NO> - - - - It is useful if you copy echomails to some local archive areas. In - this case -AREA:<OriginalEchoID> - kludge line to inform you from where you copied the mail to. This - keyword should be enabled in the destination area parameters when - used in the Random System group. - - - - If enabled, GoldED+ will insert the - - - - - - This keyword can be used globally and in a - Random System group. - Do not enable this unless you know what you doing! - - - - Mail reader. - - - - , - - - - - - - AREACOPYDIRECT - - - - - <YES/NO> - - - - This keyword controls whether copy/move functions should bypass area - selection screen. The destination area should be set with - keyword. - - - - If enabled, the destination area selection list is bypassed, thereby - making possible a - - - - - - This keyword can be used globally and in a - Random System group. - - - - Mail reader. - - - - , - , - , - , - - - - - - - AREACOPYTO - - - - - - - - Sets the default area for the copy/move functions. Typically you - could set it to a safe/permanent storage type of area. - - - - The default destination area for the copy/move functions. - - - - This keyword can be used globally and in a - Random System group. - The forward function uses the - area instead. - - - - Mail reader. - - - - , - , - , - , - , - - - - - - - AREADEF - - - - - <echoid> <> - <group> <type> <msgbase> <path/board> - <aka> <(attrs)> - [] - - - - This keyword defines a mail area in GoldED+. It looks a - lot like the keyword. Additional - parameters are the - - - - - - echoid - - - Mail area identifier. - - - - - - - - Area description in quotes. - - - - - group - - - Group ID uppercase letter (A-Z) or 0 if not in a group. Use - #groupnumber to specify group numbers in the 1-999 range. - - - - - type - - - - - - - msgbase - - - - - - - path/board - - - Area path, board number or base filename. - - - - - aka - - - Address for the area, or . for the main address. - - - - - (attrs) - - - Default attributes in brackets. - - - - - - - - Optional default origin in quotes. - - -
- - - - If more than one area defined to the same path or areatag then last - definition overrides previous ones. - The possibility of using 'able area configuration - for several setups with different addresses, for example two people - sharing the same msgbase. - If you wish to read packed area (f.e. from CD archive) path/board field, set keyword. - This feature is not supported for - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - AREADESC - - - - - <echoid> <> - [group] [aka] [(attrs)] - [] - - - - Adds a description and optionally a group letter, AKA, - attributes and origin to an existing (previously defined) - area. This is useful if you use an areafile that does not contain - descriptions, groups, akas, attributes or origins. - - - - - - - echoid - - - Mail area identifier. - - - - - - - - Area description in quotes. - - - - - group - - - Optional groupid uppercase letter (A-Z) or 0 if not in a group. - Use #groupnumber to specify group numbers in the 1-999 - range or - to keep the existing groupid. - - - - - aka - - - Optional AKA address for the area, or . for - main AKA, or - to keep the existing - AKA. - - - - - (attrs) - - - Optional default attributes in brackets, - to keep the - existing attributes. Note that if they are specified, they are - added to the default net/echo/local attributes. - - - - - - - - Optional default origin in quotes. - - -
- - - - You cannot skip any of the optional parts in the middle, even if you - only want to set, say, an origin. Use - to keep the existing - value for the parts you skip. - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - AREAEXCL - - - - - - - - With this keyword, you can define the echoids of areas which should - be ignored by , to exclude areas you are - not interested in reading. - - - - The - - - You can use the keyword to - reinclude areas which have been excluded with - This keyword must be placed before any of - , - , - or keywords. - - - - Mail reader. - - - - , - , - , - , - - - - -AREAEXCL * ; Excludes all areas. -AREAEXCL *INTER* ; Excludes all areas containing INTER anywhere in the - ; echoid. -AREAEXCL INT*.* ; Excludes all areas beginning with INT and - ; containing a dot anywhere in the echoid. - - - - - - AREAFILE - - - - - <type> [path/file] - [switches] - - - - - - - - - - - - Name of the program. - - - - - path/file - - - Filename or path to the area setup files. - - - - - - - Areafile specific switches. - - -
- - - - For most programs, GoldED+ can automatically find the - path or filename using environment variables. By default, - . - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - AREAFILEGROUPS - - - - - <YES/NO> - - - - In some setups, you can - groups the areas using single letters (A-Z) or numbers (#1-999). - - - - If this keyword is enabled, GoldED+ will use the area - groupid instead of the area echoid when gathering area specific - information from the Random System - group. - - - - - - - This have only sence if you using Random - System groups. - - - - Mail reader. - - - - chapter - - - - - - AREAFORWARDDIRECT - - - - - <YES/NO> - - - - This keyword controls whether forward functions should bypass area - selection screen. The destination area should be set with - keyword. - - - - If enabled, the destination area selection list is bypassed, thereby - making possible a - - - - - - This keyword can be used globally and in a - Random System group. - - - - Mail reader. - - - - , - , - , - - - - - - - AREAFREQDIRECT - - - - - <YES/NO> - - - - This keyword controls whether filerequest functions should bypass - area selection screen. The destination area should be set with - keyword. - - - - If enabled, the destination area selection list is bypassed, thereby - making possible a - - - - - - This keyword can be used globally and in a - Random System group. - If you (like most) only have one mailer netmail area, you can enable - this feature globally for simpler file requests. - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - , - - - - - - - AREAFREQTO - - - - - - - - Sets the default area for the filerequest functions. - - - - The default destination area for the filerequest functions. - - - - First netmail area. - - - - This keyword can be used globally and in a - Random System group. - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - , - , - - - - - - - AREAINCL - - - - - - - - With this keyword, you can define the echoids of areas which should - be reincluded by keyword. - - - - The - - - This keyword must be placed before any of - , - , - or keywords. - - - - Mail reader. - - - - , - , - , - , - - - - -AREAINCL * ; Includes all areas. -AREAINCL *INTER* ; Includes all areas containing INTER anywhere in the - ; echoid. -AREAINCL INT*.* ; Includes all areas beginning with INT and - ; containing a dot anywhere in the echoid. - - - - - - AREAISEMAIL - - - - - - - - These keyword is designed to mark areas which are read from an - as - - - The - - - This keyword must be placed before any of - , - , - or keywords. - - - - Mail reader. - - - - , - , - , - , - - - - -AREAISEMAIL djgpp*, golded-plus* - - - - - - AREAISNEWS - - - - - - - - These keyword is designed to mark areas which are read from an - as - - - The - - - This keyword must be placed before any of - , - , - or keywords. - - - - Mail reader. - - - - , - , - , - , - - - - -AREAISNEWS alt.*, rec.*, sci.* - - - - - - AREAKEEPLAST - - - - - <YES/NO> - - - - This keyword controls whether - at exit and read it back when run next time. The contents of the file - is a list of lastread information for each area as it was at last - scan. - This feature is helpful when you know that there have not been tossed - new mail and don't want to wait for a full msgbase scan. Now you can - just hit <ESC> at the startup screen to abort the area scan and - - It also makes the - - - Setting this keyword to - - - - - - - - - Mail reader. - - - - , - , - - - - - - - AREALISTECHOMAX - - - - - - - - Allows you to specify a fixed or dynamically sized width of the - - - - If a negative value is specified, the width will be the that of the - widest echoid in the arealist plus the negative value. This might be - useful if some long-name echoes have uninteresting ends, such as - - - - - - - The arealist can dynamically resize the EchoID column is done against the - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - - - - - - AREALISTFORMAT - - - - - - - - The arealist column layout is configurable. This keyword allows you - to change the layout to whatever you like. - - - - The string should be composed from the following letters: - - - - Letter - - - Meaning - - - Default width - - - - - - - Area number - - - 4 - - - - - - - Marked - - - 1 - - - - - - - Description - - - Dynamic - - - - - - - Number of messages - - - 6 - - - - - - - Personal mail mark ( - - 1 - - - - - - - Number of unread/new messages - - - 6 - - - - - - - Changed since last scan mark ( - - 1 - - - - - - - Echoid - - - - - - - - - - Groupid - - - Dynamic: 0, 1 or 3 - - -
- You can also specify widths for each or particular fields if you - don't like the defaults by putting number right after the letter. - If you leave out a letter, that column will not be shown. - - - - - - - - Use only the defined letters. Use spaces to specify required space - between columns. Use only positive numbers for widths. Failure to - obey these rules may cause undocumented behaviour. - - - - Mail reader. - - - - , - , - , - , - , - , - , - - - - - - - - - - AREALISTGROUPID - - - - - <YES/NO> - - - - This feature provides a way to hide group ID on the arealist screen, - in a column to the right of the - - - If enabled, the arealist screen will display the groupid letters, if - any. - - - - - - - The same effect is achieved by skipping definition. - - - - Mail reader. - - - - , - , - - - - - - - AREALISTGROUPORDER - - - - - - - - This keyword allows to change the order in which areas will be sorted - when sorting by group ID is used. If some groups are not found in the - - - - The only parameter is string which specifies groups order. You may - use #groupnumber to specify group numbers in the 1-999 range. - - - - Empty string. - - - - Mail reader. - - - - , - , - - - - - - - AREALISTNOS - - - - - <YES/NO> - - - - This keyword allows to specify whether board number or sequential - area number will be displayed in the arealist. - - - - If enabled, - - - - - - Mail reader. - - - - , - , - , - - - - - - - AREALISTPAGEBAR - - - - - <YES/NO> - - - - Enables or disables a pagebar (scrollbar) in the arealist. - - - - If enabled, - - - - - - Mail reader. - - - - , - , - , - - - - - - - AREALISTSCAN - - - - - <> - [path]<filename> [-delete] - - - - This keyword allows you to define additional menu items for the - arealist scanning menus ( - - - The first two characters of the menu text are the - The filename specifies a plain text file, with the echoids (wildcards - allowed) of the areas you want to scan when the menu item is - selected. There can be several echoids on each line in the file. If - no path is given, the file is loaded from the - . - The - - - Some mail processors automatically delete their list after using it - for replylinking. You may want to do some creative stuff with - batchfiles to grab a copy. - - - - Mail reader. - - - - - - - -=== Cut, NEWSGRPS.LST === -ALT.*, COMP.*, MISC.*, NEWS.* -REC.*, SOC.*, SCI.*, TALK.* -=== Cut === - -=== Cut from an import batchfile === -gecho mgr toss pack -tossbad -if exist import.jam type import.jam >>import.all -if exist import.hmb type import.hmb >>import.all -if exist import.sdm type import.sdm >>import.all -mbutil link -clean -=== Cut === - - - - - - AREALISTSORT - - - - - - - - This keyword defines how the area list should be sorted. You can - override the default setting from the commandline with the - -s switch. - - - - The <sortspec> can be composed of the following types: - - - - - - Sort by aka. - - - - - - - Sort by board number. - - - - - - - Sort by description. - - - - - - - Sort by echoid. - - - - - - - Sorts all - - - - - - Sort by group (if any). - - - - - - - Sorts all marked areas first. - - - - - - - Sort by original order. - - - - - - - Sort by personal mail count. - - - - - - - Sort by personal mail presence. - - - - - - - Sort area separators first. - - - - - - - Sort by type (according to - ). - - - - - - - Sort by unread messages count (try it!). - - - - - - - Sort by unread messages presence (try it!). - - - - - - - Sort by msgbase type. - - - - - - - Sorts all areas with - - - - - - Sort by msgbase path. - - - - - - - Descending sort (largest first). - - - - - - - Ascending sort (smallest first) (default). - - -
- - - - - - - In practice - The - The - The - keyword. - - - - Mail reader. - - - - chapter, - chapter, - , - , - , - , - , - , - , - , - , - , - , - - - - -AREALISTSORT -U+TE - - - - - - AREALISTTYPE - - - - - <NEW/LAST> - - - - Defines the contents of the 4th column (the one after the - - - - - - - - Displays the amount of new (unread) msgs (Actually number of - messages after lastread mark). - - - - - - - Displays the number of the last msg read. - - -
- - - - - - - Mail reader. - - - - , - , - - - - - - - AREAPATH - - - - - - - - This keyword defines where the area setup files are located when - keyword is used. It is - also defines default path for the semaphores. - - - - The - - - Most types can find the path - using the environment variable(s) specific for the program(s). Such - environment variables (or a path specified with the - definition) always overrides - the . - - - - Mail reader. - - - - chapter, - , - - - - - - - AREAPMSCAN - - - - - - - - This keyword defines areas which will be automatically scanned for - personal mail when starting - - - The - - - It is recommended to have to scan all areas at startup. If you don't - want to wait for the scan to complete, you can abort the scan by - pressing <ESC> during startup. - - - - Mail reader. - - - - , - , - , - , - - - - -AREAPMSCAN * ; Scan all areas. -AREAPMSCAN *INTER* ; Scan all areas containing INTER anywhere in the - ; echoid -AREAPMSCAN INT*.* ; Scan all areas beginning with INT and - ; containing a dot anywhere in the echoid - - - - - - AREAPMSCANEXCL - - - - - - - - With this keyword you can prevent areas from being scanned with - on startup. - - - - The - - - This is good if you use - to scan all areas, but have some big areas which slows it down. - You can use the - keyword to reinclude areas which have been excluded with - - - - Mail reader. - - - - , - , - , - , - - - - - - - AREAPMSCANINCL - - - - - - - - This keyword allows to specify areas which are to be scanned with - even if they were - excluded with . - Useful for partial reversal of wildcard specs in the excludes. - - - - The - - - Mail reader. - - - - , - , - , - , - - - - - - - AREAREADONLY - - - - - <SOFT/HARD> - - - - This option is designed for those who setup a system for new computer - users who might be confused enough to enter a message in a read-only - area despite the warning menu. - - - - If this keyword is set to R/O area attribute. The - - - - - - Mail reader. - - - - chapter, - , - , - - - - - - - AREARENAME - - - - - - - - Renames one echoid to another. The feature is meant to be used in - connection with AREAFILE, where some types do not store - echoids with the areas (and GoldED+ then automatically - gives them unique echoids). Also you may rename areas with long - echoid to the shorter one. - - - - - - - Mail reader. - - - - , - , - - - - -AREARENAME NET001 NETMAIL -AREARENAME ECHO001 BAD_MSGS -AREARENAME LOCAL001 BBS.USERS - - - - - - AREAREPLYDIRECT - - - - - <YES/NO> - - - - This keyword controls whether - - Contents of the . - - - Area set with - keyword. - - - Current area. - - - - - - If enabled, - - - - - - This keyword can be used globally and in a - Random System group. - It is probably not a good idea to enable this keyword globally. - If you run a utility or have a mail processor which copies personal - mail to a separate area and puts an AREAREPLYDIRECT in it. - - - - Mail reader. - - - - , - , - , - - - - -GROUP ECHO_PERSONAL - AREAREPLYDIRECT YES -ENDGROUP - - - - - - AREAREPLYTO - - - - - - - - Sets the default area for the reply and forward functions. Typically - you could set it to a safe/permanent storage type of area. - - - - The default destination area for the reply and forward functions. - - - - First netmail area. - - - - This keyword can be used globally and in a - Random System group. - - - - Mail reader. - - - - , - , - , - , - - - - - - - AREASCAN - - - - - - - - This keyword defines areas which will be automatically scanned for - new mail when starting - - - The - - - It is recommended to have to scan all areas at startup. If you don't - want to wait for the scan to complete, you can abort the scan by - pressing <ESC> during startup. - - - - Mail reader. - - - - , - , - , - , - - - - -AREASCAN * ; Scan all areas. -AREASCAN *INTER* ; Scan all areas containing INTER anywhere in the - ; echoid -AREASCAN INT*.* ; Scan all areas beginning with INT and - ; containing a dot anywhere in the echoid - - - - - - AREASCANEXCL - - - - - - - - With this keyword you can prevent areas from being scanned with - on startup. - - - - The - - - This is good if you use - to scan all areas, but have some big areas which slows it down. - You can use the - keyword to reinclude areas which have been excluded with - - - - Mail reader. - - - - , - , - , - , - - - - - - - AREASCANINCL - - - - - - - - This keyword allows to specify areas which are to be scanned with - even if they were - excluded with . - Useful for partial reversal of wildcard specs in the excludes. - - - - The - - - Mail reader. - - - - , - , - - , - , - - - - - - AREASCANSORT - - - - - - - - When scanning areas, - - - The <sortspec> described in details in the - chapter. - - - - - - - Mail reader. - - - - - - - - - - AREASEP - - - - - <echoid> <> - <group> <type> <aka> - - - - You can define area separation lines between groups or areatypes. - - - - - - - - - Mail area identifier. - - - - - - - - Area description in quotes. - - - - - - - Group ID uppercase letter (A-Z) or 0 if not in a group. Use - #groupnumber to specify group numbers in the 1-999 range. - - - - - - - - - - - aka - - - Address for the area, or . for the main address. - - -
- - - - The area separation lines are implemented like a special kind of - area, and are therefore sorted in the arealist just as if they were - actual areas. This is also the reason why you can place the cursor - bar on the separation lines. The fuzzy feature may be used to quickly - go to an area group, that's why cursor can be placed on separation - lines. - When configuring area separation lines, be careful to consider the - , so that the lines - are sorted into the positions you want. If you don't sort areas, you - must make sure that the and - lines. - You will note that the separation lines are not fully connected into - the left and right edges. This is both by design and for practical - reasons (easier to implement), not a bug. - Currently the descriptions are hardcoded to the natural location in - the description column. - - - - Mail reader. - - - - , - , - , - , - , - , - , - - - - - - - - - - - AREASTART - - - - - - - - Normally GoldED+ starts by displaying the arealist, to - let you select which area you want to read. If this keyword is - defined, the arealist is bypassed and AREASTART with the - -e commandline switch. - - - - The - - - Mail reader. - - - - chapter - - - - - - AREATYPEORDER - - - - - <type1> <type2> <type3> - <type4> <type5> - - - - This keyword allows you to change the ordering of the different - area types when sorted by - . - - - - The following types are allowed: - - - - - - Mail reader. - - - - , - - - - - - - AREAYOUWROTETO - - - - - - - - - - - The default destination area for the mails written by you. - - - - This keyword can be used globally and in a - Random System group. - The mail will not be copied if you use - READchangemsg function. - - - - Mail reader. - - - - , - , - , - - - - - - - ASKDELORIG - - - - - <YES/NO> - - - - This keyword allows to automatically delete mail in netmail and local - area after replying on it. - - - - If enabled, you will be asked if the message you just replied to - should be deleted. Otherwise it is left untouched. - - - - - - - This keyword is only functional in netmail and local areas. - - - - Mail reader. - - - - , - , - - - - - - - ATTACHPATH - - - - - - - - Defines the default path when selecting files for attachement. - - - - The default - - - Mail reader. - - - - chapter, - chapter, - , - - - - - - - ATTRIBSATTACH - - - - - - - - Defines the attributes that are added to the existing - attributes of a message when the file attach attribute is toggled on. - - - - Available chapter. - - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSCC - - - - - - - - Defines the default attributes of carbon copy messages. K/S attribute. - - - - Available chapter. - - - - - - - Mail reader. - - - - chapter, - Carbon Copy and Crossposting chapter, - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSCFM - - - - - - - - Defines the default attributes of the confirmation receipt message. - - - - Available chapter. - - - - - - - Suggested attribute is: - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSECHO - - - - - - - - Defines the default attributes of messages entered in echomail areas. - - - - Available chapter. - - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSEMAIL - - - - - - - - Defines the default attributes of messages entered in e-mail areas. - - - - Available chapter. - - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSFRQ - - - - - - - - Defines the attributes to use for messages generated with the file - request function. - - - - Available chapter. - - - - - - - Suggested attributes are: K/S - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSLOCAL - - - - - - - - Defines the default attributes of messages entered in local areas. - - - - Available chapter. - - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSNET - - - - - - - - Defines the default attributes of messages entered in netmail areas. - - - - Available chapter. - - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBSNEWS - - - - - - - - Defines the default attributes of messages entered in news groups. - - - - Available chapter. - - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - ATTRIBUTES - - - - - - - - Defines the default attributes for area members of the current - Random System group. - - - - Available chapter. - - - - This keyword is valid Random System group. - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , - , - , - , - , - , - , - , - - - - - - - BEEPCOMMENT - - - - - <YES/NO> - - - - This keyword enables or disables noise when the cursor in the - internal editor is moved across a word defined with the - keyword. - - - - If enabled, - - - - - - Mail reader. - - - - , - , - , - , - , - , , - - - - - - - BEEPFACTOR - - - - - - - - This keyword allows to change the noise speed made by the - , - , - , - , and - keywords. - - - - The - - - - - - This keyword is valid Random System group. - - - - Mail reader. - - - - , - , - , - , - , - - - - - - BEEPLOCALMSG - - - - - <YES/NO> - - - - This keyword enables or disables noise when - - - If enabled, - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , - , , - - - - - - - BEEPNOISES - - - - - <YES/NO> - - - - This is the - - - If enabled, - - - - - - Mail reader. - - - - chapter, - , - , - , - , - , , - - - - - - - BEEPYOURMAIL - - - - - <YES/NO/ALWAYS> - - - - This keyword enables or disables noise when 's. - - - - If set to - - - - - - Mail reader. - - - - , - , - , - , - , , - - - - - - - CARBONCOPYLIST - - - - - <KEEP/NAMES/VISIBLE/HIDDEN/REMOVE> - - - - This keyword specifies the format of the carbon copy list, as it will - look after processing. You can also change the format in the - - - - The list specification items have the following meaning: - - - - - - Keep the list as entered - - - - - - - Convert list to - - - - - - Convert list to - - - - - - - - - Remove the list completely - - -
- - - - - - - Mail reader. - - - - Carbon Copy and Crossposting chapter, - - - - - - - COLOR - - - - - - - - Using this keyword you can define or redefine all the colors used - in - - - The detailed description for chapter. - - - - Mail reader. - - - - chapter, - - - - - - - COLORSET - - - - - <NORMAL/INTENSE/MONO> - - - - Three color setups are built-in, and can be selected with this - keyword. - - - - The - - - If color video adapter is detected then - - - Mail reader. - - - - chapter, - - - - - - - CONFIRMFILE - - - - - - - - 's with the - - - The - - - - - - Mail reader. - - - - chapter, - chapter, - , - , - , - - - - - - - CONFIRMRESPONSE - - - - - <YES/NO/ASK> - - - - An unreceived message to you with the CFM attribute set tells - - - - - - - - - - Mail reader. - - - - chapter, - , - , - , - , - - - - - - - COOKIEPATH - - - - - - - - Defines the default path for the - - - The default - - - - - - - Mail reader. - - - - chapter, - - - - - - - CROSSPOST - - - - - <YES/NO/ASK> - - - - This keyword configure prompt appearance when saving message which - contains crosspost tokens in the body. - - - - - - - - - - Mail reader. - - - - - - - - - - CROSSPOSTLIST - - - - - <RAW/VERBOSE/YES/NONE> - - - - This keyword specifies the format of the crosspost list, as it will - look after processing. You can also change the format in the - menu before processing - (if menu enabled). - - - - The list specification items have the following meaning: - - - - - - Keep the list as entered - - - - - - - Change the list to lines of "* Crossposted in ..." - - - - - - - Same as above, but expand echolist in line rather than in - column - - - - - - - Crosspost without a list in the msgs - - -
- - - - - - - Mail reader. - - - - Carbon Copy and Crossposting chapter, - , - - - - - - - CTRLINFO - - - - - <YES/NO/TEARLINE,ORIGIN> - - - - Specifies if you want a tearline and/or origin in your messages. - - - - The tokens have the following meaning: - - - - - - Enable both tearline and origin - - - - - - - Disable all control info - - - - - - - Enable tearline, can be used with - - - - - - Enable origin, can be used with - -
- - - - This keyword is valid Random System group. - This may be helpful for - - - Mail reader. - - - - , - , - , - , - , - , - , - , - - - - -CTRLINFO YES ; Add both tearline and origin -CTRLINFO TEARLINE ORIGIN ; Same as above in other words -CTRLINFO TEARLINE ; Add only a tearline -CTRLINFO ORIGIN ; Add only an origin - - - - - - CTRLINFOECHO - - - - - <YES/NO/TEARLINE,ORIGIN> - - - - Specifies if you want a tearline and/or origin in your echomail - messages. - - - - The tokens have the following meaning: - - - - - - Enable both tearline and origin - - - - - - - Disable all control info - - - - - - - Enable tearline, can be used with - - - - - - Enable origin, can be used with - -
- - - - - - - Changing the default may cause unpredictable behaviour with some - echomail processors so it is not recommended to change it. - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - - - - - - - CTRLINFOEMAIL - - - - - <YES/NO/TEARLINE,ORIGIN> - - - - Specifies if you want a tearline and/or origin in your - - - - The tokens have the following meaning: - - - - - - Enable both tearline and origin - - - - - - - Disable all control info - - - - - - - Enable tearline, can be used with - - - - - - Enable origin, can be used with - -
- - - - - - - Changing the default is not recommended. - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - - - - - - - CTRLINFOLOCAL - - - - - <YES/NO/TEARLINE,ORIGIN> - - - - Specifies if you want tearline and origin in your messages in - local areas. - - - - The tokens have the following meaning: - - - - - - Enable both tearline and origin - - - - - - - Disable all control info - - - - - - - Enable tearline, can be used with - - - - - - Enable origin, can be used with - -
- - - - - - - In local areas, the tearline and origin is normally never required - but can be used for cosmetic purposes. - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - - - - - - - CTRLINFONET - - - - - <YES/NO/TEARLINE,ORIGIN> - - - - Specifies if you want tearline and origin in your netmail messages. - - - - The tokens have the following meaning: - - - - - - Enable both tearline and origin - - - - - - - Disable all control info - - - - - - - Enable tearline, can be used with - - - - - - Enable origin, can be used with - -
- - - - - - - In netmail areas, the tearline and origin is normally never required - but can be used for cosmetic purposes. Some robots reqire tearline - in the message. - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - - - - - - - CTRLINFONEWS - - - - - <YES/NO/TEARLINE,ORIGIN> - - - - Specifies if you want a tearline and/or origin in your - - - - The tokens have the following meaning: - - - - - - Enable both tearline and origin - - - - - - - Disable all control info - - - - - - - Enable tearline, can be used with - - - - - - Enable origin, can be used with - -
- - - - - - - Changing the default is not recommended. - - - - Mail reader. - - - - , - , - , - , - , - , - , - , - - - - - - - DISPAREANO - - - - - <YES/NO/ALWAYS> - - - - This keyword specifies if - - - When set to - - - - - - Mail reader. - - - - - - - - - - DISPATTACHSIZE - - - - - <BYTES/KBYTES/NO> - - - - Controls how the size of attached files is displayed in the header. - - - - The following options are provided: the exact size in - - - - - - If the - - - Mail reader. - - - - , - - - - - - - DISPAUTONEXT - - - - - <YES/NO> - - - - Controls which message will be displayed when entering an area. - - - - If enabled, - - - - - - Mail reader. - - - - - - - - - - DISPHDRDATESET - - - - - - - - Specifies the position and length of the date field in the header - display. - - - - Specifies the - - - -20 20 - - - - Mail reader. - - - - , - - - - - - - DISPHDRNAMESET - - - - - - - - Specifies the position and length of the from/to name field in the - header display. - - - - Specifies the - - - 8 36 - - - - Mail reader. - - - - , - , - - - - - - - DISPHDRNODESET - - - - - - - - Specfies the position and length of the from/to node address field in - the header display. - - - - Specfies the - - - 44 16 - - - - The attributes display moves along with the DISPHDRNODESET - values. - - - - Mail reader. - - - - , - , - - - - - - - DISPLISTCURSOR - - - - - <TOP/NEARTOP/MIDDLE/NEARBOTTOM/BOTTOM> - - - - Selects the starting position of selection bar in the message list - and nodelist browsers. - - - - - - - - - At the top if possible - - - - - - - At top + 1/3 if possible - - - - - - - At middle of possible - - - - - - - At bottom - 1/3 - - - - - - - At bottom - - -
- - - - - - - Mail reader. - - - - - - DISPLISTWRAP - - - - - <YES/NO> - - - - Enables or disables wrap-around when the selection bar in the main - list/browser windows reaches the top or bottom. - - - - If set to - - - - - - Mail reader. - - - - - - DISPLOCALHIGH - - - - - <YES/NO> - - - - This keyword controls whether - - - If enabled, - - - - - - Mail reader. - - - - chapter, - , - , - , - - - - - - - DISPMARGIN - - - - - - - - This keyword defines the right margin (display width) used for - message display. - - - - If the - - - 0 - - - - If the keyword is - enabled, the right margin is automatically decreased by one char. - - - - Mail reader. - - - - READdecreasemargin, - READincreasemargin, - , - , - , - , - - - - - - - DISPMSGSIZE - - - - - <BYTES/KBYTES/LINES/NO> - - - - When enabled, this keyword displays the msgbody size in the lower - left side of the header. The size displayed is for the message body - text only, the header and NUL-terminator (and anything that may lurk - beyond it) is excluded from the calculation. - - - - The following options are provided: the exact size in - - - - - - This feature only works when is enabled). - If the - - - Mail reader. - - - - , - - - - - - - DISPPAGEBAR - - - - - <YES/NO> - - - - If enabled, a - - - If enabled, - - - - - - Pagebar is only displayed if a message is longer than a - screenful. - The pagebar automatically decreases the - by one char. - - - - Mail reader. - - - - , - , - , - - - - - - - DISPREALMSGNO - - - - - <YES/NO> - - - - This keyword controls how the - - - If set to - - - - - - Normally the relative numbers are best, because they reflect the - actual number of messages in the system. - - - - Mail reader. - - - - READtogglerealmsgno - - - - - - DISPSOFTCR - - - - - <YES/NO> - - - - This option controls how - - - If enabled, - - - - - - Enabling this feature is feature - working. - The - The similar functionality may be obtained by defining translation - table with - Note that by enabling this feature, you - - - Mail reader. - - - - , - - - - - - - DISPSTATUSLINE - - - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - DISPTABSIZE - - - - - - - - This keyword defines the tab size (number of spaces) used when - displaying the tab (EDITtab and - EDITtabreverse, and when importing external data - in the internal editor. - - - - The - - - 8 - - - - If you use an external editor, you should switch it to create spaces - instead of tabs, because tabs are technically not allowed in - - - - Mail reader. - - - - EDITimportquotebuf, - EDITimporttext, - EDITpaste, - EDITtab, - EDITtabreverse - - - - - - DOSPROMPT - - - - - <YES/NO> - - - - Controls whether - - - If set to keyword in - the language configuration file to the system shell. - - - - - - - This feature is known to be broken on some platforms. - - - - Mail reader. - - - - AREAdosshell, - EDITdosshell, - FILEdosshell, - LISTdosshell, - NODEdosshell, - READdosshell, - , - - - - - - - EDITAUTOATTACH - - - - - <YES/NO> - - - - If you use drivespec ( - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITAUTOSAVE - - - - - - - - This keyword provides the way for keeping automatic backup of the - message you are writing. The saved file can be restored with the - - keyword. - If disaster strikes (crash, lockup, power blackout, etc.) while - you are writing a message in the internal editor, this feature - lets you continue from the last autosaved message, which will - popup automatically when you enter the internal editor again. - - - - If a non-zero value is given, the internal editor will automatically - execute the - - - 30 - - - - This feature only works 100% if - is set to is set to - - - Mail reader. - - - - , - - - - - - - EDITCHANGEDATE - - - - - <ALWAYS/YES/NO> - - - - This keyword controls whether - - - If set to - - - - - - Mail reader. - - - - READchangemsg - - - - - - EDITCHARPARA - - - - - - - - This keyword defines the character - - - The - - - - - - This keyword is primarily for debugging, the suggested replacement - is a paragraph sign ( - - - Mail reader. - - - - - - - - - - EDITCHARSPACE - - - - - - - - This keyword defines the character - - - The - - - - - - This keyword is primarily for debugging, the suggested replacement - is a small dot (CP437 250). - - - - Mail reader. - - - - - - - - - - EDITCOMMENT - - - - - <> - <> - - - - This feature allows you to define words which causes - - - The - - - Mail reader. - - - - , - , - - - - - - - - - - EDITCOMPLETION - - - - - <> - <> - - - - This keyword allows you to define abbreviations which will be - automatically expanded to full words or sentences when typed in - the internal editor. - - - - The - - - The abbreviation is case-sensitive. If is defined - as an abbreviation, completion will is typed. - - - - Mail reader. - - - - , - - - - - - - - - - EDITCRLFTERM - - - - - <YES/NO> - - - - This keyword controls the format to be used for the paragraph line - termination. - - - - If set to CR/LF combination. If set to - - - - - - This option was created to fix a problem with an older version of the - CR/LF termination of kludge lines. - - - - Mail reader. - - - - - - EDITFIELDCLEAR - - - - - <YES/NO> - - - - This keyword controls the behaviour of the input-fields, if a - non-edit key is the first key pressed. - - - - If set to - - - - - - Mail reader. - - - - - - - - - - - EDITHARDLINE <string> - -

- ("<<") -

-

- The string is needed if you use an external editor that terminates - all lines with a CR or CR/LF. The hardline string acts as a text - paragraph terminator, and the normal CR's are ignored. -

-

- The concept of "hardlines" is explained in the Hardline Feature - chapter. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITHARDLINES <yes/no> - -

- (yes) -

-

- This keyword enables the "hardline" feature. If disabled, the - EDITHARDLINE string is never written to the editor message file, - and the editor message file is read back exactly as entered, - including terminating CR's on all lines. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITHARDTERM <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will hard-terminate all lines in your messages - at the editor margin. It is recommended to enable this keyword for - Internet e-mail and newsgroups, because some user-unfriendly - Internet software does not wrap long lines properly. But DON'T - enable it in normal FidoNet echomail. -

-

- This keyword can be used globally and in Random System groups. - , - -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITHDRNAMESET <pos> <len> - -

- (8 36) -

-

- Specfies the position and length of the from/to name field in the - header edit display. If a negative value is specified, that value - is added to the current display width. -

- - - - EDITHDRNODESET <pos> <len> - -

- (44 36) -

-

- Specfies the position and length of the from/to node address field - in the header edit display. If a negative value is specified, that - value is added to the current display width. -

- - - - EDITHEADERATTRS <yes/no> - -

- (yes) -

-

- This keyword allows you to turn off the large attributes window - that is shown during header edit. Even if the window is turned - off, the Alt-keys are still active for toggling attributes. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITHEADERFIRST <new,changes,replies,forwards,yes/no> - -

- (yes) -

-

- This keyword controls the circumstances that will present you with - the header editor first of all. -

-

- New When entering a new message. - Changes When changing a message - Replies When making a reply. - Forwards When forwarding a message. - Yes Always (all of the above). - No Never. -

-

- The New, Changes, Replies and Forwards values can be combined. YES - is equivalent to enabling all four of these. -

-

- For example, we want to edit the header only when entering a new - message or when changing a message: -

-

- EDITHEADERFIRST New, Changes -

-

- If the circumstances match the setup of this keyword, the header - edit will be bypassed and you will start directly in the EDITMENU - (if enabled) or in the internal or external editor. A new menu - item has been added in the EDITSAVEMENU, "Edit Header", which - allows you to edit the header after you have written your message, - but before it is finally saved. -

-

- If you set EDITHEADERFIRST to NO, you must either have the - EDITSAVEMENU enabled, or use the internal editor, because - otherwise it is not possible to edit the header at all. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITINTERNAL <yes/no> - -

- (yes) -

-

- Specifies if the internal editor should be the default, even if an - external editor is defined. You can always change the setting in - the editor menu (if EDITMENU is enabled) before you start writing - your message. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITMENU <yes/no> - -

- (yes) -

-

- This keyword enables or disables the "Edit menu" that pops up - right after you have edited the message header. If you disable the - menu, you will go to the internal or external editor immediately - and save a keystroke, but you will of course lose the features - available from the menu, such as selection of template etc. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITMIXCASE <yes/no> - -

- (no) -

-

- If this keyword is enabled, GoldED+ will automatically format the - name with uppercase the first letter in words and lowercase the - rest, when entering names in the header. -

-

- Examples: -

-

- "odinn sorensen" or "ODINN SORENSEN" -

-

- These would be re-cased to "Odinn Sorensen". -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITOR <commandline> [@file] [@line] - -

- With GoldED+ it is possible to use your favorite text editor or - even word processor to write messages. With this keyword you - specify the commandline for the editor. -

-

- If you use a word processor, be sure to make it export clean ASCII - text files without control codes. -

-

- <commandline> Program commandline. - @file Token which is replaced by the editor message - filename. - @line Token which is replaced by the @Position - template line number. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITORFILE <file> - -

- (GOLDED.MSG) -

-

- Defines the name of the temporary editor message file. This file - is written by GoldED+ when swapping to the external editor, or when - using the EDITsavefile command in the internal editor. -

-

- The file is written in the GOLDPATH if there is no explicit path. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITQUOTEMARGIN <margin> - -

- (75) -

-

- Sets the right margin for editing quoted lines in the internal - editor. This should be set to the same or wider than the - QUOTEMARGIN. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITREPLYRE <yes/no/numeric> - -

- (no) -

-

- If enabled, GoldED+ inserts the "Re:" string in front of the - subject when you reply to a message. If not enabled, GoldED+ will - strip any leading "Re:" when you reply to a msg. -

-

- The "Re:" string in subjects is an obsolete practice, and today it - only slows down modern replylinking software. Do yourself and - others a favor and let GoldED+ strip the Re: in your replies. -

-

- The "numeric" option makes GoldED+ use numeric Re:'s, of the form - "Re^n:". -

-

- This keyword can be used globally and in Random System groups. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITSAVEMENU <yes/no> - -

- (yes) -

-

- This keyword enables or disables the "Save menu" that pops up - after you have edited your message in the internal or external - editor. If you disable the menu, your message will be saved (or - discarded if not edited) immediately and save you a keystroke, but - you will also lose the features available from the menu. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITSAVEUTIL <utilno> <"L menu text"> - -

- Defines the external utilities that will be added to the - EDITSAVEMENU (if enabled). The menu text is inserted in the menu. - The first two characters of the menu text are the "hotkey" letter - that will be highlighted in the menu text, plus a space. Example: -

-

- EDITSAVEUTIL 1 "S PGP Sign the msg" - EDITSAVEUTIL 2 "l PGP Clear-Sign the msg" - EDITSAVEUTIL 3 "E PGP Encrypt the msg" - EDITSAVEUTIL 4 "p PGP Encrypt & Sign the msg" -

-

- If you have changed the default language in this menu (in - GOLDLANG.CFG), then make sure the highlight letters don't clash. -

-

- With EDITSAVEUTIL definitions and EDITSAVEMENU enabled, you can - directly call an external utility to do things like encoding or - encrypting msgs before saving them. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITSOFTCRXLAT <char> - -

- If a translation char is defined, GoldED+ will translate the - soft-cr character (ASCII 141, HEX 8D) while saving message to base. - The following example translates the soft-cr to an 'H' (for use in Russia): -

-

- EDITSOFTCRXLAT H -

-

- You also have to enable the DISPSOFTCR keyword. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITSPELLCHECK <commandline> [@file] - -

- While in the internal editor, you can use the EDITspellcheck - command to save your message to a file and shell to external - spellchecking software. When the check is completed, the corrected - file is read back and you can continue editing your message. The - EDITspellcheck command internally uses the EDITsavefile and - EDITloadfile commands. -

-

- <commandline> Spellchecker program commandline. - [@file] Token which is replaced by the message filename - (defined by the EDITORFILE keyword). -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EDITUNDELETE <lines> - -

- (50) -

-

- This keyword defines the number of lines to keep in the undelete - buffer between messages. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EMPTYTEARLINE <yes/no> - -

- (no) -

-

- With this keyword enabled, GoldED+ will always strip the tearline - down to just the three dashes, "---", and instead inserts the PID - (Product IDentification) kludge line, which contains the same - information, but in a safer form in a safer place. The PID kludge - is proposed in FidoNet document FSC-0046. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - ENCODEEMAILHEADERS <yes/no> - -

- (yes) -

-

- By default headers in e-mails MIME-encoded according to RFC. In - Russia it is general practice not to encode headers, so you - probably want to say No here if you're in Russia ;-) This keyword - supported only in -asa versions. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - ENDGROUP - -

- Ends a Random System GROUP definition. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EVENT <eventtype> <eventcommand [parameters]> - -

- This keyword allows you to specify which soundfile to play when a - specfic event occurs. The following <eventtype>'s are defined: -

-

- EVENTTYPE TRIGGER: -

-

- Arealist When the arealist shows. - AskYesNo Any Yes/No type prompt. - Attention Warnings or information popup messages. - DosShell When entering a DOS or OS/2 shell. - EditComment When an editcomment is found. - EndOfMsgs When there are no more msgs in the area. - ErrorFatal Fatal error exit. - Exit Exit from GoldED+. - JobDone Successful completion of a job. - JobFailed Unsuccessful completion of a job. - MsgDeleting When deleting a msg. - MsgFromYou When a msg from you is found. - MsgIsLocal When a msg marked Local is found. - MsgIsTwit When a msg from a Twit is found. - MsgToYou When a msg to you is found. - SearchFailed Search operation failed. - SearchSuccess Search operation was successful. - Startup When the GoldED+ startup screen shows. -

-

- There is currently only one <eventcommand> defined: -

-

- PLAY <filename.ext/beepnoise>. -

-

- The parameter to PLAY can be either a sound file or one of the - following standard beepnoises: -

-

- TheEnd A high and a low note. - GotIt Two sets of low-high notes. - TooBad A falling note. - ToYou A rising and falling note. - SayBiBi A single beep. - SOS Morse S O S (...---...). -

-

- If a sound file is specified, the sound driver must support the - format. -

-

- The DOS and 386 versions need a Goldware Sound API compatible TSR - or program loader which installs an interrupt service function on - the multiplex interrupt 2Dh. See the chapter about the Goldware - Sound API for more details. The GCTVSAPI program loader (released - separately) currently only supports the CT-VOICE.DRV driver for - .VOC files. -

-

- The OS/2 version relies on MMPM/2 (using the mciSendString API - call) to play the sound files. On my system with a Sound Blaster - Pro, MMPM/2 plays both .WAV and (to my surprise) .VOC files. It - even plays .MID files :-) -

-

- The Win32 version uses the Win32 API to play the sound files. It - should be able to play any multimedia file that Windows knows how - to handle. -

-

- Example usages: -

-

- EVENT MsgToYou PLAY HIMAN.VOC - EVENT MsgIsTwit PLAY SHOTGUN.VOC -

-

- You have to select the sounds carefully and probably with a lot of - experimentation, unless you want to turn your mailreader into a - honking, wailing and farting monster and drive your poor family or - yourself nuts with a cacophony of noises... -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EXCLUDENODES <addressmask> - -

- You can define up to 50 different addressmasks to be excluded from - the compiled nodelists. Use this if you are short of space, or the - nodelist compile takes very long on your system. This keyword is - used by GoldNODE. -

-

- Excluded nodes can be re-included with the INCLUDENODES keyword. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EXTERNOPTIONS <-options> - -

- Defines the default options for the EXTERNUTIL's. Valid options: -

-

- -Cls * Clear screen. - -Cursor * Cursor in shell. - -KeepCtrl * Keep control lines in the message. - -Pause Pause for keypress before returning to GoldED+. - -PauseOnError * Pause only if utility errorlevel is nonzero. - -Reload * Reload the message file (@file). - -Wipe Wipe editorfile and temporary file after use. -

-

- Plus the reverse options with a "No" prefix, for example -NoCls. - The default options are marked with an asterisk (*). -

-

- Use -NoKeepCtrl when you want to clearsign a message. This will - strip the control lines (kludges, tearline and origin) from the - message before passing it to the external utility. The tearline - and origin is appended to the message when reloading it. The - default is to keep control lines in the message. -

-

- Use -Wipe when you want the temporary unencrypted message files to - be wiped and removed from the disk after they have been read into - memory. GoldED+ wipes a file by writing a block of 512 random bytes - over the entire length of the file, then truncating it to zero - bytes and finally deleting it. The default is not to wipe files. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EXTERNUTIL <utilno> [-options] <commandline> - -

- This new feature can be used to "filter" msgs, for example calling - PGP or other encryption utilities. -

-

- The <utilno> must be in the range 1 to 24 for utilities that will - be called with key definitions (see below). Higher numbers can be - used for utilities that are called from the EDITSAVEMENU (if - enabled). See the EDITSAVEUTIL keyword for details. -

-

- The default options are those specified with the EXTERNOPTIONS - keyword. With [-options], you can change the those options locally - for specific utils. See the EXTERNOPTIONS keyword for a list of - valid options. -

-

- The <commandline> specfies the DOS or OS/2 commandline you want to - execute. This works in the same way as for the external editor and - spellchecker. See the manual for details about this, especially if - you want to execute batchfiles. In the <commandline> you can use - @tokens to transfer information from the msg to the commandline. - The @tokens are the same as for templates, and in addition you can - use two other @tokens: -

-

- @path The GOLDPATH, including a trailing backslash. - @file The full filename of the message file (GOLDED.MSG) - that will be written to disk before the utility is - called. - @tmpfile The full filename of a temporary message file - (GEDTMPxx.xxx) that will be written to disk before the - utility is called. -

-

- Examples: -

-

- EXTERNUTIL 1 c:\4dos\4dos.com /c c:\crypt\encrypt.bat @file - EXTERNUTIL 2 c:\4dos\4dos.com /c c:\crypt\decrypt.bat @file -

-

- To call a defined external utility, you must assign a key to it. - There are 24 new keyboard commands you can use in GOLDKEYS.CFG for - this purpose: -

-

- ExternUtilNN -

-

- Where NN is in the range 01 to 24 _with_ leading zero. Examples: -

-

- F11 ExternUtil01 - F12 ExternUtil02 -

-

- Then if you press F11, you would call external utility number 1 - and so on. The ExternUtilNN keywords ONLY work in reader mode, not - in the internal editor or any other place. -

-

- HOW IT WORKS: -

-

- 1. Just before the external utility is called, GoldED+ writes the - current message text to the GOLDED.MSG file in the GOLDPATH. - The file is written as a textfile with each line CR-LF - terminated. The content is exactly as you see it on the - screen, which means that kludges are only included if you have - enabled kludge viewing. If the -NoKeepCtrl option is used, - kludges, tearline and origin are stripped before the file is - written. If the token @tmpfile is used, a temporary file named - GEDTMPxx.xxx (where xx.xxx is something unique) is created - with exactly the same content as @file. -

-

- 2. GoldED+ clears the screen and then calls the utility. -

-

- 3. The utility can now load and process the @file and/or - @tmpfile, or do anything else you want. It doesn't have to - have anything to do with the current msg. You could call a - spreadsheet, a game, whatever. But I think this feature will - mainly be used for utilities that process the @file. If the - utility processes the @file, it could write the changes back - to the @file. -

-

- 4. After returning from the utility, GoldED+ reloads the @file and - displays it just as if it was the current message. For - example, if your utility was a decrypter and the msg was - encrypted, you would now see the decrypted msg. Neat eh? :-) -

-

- 5. If you want to make the reloaded text permanent (save it in - the msg), you can use the Change Msg function and immediately - choose "Save Message" from the Editing menu (if enabled with - EDITMENU Yes). This is in fact the method you could use if you - wanted to EN-crypt a msg (however, it is easier to use the - method which involves the EDITSAVEUTIL keyword). -

-

- The QUOTESPACING feature can interfere with encoded msgs that - include the '>' character at the beginning of lines (often seen in - uuencoded msgs), by automatically inserting blank lines before and - after the lines with '>'. I have therefore changed the - quotespacing default from YES to NO. Be sure to check if you have - a different setting if you are using an older edition of the - advanced configuration files. -

-

- If the string "-----BEGIN PGP MESSAGE-----" is found as the first - 27 characters in a reloaded message, GoldED+ will automatically add - the FSC-0073 kludge "^aENC: PGP" to indicate that the message is - encrypted. This kludge may be used by some software to set up - alternative routing for encrypted mail which would otherwise be - bounced if sent through normal channels. -

-

- See the "Using PGP as an External Utility" chapter for batchfile - examples and instructions on how to use this new feature with PGP. -

-

- !!! IMPORTANT !!! From FidoNet Policy 4.07 (chapter 2.1.4): -

-

- "[..] Therefore, encrypted and/or commercial traffic that is - routed without the express permission of all the links in the - delivery system constitutes annoying behavior." -

-

- So be careful with this feature! -

-

- TIP: You can use the EXTERNUTIL feature to setup keys to view or - print an attached fax. Use something like this in GOLDED.CFG: -

-

- EXTERNUTIL 11 c:\zfax\zfax.com pf @subject ; print fax - EXTERNUTIL 12 c:\zfax\zfax.com vf @subject ; view fax -

-

- And this in GOLDKEYS.CFG: -

-

- @F11 ExternUtil11 ; Press Alt-F11 to print the fax - @F12 ExternUtil12 ; Press Alt-F12 to view the fax -

-

- Or choose your own key assignments and fax view/print utils. -

-

- Note that this assumes that the fax file is listed in the subject - line like an attached file. -

-

- NOTE: If you're running GoldED+/386 and try to use a Win32 program - as an EXTERNUTIL, you might get the error "This program cannot be - run in DOS mode". You can work around this by calling the Win32 - program via the shell. For example if this call fails: -

-

- EXTERNUTIL 1 c:\utl\mywin32.exe @file -

-

- Replace it with: -

-

- EXTERNUTIL 1 command.com /c c:\utl\mywin32.exe @file -

-

- Then it should work. If not, try using full path to command.com. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EZYCOMMSGBASE <path> - -

- Defines the base path for the Ezycom msgbase. If not set, AREAFILE - Ezycom will set it. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EZYCOMUSERBASE <path> - -

- Defines the base path for the Ezycom userbase. If not set, - AREAFILE Ezycom will set it. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - EZYCOMUSERNO <userno> - -

- (0) -

-

- Defines the lastread set used in the Ezycom message base. -

- - - - <YES/NO> - - - - This keyword controls statusline appearance in the - - - If set to - - - - - - Mail reader. - - - - , - - - - - - - - - - - - - - - - - FIDOHWMARKS <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will use the echomail "highwater mark" (1.MSG) - to determine if a message is "sent" or "unsent" in *.MSG areas. -

-

- NOTE: Some older echomail processors do not update the highwater - mark in a way that GoldED+ can recognize. If all messages appear to - marked "Uns", even after the mail has been scanned out, try - turning off this keyword. -

- - - - FIDOLASTREAD <file> - -

- (LASTREAD) -

-

- Defines the filename of the *.MSG lastread files. DO NOT specify a - path. -

- - - - FIDOMSGTYPE <Opus/FTS1> - -

- (Opus) -

-

- This keyword defines the default format of Fido *.MSG files. It is - only used by some AREAFILE's when reading external area - configuration files, where the preferred format is unknown. -

-

- The FTS1 (FTS-0001.012 and later) format uses zone/point fields, - where the Opus format uses date/time stamps. When set to Opus - format, GoldED+ interprets the date/time stamps as DOS-style - bitmapped date/time. -

- - - - FIDONULLFIX <yes/no> - -

- (no) -

-

- If set to YES, GoldED+ will replace NUL chars with LF chars in the - msg body when reading a Fido *.MSG file. This is slower of course, - but not noticably on fast machines. -

-

- This option was created to enable GoldED+ users to read msgs that - were created/handled by brain-dead programs (I don't have names, - sorry) which are not obeying our primary technical standard: - FTS-0001. FTS-1 states that a NUL terminates the msg body. But - sometimes msgs are encountered which have a NUL as the first char - in the msg body or perhaps in other places, thereby causing GoldED+ - to show a blank or cut-off msg. In some Pascal-based readers, such - as FM, these msgs can be read anyway, because in Pascal a NUL does - not terminate a string like in C/C++. -

-

- NOTE: Even if the new FIDONULLFIX keyword is disabled, GoldED+ will - still fix a NUL if it is the _first_ character in the msg body. - This probably fixes most of these buggy msgs without the overhead - of checking the entire msg. -

- - - - FIDOUSERLIST <file> - -

- Path and filename of a FIDOUSER.LST file. -

-

- This file is expected to be sorted in ascending alphabetical order - using plain ASCII case-insensitive sort. Each line in the list is - expected to be 60 characters plus a CR and a LF, or in other words - records of 62 bytes each. If the list is produced by a nodelist - compiler, everything should be okay, but be careful if you have - edited the file manually. Note that a FIDOUSER.LST file only - supports a name lookup (to get the address). -

- - - - FIDOUSERNO <userno> - -

- (0) -

-

- This is an index into the FIDOLASTREAD file. Each user occupies 2 - bytes in the lastread file. -

- - - - FILEALIAS <alias> <filename> - -

- Used to define short alias names for filenames. If you regularly - write msgs to different files in different paths, this feature is - very useful, and reduces the risk of typing wrong. -

-

- Example: -

-

- FILEALIAS DKB R:\DKBBS\DKBBS -

-

- With this file alias, you can simply write "DKB" at the filename - prompt, and the long filename will be used. -

- - - - FILELISTPAGEBAR <yes/no> - -

- (yes) -

-

- Enables or disables a pagebar (scrollbar) in the file attach list - function. -

- - - - FORCETEMPLATE <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will popup a template selection menu when you - start writing a new msg or reply. If you have both TEMPLATE(s) and - FORCETEMPLATE in a Random System group, you can tell GoldED+ to use - the random template(s) by hitting ESC instead of selecting from - the menu. -

-

- This keyword can be used globally and in Random System groups. -

- - - - FORMFEEDSEPARATOR <yes/no> - -

- (no) -

-

- Used when saving messages to file. If enabled, it inserts a Form - Feed (12d) character after each message. -

- - - - FRQEXT <.ext> - -

- With this keyword you can add extra known filename extensions for - the filerequest function. The following extensions are already - known by default, and need not be defined (duplicate definitions - are ignored): -

-

- .ARC .ARJ .DOC .EXE .GIF .LHA .LZH .JPG .PAK .PNG .RAR .RUN .SDA - .SDN .TXT .ZIP .ZOO -

-

- Each extension _must_ have the leading dot. -

-

- Example: FRQEXT .XYZ -

- - - - FRQNODEMAP <to-node> <from-node> - -

- This keyword is used for the file request feature (Ctrl-F). It - allows you to define mappings from a nodenumber used in a file - announcement to another nodenumber. This is useful in the cases - where a multi-line system announces files using their primary - nodenumber, which may be a regular V34 modem number, but they also - have an ISDN number, which you would prefer to use instead. - Examples: -

-

- // change-to: from: - FRQNODEMAP 2:236/99 2:236/100 - FRQNODEMAP 2:236/1043 2:236/43 -

-

- So, if I saw a file announcement from 2:236/100, and requested - some files, the request would automatically be addressed to - 2:236/99. -

- - - - FRQOPTIONS <options> - -

- (FromTop) -

-

- Defines options for the file request function: -

-

- Sort Sort the list of files alphabetically. - FromTop Scan the message from the top of the message. - NotFromTop Scan the message from the top of the screen. - NoFiles Don't list the file FILES if no files were found. - NoWazooMsg Don't save the request message. - Fast Bypass the header edit and save the msg immediately. -

-

- By default, the "FromTop" option is enabled. If you often request - files from very long announcement messages, you might find it very - useful to set the "NotFromTop" option. -

-

- The "NoFiles" option was added because if no filenames are found - in a message, the file request function defaults to listing the - magic name FILES instead of complaining that no files were found. -

-

- If the FRQWAZOO keyword is enabled, the default behaviour is to - save the request message with the FRQ attribute stripped. Use the - "NoWazooMsg" option if you don't want the request message. -

-

- Use the "Fast" option if you find that you almost never change the - destination of the file request message anyway. If you enable this - option, remember that you can always go over to the netmail area - and change the file request message before it is sent. -

-

- The UseFlowFile option enables a feature which was default in - 2.50, but which I have been informed is problematic for modern - mailers in some setups. The default is now to ONLY create/update - the .REQ file and NOT also touch/create a .?LO flowfile. -

- - - - FRQWAZOO <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will create WaZOO .REQ files instead of file - request messages. You must define an OUTBOUNDPATH if you enable - this feature. -

- - - - GEDHANDSHAKE <yes/no> - -

- (yes) -

-

- If this switch set to yes GoldEd displays handshake char in - statusline. If you annoyed with this feature you could hide this - character by setting this option to no. -

- - - - GERMANKEYBOARD <yes/no> - -

- (autodetect) -

-

- This option is meanful for w32 version only. Due to right Alt key - required to enter some native characters in german version of - Windows it could be defined to yes for this. -

- - - - GOLDBASEPATH <path> - -

- Specifies the directory where GoldED+ can find the Goldbase msgbase - files. -

- - - - GOLDBASESYSPATH <path> - -

- Specifies the directory where GoldED+ can find the NETMAIL.DAT and - ECHOMAIL.DAT files of the Goldbase msgbase. If not specified, the - GOLDBASEPATH is used. -

- - - - GOLDBASEUSERNO <userno> - -

- (0) -

-

- Specifies the lastread set used in the Goldbase message base. -

- - - - GOLDPATH <path> - -

- This is the path where GoldED+ finds all it's control files. It is - not necessary to define this, unless you have special needs. The - GOLDPATH defaults to directory where the GOLDED.CFG file was - found. -

- - - - GROUP <groupname> - -

- Starts a Random System group. See the Random System chapter for - details. -

- - - - HIGHLIGHTUNREAD <yes/no> - -

- (no) -

-

- If enabled, GoldED+ updates (increases) the "timesread" field in - each message that you read. If set to NO, it doesn't touch the - message. The YES setting causes a slight performance decrease, - because the header of each message has to be read, the timesread - field updated and the header written back to disk. The update - happens immediately after the message is displayed, so you may not - notice it at all. A message is only updated if the timesread field - contains the value 0 (zero). -

-

- This keyword only works in the following msgbase formats: Fido - (*.MSG), Hudson, Goldbase, JAM, Squish, Ezycom and AdeptXBBS. In - Squish and Ezycom, there is no timesread field, but I have annexed - a reserved message attribute (in Squish, 0x00080000, now called - MSGSEEN; in Ezycom, extattr 0x80) for the purpose of marking a - message as read at least once. The other formats (PCBoard, - WildCat) have no timesread field, but they have reserved fields or - attributes which *could* be used. -

- - - - HUDSONPATH <path> - -

- Specifies the directory where GoldED+ can find the Hudson msgbase - files. -

- - - - HUDSONSIZEWARN <size in bytes> - -

- (16000000) -

-

- When the Hudson MSGTXT.BBS file exceeds this size, GoldED+ starts - to warn that the msgbase is getting dangerously close to the - structural limit (which is 16MB for the MSGTXT.BBS file). With - this keyword you can raise or lower the warning size in case you - think the default is too low or too high. -

- - - - HUDSONSYSPATH <path> - -

- Specifies the directory where GoldED+ can find the NETMAIL.BBS and - ECHOMAIL.BBS files of the Hudson msgbase. If not specified, the - HUDSONPATH is used. -

- - - - HUDSONUSERNO <userno> - -

- (0) -

-

- Specifies the lastread set used in the Hudson message base. -

- - - - IGNORECHARSET <yes/no> - -

- (no) -

-

- If set to yes then GoldEd ignores CHRS kludges in messages thus - you will be able to switch codepage in messages with inappropriate - charset. -

- - - - IMPORTBEGIN <text> - -

- ("=== Cut ===") -

-

- This keyword, together with IMPORTEND, defines some text to add in - the beginning and end of an imported text file in the internal - editor. If only IMPORTBEGIN is defined, the text is also used for - the IMPORTEND. The <text> may be enclosed in quotes ("") if - leading or trailing spaces are needed. The quotes are stripped. -

-

- The replacement token "@file" can be used in the <text>. It will - be replaced with the import filename as entered. -

-

- Example: -

-

- IMPORTBEGIN === Cut Begin: @file === - IMPORTEND === Cut End === -

- - - - IMPORTEND <text> - -

- (same as IMPORTBEGIN) -

-

- See IMPORTBEGIN. -

- - - - INBOUNDPATH <path> - -

- (defaults to GOLDPATH) -

-

- The inbound path is currently only used with the file request - feature (the READfilerequest command, <Ctrl-F>). If you use this - feature, GoldED+ will put the file descriptions into a FILES.BBS in - the inbound path, ready for when the requested files are moved to - the correct file areas. -

- - - - INCLUDE - - - - - - - - This tells the configuration file reader to stop reading the current - configuration file, and start reading the file specifyed as an - extra configuration source, then resume reading the previous - configuration file. - - - The - - - Mail reader and nodelist compiler. - - - - - - INCLUDENODES <addressmask> - -

- You can define up to 50 different addressmasks to be included from - the compiled nodelists. This is only used in conjunction with the - EXCLUDENODES keyword to include otherwise EXcluded nodes. This - keyword is only used by GoldNODE. -

- - - - INPUTFILE <filename> - -

- (*) -

-

- Defines the default name in the internal editor file import - function. -

-

- GoldED+ can automatically uuencode and apply a base64 encoding to - the files during importing them into the internal editor. -

-

- NOTE: This is a very simple implementation of encoders. It cannot - split large files over several messages. The file mode number 644 - is hard-coded and has nothing to do with the actual file mode. -

-

- This keyword can be used globally and in Random System groups. -

- - - - INTENSECOLORS <yes/no> - -

- (no) -

-

- GoldED+ is capable of switching off the "blink" color, and thereby - enabling the use of bright background (paper) colors. Enable this - keyword, and try out one of the intense color setup examples. -

- - - - INTERNETADDRESS <internet-address> - -

- Specifies your Internet address. This must be the address only, no - name. The INTERNETADDRESS and USERNAME will be combined to a - standard "From: internetaddresss (username)" headerline when you - write e-mail or articles. -

-

- Example: -

-

- USERNAME Odinn Sorensen - INTERNETADDRESS odinn@ibm.net -

-

- Produces the RFC line: -

-

- From: odinn@ibm.net (Odinn Sorensen) -

- - - - INTERNETDOMAIN <domainname> - -

- (username%domain.net) -

-

- Defines the domain-part of outgouing Message-ID's. If you don't - know your full domain, leave it as default, which should work just - fine. -

- - - - INTERNETGATE [gatename<,>]<address> - -

- Defines the local Internet gate you use when sending netmail to - Internet users. This option is activated when you write an - Internet address in the TO: field in the header display. GoldED+ - detects the Internet address by looking for the '@' character. If - detected, GoldED+ puts the gate address from INTERNETGATE in the - TO: address field. If you have defined the optional gate name - (typically UUCP), GoldED+ also replaces the typed Internet address - with the gate name and puts the Internet address in a TO: line in - the message body. Some gate software accepts the Internet address - directly in the header, while other software may need the special - (UUCP) name and a separate TO: line. Examples: -

-

- INTERNETGATE UUCP, 1:105/42 ; Standard, with gate name - INTERNETGATE 2:230/9316 ; My uplink runs GIGO software -

-

- This keyword can be used globally in GOLDED.CFG, if you only ever - use one gate, or in GROUP's for specific areas in GOLDRAND.CFG if - you have multiple netmail areas and regularly use more than one - gate. -

-

- NOTE: If you enable the INTERNETRFCBODY keyword, you should always - use the gatename UUCP, because otherwise the gateway software may - send duplicate copies (carbon copies) of your e-mails. -

- - - - INTERNETLOOKUP <yes/no> - -

- (no) -

-

- If set to Yes, GoldED+ will check the systemname in the nodelist - when doing a lookup and if the systemname looks like an Internet - address (contains an '@' char), the msg will be addressed to that - Internet address using the INTERNETGATE name/address if defined. -

-

- For example, let's say there was something like this in the - nodelist: -

-

- ,999,somebody@somewhere,Whereever,Some_Body,... -

-

- And this in my GOLDED.CFG: -

-

- INTERNETLOOKUP Yes - INTERNETGATE 2:230/9316 -

-

- Then if I did a lookup of "Some Body" and selected the entry with - the Internet address, GoldED+ would make a msg looking like this: -

-

- -------------------------------------- - From : odinn@winboss.dk 2:236/77 - To : somebody@somewhere 2:230/9316 - Subj : whatever - -------------------------------------- -

-

- Or if my gate was defined as "INTERNETGATE UUCP 2:230/9316": -

-

- -------------------------------------- - From : odinn@winboss.dk 2:236/77 - To : UUCP 2:230/9316 - Subj : whatever - -------------------------------------- - To: somebody@somewhere -

-

- So what's the use of all this? It allows you to make a - nodelist-style list of users with Internet addresses and use it - with GoldED+ so that you can do a lookup of normal names instead of - trying to remember strange Internet addresses. Of course something - similar could be done using the ADDRESSMACRO's, but with the - nodelist approach, you could build a "network" of users which have - offline Internet access via FTN-gate software and distribute the - nodelist for automatic processing. -

- - - - INTERNETMSGID <yes/no> - -

- (no) -

-

- Specifies whether the FTN MSGID kludge should contain an RFC1036 - compatible Message-ID or the normal FTS-9 format. Note that using - the RFC1036 format in MSGID breaks the FTS-9 (version 001) - specification, so please don't use this feature in FidoNet netmail - or echomail. As a safeguard, GoldED+ will only use the RFC1036 - format in areas specifically marked as e-mail or newsgroups, using - the SOUPEMAIL and SOUPNEWSRCFILE keywords or using the Email and - News area types with the AREADEF keyword, even when INTERNETMSGID - is set to YES globally. -

- - - - INTERNETREPLY <yes/no> - -

- (yes) -

-

- When INTERNETREPLY is enabled, GoldED+ always uses the FSC-35 - REPLYADDR/REPLYTO kludges to gate replies to msgs from Internet - correctly. If disabled, GoldED+ only uses the FSC-35 method if the - Internet address is too large to fit in the max-35-character TO: - header field. Some gate software requires that the FSC-35 method - is used, while other software accepts Internet addresses directly - in the header. -

- - - - INTERNETRFCBODY <yes/no> - -

- (no) -

-

- Tells GoldED+ whether to look for and process RFC headerlines at - the top of the message body, before the first empty line. Also - tells GoldED+ to insert its own RFC headerlines at the top of the - message body instead of as kludge lines. This option should only - be used when receiving Internet mail as QWK packets where the RFC - headerlines are usually found at the top of the messages, or when - sending Internet mail via FTN packet to a gateway running GIGO. - GIGO does not recognize RFC header in kludges, but it does - recognize them at the top of the messages, if it is properly - configured (with lines of "Allow_Xxx:" in GIGO's HEADERS.CFG, - where Xxx are the RFC headerlines the gate administrator wants to - allow). -

- - - - INVALIDATE <type> <"findstring"> <"replacestring"> - -

- This is used to invalidate (change) certain control strings in - quoted text. Use this in conjunction with old versions of D'Bridge - or other software that chokes on control strings in quoted text. - As an added bonus feature, if the tearline or origin is - invalidated to a null string (""), they will not be quoted at all. -

-

- The <type> can be one of the following: -

-

- Tearline Invalidate tearline ("---"). - Origin Invalidate origin (" * Origin: "). - Seenby Invalidate SEEN-BY's. -

-

- By default, the following invalidations are used: -

-

- INVALIDATE Tearline "---" "-+-" - INVALIDATE Origin " * Origin: " " + Origin: " - INVALIDATE Seenby "SEEN-BY" "SEEN+BY" -

-

- If you want to disable invalidation entirely, use this: -

-

- INVALIDATE Tearline "---" "---" - INVALIDATE Origin " * Origin: " " * Origin: " - INVALIDATE Seenby "SEEN-BY" "SEEN-BY" -

-

- The defined INVALIDATEs are also used during importing a file when - editing a mail in the internal message editor. -

- - - - JAMHARDDELETE <yes/no> - -

- (no) -

-

- The default setting makes GoldED+ conform to the JAMAPI specs when - deleting msgs in JAM msgbases. This means that deleted msgs are - only marked as such in the message header, not in the index. As a - result, GoldED+ will find and display the deleted msgs until you - run a message pack utility to physically remove the deleted msgs. -

-

- If JAMHARDDELETE is set to Yes, GoldED+ will zap the reference to - the message in the index when deleting msgs. This way the deleted - msgs will not show up again later. The drawback of this approach - is that it is hard to undelete msgs, and may break other software - which assume 100% to-the-letter conformance to the specs. Note - however, that the hard-delete method is transparent to normal use - of JAM msgbases. Probably the only software that might break are - undelete utilities. -

-

- For the techies and programmers, the hard-delete method is simply - setting both UserCRC and HdrOffset in the index to 0xFFFFFFFF - instead of only the UserCRC. According to the JAMAPI specs, a - value of 0xFFFFFFFF in HdrOffset means that "there is no - corresponding message header". Sounds remarkably like a deleted - msg, right? :-) -

- - - - JAMPATH <path> - -

- (defaults to the HUDSONPATH) -

-

- Defines the path where GoldED+ can access the NETMAIL/ECHOMAIL.JAM - files, which are used by mail processors to find and scan out mail - written by users. -

-

- GoldED+ can handle enviroment variables correctly in paths - specified in connection with this keyword. For example, if a path - is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in - AUTOEXEC.BAT (or whatever), then GoldED+ translates the path to - C:\POINT\path\name. - NOTE: The translation is done at config compile time, so if you - change the environment variable and haven't changed anything else - that would cause GoldED+ to recompile it's config, you must force - it with the -F or -FF command parameter. -

- - - - KEYBCLEAR <yes/no> - -

- (no) -

-

- Tells GoldED+ whether or not to clear the keyboard buffer on - startup. This also clears KEYBSTACK or commandline key stuffing. - In older versions of GoldED+, it was necessary to enable this - keyword if you had renamed GOLDED.EXE to DBEDIT.EXE. This version - detects the .EXE renaming and automatically enables KEYBCLEAR, - regardless of the configuration setting. -

- - - - KEYBDEFAULTS <yes/no> - -

- (yes) -

-

- GoldED+ defines a default keyboard configuration setup internally. - The keys can be reconfigured in the GOLDKEYS.CFG file. By default, - the internal keyboard setup is active always, redefinable with the - definitions in GOLDKEYS.CFG. But in some cases it can be - preferrable that the internal keyboard setup is turned off, so - that only the keys in GOLDKEYS.CFG are active. If you want this, - set KEYBDEFAULTS to NO. -

- - - - KEYBEXT <yes/no> - -

- (detect) -

-

- If enabled, GoldED+ will use extended bios calls to read the - keyboard. With the extended keyboard, you can use keys like - <Alt-Left>, <Alt-Home> and other extended keys. If you don't have - an extended keyboard, don't despair - using a few neat tricks, I - have made it possible to use some of the extended keys even with a - non-extended keyboard. -

- - - - KEYBMODE <poll/block> - -

- (poll) -

-

- If this option is set to Poll, GoldED+ switches its keyboard - handling code from "blocking" to "polling" mode. This enables - GoldED+ to provide a continuously running statusline clock, - automatic internal editor autosave, timeout exit and screensaver. - If set to Block, the timeout exit and screensaver are disabled, - and the clock and autosave are dependent on key presses. -

-

- In order to minimize waste of CPU resources in keyboard polling - mode, GoldED+ automatically detects DESQview, Windows and OS/2 and - releases timeslices during the keyboard poll. -

- -KEYBSTACK <keystring> -

- With this keyword, you can "stack" keys in the keyboard buffer. - The KEYBSTACK can be overridden by commandline keystacking, which - uses the same syntax. -

-

- The <keystring> can be a mixture of the following: -

-

- ^Char Ctrl-key (^Letter). - ~Char Ctrl-key (~Letter). (Use this with 4DOS!). - @Key Alt-key (@Number or @Letter). - Char Literal character. - "String" String, enclosed in double quotes. - 'String' String, enclosed in single quotes. - Number Keyboard scan code (decimal). - ! Clear keyboard buffer. -

-

- Whitespace (space and tab) is ignored, except in quoted strings. -

-

- See the chapter for more info. -

- - - - KLUDGE <kludge-definition> - -

- The definition may optionally be enclosed in quotes. A definition - must be enclosed in quotes if it contains leading or trailing - spaces. The KLUDGE tells GoldED+ which kludges it should consider - as "known" in addition to the built-in known kludges. -

-

- Here are a bunch of examples, most of which are kludges generated - by the GIGO Internet gateway software: -

-

- KLUDGE " " ; For wrapped kludges - KLUDGE "Content-Type:" - KLUDGE "Date:" - KLUDGE "From:" - KLUDGE "In-Reply-To:" - KLUDGE "Message-Id:" - KLUDGE "Mime-Version:" - KLUDGE "Organization:" - KLUDGE "Newsgroups:" - KLUDGE "Received:" - KLUDGE "Reply-To:" - KLUDGE "Sender:" - KLUDGE "Subject:" - KLUDGE "To:" - KLUDGE "Errors-To:" - KLUDGE "FTN-From:" ; X-FTN-From: - KLUDGE "ORIGREF:" ; Gated? - KLUDGE "ORIGID:" ; Gated? - KLUDGE "RFC-" ; Seen in NET_DEV -

-

- The kludges defined with KLUDGE are not case-sensitive, but when - GoldED+ looks for the kludges, it matches to the exact length. This - means that for example "RFC-" will match all kludges beginning - with that string. -

-

- The ASCII 1 kludge char should not be included in the definition - string, but GoldED+ can handle it if you do. -

- - - - KLUDGECHRS <yes/no> - -

- (yes) -

-

- If set to YES, GoldED+ uses the "^aCHRS" kludge instead of the - "^aCHARSET" kludge when appropriate. -

- - - - LOADLANGUAGE <file> - -

- If defined, this keyword will load a language definition file. -

-

- This feature can be used to load a small set of national language - definitions in national areas, an english set in international - areas, etc. Typically this would be used to load the definitions - of the date/time strings for use in the template and the - Msg/From/To/Subj strings in the header display. -

-

- In the ADVANCED archive, a set of GEDLNG*.CFG files are provided, - which are designed for use with LOADLANGUAGE. Please note that - there is also a @loadlanguage template token. This way you can - choose to load a language file from the template, or by using the - Random System. The template token takes precedence over the - LOADLANGUAGE in the Random System, but if both are defined, both - will be loaded. -

-

- This keyword can be used globally and in Random System groups, but - it is probably not very useful when used globally. -

- - - - LOGFILE <file> - -

- (GOLDED.LOG) -

-

- Defines the name of the GoldED+ logfile. You should not change the - default. -

- - - - LOGFORMAT <fd,max,bink,qbbs,db> - -

- (fd) -

-

- Defines the log format GoldED+ should use when writing to the - logfile. -

- - - - LOOKUPECHO <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will use nodelist lookup when entering the TO: - name in msgs in echomail areas. -

-

- GoldED+ *won't* lookup the name if it exactly matches the current - WHOTO - text. This is a feature, because a lookup of "All" is not - very useful. :-) -

- - - - LOOKUPLOCAL <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will use nodelist lookup when entering the TO: - name in msgs in local areas. -

-

- GoldED+ *won't* lookup the name if it exactly matches the current - WHOTO - text. This is a feature, because a lookup of "All" is not - very useful. :-) -

- - - - LOOKUPNET <yes/no> - -

- (yes) -

-

- If enabled, GoldED+ will use nodelist lookup when entering the TO: - name in msgs in netmail areas. -

- - - - LOOKUPUSERBASE <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will attempt to find a matching username in the - user database if a to-name with wildcards is entered in echo or - local areas. -

-

- The userbase lookup feature is not new, but a need arose for an - option to turn off the lookup. I decided to let the default be to - disable the lookup. Previously the lookup was always enabled. -

- - - - MAILINGLIST <echoid> <senderaddress> [contribution address] - -

- Defines one or more mailing lists. When importing e-mail from a - SOUP packet, GoldED+ will look at the Internet address in the - "Sender" header and if it matches one of the MAILINGLIST's, the - e-mail will be tossed to the defined area. Note that GoldED+ - supports only participation in, not hosting of mailing lists. The - contribution address is the destination Internet address for mail - you write to the mailing list - the address is typically given to - you when you subscribe to a list. If the contribution address is - not specified, the senderaddress is assumed. -

- - - - MAILTOSS <echoid> <contribution-address> <pattern> - -

- This is acutally the same as MAILINGLIST in disguise with the - parameters recorded and it also enables the full set of pattern - matching. The <pattern> can be written exactly as if in the prompt - for the advanced search feature. -

-

- Any number of MAILTOSS lines can be given for a particular list, - if there is for some reason no single way to identify the list. -

-

- When determining the contribution address, the first MAILTOSS - (or MAILINGLIST) that matches the echoid is chosen. -

-

- MAILTOSS and MAILINGLIST can both be used at the same time and for - the same lists. MAILINGLIST is always the faster, because it looks - only at specific headerlines. MAILTOSS uses much more complex - pattern matching and can even match based on message body content. -

- - - - MAPPATH <server filespec> <local filespec> - -

- This keyword is used to map paths, for example if you have - different drive letters on a server machine and a workstation. You - might have your FidoNet mailer and mail processor setup to run - with the server drive letter (C:), but run GoldED+ from a - workstation where that drive is mapped to a different letter (J:). - If you use AREAFILE's to get the area configuration for GoldED+, - you need to use MAPPATH to map the server drive letter to the - workstation equivalent. -

-

- Another case might be that you have a setup with DOS-style paths - and want to run the Linux version with the same GoldED+ setup. You - can then use MAPPATH to map the DOS drive-based paths to Unix - style paths. -

-

- Examples: -

-

- MAPPATH C: J: - MAPPATH C:\ /mnt/dos/c/ -

-

- NOTE: You don't have to worry about backslash/forwardslash in this - case - they are always mapped automatically to the correct type - for the operating system. -

- - - - MEMBER <echoid> - -

- Defines Random System group members. See the Random System chapter - for details. -

- - - - MENUDROPMSG <yes/no> - -

- (no) -

-

- Defines the default selection in the "Drop This Msg?" menu. -

- - - - MENUMARKED <marked/current/previous/default> - -

- (default) -

-

- Specifies the position of the selection bar in the Marked/Current - menu. -

-

- Marked Set selector to Marked. - Current Set selector to Current. - Previous Set selector to previously selection. - Default Set selector to Marked if there are marked msgs. -

-

- Note that older versions (before 2.50) used the equivalent of the - "previous" setting. -

- - - - MOUSE <yes/no> - -

- (no) -

-

- The mouse support in GoldED+ is currently not functional, so this - keyword is ignored. -

- - - - MSGLISTDATE <written/arrived/received/no> - -

- (written) -

-

- Can be used globally and in groups. This keyword specifies the - default date shown in the right column in the message list. If - "no" is specified, the date column is removed and the space used - to widen the other columns. Personally I prefer to see the - "arrived" date, which is why I implemented this feature. -

-

- The key command LISTtoggledate (Ctrl-D) toggles between them. -

-

- Note that the "arrived" date doubles as the "processed" date for - messages that are written locally and scanned out from your - messagebase. -

-

- Not all messagebase formats supports all three dates. The table - below shows which messagebase supports which dates: -

-

- Written Arrived Received - JAM X X X - *.MSG X X - Squish X X - Ezycom X X - Hudson X - Goldbase X - PCBoard X -

-

- If a date is not supported, "n/a" (for "not available") is shown - instead. -

- - - - MSGLISTFAST <yes/no> - -

- (yes) -

-

- The message lister can operate in two ways, fast or slow. In the - fast mode, only the message headers are loaded for the list - information. Depending on the msgbase format and message type, - some information may not be quite the same when presented in the - lister because information which is gathered from kludges or other - control information in the message text will be missing. Most of - the time this may not be a problem, so if you want speed, chose - the fast mode (default). -

-

- The slow mode loads and fully interprets the content of each - message before the message list is presented. The slowness is most - noticable when entering the lister and when paging up and down. - You may want to use the slow mode for areas with Internet - newsgroups and e-mail, where GoldED+ uses the "From" kludge to get - the real name of the message writer. -

-

- This keyword can be used globally and in Random System groups. -

- - - - MSGLISTFIRST <yes/no> - -

- (no) -

-

- If enabled, GoldED+ automatically starts the message lister when - entering an area. -

-

- This keyword can be used globally and in Random System groups. -

- - - - MSGLISTHEADER <yes/no> - -

- (no) -

-

- If enabled, GoldED+ shows the header of the current message when - you scroll the bar up and down. This is how it worked in previous - versions. If disabled, GoldED+ does not show the header and instead - uses the screen space to show more messages. By eliminating the - header display, it is also much faster at scrolling the list. -

-

- This keyword can be used globally and in Random System groups. -

- - - - MSGLISTPAGEBAR <yes/no> - -

- (yes) -

-

- Enables or disables a pagebar (scrollbar) in the message list. -

- - - - MSGLISTVIEWSUBJ <yes/no> - -

- (yes) -

-

- If enabled, GoldED+ will display the full subject in the bottom - border of the list window. Note that this feature slows down - scrolling a bit. -

- - - - MSGLISTWIDESUBJ <yes/no> - -

- (no) -

-

- If enabled, the Subject column is made wider by removing the To - column. This is especially useful in gated Internet newsgroups, - where the To name is always "All". -

-

- You can toggle between wide and short subject with Ctrl-B - (keycommand LISTtogglewidesubj). -

-

- This keyword can be used globally and in Random System groups. -

- - - - NAMESFILE <file> - -

- (NAMES.FD) -

-

- GoldED+ supports the "address macro" file supported by FrontDoor - and Maximus. If no path is specified, the file is first searched - for in the path from the "FD" environment variable and then the - GOLDPATH, if the FD variable failed. -

-

- The address macros are added *after* those defined with the - ADDRESSMACRO keyword (if any) (see this for details on the - format). -

- - - - NETNAME - -

dummy text

- - - - NICKNAME <your pseudo> - -

- Defines the nick name (pseudo) for the current USERNAME. Can be - used globally and in random system groups. - -

- - - - NODELIST <file> [zone/addr] - -

- Here you define up to 255 nodelists that are used by GoldED+ and the - companion nodelist compiler GoldNODE. The nodelists must generally - be in the standard "St.Louis" nodelist format, but they can also - contain FrontDoor/Version7 style Boss/Point extensions. The - default zone is defined by the first ADDRESS or AKA, but can be - overridden by adding the zone number or a full address after the - filename. GoldED+ currently needs it's own special index files to - use the nodelists. These index files are created by GoldNODE. -

-

- <file> Nodelist file. If the extension is .999 or a - wildcard (".*"), the newest file with a numeric - extension is used. - [zone/addr] Default zone or address for the nodelist (if no - zone info is present in the list itself). -

-

- See also the USERLIST keyword, and the Nodelist Browsing chapter. -

-

- NOTE: If you have nodelists with duplicate some of each others - nodes, the nodelist with the newest or most correct entries should - be placed LAST, and you should use the -D (remove duplicates) - option with GoldNODE. -

- - - - NODELISTWARN <yes/no> - -

- (yes) -

-

- If set to YES, GoldED+ will warn you during startup if one or more - nodelists are missing. Use NO to disable the warning if it bothers - you or you delete/pack your nodelists when the nodelists are - compiled. -

-

- NOTE: GoldED+ can work fine with lookups etc. without nodelists as - long as it can access its own indexes (GOLDNODE.GX?). Only the - extra details will be missing. -

- - - - NODEPATH <path> - -

- This is where GoldED+ and GoldNODE finds the nodelist files and - indexes. -

- - - - NODEPATHFD <path> - -

- Path where GoldED+ can find the FrontDoor nodelist index files. -

- - - - NODEPATHIM <path> - -

- Path to the InterMail nodelist index files. This is actually just - an alias name of the NODEPATHFD keyword, since InterMail and - FrontDoor uses the same nodelist index files. -

- - - - NODEPATHV7 <path> - -

- Path where GoldED+ can find the Version 7 nodelist index files. -

-

- NOTE: For the Version 7 nodelist index support, GoldED+ *requires* - that the files SYSOP.NDX, NODEX.NDX and NODEX.DAT are present. - None of these files may be missing and no other filenames are - supported. Multiple sets of index files are not supported. -

- - - - NODEV7FLAGS <flag> <value> - -

- The Version 7 nodelist index does not by default define any - nodelist flags except the CM flag. Unfortunately the V7 index does - not point to the actual nodelist, it only has some bits which are - marked "reserved" in the specifications. The NODEV7FLAGS keyword - allows you to define the meaning of each of these bits. -

-

- The <value> field can be a number or a bit number. Allowed numbers - are: 32, 64, 128, 256, 512, 1024, 2048, 8192 and 16384. Allowed - bit numbers are: b5, b6, b7, b8, b9, b10, b11, b13 and b14. -

-

- Example: -

-

- NODEV7FLAGS MO b5 - NODEV7FLAGS LO b6 - NODEV7FLAGS MN b7 - NODEV7FLAGS NC b8 - NODEV7FLAGS ZEC b9 - NODEV7FLAGS REC b10 - NODEV7FLAGS NEC b11 - NODEV7FLAGS XA b13 - NODEV7FLAGS XX b14 -

-

- See also the NODEV7MODEM keyword for other nodelist flags. -

-

- The nodelist flag bits in the index files are put in by your - Version 7 nodelist compiler. You must make sure that the nodelist - flag definitions in your nodelist compiler setup match those in - your GoldED+ setup. -

- - - - NODEV7MODEM <type> <value> - -

- The Version 7 nodelist index does not by default define any - nodelist modem type flags. Unfortunately the V7 index does not - point to the actual nodelist, it only has some bits which are - marked "reserved" in the specifications. The NODEV7MODEM keyword - allows you to define the meaning of each of these bits. -

-

- The <value> field can be a number or a bit number. Allowed numbers - are: 1, 2, 4, 8, 16, 32, 64 and 128. Allowed bit numbers are: b0, - b1, b2, b3, b4, b5, b6 and b7. -

-

- Example: -

-

- NODEV7MODEM VFC b0 - NODEV7MODEM HST b1 - NODEV7MODEM V34T b2 - NODEV7MODEM V32B b3 - NODEV7MODEM V34 b4 - NODEV7MODEM V42B b5 - NODEV7MODEM ZYX b6 - NODEV7MODEM ISDN b7 -

-

- See also the NODEV7FLAGS keyword for other nodelist flags. -

-

- The modem type bits in the index files are put in by your Version - 7 nodelist compiler. You must make sure that the modem type - definitions in your nodelist compiler setup match those in your - GoldED+ setup. -

- - - - ORGANIZATION <text> - -

- Specifies the content of the RFC Organization header for Internet - messages. -

- - - - ORIGIN <"string"> - -

- You can define many different origins for use in GoldED+. You can - select one of the defined origins from the Origin selection menu - (the READchangeorigin keyword), which is also available from the - EDITMENU and the EDITSAVEMENU. -

-

- Leading and/or trailing spaces can be added by enclosing the - origin string in quotes. -

-

- This keyword can be used globally and in a Random System group. -

-

- NOTE: Origins defined in the Random System will always override - the global origins defined with this keyword, except when they are - selected from the EDITSAVEMENU. -

- - - - OUTBOUNDPATH <path> - -

- Defines a Binkley-style outbound path. Currently only used for - WaZOO .REQ file requests (see FRQWAZOO). This should be the name - of your primary outbound without extension. -

- - - - OUTPUTFILE <file> - -

- This is the default name of the file written using the - READwritemsg command. -

-

- This keyword can be used globally and in a Random System group. -

- - - - PCBOARDPATH <path> - -

- Defines the default path where GoldED+ should look for the PCBoard - setup files if it can't find the PCBOARD environment variable. -

- - - - PCBOARDUSERNO <userno> - -

- (0) -

-

- Specifies the lastread set used in the PCBoard message base. -

- - - - PERSONALMAIL <startup,allnames> - -

- Specifies options regarding the personal mail scan feature. None - of them are enabled by default. -

-

- If the "startup" option is used, GoldED+ scans for personal mail - while doing the startup mail scan. -

-

- If the "allnames" option is used, GoldED+ scans for mail to all the - USERNAME's instead of only the first. The default is not to scan - for personal mail at startup and to scan only for the first name. - This is faster. -

-

- Example: -

-

- PERSONALMAIL Startup, AllNames -

-

- The example makes GoldED+ scan for personal mail to all your - USERNAME's at startup. -

- - - - PLAY <filename.ext/beepnoise> - -

- See the EVENT keyword for a definition of the PLAY parameters. - You may specify -

- Bugs: At least one -

- This keyword can be used globally and in a Random System group. -

- - - - PRINTDEVICE <devicename> - -

- (PRN) -

-

- Defines the name of the device used for printing. PRN is the - default, but LPTx can also be used. Printers on COMx ports may - also work, but this has not been tested. -

-

- Devices are opened in Write-Only text mode. The function has been - successfully tested to work with two popular peer-to-peer network - packages. -

-

- You should NOT use a filename as devicename. Use the filename - option in the Write menu instead. -

- - - - PRINTFORMFEED <yes/no> - -

- (yes) -

-

- Used when printing messages. If enabled, it prints a Form Feed - (12d) character after each message. -

- - - - PRINTINIT <printstring> - -

- This keyword defines the command string sent to your printer to - initialize it before the actual printing. -

-

- The <printstring> can contain items like these: -

-

- $Hex A hexadecimal string. - #Decimal A decimal (integer) number. - "String" Text string, enclosed in double quotes. - 'String' Text string, enclosed in single quotes. - Other chars Ignored. -

- - - - PRINTLENGTH <lines> - -

- (60) -

-

- Defines the number of lines per page for printing. A formfeed is - printed when every time PRINTLENGTH lines have been printed. -

- - - - PRINTMARGIN <characters> - -

- (80) -

-

- The right margin to use in printed messages. -

- - - - PRINTRESET <printstring> - -

- This keyword defines the command string sent to your printer to - reset it after printing. -

-

- <printstring> See the PRINTINIT keyword. -

- - - - QUOTEBLANK <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will put the QUOTESTRING on blank lines in the - quote. Otherwise blank lines are left blank in quotes. -

- - - - QUOTEBUFFILE <filename> - -

- If used, it sets the default filename for the quotebuffer. If no - path is specified, the GOLDPATH is used. -

-

- This keyword can be used globally and in Random System groups. -

-

- NOTE: If this keyword is used in globally (in GOLDED.CFG), it - effectively disables the automatically named quotebuffers, as - described in the chapter about the QUOTEBUFMODE keyword. -

- - - - QUOTEBUFMODE <ask/append/overwrite> - -

- (ask) -

-

- Specifies what GoldED+ should do, if the quotebuffer file exists - already. -

-

- Ask A menu asks you to select append/overwrite/skip. - Append Always append, no asking. - Overwrite Always overwrite, no asking. -

-

- The "always overwrite" mode is not very useful I guess, but it's - there if you need it. -

-

- The quotebuffer feature automatically creates special filenames - for the buffer file, using these guidelines: -

-

- FORMAT FILENAME LOCATION - Fido GOLDED.QBF In the directory with the *.MSG's. - Hudson GOLDHxxx.QBF In the HUDSONPATH. - Squish filename.QBF Where the Squish area is. - Ezycom GLDxxxxx.QBF In the EZYCOMMSGPATH. - JAM filename.QBF Where the JAM area is. - Goldbase GOLDGxxx.QBF In the GOLDBASEPATH. - PCBoard filename.QBF Where the PCBoard area is. -

-

- Note that they all have extension .QBF so that you can easily find - them. -

- - - - QUOTECHARS ["]<chars>["] - -

- Defines up to 10 chars to recognize in addition to '>' as quote - string chars. This is most useful in gated Internet newsgroups, - where chars such as '|', ':' and ';' are sometimes used instead of - the '>'. -

-

- This keyword can be used globally and in Random System groups. -

-

- Example: -

-

- Group Internet: - Member alt.*, comp.*, net.email - Quotechars "|:;" - Username odinn@winboss.dk - EndGroup -

-

- The example is similar to the one I use myself (net.email is a - local netmail area where I import my gated e-mail from - winboss.dk). The username is my actual Internet address. -

-

- Note that using additional quotechars such as '|' and ':' may - cause odd results when quoting in the cases when they are actually - NOT used in a message as quotechars. Consider for example quoting - a smiley :-) -

- - - - QUOTECTRL <Tearline,Origin,yes/no> - -

- Specifies if you want quote tearline and/or origin in your - messages. -

-

- This keyword can be used in random system groups. -

- - - - QUOTEMARGIN <chars> - -

- (70) -

-

- The margin to which quotes are wrapped. A negative value means - that the negative value is added to the DISPMARGIN (not - recommended). -

- - - - QUOTESPACING <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will automatically add blank lines before and - after a block of quoted text, if none are present already. This - improves the readability of some messages. -

- - - - QUOTESTOPS - - - - - - - - If one of characters defined by this keyword found before quotechar - then line will be not treated as quote. - - - - - - - - - - QUOTESTRING <quotespec> - -

- (" FL> ") -

-

- With this keyword you define how you want the quotestring to look - in your quoted replies. -

-

- The <quotespec> can contain these characters: -

-

- F Replaced with the first letter of the first name. - M Replaced with the letters of the middle names. - L Replaced with the first letter of the last name. - > Required quote-char. - Spaces Cosmetics. -

-

- Other characters are allowed but *not* recommended. -

-

- This keyword can be used globally and in Random System Groups. -

- - - - QUOTEWRAPHARD <yes/no> - -

- (yes) -

-

- This keyword controls behaviour of quoted text (wrap or reflow). -

- - - - QWKBADMSGS <echoid> - -

- Specifies the area where messages in unknown conferences are put. - If you get messages tossed here by accident, you must move them - manually to the correct area. If the badmsgs area is not defined, - the messages will silently disappear. Messages tossed to the - badmsgs area will have the control line "AREA:<bbsid>_<confno>" at - the top of the message. -

- - - - QWKCONFMAP <bbsid> ["]<confname>["] <echoid> - -

- Defines the mapping between the BBSID and conference names in the - QWK packets and the echoid name of the conference as required by - GoldED+. You MUST define a mapping for every conference that you - subscribe to. If you don't, the messages will be tossed to the - area defined by QWKBADMSGS or disappear. The <bbsid> is the name - listed on line 5 in CONTROL.DAT after the comma. The <confname> is - the conference names listed on line 13 and on alternate lines - onwards in CONTROL.DAT. If a conference name contains embedded - spaces, the <confname> must be enclosed in double quotes, like - this: "Main Board". The area <echoid> must be already defined - either in an AREAFILE or using the AREADEF or AREA keywords. -

- - - - QWKEXPORTPATH <path> - -

- Path where outgoing QWK reply files (BBSID.MSG) can be placed. -

- - - - QWKIMPORTPATH <path> - -

- Path where incoming QWK packet files (CONTROL.DAT and - MESSAGES.DAT) can be found. -

- - - - QWKOPTIONS <bbsid> <options> - -

- The <bbsid> is the BBSID (same as the name of the QWK packet) for - which the options will be active. The <options> can be any or a - combination of the following, separated by commas or spaces: -

-

- KLUDGES/NOKLUDGES: Defaults to NOKLUDGES. Specifies whether or not - to include the FidoNet-style kludges at the top of messages when - exporting to QWK. NOTE: Unless you enable this option, GoldED+ will - *not* include kludges in your QWK packets. You should check if the - BBS supports kludges in QWK packets. If it does, please enable - this option. -

-

- MIXCASE/NOMIXCASE: Defaults to NOMIXCASE. Specifies whether or not - the BBS allows mixed upper/lower case in the QWK message headers. - The default is to uppercase the TO and FROM header fields when - exporting to QWK packets. -

-

- RECEIPT/NORECEIPT: Defaults to NORECEIPT. Specifies whether or not - the BBS supports return receipt requests (RRQ). If the RECEIPT - option is enabled, GoldED+ will insert "RRR" at the front of the - subject field if the RRQ attribute is set on your messages, when - exporting to QWK packets. -

- - - - QWKREPLYLINKER <cmd> - -

- Commandline for a replylinker program to call after QWK import. -

- - - - QWKTOSSLOG <file> - -

- Name of a file where GoldED+ puts the echoids of each area where - articles have been imported. The tosslog file is intended to be - used with a replylinker. If no path is given, it defaults to the - GOLDPATH. -

- - - - RA2USERSBBS <yes/no> - -

- (detect) -

-

- GoldED+ supports the two different formats of the Hudson USERS.BBS - file. With this keyword you can tell GoldED+ which format to use. -

-

- If set to YES, the RA2 format is used. Otherwise if the it is set - to NO, the Hudson format is used. -

-

- If this keyword is NOT used, GoldED+ tries to detect the format by - looking at the size of the USERS.BBS file and comparing this to - the record sizes of the RA2 and Hudson formats. -

-

- If the size matches one and not the other, the format is detected - to be of the matching type. -

-

- If the size matches both (which is quite normal), GoldED+ looks for - the RA environment variable and if found, in the RA config files - for the RA version. -

-

- If the size does not match either of them (indicating a possibly - damaged userfile), GoldED+ exits with an error message and writes - in the log with details of the problem and an advise to run a - userbase packing utility. -

-

- If used, this keyword should be placed in the configuration file - _after_ any AREAFILE keyword. -

- - - - RCVDISABLESCFM <yes/no> - -

- (yes) - - If this keyword defined to "no" then GoldEd will recognize RRq - (receipt request) and/or CFM (confirmation) flag on messages with - RCV (received) flag set. After that RRq and CFM flags will be - resetted. It is useful if your netmail tracker sets RCV flag - before you actually read messages. - chapter, - , - , - , - -

- - - - REGISTERKEY - -

- - - - REGISTERNAME - -

- These keywords do nothing and won't do anything in the future. - They were used when GoldED+ was a Shareware product. -

- - - - REM - -

- This keyword ignores everything behind it. This is useful to - comment a single line out. -

- - - - REPLYLINK <chain/direct> - -

- Defaults to "direct" for JAM and "chain" for everything else. -

-

- If set to "direct", GoldED+ will link your reply directly to the - original message. If set to "chain", it will link to the last - message in the reply chain. The default ("chain") is how GoldED+ - has done it in all previous versions. -

-

- The advantage of the "direct" linking method is that you can - easily find the the original message the reply was for. Unless of - course you have later re-linked using a chain-linking replylinker - utility. I can recommend the utility SQLINK by Serge Terekhov. - SQLINK links Squish areas using the MSGID/REPLY kludges and makes - direct links instead of chain-linking on the subject line like - most other replylinkers do. There are probably also similar - replylinkers for other msgbase formats, I just don't know them. -

- - - - REPLYLINKLIST <fast/full> - -

- (fast) -

-

- When there is more than one reply to a msg in a JAM or Squish - area, GoldED+ pops up a list of the replies. This keyword affects - the contents of the list. -

-

- In the "fast" mode, the list data is based solely on what can be - found by reading the message header, which is quite fast. - Unfortunately some software does not (or cannot) fill the header - with the correct origination address. In that case, set this - keyword to "full", which makes GoldED+ read and scan each message - for control data to get the origination address. That can be very - slow. -

- - - - ROBOTNAME <name> - -

- A "robot" is a program on the Boss or Uplink system which responds - automatically to netmail messages. Usually the robot links or - unlinks echomail areas or distributed files. -

-

- The following ROBOTNAME's are defined by default: -

-

- AreaFix, AreaMgr, FileFix, AreaLink, AllFix, Raid, GEcho. -

-

- If you write a netmail message where the TO: name is one of the - robot names, GoldED+ will ignore any template definition, and give - you a blank msg (possibly with a tearline) to edit. -

- - - - SCREENBLANKER <seconds> [BLACK] - -

- (180) -

-

- If non-zero, GoldED+ will blank the screen after the defined number - of seconds, and put a small moving window up instead. Hitting any - key (including shiftkeys) will return the screen to normal. If - zero, no blanking is done. -

-

- If the additional parameter "BLACK" is given, GoldED+ will switch - the screen completely black instead of showing its own animated - screenblanker. This is useful if you have a monitor with - powersaving-features. -

-

- Example: -

-

- SCREENBLANKER 300 BLACK -

-

- NOTE: This feature only works if KEYBMODE is set to "poll". -

- - - - SCREENMAXCOL <columns> - -

- (0) -

-

- On some systems, GoldED+ may no detect the correct display size. - With this keyword you can force a specific size. If zero, - autodetect is used. -

- - - - SCREENMAXROW <rows> - -

- (0) -

-

- On some systems, GoldED+ may not detect the correct display size. - With this keyword you can force a specific size. If zero, - autodetect is used. -

- - - - SCREENPALETTE <reg> <value> OR <reg> (red green blue) - -

- You can change the color palette used in GoldED+. The palette has - 16 color registers, corresponding to the 16 colors from black (0) - to intense white (15). By changing the values in the palette - registers, it is possible to make any of the 16 colors a - completely different color. You can even make the background - colors intense, without using the intense color feature. There are - 64 different colors to chose from. -

-

- To configure the palette colors in GoldED+, the SCREENPALETTE - keyword is used. There are two different syntaxes: -

-

- SCREENPALETTE <reg> <value> - SCREENPALETTE <reg> (red green blue) -

-

- So you can either compose the color value using separate red, - green, blue components, or directly use a precalculated value. The - red/green/blue values can only be in the range 0-3. -

-

- These are the original palette values: -

-

- SCREENPALETTE 0 (0 0 0) - SCREENPALETTE 1 (0 0 2) - SCREENPALETTE 2 (0 2 0) - SCREENPALETTE 3 (0 2 2) - SCREENPALETTE 4 (2 0 0) - SCREENPALETTE 5 (2 0 2) - SCREENPALETTE 6 (2 2 0) - SCREENPALETTE 7 (2 2 2) - SCREENPALETTE 8 (1 1 1) - SCREENPALETTE 9 (1 1 3) - SCREENPALETTE 10 (1 3 1) - SCREENPALETTE 11 (1 3 3) - SCREENPALETTE 12 (3 1 1) - SCREENPALETTE 13 (3 1 3) - SCREENPALETTE 14 (3 3 0) - SCREENPALETTE 15 (3 3 3) -

-

- Copy these lines into your GOLDED.CFG and start experimenting! :-) -

-

- If you have written a program to edit the palette and write a - GoldED+ palette setup file, please don't keep it a secret! :-) -

- - - - SCREENSHADOWS <yes/no> - -

- (yes) -

-

- If enabled, all relevant windows and menus in GoldED+ will have - shadows. -

- - - - SCREENSIZE <mode> - -

- (Auto) -

-

- Use this to force GoldED+ to use either 25 lines, 43/50 lines on - EGA/VGA, or even special videomodes supported by your SuperVGA - adapter (modes like 132x44, 100x40 or 80x60). -

-

- The <mode> can be one of the following: -

-

- Auto Use detected size. - 25 Switch to 25 lines. - 28 Switch to 28 lines. - 4350 Switch to 43/50 lines. - Mode <NN> Switch to videomode NN (a hexadecimal value). -

-

- Please check your video adapter manual carefully before trying out - the Mode option. SELECTING A WRONG MODE CAN DAMAGE YOUR MONITOR!!! -

-

- The Mode option is ignored in the W32 and OS/2 version. -

- - - - SCREENUSEBIOS <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will use standard BIOS calls for screen - updates. This is VERY slow, and should only be used if really - needed. Normally GoldED+ uses direct screen writes. -

-

- This feature is only interpreted in the DOS version. -

- - - - SEARCHFOR ["]<string|string|..>["] - -

- Defines a set of search strings, separated by the '|' character. - The search set defined here is the default when using the Alt-F/Z - search functions or the marking system. -

-

- The '|' character works like an OR operator. That is, the search - is successful if one OR more of the strings are matched. The '&' - character is used as the logical AND operator. -

-

- Please refer to appropriate section in user's guide for more - information. -

-

- Older versions used the ';' semicolon character as a separator, - but that conflicts with the config reader which treats the - semicolon in a special way. The semicolon is still accepted as - separator char like '|', but if semicolons are used, you MUST - enclose the search strings with quotes or the config reader will - treat the first semicolon as the start of a comment. -

-

- Examples: -

-

- SEARCHFOR string1 - SEARCHFOR string1|string2|stringx - SEARCHFOR "string1;string2;stringx" - SEARCHFOR "string 1"|string2&stringx -

-

- This keyword can be used globally and in Random System groups. -

- - - - SEMAPHORE <type> <file> - -

- This keyword defines "semaphore" files, for use with other mailer - and/or mail processing software. -

-

- The <type> can be one of the following: -

-

- NETSCAN Empty netmail scan file (for D'Bridge/FD). - ECHOSCAN Empty echomail scan file (for D'Bridge). - EXPORTLIST Echoid-list of your new messages. - IMPORTLIST Echoid-list of new imported messages. -

-

- The semaphore files are placed in the AREAPATH, if no path is - specified. -

-

- See the example .CFG files for typical semaphore filenames. -

-

- NOTE: You should not set SEMAPHORE EXPORTLIST to - %JAMPATH%\ECHOMAIL.JAM. This is incorrect and probably may cause - your mail processor to malfunction. Use the JAMPATH keyword - instead. -

-

- GoldED+ can handle enviroment variables correctly in paths - specified in connection with this keyword. For example, if a path - is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in - AUTOEXEC.BAT (or whatever), then GoldED+ translates the path to - C:\POINT\path\name. -

-

- NOTE: The translation is done at config compile time, so if you - change the environment variable and haven't changed anything else - that would cause GoldED+ to recompile it's config, you must force - it with the -F or -FF command parameter. -

-

- In addition, GoldED+ itself can watch for some semaphore files and - execute the appropiate function if it is in the arealist screen. - This can be useful if you have a multitasking system and you want - to "tell" GoldED+ that there is new mail in some areas and GoldED+ - should update its display correctly. -

-

- In detail, there are -

-

- EXITNOW <file> Quit immediately. - SCANALL <file> Scan all areas - SCANNETMAIL <file> Scan all netmail areas - SCANTHIS <file> Scan the areas listed in the file - PMSCANALL <file> PM-scan all areas - PMSCANNETMAIL <file> PM-scan all netmail areas - PMSCANTHIS <file> PM-scan the areas listed in the file - QWKIMPORT <file> Import QWK packets - QWKEXPORT <file> Export to QWK - SOUPIMPORT <file> Import SOUP packets - SOUPEXPORT <file> Export to SOUP - IDLETIME <seconds> Number of seconds between checks -

-

- If SEMAPHORE IDLETIME is defined and non-zero, then GoldED+ will - check this list of semaphore files when the user has not pressed a - key in the specified number of seconds. The semaphores are only - checked when the arealist screen is active. If a semaphore file is - found, the file is deleted and then the action is performed. If no - path is given for the files, the GOLDPATH is assumed. -

-

- Example: -

-

- SEMAPHORE SCANALL SCANALL.NOW - SEMAPHORE IDLETIME 30 -

-

- This causes GoldED+ to check every 30 seconds for the SCANALL.NOW - file in the GOLDPATH, and scan all areas if it's found. -

- - - - SERIALNO - -

- Everything mentioned above about REGISTERKEY and REGISTERNAME - applied to this keyword. -

- -SHAREMODE <yes/no/mode#> -

- (yes) -

-

- If enabled, GoldED+ opens all files in a SHARE.EXE compatible mode. -

-

- The default share-mode is "Share Deny None", but another may be - specified directly if you give the mode number as the keyword - parameter (decimal). -

-

- It is normally not necessary to change the default. -

- - - - SOUNDPATH <path> - -

- (defaults to the GOLDPATH) -

-

- Tells GoldED+ where to find the sound files for the PLAY and EVENT - keywords. -

- - - - SOUPBADMSGS <echoid> - -

- Specifies the area where "bad messages" from SOUP packets can be - tossed. It should be an echomail or newsgroup area. -

- - - - SOUPEMAIL <echoid> - -

- Specifies the area where Internet e-mails can be tossed. It must - be a netmail or e-mail area. -

- - - - SOUPEXPORTMARGIN <margin> - -

- (76) -

-

- This is the margin that GoldED+ will hard-wrap to when exporting to - SOUP packets. If you're getting complaints that your lines are too - long, you may want to set this to 70 or 60. -

-

- NOTE: You should NOT enable EDITHARDTERM in email and newsgroups - that are exported to SOUP. If you do, your messages will probably - be exported with short line "droppings" after the wrapping margin. -

- - - - SOUPEXPORTPATH <path> - -

- Path where outgoing SOUP reply packet files (REPLIES and - GOLD*.MSG) can be placed. -

- - - - SOUPIMPORTPATH <path> - -

- Path where the incoming SOUP packet files (AREAS and *.MSG) can be - found. -

- - - - SOUPNEWSRCFILE <file> - -

- Name with full path of the NEWSRC file which lists the newsgroups - you are connected to. GoldED+ uses the list to mark the matching - areas as newsgroups. These will then be scanned for outgoing mail - when starting a SOUP export. -

- - - - SOUPREPLYLINKER <cmd> - -

- Commandline for a replylinker program to call after SOUP import. -

- - - - SOUPREPLYTO <internet-address> - -

- Internet-Address other users should use when they respond to your - mails (Reply-To Headerline). -

- - - - SOUPTOSSLOG <file> - -

- Name of a file where GoldED+ puts the echoids (newsgroup names) of - each area where articles have been imported. The tosslog file is - intended to be used with a replylinker. If no path is given, it - defaults to the GOLDPATH. -

- - - - SQUISHDIRECT <yes/no> - -

- (no) -

-

- If enabled, then in Squish areas, if the DIR (direct) attribute is - set on a message, GoldED+ will automatically set both the CRA - (crash) and HLD (hold) attributes when saving the message. -

-

- According to the Squish Developers Kit, this is the way to tell - SquishMail that a message should be routed direct, because - SquishMail does not recognize the FLAGS kludge where the DIR - attribute is normally found. This keyword should probably only be - used with SquishMail (the mail processor) and then only when used - with Binkley or other so-called "static" mailers. DON'T use it - with FrontDoor! -

- - - - SQUISHSCAN <api/quick> - -

- (quick) -

-

- Specfies whether to use a quick scanning method which only looks - in the .SQI files. This will normally work fine, but may fail - slightly in obscure cases, especially when used with Squish 1.0x - or programs using the old version of the MSGAPI. If you suspect - problems, try to set this keyword to "api", which tells GoldED+ to - look in the .SQD file for an exact count of active msgs in the - .SQI file. -

-

- NOTE: GoldED+ does NOT use the original MSGAPI by Scott Dudley. - Since version 2.50, a completely rewritten implementation is used. -

- - - - SQUISHUSERNO <index> - -

- (0) -

-

- This sets the lastread index number for the Squish *.SQL lastread - files. Lowest number is 0 (zero), highest is (in theory) 65534. -

-

- If used, this disables the use of USER.BBS to find the index - number, and will in effect also stop GoldED+ from creating USER.BBS - or any new entries in it (useful in a single-user point system). - If a Squish msgbase is shared between several users, and you don't - want to have a USER.BBS (recommended in such a case), each user - must have a unique SQUISHUSERNO in their GOLDED/GOLDAREA.CFG. -

- - - - SQUISHUSERPATH <path>[file] - -

- This keyword defines the path where GoldED+ can find and use/create - your USER.BBS file, which is used in connection with the Squish - area lastreads. You can also specify the exact filename if not - USER.BBS. -

-

- If this path or filename is not defined, GoldED+ will instead take - the one specified with AREAFILE Squish or AREAFILE Maximus - (whichever comes first), or failing that, use the MAXIMUS or - SQUISH environment variables. If even that fails, the AREAPATH or - GOLDPATH is used. If AREAFILE Maximus is used, GoldED+ gets the - filename from MAX.PRM. -

- - - - STATUSLINECLOCK <yes/no> - -

- (yes) -

-

- If enabled, GoldED+ will display a clock in HH:MM:SS format in the - right side of the statusline. -

-

- You can redefine the clock format with the language keyword - ST_STATUSLINETIMEFMT in GOLDLANG.CFG. See the Language Definition - chapter to details about the date/time codes you can use. -

-

- NOTE: The clock will only run continuously if KEYBMODE is set to - "poll". -

- - - - STATUSLINEHELP <yes/no/nologo> - -

- (no) -

-

- If set to YES, GoldED+ will replace the "logo" in the left side of - the statusline with a text saying "F1 Help". This is for use in - "point package" setups where the user may be a complete novice, - maybe even to computers, and who needs to be guided to the help - screens. The "F1 Help" text is configurable with the - ST_STATUSLINEHELP language keyword (put it in GOLDLANG.CFG). -

-

- If set to NO, GoldED+ will display it's logo (name and version) in - the left side of the statusline. -

-

- If set to NOLOGO, GoldED+ will not display anything in the left - side. The middle part is extended to fill the space on the left - side. -

- - - - STYLECODES <yes/hide/no> - -

- (hide) -

-

- If enabled (yes or hide), GoldED+ will highlight text surrounded by - one of the following characters in a different color: '*' for bold - text, '/' for italic text, '_' for underlined text and '#' for - reversed text. These are commonly used "stylecodes" which add - emphasis to the text, without making it harder to read. Examples: - *This* will be shown in bold color, /this/ in italic color and - _this_ in underlined color. It is also possible to combine styles, - such as */this/*, in bolditalic color. -

-

- The differ in yes and hide is that hide strips surrounding - stylecodes. -

-

- Described values are specific to -asa. Official vesions starting - at 3.00beta3 has bug in implementation which causes GoldEd to - ignore this keyword. Realization of this keyword in -asa versions - compatible with official versions prior to 3.00beta3. -

-

- To define the highlight colors, use COLOR STYLECODE. See the color - chapter for details. -

- - - - STYLECODEPUNCT <"charlist"> - -

- (!\"$%&()+,.:;<=>@[\]^`{|}~) - - - - STYLECODESTOPS <"charlist"> - -

- ("") -

-

- The STYLECODEPUNCT keyword specifies all the characters that - punctuates words. The stylecode line parser scans forward until it - meets one of these characters and then looks back to see if it - found a word with stylecodes around it. -

-

- The STYLECODESTOPS keyword specifies characters which, if found - within the word to be highlighted, causes the highlight to be - cancelled. -

-

- These keywords were added to allow users to experiment with the - characters for punctuation and stop for stylecode sequences. This - is mostly to illustrate the point that it is almost impossible to - make stylecodes work in every case you want without getting a lot - of false highlights too. Please keep in mind that stylecodes are, - and always will be, a primitive and very error-prone method for - adding highlights to message text. The defaults are: -

-

- STYLECODEPUNCT !\"$%&()+,.:;<=>@[\]^`{|}~ - STYLECODESTOPS -

-

- Note that the double-quote (") must have the backslash (\) in - front of it - the sequence (\") is translated to a single ("). -

- - - - TAGLINE <string or filename> - -

- Defines one or more taglines. A tagline collection filename can be - specified if prepended with an '@' character, like this: TAGLINE - @TAGLINE.LST. If a tagline collection file is used, GoldED+ will - create an index file for it the first time it is used or any time - the file is edited. The index file has the same name, but - extension ".SDX". The index file is an array of 32-bit long - integers, containing the offset of each line in the tagline - collection file. -

-

- This keyword can be used globally and in a Random System group. -

-

- Taglines defined in the Random System *always* overrides the - default global taglines defined with this keyword. -

- - - - TAGLINECHAR <char> - -

- ('.') -

-

- Defines the character GoldED+ uses when putting a tagline in your - message. The default is '.'. You should not change this default. - GoldED+ itself only recognizes taglines with '.' or '_' - (underscore). -

- - - - TAGLINESUPPORT <yes/no> - -

- (yes) -

-

- Allows you to turn off the internal tagline support, in case it - turns out to be too buggy or if you want to use one of the many - good external tagline utilties out there instead. -

- - - - TASKTITLE <string> - -

- (@longpid) -

-

- Sets window title in Win32 and OS/2 versions, ignored in other. -

- - - - TEARLINE <string> - -

- (@longpid @version) -

-

- Here you can define your default tearline. The tearline can be up - to 76 chars long (excluding the leading "--- "), but beware that - policies (such as FidoNet ECHOPOL1) may set a significantly lower - limit (around 30). -

-

- This keyword can be used globally and in a Random System group. -

-

- Tearlines defined in the Random System *always* overrides the - default tearline defined with this keyword. -

-

- If your tearline does not contain at least the string "GoldED" or - "GED", GoldED+ will automatically insert it's PID kludge. See also - description of USEPID keyword. -

- - - - TEMPLATE <file> ["desc"] [match-address] - -

- (GOLDED.TPL) -

-

- You can define many different template files. The templates can be - switched using the READchangetemplate (Ctrl-T) popup menu or the - EDITMENU. -

-

- The optional "desc" can be used to give the templates more - meaningful names like "International template" instead of - non-obvious names like "GOLDED.TPL". If a description is used, it - must appear before the match-address. It must always be enclosed - in quotes, even if it is only one word. -

-

- The match-address is an address mask (wildcards allowed) which can - be used to tell GoldED+ to select that template if the destination - address on a message you write matches the match-address. The - matching will only take place if the TEMPLATEMATCH keyword has - been enabled. -

-

- This keyword can be used globally and in a Random System group. In - Random System groups, only the <file> parameter can be used. -

-

- Templates defined in Random System groups always override the - globally defined templates, except when selected from the EDITMENU - or when automatic template matching is in effect. -

-

- To override the automatic template matching, start by selecting a - template manually using the READchangetemplate (Ctrl-T) command or - the EDITMENU. -

-

- Currently only one match-address per template can be specified, - but you can specify several TEMPLATE keywords for the same file. -

-

- Example: -

-

- // Use DANSK.TPL for messages to Danish nodes/points. - TEMPLATE DANSK.TPL "Danish" 2:23/* - TEMPLATE DANSK.TPL "Danish" 2:234/* - TEMPLATE DANSK.TPL "Danish" 2:235/* - TEMPLATE DANSK.TPL "Danish" 2:236/* - TEMPLATE DANSK.TPL "Danish" 2:237/* - TEMPLATE DANSK.TPL "Danish" 2:238/* -

-

- // Use INTERNET.TPL for messages to the WinBoss gateway - TEMPLATE INTERNET.TPL "Internet" 2:230/9316 -

-

- // Use ENGLISH.TPL for messages to everywhere else - TEMPLATE ENGLISH.TPL "English" * -

- - - - TEMPLATEMATCH <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will select a template which matches the - destination address on messages that you write. This keyword can - be used globally or in random system groups. -

- - - - TEMPLATEPATH <path> - -

- (defaults to the GOLDPATH) -

-

- Defines the default path for msg templates. Use this if you want - to place templates in a path separate from the GOLDPATH. -

- - - - TEMPPATH <path> - -

- Defines the directory where temporary files are placed by GoldED+ - and GoldNODE. -

-

- This path should *NOT* point to a RAM disk or other volatile - media! -

-

- GoldNODE uses this path to store a temporary file which can become - as large as the largest index file (GOLDNODE.GXN), so again, don't - point it to a small RAM disk. If GoldNODE cannot find a TEMPPATH, - it will use the NODEPATH instead. -

- -TIMEOUT <seconds> -

- (0) -

-

- Similar to the screen blanking (SCREENBLANKER) feature, GoldED+ can - auto-exit after a specified period of time. Useful if you are in a - hurry (or didn't get enough sleep last night ;-), and run GoldED+ - from your mailer shell. The timeout value can be overridden with - the -T commandline option. -

-

- NOTE: This feature only works if KEYBMODE is set to "poll". -

- - - - TIMEOUTSAVEMSG <yes/no> - -

- (yes) -

-

- If set to YES, GoldED+ behaves as usual: It saves the (perhaps - partially written) msg text in the internal editor to the msgbase - and exits. If set to NO, GoldED+ will save the msg text in - GOLDED.MSG just as if EDITAUTOSAVE function was in use and the - power went out. Next time you started GoldED+ and entered a msg, it - would detect the "lost" msg and ask you if it should be continued. -

- - - - TITLESTATUS <yes/no> - -

- (yes) -

-

- If enabled then brief status will be added to title. (Win32 and - OS/2 versions only) -

- - - - TWITMODE <mode> - -

- (Blank) -

-

- In GoldED+ you can define several "Twit" names, addresses or - subjects. With this keyword you can specify the action taken when - a Twit message is encountered. -

-

- The <mode> can be one of the following: -

-

- Show Show twit messages. - Blank Blank twit messages. - Skip Skip twit messages, unless to your USERNAME's. - Ignore Skip twit messages, always. - Kill Deletes twit messages, *without* confirmation! -

-

- This keyword can be used globally and in a Random System group. -

- - - - TWITNAME <name/address> - -

- With this keyword, you can specify "Twit" names and/or addresses. - When a Twit name/address is detected, the TWITMODE setting will - determine the action taken. -

- - - - TWITSUBJ <"string"> - -

- With this keyword, you can specify "Twit" subjects. When a Twit - subject is detected, the TWITMODE setting will determine the - action taken. The subject string is searched in the entire subject - text, so you can specify a partial twit subject. Twit subjects are - limited to maximum 35 characters. -

- - - - TWITTO <yes/no> - -

- (no) -

-

- If enabled, GoldED+ will check both from- and to-names when - checking for twitnames. By default only the from-names are - checked. -

-

- This is a global keyword and won't work as intended if used in a - random system group. -

- - - - UNPACKER - -

- Added ability to READ packed messagebases. You need to add PKD - attribute to such echo definition and specify UNPACKER for the - extension defined. You should pack all files from the single - messagebase to the archive with the same name. For *.msg areas you - should add the directory as well. When entering to the archived area - UNPACKER will be executed to unpack files to TEMPPATH. On exit, all - files will be deleted. - - New UNPACKER keyword have the following syntax: - - UNPACKER >extension< > - - - - USEAREA <yes/no> - -

- (yes) -

-

- If set to no then GoldEd will not recognize - - - - USECHARSET <yes/no> - -

- (yes) -

-

- If set to no then GoldEd will not generate @CHRS and @CHARSET - kludges. -

- - - - USEFLAGS <yes/no> - -

- (yes) -

-

- If enabled, GoldED+ inserts the FLAGS kludge for certain extended - attributes, as defined in FSC-0053 by Joaquim H. Homrighausen, and - supported by FrontDoor, D'Bridge, IMail and other modern software. - GoldED+ uses FLAGS to emulate the Hold and Freq attributes which - are not defined in the Hudson message format. -

- - - - USEFWD <yes/no/ask> - -

- (yes) -

-

- If enabled, GoldED+ inserts the FSC-0092 kludges introduced by the - author of FleetStreet, Michael Hohner. These are -

-

- FWDFROM The original From-Name - FWDORIG The original From-Aka - FWDTO The original TO-Field - FWDDEST The original TO-aka (only in netmails) - FWDSUBJ The original subject - FWDAREA The original areatag - FWDMSGID The original MSGID (useful for reply-linking) -

-

- When forwarding, GoldED+ now adds these kludges, unless the - original message already contains them, in which case they are - preserved. When doing a normal reply (Alt-Q or Alt-R) to a message - with the FWD kludges, GoldED+ replies to the forwarder. To reply to - the from-name in the forwarded message, use the comment-reply - function (Alt-G). If the message contains the FWDAREA kludge, you - can reply to the forwarder in the original area (Alt-N) or reply - to the from-name in the original area (Alt-B). Note that it is not - possible to reply to the to-name of a message with the FWD - kludges, and it is also not possible to reply to the to-name of - the forwarded message (the FWDTO name). -

- - - - USEINTL <type> - -

- (yes) -

-

- The INTL kludge is normally only inserted in netmail messages, if - the origination zone is different from the destination zone (the - "Auto" setting), but on systems with many AKA's in the mailer, it - might be useful/necessary to add it ALWAYS (the "Yes" setting). - The "No" option should never be used. -

-

- The <type> can be one of the following: -

-

- Auto Only insert in inter-zone netmail. - Yes Always insert. Recommended and default. - No Never insert. -

- - - - USEMSGID <yes/no> - -

- (yes) -

-

- If enabled, the MSGID kludge is inserted in netmail and echomail, - and the REPLY kludge is inserted when replying to a msg with a - MSGID. -

-

- The MSGID kludge is defined in FidoNet document FTS-9. -

- - - - USEPID <yes/no> - -

- (no if GoldEd mentioned in tearline, yes otherwise) -

-

- If disabled then @PID kludge will not be used in your messages - regardless of tearline contents. -

- - - - USERLIST <file> [zone/addr] - -

- In addition to normal nodelist support, GoldED+ also supports the - "FIDOUSER.LST" style userlist format. The default zone is defined - by the first ADDRESS or AKA, but can be overridden by adding the - zone number or a full address after the filename. -

-

- <file> Userlist file in FIDOUSER.LST format. - [zone/addr] Default address for the userlist (if no zone info - is present). -

- - - - USERLISTFILE <file> - -

- (GOLDED.LST) -

-

- GoldED+ can generate a list of all users in the current area. This - keyword defines the default name of the FIDOUSER.LST style - userlist output file generated with the READmakeuserlist command. -

- - - - USERNAME <name>[[,]< >address] - -

- You can define many different names/aliases. When GoldED+ finds an - un-received message to one of your USERNAME's, it is marked as - received. Useful if you use alias names in some conferences. It is - possible to change the current name using the READchangeusername - popup menu. -

-

- For msgbase formats with an associated user database, GoldED+ uses - the *first* defined USERNAME to look in the user database for - which lastread record to use. If your name is not found, it is - added and a new lastread record created. -

-

- Example: -

-

- USERNAME Odinn Sorensen, 2:236/77.999 -

-

- This keyword can be used globally and in a Random System group. -

- - - - USETZUTC <yes/no> - -

- (no) -

-

- Activates usage of TZUTC kludge in your messages. You should - properly setup timezone information in your OS. For example, - in DOS you should set environment variable TZ to something - like this: -

-

- TZ=MSK-3MSD,M3.5.0/02:00,M10.5.0/03:00 -

-

- This line valid for Moscow, Russia. -

-

- This option could be used in random system groups. -

- - - - UUDECODEPATH <path> - -

- Specifies the path where files are placed when using the uudecode - feature. Files are placed in current directory if a path is not - specified. -

-

- The specified path *must* exist ! -

- - - - VIEWHIDDEN <yes/no> - -

- (no) -

-

- Hidden lines are "unknown" kludge lines. If enabled, hidden lines - will be displayed (in a different color) when reading msgs. -

-

- A hidden line is defined as a line which has the FidoNet kludge - char (^a, ASCII 1) as the first char and is not on the list of - internally or user defined known kludges. -

-

- This keyword can be used globally and in a Random System group. -

-

- IMPORTANT NOTE: -

-

- In some conferences the hidden lines are used to give witty - comment "between the lines" in the plain text, but generally it is - considered a bad practice and should be avoided because it may - cause severe technical problems if a witty comment in a hidden - line happens to match a (perhaps experimentally) defined kludge - somewhere. It should also be noted that hidden lines are not kept - in their original places when used in the JAM msgbase. This is due - to the way the JAM specification stores FidoNet kludges. -

- - - - VIEWKLUDGE <yes/no> - -

- (no) -

-

- If enabled, known kludge lines will be displayed (in a different - color) when reading msgs. -

-

- Known kludges are those defined internally in GoldED+ plus those - defined with the KLUDGE keyword. -

-

- This keyword can be used globally and in a Random System group. -

- - - - VIEWQUOTE <yes/no> - -

- (yes) -

-

- This is an experimental feature. It is similar to the VIEWHIDDEN - and VIEWKLUDGE keywords, but for quoted text. I implemented it - because I was annoyed with the excessive quoting often seen in - Internet newsgroups. When this keyword is set to NO, GoldED+ - attempts to trim down the quotes so that only the first line of - each quote block is shown. It is not always successful, sometimes - the result is not so useful. -

-

- A key command has been added to supplement this feature: - READtogglequote. Suggested key assignment: Ctrl-V. Example: -

-

- ^V READtogglequote -

-

- Try it out if you are annoyed with excessive quotes. -

-

- This keyword can be used globally and in a Random System group. -

- - - - WHOTO <name> - -

- This name is inserted in the TO: name field, when entering new - messages (not replies) in echomail or local areas. -

-

- This keyword can be used globally and in a Random System group. -

- - - - WILDCATUSERNO <userno> - -

- Defines the lastread set used in the WildCat! 4.x message base. -

- - - - WRITETEMPLATE - -

- - - - XLATCHARSET <importid> <exportid> <file> - -

- This keyword defines character set translation table files. -

-

- <importid> Charset import identifier. - <exportid> Charset export identifier. - <file> Charset translation table file. -

-

- See the Character Translation chapter for details. -

- - - - XLATESCSET <import> <export> <escfile> - -

- This keyword defines escape sequence translation table files. -

-

- <importid> Escset import identifier. - <exportid> Escset export identifier. - <file> Escape sequence translation table file. -

-

- See the Character Translation chapter for details. -

- - - - XLATEXPORT <charsetid> - -

- Defines the export charset for your messages. See the Character - Translation chapter for details. -

-

- This keyword can be used globally and in a Random System group. -

-

- It can also be used in templates (the @xlatexport token). -

- - - - XLATIMPORT <charsetid> - -

- (IBMPC) -

-

- Defines the local charset for your machine. See the Character - Translation chapter for details. -

-

- This keyword can be used globally and in a Random System group. -

- - - - XLATLOCALSET <charsetid> - -

- (IBMPC) -

-

- Use this keyword to specify the actual physical charset in effect - for text screen display. This was previously the hardcoded value - IBMPC, corresponding to the IBM codepage 437 (or the nordic - edition 865). -

-

- NOTE: All charset translation files must translate from and to the - charset identified with the XLATLOCALSET keyword! -

- - - - XLATPATH <path> - -

- This is the path where GoldED+ tries to find the XLATCHARSET and - XLATESCSET files. -

- - - - ZONEGATING <yes/no/ask> - -

- (ask) -

-

- When writing a netmail message to a destination in another zone, - you can either send the message directly (No) or via the local - ZoneGate (Yes). You can also be consulted each time (Ask). GoldED+ - won't ask if Cra or Hld attribute is set. -

-

- - - - - - - Obsolete Keywords - -

-This is a list of keywords which were used in various older versions. -These keywords are now obsolete, either because they have been renamed -or replaced, or if they no longer have any function. Most of the -keywords are still active and remapped to the new names. -

-

-To check if you have obsolete keywords in your setup, run GoldED+ with -the -F -D commandline parameters. Then if you get a number of "Unknown -keyword" warnings, you should replace the old keywords with the new -ones or remove them. -

-

- Old keyword: New keyword: -

-

- AREAAUTOFREQ AREAFREQTO - AREABADMSGS SOUPBADMSGS - AREASORT AREALISTSORT - ASSIGNTO MEMBER - AUTOATTACH EDITAUTOATTACH - BLANKTIME SCREENBLANKER - BOARDNOS (removed) - CCATTRIB ATTRIBSCC - CCLIST CARBONCOPYLIST - CFMATTRIB ATTRIBSCFM - CHANGEDATE EDITCHANGEDATE - CHANGEPROMPT (removed) - CHARSET XLATCHARSET - CLEARKEYS (removed) - COLOUR COLOR - COMMENTNOISE BEEPCOMMENT - COOKIEFILE (removed) - CRLFTERM EDITCRLFTERM - DELORIG ASKDELORIG - DISPMSGLIST MSGLISTFIRST - DISPMSGLISTFAST MSGLISTFAST - DISPSTYLECODES STYLECODES - DOSSWAP (removed) - ECHOATTRIB ATTRIBSECHO - ECHOINFO CTRLINFOECHO - EDITMARGIN (removed) - EDITORVERSION (removed) - ELIMSNOW (removed) - ESCSET XLATESCSET - EXCLAREA AREAEXCL - EXPORTCHARSET XLATEXPORT - EXTKEYS (removed) - FIDOLASTREADNO FIDOUSERNO - FIELDCLEAR EDITFIELDCLEAR - FILECHECK (removed) - FILECHECKALL (removed) - FREEAREA (removed) - FREETEAR (removed) - GOLDEDCFM CONFIRMFILE - GOLDEDLOG LOGFILE - GOLDEDLST USERLISTFILE - GOLDEDMSG EDITORFILE - GOLDEDNAM NAMESFILE - GOLDEDPRN OUTPUTFILE - GOLDHELP (no longer documented) - GOLDKEYS (no longer documented) - GOLDLANG (no longer documented) - GOLDRAND (no longer documented) - GOLDXLAT (no longer documented) - HARDLINE EDITHARDLINE - HARDLINES EDITHARDLINES - HWMARKS (removed) - INCLAREA AREAINCL - INTERNALEDITOR EDITINTERNAL - LASTREAD FIDOLASTREAD - LASTREADUSER FIDOUSERNO - LISTWRAP (removed) - LOCALATTRIB ATTRIBSLOCAL - LOCALCHARSET XLATIMPORT - LOCALHIGHLIGHT (removed) - LOCALINFO CTRLINFOLOCAL - LOCALNOISE (removed) - MAPDRIVE MAPPATH - MATCHAKA AKAMATCH - MAXCOLS SCREENMAXCOL - MAXMSGSIZE (removed) - EDITMSGSIZE (removed) - MAXROWS SCREENMAXROW - MIXCASE EDITMIXCASE - MULTIQBBS (removed) - NETATTRIB ATTRIBSNET - NETINFO CTRLINFONET - NETTEAR CTRLINFONET performs similar function - NEXTAREA AREANEXT - NEXTMSGS (removed) - NODELISTPAGEBAR (removed) - NOISEFACTOR (removed) - OVERLAY (removed) - OVERLAYEMS (removed) - OVERLAYEXT (removed) - PAGEBAR (removed) - QBBSINCRESCAN (removed) - QBBSPATH HUDSONPATH - QBBSREBUILD (removed) - QBBSSCAN (removed) - QMSGPATH HUDSONPATH - REALMSGNO (removed) - REBUILD (removed) - RENAREA AREARENAME - REPLYRE EDITREPLYRE - RIGHTMARGIN DISPMARGIN - SAVEMENU EDITSAVEMENU - SAVETIME EDITAUTOSAVE - SAYBIBI (removed) - SCANAREA AREASCAN - SCREENELIMSNOW (removed) - SCREENUSEANSI (removed) - SHADOWS (removed) - SHARE SHAREMODE - SHOWTWITS TWITMODE - SIGNALFILE SEMAPHORE - SOUNDDEVICE (removed) - SPACEQUOTES (removed) - SPELLCHECKER EDITSPELLCHECK - STACKKEYS KEYBSTACK - STARTECHO AREASTART - SWAPALL (removed) - SYSOP USERNAME - TABSIZE DISPTABSIZE - TAGLINEFILE (removed) - TIMESLICE (removed) - TIMEZONEOFFSET USETZUTC performs similar function - UNDELETELINES EDITUNDELETE - USEBIOS SCREENUSEBIOS - XPLIST CROSSPOSTLIST -

-

- - - - - - Location Dependent Configuration Keywords - -

-The following configuration keywords are location dependent and should -be placed in a particular order in the configuration file(s). Keywords -that are *not* listed can be placed anywhere you want. -

-

-The keywords are listed in groups of those that depend on each other. -They are listed in the recommended order within each group. The order -between the groups is not important, with one noted exception. -

-

-Name/Address/Areas: - USERNAME - ADDRESS - AKA - ATTRIBSNET Specifies default attributes for AREAFILE etc. - ATTRIBSECHO As above. - ATTRIBSLOCAL As above. - FIDOMSGTYPE - PCBOARDPATH Recommended if you use PCBoard. - MAPPATH - AREARENAME Rename occurs before AREAEXCL/INCL. - AREAEXCL - AREAINCL - AREAISEMAIL - AREAISNEWS - AREAPATH Default path for the AREAFILE's. - AREAFILE - RA2USERSBBS Overrides AREAFILE RemoteAccess. - AREADESC Add description and more to some AREAFILE's. - AREA Overrides areas in AREAFILE's. - AREADEF As above. -

-

-Paths: - GOLDPATH - TEMPPATH MUST be in GOLDED.CFG. Used only by GoldNODE. -

-

-Nodelists: MUST be below ADDRESS/AKA and ONLY in GOLDED.CFG! - NODEPATH - NODELIST - USERLIST - EXCLUDENODES Remember to replace "ALL" with '*'. - INCLUDENODES As above. -

-

-Colors: - INTENSECOLORS Selects a default intense colorset if enabled. - COLORSET Selects a default colorset. - COLOR -

-

-External utils: - EXTERNOPTIONS - EXTERNUTIL -

-

-Character translation: - XLATPATH - XLATCHARSET - XLATESCSET -

-

-Random System: - GROUP Starts a group. - MEMBER Defines areas that are members of the group. - <Group Items> See the Random System chapter for a list. - ENDGROUP Ends a group. -

-

- - - -Message Attributes Reference -

-This is a list and description of all message attributes that are -supported by GoldED+ in the keywords that accept attribute settings or -can be displayed in the header. -

-

-A/S Archive/sent. -ARQ Audit request. -ATT File attached. -CFM Confirmation receipt requested. -COV Fax cover letter. -CRA Crash - high priority mail. -DEL Deleted. -DIR Direct. Don't route this message. -FAX Fax image attached. -FRQ File request. -GRP Group message. -HIR Fax hi-resolution image. -HLD Hold for pickup. -HUB Host- or Hub-route message. -IMM Immediate - Send message NOW! -K/S Kill/sent. Delete message automatically after it is sent. -KFS Kill/file/sent. Delete attached files after they are sent. -LET Fax letterhead. -LOC Local. Message was written on your system. -LOK Lock. Prevents send/delete/purge/editing. -ORP Orphan. Could not be sent because destination node is unknown. -PKD Packed. Used in area definitions to unpack before using. -PRN Msg has been printed. Specific for Squish (bitvalue 00040000h). -PVT Private. Message may only be read by the addressee and author. -R/O Read only. Used in area definitions to prevent writing. -RCV Received. Read by the addressee. -RRC Return receipt. -RRQ Return receipt requested. -RSV FTS-1 reserved (unused) attribute. -SIG Fax signature. -SNT Sent. Message has been sent or exported from the msgbase. -TFS Truncate/file/sent. Truncate files to zero length when sent. -TRS Transit. Message passing through, not for you. -UNS Unsent message. -URQ Update file request. -XMA Xmail. Attach does not conform to the ARCmail 0.60 standard. -ZON Zonegate. Route through zonegate if possible. -

-

- - - -Area Configuration -

-GoldED offers a wide variety of methods for defining message areas. -You can define each area manually in the GOLDED.CFG file (or an -INCLUDE'ed GOLDAREA.CFG file), or you can tell GoldED+ to read the area -setup files of many popular BBS/mailer/mail processor packages. -

-

-For manual definition of areas, use the AREA or AREADEF (recommened) -keywords. -

-

-For external area configuration, the general syntax for the AREAFILE -keyword is: -

-

- AREAFILE <programname> [path or filename(s)] [-options] -

-

-Available options: -

-

--S<sortspec> -

-

- If you are *not* using the global AREALISTSORT keyword for sorting - all the areas, you can sort the areas of each AREAFILE separately. - See the AREALISTSORT keyword for the definition of <sortspec>. -

-

-If no path is specified, the appropriate environment variable or the -AREAPATH is used to find the files. -

-

-The <programname> can be one of the following: -

- - - AdeptXBBS - -

- Reads the AdeptXBBS configuration files. -

-

- Looks for the ADEPTXBBS environment variable. -

- - - - AreasBBS - -

- GoldED+ is can handle a wide variety of AREAS.BBS type files. It - can read and distinguish between the old CONFMAIL style with paths - for *.MSG areas, the Hudson/Goldbase style with board numbers, the - Squish style with "$basename" and the JAM style with "!basename". -

-

- The disadvantage of using an AREAS.BBS is that there are no area - descriptions. The echoid is used as description instead. However, - GoldED+ will use any text behind a semicolon on definition lines as - description. This may or may not be compatible with mail - processors, so be careful. A better solution may be to use the - AREAFILE Echolist to add descriptions from a separate file. -

-

- One or more AREAS.BBS files may be specified on the same line. -

- - - - Concord - -

- Support is planned but not yet implemented. -

- - - - Crashmail - -

- Reads the CrashMail II configuration file. -

- - - - D'Bridge - -

- Reads the DBRIDGE.AA1/.AA2 files (for version 1.30) or the - DBRIDGE.ADF of the later versions. -

-

- Looks for the "DBRIDGE" and "DB" environment variables. -

- - - - Dutchie - -

- Reads the DUTCHIE.ARE file. -

-

- Looks for the "DUTCHIE" environment variable. -

- - - - Echolist - -

- Reads a simple ascii-text file containing an echolist in this - format: -

-

- <echoid> <description> -

-

- or DZ-format (requires -DZ switch): -

-

- [Status], Tag, Comment, Moderator's Name, Address,[Flags] -

-

- This feature adds descriptions to already existing areas in - GoldED+. Example: -

-

- AREAFILE AreasBBS AREAS.BBS - AREAFILE EchoList ECHOLIST.TXT - AREAFILE EchoList echo5020.lst -dz -

-

- Descriptions for unknown echoids are ignored. Blank lines and - lines beginning with characters which are illegal in echoids (such - as ';') are also ignored. -

-

- Additional switch -SqaFix could be used to read echolist and groups - from SqaFix configuration file: -

-

- AREAFILE Squish C:\SQUISH\ - AREAFILE EchoList C:\SQUISH\SQAFIX.CFG -SqaFix -

- - - - Ezycom - -

- Reads CONFIG.EZY and MESSAGES.EZY. Supports Ezycom 1.02 and 1.10g, - but not 1.01. -

-

- Looks for the "EZY" and "TASK" environment variables. -

- - - - FastEcho - -

- Reads the FASTECHO.CFG file. Supports version 1.10 up to 1.46. -

-

- Looks for the "FASTECHO" environment variable. -

- - - - Fidoconfig - -

- Reads fidoconfig (used in Husky Project software). Supports - version 0.15. Used parser is more powerful than original from - fidoconfig, due to it strictly follows specification from proposal - and implements all features from there. Additionaly it implements - groups not described in proposal but used in in library. -

-

- Looks for the "FIDOCONFIG" environment variable. -

- - - - FidoPCB - -

- Reads FIDOPCB.CFG. Supports version 1.x. -

-

- Looks for the "FIDOPCB" environment variable. -

- - - - FMail - -

- Reads FMAIL.CFG and FMAIL.AR. Supports versions 0.92, 0.98, 1.0g, - and 1.20. -

-

- Looks for the "FMAIL" environment variable. -

- - - - FrontDoor - -

- Reads the SETUP.FD/FD.SYS and FOLDER.FD/FOLDER.SYS files. If you - want the real echoid's attached to the areas, you will also need - to supply the filename of the relevant AREAS.BBS file(s). Supports - versions 1.99c and 2.xx. -

-

- Looks for the "FD" environment variable. -

- - - - GEcho - -

- Reads SETUP.GE and AREAFILE.GE. Supports versions 1.00, 1.02, - 1.10, 1.11 and 1.20. -

-

- Looks for the "GE" environment variable. -

- - - - IMAIL - -

- Reads the IMAIL.CF and IMAIL.AR files. Supports version 1.60, - 1.7x and 1.8x. -

-

- Looks for the "IMAIL" environment variable. -

- - - - InterMail - -

- Reads the FD.SYS/IMSYS.CFG and FOLDER.CFG/IMFOLDER.CFG files. - Supports version 2.26 and newer. -

-

- Looks for the "IM" environment variable. -

- - - - LoraBBS - -

- Reads the CONFIG.DAT and SYSMSG.DAT files. Supports version 2.33, - 2.40 and possibly others. -

-

- Looks for the "LORA" and "LORABBS" environment variables. -

- - - - Maximus - -

- Reads the MAX.PRM and AREA.DAT or MAREA.DAT files. Compatible (or - should be) with both the old (1.xx) and (2.xx) and new (3.xx) - formats. If your AREA.DAT is named differently, you must supply - the correct filename. -

-

- Looks for the "MAXIMUS" environment variable. -

- - - - ME2 - -

- Reads the old ME2 editor AREADESC.ME2 file and AREAS.BBS file(s). - You must supply the names of both files. -

- - - - Opus - -

- Reads the Opus 1.1x SYSTEM??.DAT files or the Opus 1.7x SYSMSG.DAT - file. -

-

- Looks for the "OPUS" environment variable. -

- - - - ParToss - -

- Reads the ParToss configuration file. -

- - - - PCBoard - -

- Reads the PCBOARD.DAT, CNAMES.@@@ and CNAMES.ADD files. Supports - version 14.x and 15.x, up to and including 15.22. Note that, - depending on the version, echoid's may not be read from this - format. If the echoid is not available, the description is used as - echoid, after conversion to uppercase and spaces to underscores. -

-

- Looks for the "PCBOARD" environment variable. -

- - - - Portal - -

- Reads the PORTAL*.CFG and PORTAL.ARE files. -

-

- Looks for the "POPCMDLINE" environment variable. -

- - - - ProBoard - -

- Reads MSGAREAS.PB. Supports version 2.0. -

-

- Looks for the "PB" environment variable. -

- - - - QEcho - -

- Reads /etc/qecho/AreaList. Supports version patched by Eugene - Sorochinsky for JAM messae base support. -

- - - - QFront - -

- Reads QORIGIN.DAT and QECHOS.DAT. Supports version 1.13b. -

-

- Looks for the "QFRONT" environment variable. -

- - - - QuickBBS - -

- Reads the CONFIG.BBS or QUICKCFG.DAT and MSGCFG.DAT files. To get - the real echoid's, you must also supply the filename of the - relevant AREAS.BBS. -

-

- Looks for the "QUICKBBS" and "QBBS" environment variables. -

- - - - RaEcho - -

- Reads AREAS.RAE. Supports version 1.00 and 1.01. -

-

- Looks for the "RAECHO" environment variable. -

- - - - RemoteAccess - -

- Reads the MESSAGES.RA file. To get the real echoid's, you must - also supply the filename of the relevant AREAS.BBS. Supports - versions 0.xx, 1.xx, 2.0x and 2.5x. -

-

- Looks for the "RA" environment variable. -

- - - - Squish - -

- Reads SQUISH.CFG and AREAS.BBS (if used). Supports version 1.0x - and 1.1x. The "Include <filename>" feature of Squish 1.10 is also - supported. -

-

- The optional /G switch specifies the default group of the imported - areas, i.e. /g=G or /g=#103. -

-

- Looks for the "SQUISH" and "MAXIMUS" environment variables. -

- - - - SuperBBS - -

- Reads CONFIG.BBS, SCONFIG.BBS and BOARDS.BBS. Supports version - 1.16 and 1.17. -

-

- Looks for the "SUPERBBS" and "SBBS" environment variables. -

- - - - timEd - -

- Reads TIMED.CFG and any included file. Also reads the - configuration from other mail software defined in TIMED.CFG. -

-

- Looks for the "TIMED" environment variable. -

- - - - Termail - -

- This is for the Terminate Mail system (Termail). GoldED+ does - currently only support Termail 4.00 und 5.xx style .CFG-files. -

-

- Reads TM.CFG and any AREAFILE (an AREAS.BBS type file) defined - there. -

-

- NOTE: If you use this, you must start GoldED+ in the Termail - directory, because the standard TM configuration files use - relative paths. -

-

- Looks for the "TM" environment variable. -

- - - - TosScan - -

- Reads the FD.SYS/SETUP.FD and AREAFILE.FD files. Supports version - 1.00 and FrontDoor 1.99c and 2.xx. -

-

- Looks for the "FD" environment variable. -

- - - - WaterGate - -

- Reads the WTRCFG.TDB and AREABASE.TDB files. Supports version - 0.93. -

- - - - WMail - -

- Reads the WMAIL.PRM and AREAS.PRM files. Supports version 2.2. -

-

- Looks for the "WMAIL" environment variable. -

- - - - XMail - -

- Reads the AREAS.XM file. Supports version 1.00. -

-

- Looks for the "XM" environment variable. -

- - - - -The Random System -

-With the Random System, you can define area-specific sets of origins, -tearlines, templates, usernames and many other items. If -more than one item of each type is specified, a random one is picked - -a Random System. This is a very useful feature when (for example) -participating in conferences with different languages. -

-

-The Random System is built on the idea of "groups". A group is a -collection of "items", belonging to the group. You can assign one or -more echomail areas, designated by their echoid's to a group. Groups -can also be specified for just a single echo, and DOS/4DOS-style -wildcards can be used to simplify the assignment of echoes with common -strings in their name, such as *.DK, SIG.* and so on. In this way, you -could for example setup one group for all national echoes, another for -special local echoes, a third for international echoes etc. -

- - - Defining Groups - -

-The general syntax of a group definition is: -

-

-GROUP <id>[:] - ; items go here - [Member <id list>] -ENDGROUP -

-

-The Group <id> can be one of three things: -

-

-1. A group letter or #number, matching the group letters or numbers - used in the AREAFILE's of D'Bridge, GEcho, IMAIL, TosScan and many - others. To use this feature, you need to enable the AREAFILEGROUPS - keyword. -

-

-2. An individual echoid or echoid mask (wildcards can be used). The - items are then simply defined below the Group line. -

-

-3. A group label, terminated by a colon (:). The group items are - defined below the Group line. Echoes are assigned to the group by - adding one or more Member statements. -

-

-You can't assign a group to another group. It will not harm, but it -also won't work :-) -

-

-The order of groups is very important. GoldED+ scans the groups from -the top down. This means that the most general groups must be placed -at the bottom and exceptions (individual areas for example) must be -placed at the top. -

- - - - Defining Random Items - -

-The random items are defined much like in the main GoldED+ -configuration file. -

-

-If more than one of each item is defined within a group, those items -will be picked randomly (hence the name "Random System"), while GoldED+ -collects items when entering an area. -

-

- Random Item Keywords: , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - , - . -

-

-See the Configuration Keyword Reference chapter for details about each -keyword. -

- - - - Random System Example - -

-Below is an example of how a Random System could be setup. Note how -the letter group 'D' goes first, followed by the explicit group -definitions for the NERDS and FOO echoes. Then comes the more general -groups (those with Label:'s), where the echoes are assigned with one -or more Member statements. At last there is the catch-all "Group *", -which works as the default group. -

-

-=== Cut, GOLDRAND.CFG === -

-

-Group NERDS ; For the NERDS echo. - Origin "I am a Nerd. Take me to your Loser!" -

-

-Group FOO ; This group is *only* for the FOO echo. - Tearline FooED @rev - Origin "Foo-ing my day away" -

-

-Group FooEchoes: - Member *FOO* ; Use wildcards to catch any other foo echo. - Tearline FooED @rev - Origin "This is a Foo-lish origin" -

-

-Group FidoNet: - Member NET_DEV, WORLDPOL, INTERCOOK - Member GREEN.029, C_ECHO, C_PLUSPLUS - Origin "Fight-O-Net? Good name..." - Template FIDONET.TPL - Whoto Everyone -

-

-Group SigNet: - Member SIG.* ; The wildcard is VERY handy here ;-) - Origin "To SIG or not to SIG..." - Template SIGNET.TPL -

-

-Group D ; Letter D for Danish echoes. - Template DANSK.TPL -

-

-Group * ; This is default group - Origin "Yet another forgotten echo" -

-

-=== Uncut === -

-

-See the example GOLDRAND.CFG in the ADVANCED archive for a real-life -setup similar to the one I use myself. -

- - - - - - - The Color Configuration - -

-Color configuration in GoldED+ is a bit complicated, and you probably -have to experiment quite a bit, if you want make your own setup. For -your convenience, I have added a number of example color setups, -provided by some of my many good users. I suggest you try them all and -use the one that suits you best, perhaps tuning it a bit to your -taste. -

-

-The COLOR keyword uses the following syntax: -

- - - COLOR <window> <part> <colors> - -

- <window> AREA, ASK, BACKGROUND, BRAG, HEADER, HELP, INFO, MENU, - READER, SHADOW, STATUS. -

-

- <part> BLOCK, BORDER, BTYPE, EDIT, HIDDEN, HIGHLIGHT, INPUT, - KLUDGE, NOSELECT, ORIGIN, QUOTE, SELECTOR, TEARLINE, - TITLE, WINDOW. -

-

-The <colors> are composed of [blinking] <ink> [on <paper>]. -

-

- <ink> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey, - DGrey, LBlue, LGreen, LCyan, LRed, LMagenta, Yellow, - White. -

-

- <paper> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey. -

-

-For monochrome setups we instead have: -

-

- <ink> Normal, Highlight, Reverse, Underline. -

-

-The SHADOW color does not need a <part>, because it is global. -

-

-The paper color always defaults to Black if not specified. -

-

-If <part> is "BTYPE", the <color> is a value in the range 0-3, which -defines the type of lines used when drawing menus and windows: -

-

-BTYPE 0 is single horizontal and single vertical lines. -BTYPE 1 is double horizontal and double vertical lines. -BTYPE 2 is single horizontal and double vertical lines. -BTYPE 3 is double horizontal and single vertical lines. -

-

-The default border type is always BTYPE 0. -

-

-The following is a description of the different window parts: -

- - - - Various general color items - -

- SHADOW Shadow below windows and menus. - STATUS WINDOW Status line at the bottom. - BACKGROUND WINDOW Background for the startup window. - BACKGROUND BORDER Overscan color (currently DOS only). -

-

- <anything> PAGEBAR Pagebar (scrollbar). -

-

- The PAGEBAR color specifially sets the color of the pagebars - (scrollbars) in GoldED+. A pagebar color can currently be set for - AREA, READER and MENU. Note that BORDER will set both the BORDER and - PAGEBAR colors, so remember to place the PAGEBAR color below the - BORDER color. -

- - - - Startup screen / logo window - -

- BRAG WINDOW The Copyright window. - BRAG BORDER Lines around the Copyright window. - BRAG TITLE The logo text. - BRAG HIGHLIGHT The inner logo lines. - BRAG BLOCK The outer logo lines. - BRAG BTYPE Copyright window border type. -

- - - - Area Selection Menu - -

- AREA WINDOW Descriptions, the top line (inc. search). - AREA BORDER Lines. - AREA TITLE Titles on the border. - AREA SELECTOR Selection bar. - AREA HIGHLIGHT The color for the area marks. - AREA BTYPE Window border type. -

- - - - Message Header - -

- HEADER WINDOW Header text. - HEADER BORDER Lines. - HEADER TITLE Titles on the border. - HEADER INPUT Message number input field. - HEADER EDIT Header input fields. - HEADER HIGHLIGHT Marks. - HEADER BTYPE Window border type. - HEADER FROM Header From field. - HEADER TO Header To field. - HEADER SUBJECT Header Subject field. -

-

- The FROM/TO/SUBJECT colors supplement the HEADER WINDOW color. Note - that WINDOW will also set the FROM/TO/SUBJECT colors, so remember to - place the new colors below it. -

- - - - Message Text - -

- READER WINDOW Normal message text. - READER BORDER The Pagebar. - READER QUOTE (Odd) Quoted lines. - READER QUOTE2 (Even) Quoted lines. - READER CURSOR Character at cursor pos. (int. editor). - READER KLUDHIDD Kludges and hidden lines. - READER TEARORIG Tearline and Origin. - READER BLOCK Block color (internal editor). - READER BTYPE Window border type. - READER HIGHLIGHT Search highlight in the message text. - READER KLUDGE Known kludges. - READER HIDDEN Hidden lines. (Unknown kludges). - READER SIGNATURE Internet-Style signatures ("-- "). - READER TAGLINE Taglines. (Only the one just above tearline). - READER TEARLINE Tearline. - READER ORIGIN Origin. -

-

- The KLUDGE/HIDDEN colors replaces the old KLUDHIDD color. Note that - KLUDHIDD will set both the KLUDGE and HIDDEN colors, so remember to - place the new colors below it if you keep the old definition. -

-

- The TAGLINE color is the color of taglines. GoldED+ detects a tagline - if it starts with "..." or "___" and is just above the tearline or - origin. -

-

- The TEARLINE/ORIGIN colors replaces the old TEARORIG color. Note - that TEARORIG will set both the TEARLINE and ORIGIN colors, so - remember to place the new colors below it if you keep the old - definition. -

- - - - Miscellaneous Smaller Menus - -

- ASK WINDOW Menu items. - ASK BORDER Lines. - ASK TITLE Menu title. - ASK SELECTOR Selection bar. - ASK NOSELECT Non-selectable menu items. - ASK HIGHLIGHT Hotkeys. - ASK BTYPE Window border type. -

- - - - Miscellaneous Larger Menus (Browser Windows) - -

- MENU WINDOW Menu items. - MENU BORDER Lines. - MENU TITLE Menu title. - MENU SELECTOR Selection bar. - MENU NOSELECT Non-selectable menu items. - MENU HIGHLIGHT Hotkeys/marks. - MENU UNREAD When a msg is unread. - MENU UNREADHIGH Additional highlight of to/from. - MENU UNSENT When a msg is unsent. - MENU UNSENTHIGH Additional highlight of to/from. -

- - - - Help Screens - -

- HELP WINDOW Help text. - HELP BORDER Lines. - HELP SELECTOR Current keyword. - HELP HIGHLIGHT Other keywords. - HELP BTYPE Window border type. -

- - - - Pop Up Information Windows - -

- INFO WINDOW Window text. - INFO BORDER Lines. - INFO TITLE Info title. - INFO BTYPE Window border type. -

- - - - Stylecodes - -

- STYLECODE ALL All stylecodes at once. - STYLECODE B *Bold* - STYLECODE I /Italic/ - STYLECODE BI /*BoldItalic*/ - STYLECODE U _Underline_ - STYLECODE BU _*BoldUnderline*_ - STYLECODE IU /_ItalicUnderline_/ - STYLECODE BIU _/*BoldItalicUnderline*/_ - STYLECODE R #Reverse# - STYLECODE RB *#ReverseBold#* - STYLECODE RI /#ReverseItalic#/ - STYLECODE RBI /*#ReverseBoldItalic#*/ - STYLECODE RU _#ReverseUnderline_# - STYLECODE RBU _*#ReverseBoldUnderline#*_ - STYLECODE RIU _/#ReverseItalicUnderline#/_ - STYLECODE RBIU _/*#ReverseItalicUnderline#*/_ -

-

- Note that stylecode color definitions must be placed below COLOR - READER WINDOW, because it overrides the COLOR STYLECODE definitions. -

-

-See the GEDCOL*.CFG and GEDMON*.CFG files for examples of color -configuration. -

- - - - - - - The Message Template - -

-The message template gives you a ready-made skeleton for writing your -messages in the editor. The template is one of GoldED+'s many strong -features. With this, you can eliminate the tedious typing of greetings -etc etc. GoldED+ also provides a number of replacement strings, -"tokens", to dynamically add message specific information to the -template. -

-

-As in the configuration file, a semicolon (;) first on the line makes -the line a comment. Any other line is put into the editor file, after -token expansion. Tokens are not case sensitive. -

-

-The following is a list of the tokens available: -

- - - Conditional tokens - -

- (these are replaced with a null string) -

-

-@changed Line is only inserted in Changed msgs (from others). -@comment Line is only inserted in Reply-Comments. -@echo Line is only inserted in Echomail. -@forward Line is only inserted in Forwarded messages. -@local Line is only inserted in Local messages. -@moderator Line is only inserted if substring "moderator" appeared in - from line. -@moved Line is only inserted in Reply-Moved messages. -@net Line is only inserted in Netmail. -@new Line is only inserted in New messages (not replies). -@position Specifies the starting line for the editor cursor. -@quotebuf Line is only inserted in Quotebuffered msgs. -@quoted Line is only inserted in Quoted replies. -@reply Line is only inserted in Non-Quoted Replies. -

- - - - Insert tokens - -

- (anything else on the line is ignored) -

-

-@attrib <attributes> - Adds specific message attributes. -@include <filename> - Inserts the file. -@forcefrom <"from"> - sets message FROM: field, even if non-empty - (see @setfrom) -@forcesubj <"subject"> - sets message SUBJ: field, even if non-empty - (see @setsubj) -@forceto <"to"> - sets message TO: field, even if non-empty - (see @setto) -@loadlanguage Loads a partial language config file. -@message Inserts the original message (in Forward & Change). -@quote Inserts a quote of the original message. -@random [random.txt] - Inserts random text. -@setfrom <"from"> - Sets the message FROM: field. -@setsubj <"subject"> - Sets the message SUBJ: field. -@setto <"to"> - Sets the message TO: field. -@xlatexport <charset> - Sets the export charset. -

- - - - Replacement tokens - -

- (replaced with message specific data): -

-

-@c3daddr Current user 3D (boss) address. -@caddr Current user address. -@cdate Current date. -@cdesc Current area description. -@cecho Current echoid. -@cfname Current user first name. -@clname Current user last name. -@cname Current user name. -@cpseudo Current pseudonym given by NICKNAME keyword, or @cfname. -@ctime Current time. -@ctzoffset Current timezone offset (if available and enabled). -@d3daddr Destination 3D (boss) address. -@daddr Destination address. -@dfname Destination first name. -@dlname Destination last name. -@dname Destination name. -@dpseudo Destination pseudonym (see addressbook), or @dfname. -@f3daddr Current from 3D (boss) address. -@faddr Current from address. -@ffname Current from first name. -@flname Current from last name. -@fname Current from name. -@fpseudo Current from pseudonym (see addressbook), or @ffname. -@longpid Long program id. "GoldED", "GoldED/2" or "GoldED/386". -@o3daddr Original 3D (boss) address. -@oaddr Original address. -@odate Original date. -@odesc Original area description if moved, else current. -@oecho Original echoid if moved, otherwise current. -@ofname Original first name. -@ofrom Original RFC "From" headerline. -@olname Original last name. -@omessageid Original RFC "Message-ID" headerline. -@omsgid Original MSGID kludge content. -@oname Original name. -@opseudo Original pseudonym (see addressbook), or @ofname. -@origin The current global or Random System origin. -@os2slash "/2" if running GoldED+/2. Empty otherwise. -@osslash same as above. -@otime Original time. -@otzoffset Original timezone offset (if available and enabled). -@oto Original RFC "To" headerline. -@pid Short program id. "GED", "GED/2" or "GED386". -@pseudo pseudonym (see addressbook), or @tfname. -@rev The revision number (in the form mmdd). -@serialno Emptiness. -@subject The message subject line. -@t3daddr Destination to 3D (boss) address. -@taddr Destination to address. -@tagline The current global or Random System tagline. -@tearline The current global or Random System tearline. -@tfname Destination to first name. -@tlname Destination to last name. -@tname Destination to name. -@tpseudo Destination to pseudonym (see addressbook), or @tfname. -@ver The simple version number (in the form x.yy) -@version The complete release version number of GoldED+. -@_caddr Current user address (fixed width: 19 chars). -@_cname Current user name (fixed width: 34 chars). -@_daddr Destination address (fixed width: 19 chars). -@_dname Destination name (fixed width: 34 chars). -@_oaddr Original address (fixed width: 19 chars). -@_oname Original name (fixed width: 34 chars). -@_taddr Destination to address (fixed width: 19 chars). -@_tname Destination to name (fixed width: 34 chars). -

-

-Tokens dealing with names may optionally have two parameters (each -parameter enclosed in curve brackets): your name and opponent name, -destination name additionally accepts third parameter - WhoTo name. -Here is example on how this feature could be used: -

-

- @oname{I}{You} wrote to @dname{me}{you}{everyone}: -

-

-The template text begins at the first non-comment line. -

-

-See the included GOLDED.TPL for example usage. -

-

-If you need to put some text which contains one of these tokens into a -template file, use an extra '@' in front of the token. -

-

-Example: -

-

- Internet: somebody@veryhot.com -

-

-would produce -

-

- Internet: somebody2.51yhot.com (because @ver is a token) -

-

-so write it like this instead: -

-

- Internet: somebody@@veryhot.com -

-

-The double '@' will then be translated to a single, and token -translation skips past the @token. -

- - - - - - - The Online Help System - -

-GoldED has a built-in context sensitive help system, tied to the <F1> -key (one of the very few keys that cannot be reconfigured). It -contains a complete keyboard reference and help for most situations. -It is current not as complete or sophisticated as I'd like it myself, -but this may be improved in future versions. -

-

-You can completely redefine the help screens if you wish - the -GOLDHELP.CFG file is a plain ASCII text file which contains all help -definitions. The help file is split into several help categories. Here -is an example of a couple of defined help categories: -

-

- *B 1,Help Category 1 - help text help text help text - help text help text help text - *P - help text help text help text - help text help text help text - *E -

-

- *B 2,Help Category 2 - help text help text help text - help text help text help text - *P - help text help text help text - help text help text help text - See also: ^Help Category 1^ - *E -

-

-The "*B" indicator specifies the beginning of a help category. The -format is "*B helpcatnumber[,helpcatname]". In GoldED+ the help -categories are numbered 1000-9999, split into more or less logical -groups. See the help file for assignments. There should be only one -space between the "*B" and the help category number. The help category -name is only required for cross-references. If there are no -cross-references to that help category, then you can leave the -helpcatname parameter out. -

-

-The "*P" indicator specifies a page break and is optional. You may -have as many page breaks as you'd like. The "*E" indicator specifies -the end of the help category. The "*B", "*P", and "*E" indicators must -all begin in the first column. These indicators and the help category -name are case insensitive (can be in lowercase, uppercase, or mixed). -

-

-In the definition of Help Category 2, you will notice the -crossreference to Help Category 1. All cross-referencing is done by -embedding the cross- reference category name (not number) inside -carats (^). If you need to display a carat inside the help file, use a -double carat (^^). -

-

-Any text contained outside of the "*B" and "*E" is treated as -comments. If an "*E" is not found, then the end-of-file will be -treated as an "*E". -

-

-Not all of the help categories in this help file are actually used in -the current version of GoldED+. The ones not used are empty, except for -a two-line "header". -

-

-The usable dimensions of the help window are 60 columns by 16 lines. -In the help file there is a model of the actual window. -

- - - - - - Character Translation - -

-GoldED implements several different proposals for character -translation in imported and exported messages: -

- - - FSC-0050 "Charset Identifier" - -

- by Thomas Sundblom. - - - - FSC-0051 "I51" - -

- by Thomas Gradin. - - - - FSC-0054 "CHARSET proposal" - -

- by Duncan McNutt. - - - - No FSC "Composed Characters" - -

- by Andre van de Wijdeven. -

-

-FSC-0050 is currently known to be implemented in the OPMED 3.xx -message editor, and in Opus 1.7x. It uses the same identifier as -FSC-0054 (a ^aCHARSET kludge), but is a lot simpler (but not -necessarily better). -

-

-The "I51" and "CHARSET" proposals are in the process of being merged -to one proposal, which should combine the advantages of both. They are -both based on using the LATIN-1 (also known as ISO 8859-1) character -set for extended ASCII. The LATIN-1 set is the same set used by -Windows 3.xx, Amiga and many other non-PC computers. In addition to -LATIN-1, I51 defines a set of so-called escape sequences for -characters not found in the LATIN-1 set. -

-

-"Composed Characters" became quite popular in Holland, but the author -decided to drop his proposal because it relied on escape sequences -using the so called "soft-cr" (141d, 8Dh) character. GoldED+ will -continue to support Composed as long as it seems necessary. -

-

-If you want to know more about the details, I suggest you read the -proposals or contact the authors. -

-

-GoldED currently supports two types of translation tables, the *.ESC -files and the *.CHS files. -

- - - - The ESC translation tables - -

-The *.ESC files are used for import translation of the escape -sequences defined in I51 and Composed Characters. -

-

-In the ESC files, the semicolon is used for comments. The *first* -non-comment line defines the charset the escape code are mapped TO. -This is normally IBMPC, and should not be changed. Any other -non-comment line is treated as an escape sequence definition with this -syntax: -

-

- <esc1><esc2><space><map chars>[; comment/description] -

-

-Leading spaces are *not* allowed in ESC files. <esc1> and <esc2> are -the two characters that define the escape sequence. <space> is ignored -and can be used to make the table look better. <map chars> defines the -local representation of the escape sequence, up to three characters. -Normally you would only map to one extended ascii character. The map -chars can be either the characters themselves, or decimal or -hexadecimal numbers of the form "\d<dec>" or "\x<hex>" (like in the C -programming language). -

- - - - The CHS translation tables - -

-The *.CHS files are used for import and export translation of the -CHARSET type character sets, and export of I51 and Composed escape -sequences. -

-

-The CHS files uses the format of the raw text files provided in the -CHARSET3.ZIP example implementation of FSC-0054. Study some of the -files provided if you want to know how to define them. -

-

-The two keywords XLATESCSET and XLATCHARSET are used to define which -files belong to what import and export set. You can define more than -one import and export set for each file. -

-

-The keyword XLATIMPORT defines which charset you have on your own -machine - this would normally be "IBMPC". It can be useful to change -this (using the Random System) in areas where another character set -than IBMPC is the dominant (like Amiga or MacIntosh, whatever). -

-

-The keyword XLATEXPORT defines the charset your messages should be -exported to, if any. -

-

-Confused? Yeah, I know - this is a confusing subject, and my -implementation and documentation is not perfect. Normally you will not -have to worry about it. Turn it off completely if you don't understand -it. -

- - - - - - - Keyboard Command Reference - -

-Most of the GoldED+ keyboard commands can be reached with just one -keystroke. To ease operation for experienced users of other message -editors, GoldED+ comes with several sets of keys for each of the -keyboard commands - direct non-shifted keys, Alt/Ctrl-keys and -function keys. Many of these key assignments will be familiar for -users of Msged, Msged/Q, ME2 and FM. -

-

-The following is a list of all keyboard commands, sorted by type and -alphabetically, using the format -

-

- <command> <short description> -

-

-This list is also available in the context-sensitive help system on -the <F1> key. -

-

-It is possible to almost completely redefine the keyboard - this in -done in the GOLDKEYS.CFG file, which also handles macro definition -(see later). -

- - - Arealist Commands - -

-AREAabort Abort the arealist. -AREAaskexit Exit GoldED+, prompt for final decision. -AREAboardnos Toggle sequential areas vs. board numbers. -AREAcatchup Point the lastread pointer to the last message - in the current area. -AREAdosshell Shell to DOS. -AREAdropmsgmarks Unmark all msgs in selected areas. -AREAgotofirst Move selection bar to first area. -AREAgotolast Move selection bar to last area. -AREAgotonext Move selection bar to next area. -AREAgotoprev Move selection bar to previous area. -AREAheat Heat highwatermarks. -AREAjump Move selection bar to next marked area. -AREAjumpnextmatch Move selection bar to next matching area. -AREAquitnow Exit immediately, no questions asked. -AREAscan Scan areas. -AREAscanpm Scan areas for personal mail. -AREAselect Enter the reader for the selected area. -AREAselectmarks Select which set of area marks should be used. -AREAsoundkill Stops currently played sound file. -AREAtoggle Toggle mark on the selected area. -AREAtouchnetscan Touches the SEMAPHORE NETSCAN file. -AREAwritegoldlast Write a fresh copy of GOLDLAST.LST -AREAzap Zap highwatermarks. -

- - - - Internal Editor Commands - -

-EDITabort Abort editing this message - ask first. -EDITanchor Set a block "anchor" on the current line. -EDITaskexit Exit from GoldED+ - ask first. -EDITblockdown Extend block area one line down. -EDITblockend Extend block area to the end of line. -EDITblockhome Extend block area to the beginning of line. -EDITblockleft Extend block area one character left. -EDITblockpgup Extend block area one screen up. -EDITblockpgdn Extend block area one screen down. -EDITblockright Extend block area one character right. -EDITblockup Extend block area one line up. -EDITcleardeletebuf Clears the undelete buffer. -EDITclearpastebuf Clears the cut'n'paste buffer. -EDITcopy Copies the block to the cut'n'paste buffer. -EDITcopyabovechar Inserts character same as in the same position - in previous line. -EDITcut Cut the block to the cut'n'paste buffer. -EDITdelchar Delete the char at the cursor position. -EDITdelete Delete the block. -EDITdeleteeol Delete from cursor position to end of line. -EDITdelleft Delete the char to the left of the cursor. -EDITdelline Delete the current line. (Copied to the -EDITdelltword Delete the word to the left of the cursor. -EDITdelrtword Delete the word to the right of the cursor. -EDITdosshell Shell to DOS. -EDITdupline Duplicates the current line. -EDITexitmsg Drop this message - NO ASKING! DANGEROUS! -EDITexporttext Exports the current block to a file. -EDITgobegline Move cursor to beginning of line. -EDITgobotline Move cursor to the bottom line in the display. -EDITgobotmsg Move cursor to the last line in the message. -EDITgodown Move cursor down to next line. -EDITgoeol Move cursor to the end of the line. -EDITgoleft Move cursor one position left. -EDITgopgdn Move cursor one page of lines down. -EDITgopgup Move cursor one page of lines up. -EDITgoright Move cursor one position right. -EDITgotopline Move cursor to the top line in the display. -EDITgotopmsg Move cursor to the first line in the message. -EDITgoup Move cursor up to the previous line. -EDITgowordleft Move cursor to the previous word. -EDITgowordright Move cursor to the next word. -EDITheader Edit the message header, attributes etc. -EDITimportquotebuf Imports the current quote buffer. -EDITimporttext Import text file into this message. -EDITkillquotes (ignored) -EDITloadfile Load the message file saved with EDITsavefile. -EDITlookupcursor Lookup name/node at cursor position. -EDITlookupdest Lookup TO: node. -EDITlookuporig Lookup FROM: node. -EDITnewline Terminate paragraph and/or add a new line. -EDITpaste Paste a previously cut block at the cursor. -EDITquitnow Quit GoldED+ immediately - no asking. -EDITreflow Reflows the current text or quote paragraph. -EDITsavefile Saves the current message as a file. -EDITsavemsg Save this message. -EDITsoundkill Stops currently played sound flie. -EDITspellcheck Calls an external spell checker for the msg. -EDITtab Add spaces to the next tab-stop. -EDITtabreverse Remove spaces to the prev tab-stop. -EDITtogglecase Toggle the case of the cursor character. -EDITtoggleinsert Toggle insert mode. -EDITtolower Change the cursor character to lowercase. -EDITtoupper Change the cursor character to uppercase. -EDITundelete Undelete previously deleted lines. -EDITzapquotebelow Deletes quotes below. -

- - - - File Selection Commands - -

-FILEabort Abort file selection. -FILEaskexit Exit GoldED+ - ask first. -FILEdosshell Shell to DOS. -FILEgotofirst Go to first file. -FILEgotolast Go to last file. -FILEgotonext Go to next file. -FILEgotoprev Go to previous file. -FILEmark Mark file. -FILEmarkall Mark all files. -FILEquitnow Quit GoldED+ immediately. -FILEselect Select the marked file(s). -FILEtogglemark Toggle file mark. -FILEunmark Unmark file. -FILEunmarkall Unmark all files. -

- - - - Message Lister Commands - -

-LISTabort Abort message lister. -LISTaskexit Exit GoldED+ - ask first. -LISTdosshell Shell to DOS. -LISTgotobookmark Go to BookMark message. -LISTgotofirst Go to first message. -LISTgotolast Go to last message. -LISTgotonext Go to next message. -LISTgotoprev Go to previous message. -LISTmarkingoptions Marking menu. -LISTquitnow Quit GoldED+ immediately. -LISTselect Go to reader at the selected message. -LISTtogglebookmark Toggle BookMark on the selected message. -LISTtoggledate Toggle date column content. -LISTtogglemark Toggle Mark on the selected message. -LISTtogglewidesubj Toggle between wide and short subject. -

- - - - Nodelist Browser Commands - -

-NODEabort Abort nodelist browsing. -NODEaskexit Exit GoldED+ - ask first. -NODEdosshell Shell to DOS. -NODEgotofirst Go to first node. -NODEgotolast Go to last node. -NODEgotonext Go to next node. -NODEgotoprev Go to previous node. -NODEquitnow Quit GoldED+ immediately. -NODEselect Select node. -

- - - - Message Reader Commands - -

-READaddressbookadd Add current/marked mail writer(s) to - addressbook. Ask first. -READaskexit Exit GoldED+, prompt for final decision. -READchangeaka Change default AKA address for current area. -READchangeattrs Change the attributes of the current message. -READchangemsg Change current message. -READchangeorigin Change default origin for the current area. -READchangetagline Change default tagline. -READchangetemplate Change default template. -READchangeusername Change default username. -READchangexlatimport Change default import charset. -READcommentmsg Comment-Reply to message. (Reply to TO name). -READcopymoveforward Enter the Copy/Move/Forward function menu. -READdecreasemargin Decrease message margin. For test purposes. -READdeletemsg Delete current/marked message(s). Ask first. -READdosshell Shell to DOS. -READfidorenumber Renumber Fido/Opus *.MSG files. -READfilerequest Generate a filerequest from the current msg. -READfindall Find string(s) in message header and text. -READfindheader Find string(s) in message header. -READgotobookmark Go to the "BookMark" message. -READgotofirstmsg Go to the first message in the area. -READgotolastmsg Go to the last message in the area. -READgotomsgno Go to a specific message number. -READgotonextarea Go directly to the next area. -READgotonextmsg Go to the next message. -READgotonextunread Go to the next unread message. -READgotoprevarea Go directly to the previous area. -READgotoprevmsg Go to the previous message. -READgotoprevunread Go to the previous unread message. -READgotoreplies Choose from the next messages in the replylink. -READgotoreply1st Go to the first reply to this message. -READgotoreplynext Go to the next reply to this message. -READgotoreplyprev Go to the parent message in the replylink. -READincreasemargin Increase message margin. For test purposes. -READlookupdest Lookup TO: node. -READlookuporig Lookup FROM: node. -READmakeuserlist Generate FIDOUSER.LST of users in the area. -READmakepathreport Added "path report" feature. The output file - can be processed by a RDDT (Route Diagram - Drawing Tool) utility. -READmarkingoptions Enter the marking menu. -READmessagelist Enter the message lister. -READmovecommentmsg Comment-Reply in another area. -READmovequotemsg Quote-Reply in another area. -READmsgcontinue Page down or go to next message. -READmsgend Display last part of current message. -READmsghome Display first part of current message. -READmsglinedown Scroll message display. -READmsglineup Scroll message display. -READmsgpgdn Page message display. -READmsgpgup Page message display. -READnewarea Enter the area selection screen. -READnewmsg Start a new message. -READquitnow Exit GoldED+ immediately, no questions asked. -READquotebuf Append quote of the msg to the quotebuffer. -READquotemsg Quote-Reply to message. (Reply to FROM name). -READreplymsg Reply to the current message, without quoting. -READsearch Launches the search engine. -READsoundkill Stops currently played sound file. -READthreadtree Enter the Message Threading lister. -READtogglebookmark Toggle a "BookMark" on the current message. -READtogglehexdump Toggle hexdump mode. For debugging purposes. -READtogglehiddklud Toggle display of Hidden and Kludge lines. -READtogglehidden Toggle display of Hidden lines. -READtogglekludge Toggle display of Kludge lines. -READtogglemark Toggle a message mark on the current message. -READtogglemarkread Toggle "Read Marked" mode. -READtogglepagebar Toggle the "PageBar" feature. -READtogglequote Toggle display of quoted lines. Experimental. -READtogglerot13 Toggle ROT13 encryption for the current msg. -READtogglerealmsgno Toggle between seq. or real message numbers. -READtogglestyles Toggle Disable/Show/Show+Strip of STYLECODES. -READtoggletwits Toggle Twit display - Show/Blank/Skip/Ignore. -READtouchnetscan Touches the SEMAPHORE NETSCAN file. -READtouchsemaphore Popup touch a manually entered semaphore file. -READuserbase Launches the addressbook. -READuudecode UUdecodes the current message. -READwritemsg Write message(s) to file or printer. -

- - - - Key Undefine Commands - -

-AREAundefine -EDITundefine -FILEundefine -LISTundefine -NODEundefine -READundefine -

-

-The undefine commands can used to undefine any of the built-in default -keyboard definitions. -

-

-See the Key Reference below for a list of the key symbols you can use -in keyboard redefinition. -

- - - - -Macros and Keystacking -

-GoldED has a simple keyboard macro facility, which you can use to -automate certain common operations. In addition, a "keystacking" -facility allows you to create simple automatic macros on the fly. -

-

-The macro definition syntax is modelled after the syntax used in the -QEdit text editor: -

-

- <assignment-key> Macro <commands or keys> - <assignment-key> AreaMacro <commands or keys> - <assignment-key> EditMacro <commands or keys> - <assignment-key> FileMacro <commands or keys> - <assignment-key> ListMacro <commands or keys> - <assignment-key> NodeMacro <commands or keys> - <assignment-key> ReadMacro <commands or keys> -

-

-Macros are defined in the GOLDKEYS.CFG file, where you can also find -several examples. -

-

-By using the word "Auto" as <assignment-key>, you can even define a -special macro which will be automatically executed when you start -GoldED. -

-

-Keystacking is a special form of auto-macros. You simply specify a -bunch of keys to be "stacked" in the (special internal) keyboard -buffer for sequential execution. -

-

-You can either specify a default set of keystacking in the .CFG -configuration file, or override any default keystacking by typing the -keystack definitions at the GoldED+ commandline or the GEDCMD -environment variable. -

-

-See the Key Reference chapter for a list of the key symbols you can -use in macros and keystacking. -

-

- - - - - - Key Reference - -

-Below is the list of key symbols recognized by GoldED+ for -keyboard/macro definition and keystacking. -

-

-Unshifted function keys -

-

- F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 -

-

-Shift-function keys -

-

- #F1 #F2 #F3 #F4 #F5 #F6 #F7 #F8 #F9 #F10 #F11 #F12 -

-

-Alt-function keys -

-

- @F1 @F2 @F3 @F4 @F5 @F6 @F7 @F8 @F9 @F10 @F11 @F12 -

-

-Ctrl-function keys -

-

- ^F1 ^F2 ^F3 ^F4 ^F5 ^F6 ^F7 ^F8 ^F9 ^F10 ^F11 ^F12 -

-

-Alt-Numbers -

-

- @0 @1 @2 @3 @4 @5 @6 @7 @8 @9 -

-

-Alt-Letters -

-

- @A @B @C @D @E @F @G @H @I @J @K @L @M - @N @O @P @Q @R @S @T @U @V @W @X @Y @Z -

-

-Ctrl-Letters -

-

- ^A ^B ^C ^D ^E ^F ^G ^H ^I ^J ^K ^L ^M - ^N ^O ^P ^Q ^R ^S ^T ^U ^V ^W ^X ^Y ^Z -

-

-Insert/Delete -

-

- Ins ^Ins @Ins - Del ^Del @Del -

-

-Home/End -

-

- Home ^Home @Home - End ^End @End -

-

-Page up/down -

-

- PgUp ^PgUp @PgUp - PgDn ^PgDn @PgDn -

-

-Cursor left/right -

-

- Left ^Left @Left - Right ^Right @Right -

-

-Cursor up/down -

-

- Up ^Up @Up - Down ^Down @Down -

-

-Misc other keys -

-

- Esc ^Grey* Key5 Space Tab #Tab @Tab BackSpace ^BackSpace - @BackSpace Enter ^Enter @Enter -

-

-Note that some of the Alt-keys, especially the cursor-related keys and -the F11/F12 keys, are "extended" keys normally only available on -systems with an extended keyboard bios. However, GoldED+ uses a few -tricks to make some the extended keys available on non-extended -systems. -

- - - - - - Language Definition - -

-GoldED allows you to almost completely redefine the language dependent -text in the program. -

-

-The language dependent text in GoldED+ is defined in the plain ASCII -text GOLDLANG.CFG file. -

-

-See the example language file for the actual method and format of -language redefinition. -

-

-If you are planning to translate the text in GoldED+, you should also -look into the definition of the help screens. -

-

-You do not need permission from the author before announcing or -distributing your own modified language files. -

- - - Date/Time Substitution Codes - -

-A few of the language texts can contain special date/time substitution -codes. The keywords for those are: MS_DateTimeFmt, MS_DateFmt, -MS_TimeFmt and ST_StatuslineTimeFmt. -

-

-Here are the valid substitution codes: -

-

- %a Abbreviated weekday name (Mon, Tue, Wed, ...). - %A Full weekday name (Monday, Tuesday, Wednesday, ...). - %b Abbreviated month name (Jan, Feb, Mar, ...). - %B Full month name (January, February, March, ...). - %d Day of month (01-31). - %e Day of month, with leading space for single digits (1-31). - %E Day of month (1-31). - %H Hour (00-23) (24-hour clock). - %I Hour (01-12) (12-hour clock). - %j Day of the year (001-366). - %m Month (01-12). - %M Minute (00-59). - %p AM or PM according to 12-hour clock. - %S Second (00-59). - %U Week number (00-52) where sunday is first day of the week. - %w Weekday (0-6) where 0 is sunday. - %W Week number (01-53) where monday is first day of the week. - %y Year without century (00-99). - %Y Year with century. - %% Character '%'. -

-

-The %a, %A, %b and %B codes substitute to the current language setup -loaded using the LOADLANGUAGE keyword. -

-

-*** NOTE *** -

-

-In the continuing development of GoldED+, it is impossible to -completely maintain backward compatibility of the language format or -the text defined there. New features may add and/or obsolete some -definitions, or may change the format of others. -

-

-The existing language file may contain definitions which are already -obsolete, but which I haven't had time to search for and remove, as -well as there may be some texts in GoldED+ which are not yet definable. -All this will of course be corrected in future versions. If you find -inconsistencies, please report them, because I may have overlooked -them. -

- - - - - - - Message Kludge Lines - -

-Kludge lines are special control lines, that begin with a ^a (ASCII 1) -as the first character of the line, followed by a unique identifying -name and the relevant control information. -

-

-GoldED is aware of a lot of these kludges, and supports a number of -them, if you want to have them inserted in your messages. -

-

-Some kludges are useless junk and more or less commercials for this -and that software, but a few are useful for miscellaneous purposes. In -the following, I will list (some of) the known and supported kludges, -and a short description of what they are used for. -

- - - ACUPDATE: - -

- This kludge is a feature of Squish 1.10: Message Broadcast - Modify/Delete. Read the docs for Squish 1.10 for details. -

- - - - AREA:<echoname> - -

- This is not really a kludge, and it doesn't begin with a ^a, but I - included it on the kludge list because it sometimes turned up in - echomail areas where it should have been stripped off by the mail - tosser. -

- - - - CC: <name> <address> - -

- When GoldED+ produces carbon copies, it adds to each message a full - list of the persons who get a copy. One version of this list is - hidden behind the CC: kludge. -

- - - - CHARSET:<charset identifier> - -

- Proposed in FSC-0050 and FSC-0054, this kludge is an attempt to - find a solution to the problem of the high-bit characters (like - the IBM PC vs Amiga vs Mac etc. national chars) in messages. - GoldED+ can recognize, use and generate this kludge. -

- - - - CHRC:<font change id> - -

- Proposed in FSC-0054, this is a kludge for changing fonts, - underlining and other stuff. -

- - - - CHRS:<charset identifier> - -

- Alternative FSC-0054 version of the CHARSET kludge. -

- - - - DESTADDR:<destaddress> - -

- This one is not proposed anywhere, but it looks like it gives the - address of the intended recipient. GoldED+ takes the address for - the dest field. -

- - - - DOMAIN <destdomain> <destaddress> <origdomain> <origaddress> - -

- Proposed in FSC-0038, this tries to solve the problem of mail - crossing domain boundaries. GoldED+ takes both addresses. -

- - - - EID:<crc16> <stamp> [replycrc16] <replystamp> - -

- Proposed in FSC-0031, this is used for dupe checking and reply - linking. The EID is today generally considered as garbage, but a - lot of older mail processors such as QMail still generate it. -

- - - - ENC: - -

- Signifies that the message contains encrypted data. GoldED+ will - add this kludge if it detects that the message has been encrypted - with PGP. -

- - - - EOT: - -

- End Of Text. See SOT. -

- - - - FLAGS <special attributes> - -

- Proposed in FSC-0053, this is a special netmail kludge used by the - FrontDoor and D'Bridge mailers and the IMail mail processor. It - provides extra attributes not found among the standard attributes - in the normal message/packet headers. GoldED+ uses and generates - this kludge, if you set the attributes. -

- - - - FMPT <from point> - -

- Defined in FTS-0001, this tells the point number of the - originator. Netmail only. GoldED+ can generate this line. -

- - - - FWDAREA <original area> - -

- FSC-0092: The original area in forwards. See - USEFWD and FSC-0092 for a more detailed - description. -

- - - - FWDDEST <aka> - -

- FSC-0092: The original To: address in forwards. - See USEFWD and FSC-0092 for a more detailed - description. -

- - - - FWDFROM <name> - -

- FSC-0092: The original From: name in forwards. - See USEFWD and FSC-0092 for a more detailed - description. -

- - - - FWDMSGID <aka serial#> - -

- FSC-0092: The original MSGID in forwards. - See USEFWD and FSC-0092 for a more detailed - description. -

- - - - FWDORIG <aka> - -

- FSC-0092: The original from-aka in forwards. See - USEFWD and FSC-0092 for a more detailed - description. -

- - - - FWDSUBJ <original subject> - -

- FSC-0092: The original subject in forwards. See - USEFWD and FSC-0092 for a more detailed - description. -

- - - - FWDTO <name> - -

- FSC-0092: The original To: field in forwards. See - USEFWD and FSC-0092 for a more detailed - description. -

- - - - GATECHK:<???> - -

- Some sort of gating kludge? Don't know what it's for. -

- - - - GIF:<filename> - -

- Invented by Henk Wever and used in his - Dutchie software. The filename (which does not have an - extension) indicates a GIF picture of the author of the - message. -

- - - - GROUP:<echoname> - -

- I think this one comes from stray Groupmail messages. Similar to the - AREA kludge. -

- - - - I51 (no parameters) - -

- Proposed in FSC-0051, this indicates that the message text - conforms to the ISO-8859-1 (LATIN-1) - character set, and may contain certain escape codes. The - ISO-8859-1 set is used in Amiga and - Windows 3.xx. GoldED+ can recognize, use and - generate this kludge. -

- - - - INTL <destaddress> <origaddress> - -

- Defined in FTS-0001, this one solves the problem of - crossing zone boundaries. Netmail only. GoldED+ can - generate this line. -

- - - - MSGID: <origaddress> <serialno> - -

- Defined in FTS-0009, this is a method for unique - identification of a message. It can be used for dupe checking and - replylinking. GoldED+ can generate this line. -

- - - - MSGTO: <destaddress> - -

- This one is not proposed anywhere, but it looks like it gives the - address of the intended recipient. GoldED+ takes the - address for the dest field. -

- - - - Original: <Carbon copy, original name> - -

- Generated by the FrontDoor FM editor when it - produces carbon copies. -

- - - - PATH: <list of nodes> - -

- Defined in FTS-0004, this is a valuable tool for finding - dupe links and other structural faults in the net structures. - Unfortunately the list of nodes is 2D (net/node), and this creates - problems when exporting echomail across zones. -

- - - - PTH: <list of nodes> - -

- Not yet a FSC (or is it?), this is a 5D-version of the - PATH kludge, which sticks to the top of the msg. -

- - - - PID: <identifier> <version> [serialno] - -

- Proposed in FSC-0046, this takes a stab at the tearline - abuse, and puts safe information about the first mail processing - software in the line. This could be message editors, mail scanners and - other stuff. -

- - - - Realname: <Name> - -

- This kludge was probably born in Russia because of some software was - not able to properly handle non-ASCII characters in - the header lines. Name should be written in national codepage. - Otherwise I don't see any reason for this kludge. I don't know any - software that generate this kludge. -

- - - - RFD: <id> - -

- Received For Distribution. A kludge inserted by one of the file - announcement programs. -

- - - - REPLY: <replyaddress> <replyserialno> - -

- Defined in FTS-0009, this is the MSGID - counterpart. When replying to a message with a MSGID, the - MSGID of the original is renamed to REPLY. -

- - - - RID:<stuff> - -

- Unknown kludge which looks suspiciously like the EID. -

- - - - ROUTE <list of nodes and points> - -

- Specifies route path. Currently supported by Unimail and - S\Tosser. -

- - - - SEEN-BY: <list of nodes> - -

- Defined in FTS-0004, this is a tool for finding dupe links - and other structural faults in the net structures. Depending on the - mail tosser, the seen-by's may or may not have a preceding ^a - character. Unfortunately the list of nodes is 2D (net/node), and this - can create problems when exporting echomail across zones. -

- - - - SN:<serialno> - -

- Serial number inserted by the Dutchie message editor. -

- - - - SOT: - -

- Start Of Text. See EOT. -

- - - - SPLIT: - -

- Defined in FSC-0047. A method for splitting large msgs so - that some mail processors don't choke on them. -

- - - - TCL1:, TCL2: <long hex string> - -

- Old obsolete swedish dupecheck/replylink kludge. -

- - - - TID: - -

- Tosser ID. Similar to the PID, but specifically - for mail processors. -

- - - - TOPT <to point> - -

- Defined in FTS-0001, this tells the point number of the - destination. Netmail only. GoldED+ can generate this line. -

- - - - TZ <offset from UTC> - -

- Specifies the time to add to the header time to get the - UTC (Universal Time Coordinated) time. Generated by newer - versions of the TrackMail netmail processor. -

- - - - TZUTC - -

- See TZ. GoldED+ can generate this line. -

- - - - Via: <netmail tossing info> - -

- Routed netmail messages usually gets a Via line for each node - it passes through. This can be used for tracing faults in the netmail - routing structure. -

- - - - XID:<stuff> - -

- Unknown kludge which looks suspiciously like the EID. -

- - - - - - - - + + + + + + + + + GoldED+ Reference Manual + + + +

+ Created in electronic form. +

+ + + + + + English + + + + + + + + + + + + GoldED+ + + + Reference Manual + + + + Odinn Sorensen, Dirk A. Mueller, Alexander S. Aganichev and others + + + 1990-2003 + + + + + + + + + + Introduction + +

+ +

+ IBM OS/2, +

+ Dirk A. Mueller, and + Alexander + Tsvyashchenko, Alexander + Aganichev and Haruyasu + Yoshizaki, Lanius + Corporation, Folkert J. + Wijnstra, Continental + Software, +

+ We also need to thanks all that people who have contributed configuration + files: Steve + Shapiro, Michael + Hembo, Kees + Bergwerf, +

+ Special thanks goes to + + + + + License Agreement and Copyright Notices + +

+ +

+ ( +

+ The GNU Library + General Public License ( +

+ Additionally, permission is hereby specifically given to link + Goldware + Library with any software or software library that meets the + http://www.opensource.org. This includes + +

+ The additional permission to link with non-GPL/LGPL software + may be slightly controversial. The intent is to allow developers a + greater freedom to create specialized versions of GoldED. Examples could + be a +

+ Parts of the +

+ So, even though parts of the Mike + Smedley and how to contact him, +

+ Lanius + Corporation. +

+

+ +

+ Products and company names listed are trademarks or trade names of their + respective companies. +

+ + + + + The Message Database Formats + + + + Opus, FTS-0001 + +

+ These are two variants of the same type of msgbase. It works by using + one physical file per message ( +

+ In echomail areas, this format has a special quirk: The first message + ( +

+ The variants: The + + + + QuickBBS, RemoteAccess, and Hudson + +

+ This msgbase format was invented by +

+ The format limits the total size of +

+ The first incarnations of +

+ The main virtue of this format is that it is very fast to access the + msgbase. +

+

+ The main disadvantage is that it can be very sensitive to disk + problems, and it is a common horror story that people loose their + entire msgbase because the disk developed bad clusters or some + program went berserk and messed up the msgbase files. +

+ + + + Goldbase + +

+ This is an enhanced version of the +

+ The + + + + Squish + +

+ The +

+ The use of a database for each area - instead of one file per msg, + or all msgs in one big database - makes this format fast, very + safe and resistant to disk problems. Even if something messed up a + +

+ A special feature of + + + + Ezycom + +

+ + + + + JAM + +

+ +

+ +

+ +

+ The +

+ +

+ Msg may not be displayed to user (always + displayed). +

+

+ specifies which + method to use. +

+ + + + PCBoard + +

+ The supported +

+

+ Passwords are not supported. +

+

+ The +

+ +

+ The mail waiting flags are updated when you write to people that are + named in the userbase. +

+

+ When changing a message, the new edition is saved as if it were a new + message, with a new message number, and then the old edition is + deleted. This behaviour is consistent with the way + + + + AdeptXBBS + +

+ The implementation is based on the documentation in version 1.05, + experimentation and questions to the authors. Thanks go to + +

+ The +

+ Mixing of netmail and echomail or other types of mail in the same + area is not directly supported. If an area is setup as both netmail + and echomail, +

+ +

+ The +

+ The replylinking method used by + + + + WildCat! + +

+ The +

+ WildCat features which are not supported yet: + + The message from/to title. + +

+

+ There is a keyword + , which works just + like the other <msgbase>USERNO keywords. By default + +

+ + + + + Synchronet + +

+ Synchronet + Message Base Specification version 1.21. +

+ Just like +

+ + + + + + + Nodelist and Userlist Support + +

+ +

+ In order to enable nodelist/userlist lookup and browsing, +

+ + + + + Routing Diagram Drawing Tool + +

+ Routing diagram drawing tool intended to analyse files created by + pressing key defined for READmakepathreport + action. + + + + + Commandline Reference + + + + Mail Reader Commandline Syntax + +

+ Invocation: +golded [options] [keystacking] +

+

+ Depending on used platform GoldED+ could be called + geddjg, gedcyg, gedemx, or + gedlnx. Available options are (all options are case + insensitive): + + + + Displays a help screen with all available commandline options. + + + + Specifies another configuration file than the default. See also + environment variable. + + + + Disable old configuration keywords. For backward compatibility, + GoldED+ still supports a number of old names for + some configuration keywords. It is recommended that you use + -d sometimes and rename the keywords that are + reported as unknown. + + + + If specified, GoldED+ starts directly in the + specified echo, bypassing the arealist screen. See the + AREASTART configuration + keyword for more info. + + + + Calls the SOUP packet export feature during the + startup phase. This is the same as starting it from the + areascan SOUP Packet->Export menu + item. The SOUP export happens immediately after the + regular startup area scanning (if that is enabled) and after + SOUP import. + + + + Force recompile of most configuration files, but not all. Does not + recompile the *.chs files. + + + + Force complete recompile of all configuration files, regardless of + whether they are up-to-date or not. This is equivalent to deleting + all the *.ge? files. + + + + Same as option -?. + + + + Start the quick install procedure. You should give a path to your + other mail software if it cannot be found using environment + variables or in current directory. + + + + Calls the SOUP packet import feature during the + startup phase. This is the same as starting it from the areascan + SOUP Packet->Import menu item. The + SOUP import happens immediately after the regular + startup area scanning (if that is enabled). + + +

+

+ Any non-option characters on the commandline are stuffed into the + keyboard buffer. See the chapter on keyboard definition and the + KEYBSTACK keyword for more info. +

+

+ For example, +golded @S A + makes GoldED+ go to the area scanning menu <Alt-S>, + and select scanning of <A> all areas. +

+

+ See the chapter for more info. Note, + that only those combinations described in the + KEYBSTACK chapter are allowed + here. +

+ + + + +

+ For operation in batch files, GoldED+ has a set of + errorlevel values: + + + + 032 or higher + + + Error exit (check the logfile for details). + + + + + 004 + + + Echomail entered. + + + + + 002 + + + Netmail entered. + + + + + 001 + + + Local mail entered. + + + + + 000 + + + No errors. No mail entered. + + +
+

+

+ Add values together to find the combined error levels. For example, error + level 6 is returned if netmail and echomail (2+4) was entered. +

+

+ Example of rungold.bat file: +golded.exe +if errorlevel 007 goto e_n_l +if errorlevel 006 goto e_n__ +if errorlevel 005 goto e___l +if errorlevel 004 goto e____ +if errorlevel 003 goto __n_l +if errorlevel 002 goto __n__ +if errorlevel 001 goto ____l +if errorlevel 000 goto nomail +:error + echo GoldED+ error exit! + goto end +:e_n_l + echo **** New echo, net and local mail entered. + goto end +:e_n__ + echo **** New echo and netmail entered. + goto end +:e___l + echo **** New echo and local mail entered. + goto end +:e____ + echo **** New echomail entered. + goto end +:__n_l + echo **** New net and local mail entered. + goto end +:__n__ + echo **** New netmail entered. + goto end +:____l + echo **** New local mail entered. + goto end +:nomail + echo **** No new mail entered. +:end + echo. + echo Thank you for using GoldED+! :-) +

+ + + + Nodelist Compiler Commandline Syntax + +

+ Invocation: +goldnode [options] [configfile] +

+

+ Depending on used platform GoldNODE could be called + gndjg, gncyg, gnemx, or + gnlnx. Available options: + + + + Conditional compile. + + + + Remove duplicate nodes from index. + + + + Forced compile. + + + + Quite compiled. No screen output improves speed. + + + + Set the max size of names. Normally not used. + + + + Create sorted + +

+

+ The and + environment variables. +

+

+ The nodelist index files are named keyword. +

+

+ The V7+ index is automatically used if your + is set correctly. If + +xxxx / nodex.dtp + at the bottom of the browser window, the displayed information is taken + from the raw nodelist entry, taken from the V7+ index. +

+

+ GoldNODE can read the german POINTS24-format + directly! +

+

+ and + keywords, please note + that the addressmask does not accept + + + + Routing Diagram Drawing Tool Commandline Syntax + +

+ Invocation: +rddt <routefile> [options] [address or name] +

+

+ Depending on used platform RDDT could be called + rddtdjg, rddtcyg, rddtemx, or + rddtlnx. Available options: + + + + Reserved for debugging purposes. + + + + Sets indent to n. + + + + This option used to specify yours link address. Requires option + -n. + + + + Use this option to specify your address. + + + + Decode path. + + +

+

+ Example: +RDDT path.rpt -n2:5020/604.19 -l2:5020/604 2:5020/604.19 -p +

+ + + + + + Environment Variables + +

+ These are the GoldED+ specific environment variables: + + +

+

+ When using the feature to read + external area configuration from the other programs, the individual + 's may use specific environment + variables to find the files. Please read the + chapter for specific details of each + supported . +

+ + + + + Configuration Keyword Reference + +

+ The following special symbols are used in the keyword parameter lists: + + + + [] + + + Optional parameter. + + + + + <> + + + Required parameter, not optional. + + + + + + + + Parameter must be inclosed in quotes. + + + + + / + + + Separates mutually exclusive values. + + + + + , + + + Separates possible values for the keyword. + + +
+

+

+ There's no mandatory keywords but the mail reader should have defined at + least name, address and area; nodelist compiler should have address and + either nodelist or userlist defined. +

+

+ Whenever path is expected you may use environment variables enclosed in + percent signs, f.e. %FIDO%/myfile.txt. This also valid for + input prompts where path is expected :-) +

+ + + Remarks + + + + + + + + Signifies a remark (comment) line. + + + + The + + + Any non-alphabetic non-whitespace character at the beginning of a + line makes the line a comment. By tradition, the semicolon is the + standard comment character. The semicolon (and only that) can also + be used to add a comment at the end of a configuration line. + + + + Mail reader and nodelist compiler. + + + +REM This is a comment +; This is a comment +% This is a comment +* This is a comment +// This is a comment +/* This is a comment */ +ADDRESS 2:236/77 ; Main address. +AKA 2:236/77.1 ; SysOp point. + + + + + + Conditionals + + + + + + + + + + + + These control keywords can be used to setup sections of configuration + which enable different sets of keywords depending on which version + that is used. + + + + The following conditions can be used: + + + + + + true, if DPMI32 version is used + + + + + OS/2, + + true, if OS/2 version is used + + + + + + + true, if Win32 version is used + + + + + Linux, UNIX + + + true, if + + + + Firebird + + + true, if + + + + ASA + + + true, if + + + + Yes, True, On + + + always true + + +
+ + + + Mail reader and nodelist compiler. + + + +IF OS2 + EDITOR c:\qedit\os2\q.exe @file -n@line + EDITSPELLCHECK c:\os2\cmd.exe /c c:\ss\ss.exe @file +ELIF DOS + EDITOR c:\qedit\dos\q.exe @file -n@line + EDITSPELLCHECK c:\ss\ss.exe @file +ELIF WIN32 + EDITOR c:\progra~1\far\far.exe -i -e@line @file + EDITSPELLCHECK c:\fido\goldkorr\goldkorr.exe @file /A /Q +ENDIF + + + + + + IGNORE + + + + + + + + This tells the configuration file reader to ignore all subsequent + lines until another + + + This keyword may cause unpredicable results if used within + + + + Mail reader. + + + + + + + + + ADDRESS + + + + + <zone:net/node[.point][@domain] + [,pointnet]> + + + + Your network address, can be used + interchangeably. + + + + If a zone:pointnet/point.0 in the msg header, instead of + the zone:net/node.point. Most modern + mailers and mail processors now supports the + The optional + + + This keyword can be used globally and in a + Random System group. + + + + Mail reader and nodelist compiler. + + + + , + + + + +ADDRESS 2:236/77 ; Node address +ADDRESS 2:236/77.1 ; Point address (4D) +ADDRESS 2:236/77.1, 16077 ; Point address (3D) +ADDRESS 2:236/77@fidonet ; Node address with domain + + + + + + ADDRESSBOOKADD + + + + + <YES/NO/ALWAYS> + + + + This keyword controls whether + + + Setting this keyword to + + + + + + + + It's a + + + It's a + + + It's the + + + It's the mailinglist's sender address + + + It's an UUCP + + + It's already an email address + + + Address/aka is unknown + + + It's an + + + + + + Mail reader. + + + + , + , + , + , + , + + + + + + + ADDRESSLOOKUPFIRST + + + + + <MSGID/ORIGIN> + + + + This keyword defines the first source to lookup address. If valid + address could not be found in the specifyed location then second + source is used. + + + + If defined to + + + + + + Mail reader. + + + + + + ADDRESSMACRO + + + + + subject] [,attribs]/ + + + + Defines a short name for often used addresses. Typical uses are for + + + + If (and only if) the subject is enclosed in quotes ( for the + valid attributes. You cannot have quotes within quotes (not the same + type anyway). The attribues are + A special format is supported for keyword, just put + gate name right after the /). + + + + The address macros can also be specified in an external file, like + the for details. However, you + should not use the syntax with the attributes in the + When used in the + + + Mail reader. + + + + , + + + + + + + + + + ADEPTXBBSPATH + + + + + + + + Specifyes the path where you keep your + + + The + + + Mail reader. + + + + chapter, + + + + + + + ADEPTXBBSUSERNO + + + + + + + + Specifyes the record number in the userfile and lastreads. + + + + If you are not the first user in the userfile, or are sharing the + messagebase with other + + + By default + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + + + + + + + AKA + + + + + <zone:net/node[.point][@domain] + [,pointnet]> + + + + Your network address, and + + + If a zone:pointnet/point.0 in the msg header, instead of + the zone:net/node.point. Most modern + mailers and mail processors now supports the + The optional + + + This keyword can be used globally and in a + Random System group. + + + + Mail reader and nodelist compiler. + + + + , + + + + + + + AKAMATCH + + + + + + + + This is an enhancement of the existing aka matching logic, which in + some circumstances fails to find the correct aka. + + + + If the destination address matches + Wildcards are not strictly necessary in the match zone:*/*.* or zone:, etc. + + + + When an address does not match any AKAMATCH definition, the + normal aka matching logic takes over. + + + + Mail reader. + + + + , + , + , + + + + +ADDRESS 2:236/77 ; this is primary address +AKA 22:33/44 ; this address valid for zones 21:, 22:, and 23 +AKAMATCH 21:*/*.* 22:33/44 +AKAMATCH 23: 22:33/44 + + + + + + AKAMATCHECHO + + + + + <YES/NO> + + + + This keyword controls whether + + + If set to + + + + + + Mail reader. + + + + Normally it is not desirable to enable aka matching in echomail, + because some echoes may be restricted to members of one particular + network, and an accidental wrong aka matching may attract unwanted + attention from the moderator or the compulsive flamers :-) + + + + , + , + , + + + + + + + AKAMATCHING + + + + + <YES/NO> + + + + This keyword controls whether Random System group it + is defined. When used, it overrides any global + , + , or + you may have. + + + + If set to + + + + + + This keyword is valid Random System group. + + + + Mail reader. + + + + , + , + , + + + + + + + AKAMATCHLOCAL + + + + + <YES/NO> + + + + This keyword controls whether + + + If set to + + + + + + It doesn't really make sense to do aka matching in local areas. The + keyword is just there for completeness. + + + + Mail reader. + + + + , + , + , + + + + + + + AKAMATCHNET + + + + + <YES/NO> + + + + This keyword controls whether + + + If set to + + + + + + Normally it is not desirable to enable aka matching in echomail, + because some echoes may be restricted to members of one particular + network, and an accidental wrong aka matching may attract unwanted + attention from the moderator or the compulsive flamers :-) + + + + Mail reader. + + + + , + , + , + + + + + + + APP + + + + + <programname> [text] + + + + This keyword provides a way for other programs to place configuration + data in + + + The + + + Mail reader. + + + + + + +APP OtherProg REGKEY xyaxajlsaduoiweqeq +APP OtherProg IRQ 5 + + + + + + AREA + + + + + <echoid> <> + <msgbase>[type] <location> [akano] + [attrs] + <-FILE> <type> [path/file] + [switches] + + + + This + + + + + + + + Mail area identifier. + + + + + + + Area description in () quotes. + + + + + + + F, O ( + + + + + + N (Netmail), E (Echomail), L (Local). + + + + + + + Directory path/file or board number. + + + + + + + AKA number (starting from 0) + + + + + + + R/O (Read-Only), and/or other attributes. + + +
+ + + + It is recommended to use the newer + keyword, which allows more + detailed mail area setup. + If more than one area defined to the same path or areatag then last + definition overrides previous ones. + For the keyword. + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + AREAAUTOID + + + + + <SHORT/VERBOSE/LONG> + + + + Defines how an automatically created echoid should look, when + finds an area without an + echoid. + + + + + + + VERBOSE + + + The echoids are given a name similar to the function of the + area, such as + + + + LONG + + + The echoids are numbered sequentially like this: + + + + + SHORT + + + The echoids are numbered sequentially like this: + +
+ + + + + + + Mail reader. + + + + + + + + + + AREAAUTONEXT + + + + + <YES/NO> + + + + This keyword controls where to put cursor in arealist on startup + and after exiting from an area you have been reading. + + + + If enabled, + + + + + + Mail reader. + + + + + + AREACATCHUPREAD + + + + + <YES/NO> + + + + This keyword controls whether + + + If enabled, + + + + + + This implies that + feature is + used, otherwise it has no function. + + + + Mail reader. + + + + + + + + + + AREACFMREPLYTO + + + + + + + + Sets the area where + + + The destination area for the confirmation messages. + + + + Mail reader. + + + + + , + , + , + , + , + , + + + + + + + AREACOPYADDID + + + + + <YES/NO> + + + + It is useful if you copy echomails to some local archive areas. In + this case +AREA:<OriginalEchoID> + kludge line to inform you from where you copied the mail to. This + keyword should be enabled in the destination area parameters when + used in the Random System group. + + + + If enabled, GoldED+ will insert the + + + + + + This keyword can be used globally and in a + Random System group. + Do not enable this unless you know what you doing! + + + + Mail reader. + + + + , + + + + + + + AREACOPYDIRECT + + + + + <YES/NO> + + + + This keyword controls whether copy/move functions should bypass area + selection screen. The destination area should be set with + keyword. + + + + If enabled, the destination area selection list is bypassed, thereby + making possible a + + + + + + This keyword can be used globally and in a + Random System group. + + + + Mail reader. + + + + , + , + , + , + + + + + + + AREACOPYTO + + + + + + + + Sets the default area for the copy/move functions. Typically you + could set it to a safe/permanent storage type of area. + + + + The default destination area for the copy/move functions. + + + + This keyword can be used globally and in a + Random System group. + The forward function uses the + area instead. + + + + Mail reader. + + + + , + , + , + , + , + + + + + + + AREADEF + + + + + <echoid> <> + <group> <type> <msgbase> <path/board> + <aka> <(attrs)> + [] + + + + This keyword defines a mail area in GoldED+. It looks a + lot like the keyword. Additional + parameters are the + + + + + + echoid + + + Mail area identifier. + + + + + + + + Area description in quotes. + + + + + group + + + Group ID uppercase letter (A-Z) or 0 if not in a group. Use + #groupnumber to specify group numbers in the 1-999 range. + + + + + type + + + + + + + msgbase + + + + + + + path/board + + + Area path, board number or base filename. + + + + + aka + + + Address for the area, or . for the main address. + + + + + (attrs) + + + Default attributes in brackets. + + + + + + + + Optional default origin in quotes. + + +
+ + + + If more than one area defined to the same path or areatag then last + definition overrides previous ones. + The possibility of using 'able area configuration + for several setups with different addresses, for example two people + sharing the same msgbase. + If you wish to read packed area (f.e. from CD archive) path/board field, set keyword. + This feature is not supported for + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + AREADESC + + + + + <echoid> <> + [group] [aka] [(attrs)] + [] + + + + Adds a description and optionally a group letter, AKA, + attributes and origin to an existing (previously defined) + area. This is useful if you use an areafile that does not contain + descriptions, groups, akas, attributes or origins. + + + + + + + echoid + + + Mail area identifier. + + + + + + + + Area description in quotes. + + + + + group + + + Optional groupid uppercase letter (A-Z) or 0 if not in a group. + Use #groupnumber to specify group numbers in the 1-999 + range or - to keep the existing groupid. + + + + + aka + + + Optional AKA address for the area, or . for + main AKA, or - to keep the existing + AKA. + + + + + (attrs) + + + Optional default attributes in brackets, - to keep the + existing attributes. Note that if they are specified, they are + added to the default net/echo/local attributes. + + + + + + + + Optional default origin in quotes. + + +
+ + + + You cannot skip any of the optional parts in the middle, even if you + only want to set, say, an origin. Use - to keep the existing + value for the parts you skip. + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + AREAEXCL + + + + + + + + With this keyword, you can define the echoids of areas which should + be ignored by , to exclude areas you are + not interested in reading. + + + + The + + + You can use the keyword to + reinclude areas which have been excluded with + This keyword must be placed before any of + , + , + or keywords. + + + + Mail reader. + + + + , + , + , + , + + + + +AREAEXCL * ; Excludes all areas. +AREAEXCL *INTER* ; Excludes all areas containing INTER anywhere in the + ; echoid. +AREAEXCL INT*.* ; Excludes all areas beginning with INT and + ; containing a dot anywhere in the echoid. + + + + + + AREAFILE + + + + + <type> [path/file] + [switches] + + + + + + + + + + + + Name of the program. + + + + + path/file + + + Filename or path to the area setup files. + + + + + + + Areafile specific switches. + + +
+ + + + For most programs, GoldED+ can automatically find the + path or filename using environment variables. By default, + . + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + AREAFILEGROUPS + + + + + <YES/NO> + + + + In some setups, you can + groups the areas using single letters (A-Z) or numbers (#1-999). + + + + If this keyword is enabled, GoldED+ will use the area + groupid instead of the area echoid when gathering area specific + information from the Random System + group. + + + + + + + This have only sence if you using Random + System groups. + + + + Mail reader. + + + + chapter + + + + + + AREAFORWARDDIRECT + + + + + <YES/NO> + + + + This keyword controls whether forward functions should bypass area + selection screen. The destination area should be set with + keyword. + + + + If enabled, the destination area selection list is bypassed, thereby + making possible a + + + + + + This keyword can be used globally and in a + Random System group. + + + + Mail reader. + + + + , + , + , + + + + + + + AREAFREQDIRECT + + + + + <YES/NO> + + + + This keyword controls whether filerequest functions should bypass + area selection screen. The destination area should be set with + keyword. + + + + If enabled, the destination area selection list is bypassed, thereby + making possible a + + + + + + This keyword can be used globally and in a + Random System group. + If you (like most) only have one mailer netmail area, you can enable + this feature globally for simpler file requests. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + , + + + + + + + AREAFREQTO + + + + + + + + Sets the default area for the filerequest functions. + + + + The default destination area for the filerequest functions. + + + + First netmail area. + + + + This keyword can be used globally and in a + Random System group. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + , + , + + + + + + + AREAINCL + + + + + + + + With this keyword, you can define the echoids of areas which should + be reincluded by keyword. + + + + The + + + This keyword must be placed before any of + , + , + or keywords. + + + + Mail reader. + + + + , + , + , + , + + + + +AREAINCL * ; Includes all areas. +AREAINCL *INTER* ; Includes all areas containing INTER anywhere in the + ; echoid. +AREAINCL INT*.* ; Includes all areas beginning with INT and + ; containing a dot anywhere in the echoid. + + + + + + AREAISEMAIL + + + + + + + + These keyword is designed to mark areas which are read from an + as + + + The + + + This keyword must be placed before any of + , + , + or keywords. + + + + Mail reader. + + + + , + , + , + , + + + + +AREAISEMAIL djgpp*, golded-plus* + + + + + + AREAISNEWS + + + + + + + + These keyword is designed to mark areas which are read from an + as + + + The + + + This keyword must be placed before any of + , + , + or keywords. + + + + Mail reader. + + + + , + , + , + , + + + + +AREAISNEWS alt.*, rec.*, sci.* + + + + + + AREAKEEPLAST + + + + + <YES/NO> + + + + This keyword controls whether + at exit and read it back when run next time. The contents of the file + is a list of lastread information for each area as it was at last + scan. + This feature is helpful when you know that there have not been tossed + new mail and don't want to wait for a full msgbase scan. Now you can + just hit <ESC> at the startup screen to abort the area scan and + + It also makes the + + + Setting this keyword to + + + + + + + + + Mail reader. + + + + , + , + + + + + + + AREALISTECHOMAX + + + + + + + + Allows you to specify a fixed or dynamically sized width of the + + + + If a negative value is specified, the width will be the that of the + widest echoid in the arealist plus the negative value. This might be + useful if some long-name echoes have uninteresting ends, such as + + + + + + + The arealist can dynamically resize the EchoID column is done against the + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + + + + + AREALISTFORMAT + + + + + + + + The arealist column layout is configurable. This keyword allows you + to change the layout to whatever you like. + + + + The string should be composed from the following letters: + + + + Letter + + + Meaning + + + Default width + + + + + + + Area number + + + 4 + + + + + + + Marked + + + 1 + + + + + + + Description + + + Dynamic + + + + + + + Number of messages + + + 6 + + + + + + + Personal mail mark ( + + 1 + + + + + + + Number of unread/new messages + + + 6 + + + + + + + Changed since last scan mark ( + + 1 + + + + + + + Echoid + + + + + + + + + + Groupid + + + Dynamic: 0, 1 or 3 + + +
+ You can also specify widths for each or particular fields if you + don't like the defaults by putting number right after the letter. + If you leave out a letter, that column will not be shown. + + + + + + + + Use only the defined letters. Use spaces to specify required space + between columns. Use only positive numbers for widths. Failure to + obey these rules may cause undocumented behaviour. + + + + Mail reader. + + + + , + , + , + , + , + , + , + + + + + + + + + + AREALISTGROUPID + + + + + <YES/NO> + + + + This feature provides a way to hide group ID on the arealist screen, + in a column to the right of the + + + If enabled, the arealist screen will display the groupid letters, if + any. + + + + + + + The same effect is achieved by skipping definition. + + + + Mail reader. + + + + , + , + + + + + + + AREALISTGROUPORDER + + + + + + + + This keyword allows to change the order in which areas will be sorted + when sorting by group ID is used. If some groups are not found in the + + + + The only parameter is string which specifies groups order. You may + use #groupnumber to specify group numbers in the 1-999 range. + + + + Empty string. + + + + Mail reader. + + + + , + , + + + + + + + AREALISTNOS + + + + + <YES/NO> + + + + This keyword allows to specify whether board number or sequential + area number will be displayed in the arealist. + + + + If enabled, + + + + + + Mail reader. + + + + , + , + , + + + + + + + AREALISTPAGEBAR + + + + + <YES/NO> + + + + Enables or disables a pagebar (scrollbar) in the arealist. + + + + If enabled, + + + + + + Mail reader. + + + + , + , + , + + + + + + + AREALISTSCAN + + + + + <> + [path]<filename> [-delete] + + + + This keyword allows you to define additional menu items for the + arealist scanning menus ( + + + The first two characters of the menu text are the + The filename specifies a plain text file, with the echoids (wildcards + allowed) of the areas you want to scan when the menu item is + selected. There can be several echoids on each line in the file. If + no path is given, the file is loaded from the + . + The + + + Some mail processors automatically delete their list after using it + for replylinking. You may want to do some creative stuff with + batchfiles to grab a copy. + + + + Mail reader. + + + + + + + +=== Cut, NEWSGRPS.LST === +ALT.*, COMP.*, MISC.*, NEWS.* +REC.*, SOC.*, SCI.*, TALK.* +=== Cut === + +=== Cut from an import batchfile === +gecho mgr toss pack -tossbad +if exist import.jam type import.jam >>import.all +if exist import.hmb type import.hmb >>import.all +if exist import.sdm type import.sdm >>import.all +mbutil link -clean +=== Cut === + + + + + + AREALISTSORT + + + + + + + + This keyword defines how the area list should be sorted. You can + override the default setting from the commandline with the + -s switch. + + + + The <sortspec> can be composed of the following types: + + + + + + Sort by aka. + + + + + + + Sort by board number. + + + + + + + Sort by description. + + + + + + + Sort by echoid. + + + + + + + Sorts all + + + + + + Sort by group (if any). + + + + + + + Sorts all marked areas first. + + + + + + + Sort by original order. + + + + + + + Sort by personal mail count. + + + + + + + Sort by personal mail presence. + + + + + + + Sort area separators first. + + + + + + + Sort by type (according to + ). + + + + + + + Sort by unread messages count (try it!). + + + + + + + Sort by unread messages presence (try it!). + + + + + + + Sort by msgbase type. + + + + + + + Sorts all areas with + + + + + + Sort by msgbase path. + + + + + + + Descending sort (largest first). + + + + + + + Ascending sort (smallest first) (default). + + +
+ + + + + + + In practice + The + The + The + keyword. + + + + Mail reader. + + + + chapter, + chapter, + , + , + , + , + , + , + , + , + , + , + , + + + + +AREALISTSORT -U+TE + + + + + + AREALISTTYPE + + + + + <NEW/LAST> + + + + Defines the contents of the 4th column (the one after the + + + + + + + + Displays the amount of new (unread) msgs (Actually number of + messages after lastread mark). + + + + + + + Displays the number of the last msg read. + + +
+ + + + + + + Mail reader. + + + + , + , + + + + + + + AREAPATH + + + + + + + + This keyword defines where the area setup files are located when + keyword is used. It is + also defines default path for the semaphores. + + + + The + + + Most types can find the path + using the environment variable(s) specific for the program(s). Such + environment variables (or a path specified with the + definition) always overrides + the . + + + + Mail reader. + + + + chapter, + , + + + + + + + AREAPMSCAN + + + + + + + + This keyword defines areas which will be automatically scanned for + personal mail when starting + + + The + + + It is recommended to have to scan all areas at startup. If you don't + want to wait for the scan to complete, you can abort the scan by + pressing <ESC> during startup. + + + + Mail reader. + + + + , + , + , + , + + + + +AREAPMSCAN * ; Scan all areas. +AREAPMSCAN *INTER* ; Scan all areas containing INTER anywhere in the + ; echoid +AREAPMSCAN INT*.* ; Scan all areas beginning with INT and + ; containing a dot anywhere in the echoid + + + + + + AREAPMSCANEXCL + + + + + + + + With this keyword you can prevent areas from being scanned with + on startup. + + + + The + + + This is good if you use + to scan all areas, but have some big areas which slows it down. + You can use the + keyword to reinclude areas which have been excluded with + + + + Mail reader. + + + + , + , + , + , + + + + + + + AREAPMSCANINCL + + + + + + + + This keyword allows to specify areas which are to be scanned with + even if they were + excluded with . + Useful for partial reversal of wildcard specs in the excludes. + + + + The + + + Mail reader. + + + + , + , + , + , + + + + + + + AREAREADONLY + + + + + <SOFT/HARD> + + + + This option is designed for those who setup a system for new computer + users who might be confused enough to enter a message in a read-only + area despite the warning menu. + + + + If this keyword is set to R/O area attribute. The + + + + + + Mail reader. + + + + chapter, + , + , + + + + + + + AREARENAME + + + + + + + + Renames one echoid to another. The feature is meant to be used in + connection with AREAFILE, where some types do not store + echoids with the areas (and GoldED+ then automatically + gives them unique echoids). Also you may rename areas with long + echoid to the shorter one. + + + + + + + Mail reader. + + + + , + , + + + + +AREARENAME NET001 NETMAIL +AREARENAME ECHO001 BAD_MSGS +AREARENAME LOCAL001 BBS.USERS + + + + + + AREAREPLYDIRECT + + + + + <YES/NO> + + + + This keyword controls whether + + Contents of the . + + + Area set with + keyword. + + + Current area. + + + + + + If enabled, + + + + + + This keyword can be used globally and in a + Random System group. + It is probably not a good idea to enable this keyword globally. + If you run a utility or have a mail processor which copies personal + mail to a separate area and puts an AREAREPLYDIRECT in it. + + + + Mail reader. + + + + , + , + , + + + + +GROUP ECHO_PERSONAL + AREAREPLYDIRECT YES +ENDGROUP + + + + + + AREAREPLYTO + + + + + + + + Sets the default area for the reply and forward functions. Typically + you could set it to a safe/permanent storage type of area. + + + + The default destination area for the reply and forward functions. + + + + First netmail area. + + + + This keyword can be used globally and in a + Random System group. + + + + Mail reader. + + + + , + , + , + , + + + + + + + AREASCAN + + + + + + + + This keyword defines areas which will be automatically scanned for + new mail when starting + + + The + + + It is recommended to have to scan all areas at startup. If you don't + want to wait for the scan to complete, you can abort the scan by + pressing <ESC> during startup. + + + + Mail reader. + + + + , + , + , + , + + + + +AREASCAN * ; Scan all areas. +AREASCAN *INTER* ; Scan all areas containing INTER anywhere in the + ; echoid +AREASCAN INT*.* ; Scan all areas beginning with INT and + ; containing a dot anywhere in the echoid + + + + + + AREASCANEXCL + + + + + + + + With this keyword you can prevent areas from being scanned with + on startup. + + + + The + + + This is good if you use + to scan all areas, but have some big areas which slows it down. + You can use the + keyword to reinclude areas which have been excluded with + + + + Mail reader. + + + + , + , + , + , + + + + + + + AREASCANINCL + + + + + + + + This keyword allows to specify areas which are to be scanned with + even if they were + excluded with . + Useful for partial reversal of wildcard specs in the excludes. + + + + The + + + Mail reader. + + + + , + , + + , + , + + + + + + AREASCANSORT + + + + + + + + When scanning areas, + + + The <sortspec> described in details in the + chapter. + + + + + + + Mail reader. + + + + + + + + + + AREASEP + + + + + <echoid> <> + <group> <type> <aka> + + + + You can define area separation lines between groups or areatypes. + + + + + + + + + Mail area identifier. + + + + + + + + Area description in quotes. + + + + + + + Group ID uppercase letter (A-Z) or 0 if not in a group. Use + #groupnumber to specify group numbers in the 1-999 range. + + + + + + + + + + + aka + + + Address for the area, or . for the main address. + + +
+ + + + The area separation lines are implemented like a special kind of + area, and are therefore sorted in the arealist just as if they were + actual areas. This is also the reason why you can place the cursor + bar on the separation lines. The fuzzy feature may be used to quickly + go to an area group, that's why cursor can be placed on separation + lines. + When configuring area separation lines, be careful to consider the + , so that the lines + are sorted into the positions you want. If you don't sort areas, you + must make sure that the and + lines. + You will note that the separation lines are not fully connected into + the left and right edges. This is both by design and for practical + reasons (easier to implement), not a bug. + Currently the descriptions are hardcoded to the natural location in + the description column. + + + + Mail reader. + + + + , + , + , + , + , + , + , + + + + + + + + + + + AREASTART + + + + + + + + Normally GoldED+ starts by displaying the arealist, to + let you select which area you want to read. If this keyword is + defined, the arealist is bypassed and AREASTART with the + -e commandline switch. + + + + The + + + Mail reader. + + + + chapter + + + + + + AREATYPEORDER + + + + + <type1> <type2> <type3> + <type4> <type5> + + + + This keyword allows you to change the ordering of the different + area types when sorted by + . + + + + The following types are allowed: + + + + + + Mail reader. + + + + , + + + + + + + AREAYOUWROTETO + + + + + + + + + + + The default destination area for the mails written by you. + + + + This keyword can be used globally and in a + Random System group. + The mail will not be copied if you use + READchangemsg function. + + + + Mail reader. + + + + , + , + , + + + + + + + ASKDELORIG + + + + + <YES/NO> + + + + This keyword allows to automatically delete mail in netmail and local + area after replying on it. + + + + If enabled, you will be asked if the message you just replied to + should be deleted. Otherwise it is left untouched. + + + + + + + This keyword is only functional in netmail and local areas. + + + + Mail reader. + + + + , + , + + + + + + + ATTACHPATH + + + + + + + + Defines the default path when selecting files for attachement. + + + + The default + + + Mail reader. + + + + chapter, + chapter, + , + + + + + + + ATTRIBSATTACH + + + + + + + + Defines the attributes that are added to the existing + attributes of a message when the file attach attribute is toggled on. + + + + Available chapter. + + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSCC + + + + + + + + Defines the default attributes of carbon copy messages. K/S attribute. + + + + Available chapter. + + + + + + + Mail reader. + + + + chapter, + Carbon Copy and Crossposting chapter, + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSCFM + + + + + + + + Defines the default attributes of the confirmation receipt message. + + + + Available chapter. + + + + + + + Suggested attribute is: + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSECHO + + + + + + + + Defines the default attributes of messages entered in echomail areas. + + + + Available chapter. + + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSEMAIL + + + + + + + + Defines the default attributes of messages entered in e-mail areas. + + + + Available chapter. + + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSFRQ + + + + + + + + Defines the attributes to use for messages generated with the file + request function. + + + + Available chapter. + + + + + + + Suggested attributes are: K/S + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSLOCAL + + + + + + + + Defines the default attributes of messages entered in local areas. + + + + Available chapter. + + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSNET + + + + + + + + Defines the default attributes of messages entered in netmail areas. + + + + Available chapter. + + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBSNEWS + + + + + + + + Defines the default attributes of messages entered in news groups. + + + + Available chapter. + + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + ATTRIBUTES + + + + + + + + Defines the default attributes for area members of the current + Random System group. + + + + Available chapter. + + + + This keyword is valid Random System group. + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , + , + , + , + , + , + , + , + + + + + + + BEEPCOMMENT + + + + + <YES/NO> + + + + This keyword enables or disables noise when the cursor in the + internal editor is moved across a word defined with the + keyword. + + + + If enabled, + + + + + + Mail reader. + + + + , + , + , + , + , + , , + + + + + + + BEEPFACTOR + + + + + + + + This keyword allows to change the noise speed made by the + , + , + , + , and + keywords. + + + + The + + + + + + This keyword is valid Random System group. + + + + Mail reader. + + + + , + , + , + , + , + + + + + + BEEPLOCALMSG + + + + + <YES/NO> + + + + This keyword enables or disables noise when + + + If enabled, + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , + , , + + + + + + + BEEPNOISES + + + + + <YES/NO> + + + + This is the + + + If enabled, + + + + + + Mail reader. + + + + chapter, + , + , + , + , + , , + + + + + + + BEEPYOURMAIL + + + + + <YES/NO/ALWAYS> + + + + This keyword enables or disables noise when 's. + + + + If set to + + + + + + Mail reader. + + + + , + , + , + , + , , + + + + + + + CARBONCOPYLIST + + + + + <KEEP/NAMES/VISIBLE/HIDDEN/REMOVE> + + + + This keyword specifies the format of the carbon copy list, as it will + look after processing. You can also change the format in the + + + + The list specification items have the following meaning: + + + + + + Keep the list as entered + + + + + + + Convert list to + + + + + + Convert list to + + + + + + + + + Remove the list completely + + +
+ + + + + + + Mail reader. + + + + Carbon Copy and Crossposting chapter, + + + + + + + COLOR + + + + + + + + Using this keyword you can define or redefine all the colors used + in + + + The detailed description for chapter. + + + + Mail reader. + + + + chapter, + + + + + + + COLORSET + + + + + <NORMAL/INTENSE/MONO> + + + + Three color setups are built-in, and can be selected with this + keyword. + + + + The + + + If color video adapter is detected then + + + Mail reader. + + + + chapter, + + + + + + + CONFIRMFILE + + + + + + + + 's with the + + + The + + + + + + Mail reader. + + + + chapter, + chapter, + , + , + , + + + + + + + CONFIRMRESPONSE + + + + + <YES/NO/ASK> + + + + An unreceived message to you with the CFM attribute set tells + + + + + + + + + + Mail reader. + + + + chapter, + , + , + , + , + + + + + + + COOKIEPATH + + + + + + + + Defines the default path for the + + + The default + + + + + + + Mail reader. + + + + chapter, + + + + + + + CROSSPOST + + + + + <YES/NO/ASK> + + + + This keyword configure prompt appearance when saving message which + contains crosspost tokens in the body. + + + + + + + + + + Mail reader. + + + + + + + + + + CROSSPOSTLIST + + + + + <RAW/VERBOSE/YES/NONE> + + + + This keyword specifies the format of the crosspost list, as it will + look after processing. You can also change the format in the + menu before processing + (if menu enabled). + + + + The list specification items have the following meaning: + + + + + + Keep the list as entered + + + + + + + Change the list to lines of "* Crossposted in ..." + + + + + + + Same as above, but expand echolist in line rather than in + column + + + + + + + Crosspost without a list in the msgs + + +
+ + + + + + + Mail reader. + + + + Carbon Copy and Crossposting chapter, + , + + + + + + + CTRLINFO + + + + + <YES/NO/TEARLINE,ORIGIN> + + + + Specifies if you want a tearline and/or origin in your messages. + + + + The tokens have the following meaning: + + + + + + Enable both tearline and origin + + + + + + + Disable all control info + + + + + + + Enable tearline, can be used with + + + + + + Enable origin, can be used with + +
+ + + + This keyword is valid Random System group. + This may be helpful for + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + + + +CTRLINFO YES ; Add both tearline and origin +CTRLINFO TEARLINE ORIGIN ; Same as above in other words +CTRLINFO TEARLINE ; Add only a tearline +CTRLINFO ORIGIN ; Add only an origin + + + + + + CTRLINFOECHO + + + + + <YES/NO/TEARLINE,ORIGIN> + + + + Specifies if you want a tearline and/or origin in your echomail + messages. + + + + The tokens have the following meaning: + + + + + + Enable both tearline and origin + + + + + + + Disable all control info + + + + + + + Enable tearline, can be used with + + + + + + Enable origin, can be used with + +
+ + + + + + + Changing the default may cause unpredictable behaviour with some + echomail processors so it is not recommended to change it. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + + + + + + CTRLINFOEMAIL + + + + + <YES/NO/TEARLINE,ORIGIN> + + + + Specifies if you want a tearline and/or origin in your + + + + The tokens have the following meaning: + + + + + + Enable both tearline and origin + + + + + + + Disable all control info + + + + + + + Enable tearline, can be used with + + + + + + Enable origin, can be used with + +
+ + + + + + + Changing the default is not recommended. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + + + + + + CTRLINFOLOCAL + + + + + <YES/NO/TEARLINE,ORIGIN> + + + + Specifies if you want tearline and origin in your messages in + local areas. + + + + The tokens have the following meaning: + + + + + + Enable both tearline and origin + + + + + + + Disable all control info + + + + + + + Enable tearline, can be used with + + + + + + Enable origin, can be used with + +
+ + + + + + + In local areas, the tearline and origin is normally never required + but can be used for cosmetic purposes. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + + + + + + CTRLINFONET + + + + + <YES/NO/TEARLINE,ORIGIN> + + + + Specifies if you want tearline and origin in your netmail messages. + + + + The tokens have the following meaning: + + + + + + Enable both tearline and origin + + + + + + + Disable all control info + + + + + + + Enable tearline, can be used with + + + + + + Enable origin, can be used with + +
+ + + + + + + In netmail areas, the tearline and origin is normally never required + but can be used for cosmetic purposes. Some robots reqire tearline + in the message. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + + + + + + CTRLINFONEWS + + + + + <YES/NO/TEARLINE,ORIGIN> + + + + Specifies if you want a tearline and/or origin in your + + + + The tokens have the following meaning: + + + + + + Enable both tearline and origin + + + + + + + Disable all control info + + + + + + + Enable tearline, can be used with + + + + + + Enable origin, can be used with + +
+ + + + + + + Changing the default is not recommended. + + + + Mail reader. + + + + , + , + , + , + , + , + , + , + + + + + + + DISPAREANO + + + + + <YES/NO/ALWAYS> + + + + This keyword specifies if + + + When set to + + + + + + Mail reader. + + + + + + + + + + DISPATTACHSIZE + + + + + <BYTES/KBYTES/NO> + + + + Controls how the size of attached files is displayed in the header. + + + + The following options are provided: the exact size in + + + + + + If the + + + Mail reader. + + + + , + + + + + + + DISPAUTONEXT + + + + + <YES/NO> + + + + Controls which message will be displayed when entering an area. + + + + If enabled, + + + + + + Mail reader. + + + + + + + + + + DISPHDRDATESET + + + + + + + + Specifies the position and length of the date field in the header + display. + + + + Specifies the + + + -20 20 + + + + Mail reader. + + + + , + + + + + + + DISPHDRNAMESET + + + + + + + + Specifies the position and length of the from/to name field in the + header display. + + + + Specifies the + + + 8 36 + + + + Mail reader. + + + + , + , + + + + + + + DISPHDRNODESET + + + + + + + + Specfies the position and length of the from/to node address field in + the header display. + + + + Specfies the + + + 44 16 + + + + The attributes display moves along with the DISPHDRNODESET + values. + + + + Mail reader. + + + + , + , + + + + + + + DISPLISTCURSOR + + + + + <TOP/NEARTOP/MIDDLE/NEARBOTTOM/BOTTOM> + + + + Selects the starting position of selection bar in the message list + and nodelist browsers. + + + + + + + + + At the top if possible + + + + + + + At top + 1/3 if possible + + + + + + + At middle of possible + + + + + + + At bottom - 1/3 + + + + + + + At bottom + + +
+ + + + + + + Mail reader. + + + + + + DISPLISTWRAP + + + + + <YES/NO> + + + + Enables or disables wrap-around when the selection bar in the main + list/browser windows reaches the top or bottom. + + + + If set to + + + + + + Mail reader. + + + + + + DISPLOCALHIGH + + + + + <YES/NO> + + + + This keyword controls whether + + + If enabled, + + + + + + Mail reader. + + + + chapter, + , + , + , + + + + + + + DISPMARGIN + + + + + + + + This keyword defines the right margin (display width) used for + message display. + + + + If the + + + 0 + + + + If the keyword is + enabled, the right margin is automatically decreased by one char. + + + + Mail reader. + + + + READdecreasemargin, + READincreasemargin, + , + , + , + , + + + + + + + DISPMSGSIZE + + + + + <BYTES/KBYTES/LINES/NO> + + + + When enabled, this keyword displays the msgbody size in the lower + left side of the header. The size displayed is for the message body + text only, the header and NUL-terminator (and anything that may lurk + beyond it) is excluded from the calculation. + + + + The following options are provided: the exact size in + + + + + + This feature only works when is enabled). + If the + + + Mail reader. + + + + , + + + + + + + DISPPAGEBAR + + + + + <YES/NO> + + + + If enabled, a + + + If enabled, + + + + + + Pagebar is only displayed if a message is longer than a + screenful. + The pagebar automatically decreases the + by one char. + + + + Mail reader. + + + + , + , + , + + + + + + + DISPREALMSGNO + + + + + <YES/NO> + + + + This keyword controls how the + + + If set to + + + + + + Normally the relative numbers are best, because they reflect the + actual number of messages in the system. + + + + Mail reader. + + + + READtogglerealmsgno + + + + + + DISPSOFTCR + + + + + <YES/NO> + + + + This option controls how + + + If enabled, + + + + + + Enabling this feature is feature + working. + The + The similar functionality may be obtained by defining translation + table with + Note that by enabling this feature, you + + + Mail reader. + + + + , + + + + + + + DISPSTATUSLINE + + + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + DISPTABSIZE + + + + + + + + This keyword defines the tab size (number of spaces) used when + displaying the tab (EDITtab and + EDITtabreverse, and when importing external data + in the internal editor. + + + + The + + + 8 + + + + If you use an external editor, you should switch it to create spaces + instead of tabs, because tabs are technically not allowed in + + + + Mail reader. + + + + EDITimportquotebuf, + EDITimporttext, + EDITpaste, + EDITtab, + EDITtabreverse + + + + + + DOSPROMPT + + + + + <YES/NO> + + + + Controls whether + + + If set to keyword in + the language configuration file to the system shell. + + + + + + + This feature is known to be broken on some platforms. + + + + Mail reader. + + + + AREAdosshell, + EDITdosshell, + FILEdosshell, + LISTdosshell, + NODEdosshell, + READdosshell, + , + + + + + + + EDITAUTOATTACH + + + + + <YES/NO> + + + + If you use drivespec ( + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITAUTOSAVE + + + + + + + + This keyword provides the way for keeping automatic backup of the + message you are writing. The saved file can be restored with the + + keyword. + If disaster strikes (crash, lockup, power blackout, etc.) while + you are writing a message in the internal editor, this feature + lets you continue from the last autosaved message, which will + popup automatically when you enter the internal editor again. + + + + If a non-zero value is given, the internal editor will automatically + execute the + + + 30 + + + + This feature only works 100% if + is set to is set to + + + Mail reader. + + + + , + + + + + + + EDITCHANGEDATE + + + + + <ALWAYS/YES/NO> + + + + This keyword controls whether + + + If set to + + + + + + Mail reader. + + + + READchangemsg + + + + + + EDITCHARPARA + + + + + + + + This keyword defines the character + + + The + + + + + + This keyword is primarily for debugging, the suggested replacement + is a paragraph sign ( + + + Mail reader. + + + + + + + + + + EDITCHARSPACE + + + + + + + + This keyword defines the character + + + The + + + + + + This keyword is primarily for debugging, the suggested replacement + is a small dot (CP437 250). + + + + Mail reader. + + + + + + + + + + EDITCOMMENT + + + + + <> + <> + + + + This feature allows you to define words which causes + + + The + + + Mail reader. + + + + , + , + + + + + + + + + + EDITCOMPLETION + + + + + <> + <> + + + + This keyword allows you to define abbreviations which will be + automatically expanded to full words or sentences when typed in + the internal editor. + + + + The + + + The abbreviation is case-sensitive. If is defined + as an abbreviation, completion will is typed. + + + + Mail reader. + + + + , + + + + + + + + + + EDITCRLFTERM + + + + + <YES/NO> + + + + This keyword controls the format to be used for the paragraph line + termination. + + + + If set to CR/LF combination. If set to + + + + + + This option was created to fix a problem with an older version of the + CR/LF termination of kludge lines. + + + + Mail reader. + + + + + + EDITFIELDCLEAR + + + + + <YES/NO> + + + + This keyword controls the behaviour of the input-fields, if a + non-edit key is the first key pressed. + + + + If set to + + + + + + Mail reader. + + + + + + + + + + + EDITHARDLINE <string> + +

+ ("<<") +

+

+ The string is needed if you use an external editor that terminates + all lines with a CR or CR/LF. The hardline string acts as a text + paragraph terminator, and the normal CR's are ignored. +

+

+ The concept of "hardlines" is explained in the Hardline Feature + chapter. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITHARDLINES <yes/no> + +

+ (yes) +

+

+ This keyword enables the "hardline" feature. If disabled, the + EDITHARDLINE string is never written to the editor message file, + and the editor message file is read back exactly as entered, + including terminating CR's on all lines. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITHARDTERM <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will hard-terminate all lines in your messages + at the editor margin. It is recommended to enable this keyword for + Internet e-mail and newsgroups, because some user-unfriendly + Internet software does not wrap long lines properly. But DON'T + enable it in normal FidoNet echomail. +

+

+ This keyword can be used globally and in Random System groups. + , + +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITHDRNAMESET <pos> <len> + +

+ (8 36) +

+

+ Specfies the position and length of the from/to name field in the + header edit display. If a negative value is specified, that value + is added to the current display width. +

+ + + + EDITHDRNODESET <pos> <len> + +

+ (44 36) +

+

+ Specfies the position and length of the from/to node address field + in the header edit display. If a negative value is specified, that + value is added to the current display width. +

+ + + + EDITHEADERATTRS <yes/no> + +

+ (yes) +

+

+ This keyword allows you to turn off the large attributes window + that is shown during header edit. Even if the window is turned + off, the Alt-keys are still active for toggling attributes. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITHEADERFIRST <new,changes,replies,forwards,yes/no> + +

+ (yes) +

+

+ This keyword controls the circumstances that will present you with + the header editor first of all. +

+

+ New When entering a new message. + Changes When changing a message + Replies When making a reply. + Forwards When forwarding a message. + Yes Always (all of the above). + No Never. +

+

+ The New, Changes, Replies and Forwards values can be combined. YES + is equivalent to enabling all four of these. +

+

+ For example, we want to edit the header only when entering a new + message or when changing a message: +

+

+ EDITHEADERFIRST New, Changes +

+

+ If the circumstances match the setup of this keyword, the header + edit will be bypassed and you will start directly in the EDITMENU + (if enabled) or in the internal or external editor. A new menu + item has been added in the EDITSAVEMENU, "Edit Header", which + allows you to edit the header after you have written your message, + but before it is finally saved. +

+

+ If you set EDITHEADERFIRST to NO, you must either have the + EDITSAVEMENU enabled, or use the internal editor, because + otherwise it is not possible to edit the header at all. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITINTERNAL <yes/no> + +

+ (yes) +

+

+ Specifies if the internal editor should be the default, even if an + external editor is defined. You can always change the setting in + the editor menu (if EDITMENU is enabled) before you start writing + your message. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITMENU <yes/no> + +

+ (yes) +

+

+ This keyword enables or disables the "Edit menu" that pops up + right after you have edited the message header. If you disable the + menu, you will go to the internal or external editor immediately + and save a keystroke, but you will of course lose the features + available from the menu, such as selection of template etc. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITMIXCASE <yes/no> + +

+ (no) +

+

+ If this keyword is enabled, GoldED+ will automatically format the + name with uppercase the first letter in words and lowercase the + rest, when entering names in the header. +

+

+ Examples: +

+

+ "odinn sorensen" or "ODINN SORENSEN" +

+

+ These would be re-cased to "Odinn Sorensen". +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITOR <commandline> [@file] [@line] + +

+ With GoldED+ it is possible to use your favorite text editor or + even word processor to write messages. With this keyword you + specify the commandline for the editor. +

+

+ If you use a word processor, be sure to make it export clean ASCII + text files without control codes. +

+

+ <commandline> Program commandline. + @file Token which is replaced by the editor message + filename. + @line Token which is replaced by the @Position + template line number. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITORFILE <file> + +

+ (GOLDED.MSG) +

+

+ Defines the name of the temporary editor message file. This file + is written by GoldED+ when swapping to the external editor, or when + using the EDITsavefile command in the internal editor. +

+

+ The file is written in the GOLDPATH if there is no explicit path. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITQUOTEMARGIN <margin> + +

+ (75) +

+

+ Sets the right margin for editing quoted lines in the internal + editor. This should be set to the same or wider than the + QUOTEMARGIN. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITREPLYRE <yes/no/numeric> + +

+ (no) +

+

+ If enabled, GoldED+ inserts the "Re:" string in front of the + subject when you reply to a message. If not enabled, GoldED+ will + strip any leading "Re:" when you reply to a msg. +

+

+ The "Re:" string in subjects is an obsolete practice, and today it + only slows down modern replylinking software. Do yourself and + others a favor and let GoldED+ strip the Re: in your replies. +

+

+ The "numeric" option makes GoldED+ use numeric Re:'s, of the form + "Re^n:". +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITSAVEMENU <yes/no> + +

+ (yes) +

+

+ This keyword enables or disables the "Save menu" that pops up + after you have edited your message in the internal or external + editor. If you disable the menu, your message will be saved (or + discarded if not edited) immediately and save you a keystroke, but + you will also lose the features available from the menu. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITSAVEUTIL <utilno> <"L menu text"> + +

+ Defines the external utilities that will be added to the + EDITSAVEMENU (if enabled). The menu text is inserted in the menu. + The first two characters of the menu text are the "hotkey" letter + that will be highlighted in the menu text, plus a space. Example: +

+

+ EDITSAVEUTIL 1 "S PGP Sign the msg" + EDITSAVEUTIL 2 "l PGP Clear-Sign the msg" + EDITSAVEUTIL 3 "E PGP Encrypt the msg" + EDITSAVEUTIL 4 "p PGP Encrypt & Sign the msg" +

+

+ If you have changed the default language in this menu (in + GOLDLANG.CFG), then make sure the highlight letters don't clash. +

+

+ With EDITSAVEUTIL definitions and EDITSAVEMENU enabled, you can + directly call an external utility to do things like encoding or + encrypting msgs before saving them. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITSOFTCRXLAT <char> + +

+ If a translation char is defined, GoldED+ will translate the + soft-cr character (ASCII 141, HEX 8D) while saving message to base. + The following example translates the soft-cr to an 'H' (for use in Russia): +

+

+ EDITSOFTCRXLAT H +

+

+ You also have to enable the DISPSOFTCR keyword. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITSPELLCHECK <commandline> [@file] + +

+ While in the internal editor, you can use the EDITspellcheck + command to save your message to a file and shell to external + spellchecking software. When the check is completed, the corrected + file is read back and you can continue editing your message. The + EDITspellcheck command internally uses the EDITsavefile and + EDITloadfile commands. +

+

+ <commandline> Spellchecker program commandline. + [@file] Token which is replaced by the message filename + (defined by the EDITORFILE keyword). +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EDITUNDELETE <lines> + +

+ (50) +

+

+ This keyword defines the number of lines to keep in the undelete + buffer between messages. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EMPTYTEARLINE <yes/no> + +

+ (no) +

+

+ With this keyword enabled, GoldED+ will always strip the tearline + down to just the three dashes, "---", and instead inserts the PID + (Product IDentification) kludge line, which contains the same + information, but in a safer form in a safer place. The PID kludge + is proposed in FidoNet document FSC-0046. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + ENCODEEMAILHEADERS <yes/no> + +

+ (yes) +

+

+ By default headers in e-mails MIME-encoded according to RFC. In + Russia it is general practice not to encode headers, so you + probably want to say No here if you're in Russia ;-) This keyword + supported only in -asa versions. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + ENDGROUP + +

+ Ends a Random System GROUP definition. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EVENT <eventtype> <eventcommand [parameters]> + +

+ This keyword allows you to specify which soundfile to play when a + specfic event occurs. The following <eventtype>'s are defined: +

+

+ EVENTTYPE TRIGGER: +

+

+ Arealist When the arealist shows. + AskYesNo Any Yes/No type prompt. + Attention Warnings or information popup messages. + DosShell When entering a DOS or OS/2 shell. + EditComment When an editcomment is found. + EndOfMsgs When there are no more msgs in the area. + ErrorFatal Fatal error exit. + Exit Exit from GoldED+. + JobDone Successful completion of a job. + JobFailed Unsuccessful completion of a job. + MsgDeleting When deleting a msg. + MsgFromYou When a msg from you is found. + MsgIsLocal When a msg marked Local is found. + MsgIsTwit When a msg from a Twit is found. + MsgToYou When a msg to you is found. + SearchFailed Search operation failed. + SearchSuccess Search operation was successful. + Startup When the GoldED+ startup screen shows. +

+

+ There is currently only one <eventcommand> defined: +

+

+ PLAY <filename.ext/beepnoise>. +

+

+ The parameter to PLAY can be either a sound file or one of the + following standard beepnoises: +

+

+ TheEnd A high and a low note. + GotIt Two sets of low-high notes. + TooBad A falling note. + ToYou A rising and falling note. + SayBiBi A single beep. + SOS Morse S O S (...---...). +

+

+ If a sound file is specified, the sound driver must support the + format. +

+

+ The DOS and 386 versions need a Goldware Sound API compatible TSR + or program loader which installs an interrupt service function on + the multiplex interrupt 2Dh. See the chapter about the Goldware + Sound API for more details. The GCTVSAPI program loader (released + separately) currently only supports the CT-VOICE.DRV driver for + .VOC files. +

+

+ The OS/2 version relies on MMPM/2 (using the mciSendString API + call) to play the sound files. On my system with a Sound Blaster + Pro, MMPM/2 plays both .WAV and (to my surprise) .VOC files. It + even plays .MID files :-) +

+

+ The Win32 version uses the Win32 API to play the sound files. It + should be able to play any multimedia file that Windows knows how + to handle. +

+

+ Example usages: +

+

+ EVENT MsgToYou PLAY HIMAN.VOC + EVENT MsgIsTwit PLAY SHOTGUN.VOC +

+

+ You have to select the sounds carefully and probably with a lot of + experimentation, unless you want to turn your mailreader into a + honking, wailing and farting monster and drive your poor family or + yourself nuts with a cacophony of noises... +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EXCLUDENODES <addressmask> + +

+ You can define up to 50 different addressmasks to be excluded from + the compiled nodelists. Use this if you are short of space, or the + nodelist compile takes very long on your system. This keyword is + used by GoldNODE. +

+

+ Excluded nodes can be re-included with the INCLUDENODES keyword. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EXTERNOPTIONS <-options> + +

+ Defines the default options for the EXTERNUTIL's. Valid options: +

+

+ -Cls * Clear screen. + -Cursor * Cursor in shell. + -KeepCtrl * Keep control lines in the message. + -Pause Pause for keypress before returning to GoldED+. + -PauseOnError * Pause only if utility errorlevel is nonzero. + -Reload * Reload the message file (@file). + -Wipe Wipe editorfile and temporary file after use. +

+

+ Plus the reverse options with a "No" prefix, for example -NoCls. + The default options are marked with an asterisk (*). +

+

+ Use -NoKeepCtrl when you want to clearsign a message. This will + strip the control lines (kludges, tearline and origin) from the + message before passing it to the external utility. The tearline + and origin is appended to the message when reloading it. The + default is to keep control lines in the message. +

+

+ Use -Wipe when you want the temporary unencrypted message files to + be wiped and removed from the disk after they have been read into + memory. GoldED+ wipes a file by writing a block of 512 random bytes + over the entire length of the file, then truncating it to zero + bytes and finally deleting it. The default is not to wipe files. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EXTERNUTIL <utilno> [-options] <commandline> + +

+ This new feature can be used to "filter" msgs, for example calling + PGP or other encryption utilities. +

+

+ The <utilno> must be in the range 1 to 24 for utilities that will + be called with key definitions (see below). Higher numbers can be + used for utilities that are called from the EDITSAVEMENU (if + enabled). See the EDITSAVEUTIL keyword for details. +

+

+ The default options are those specified with the EXTERNOPTIONS + keyword. With [-options], you can change the those options locally + for specific utils. See the EXTERNOPTIONS keyword for a list of + valid options. +

+

+ The <commandline> specfies the DOS or OS/2 commandline you want to + execute. This works in the same way as for the external editor and + spellchecker. See the manual for details about this, especially if + you want to execute batchfiles. In the <commandline> you can use + @tokens to transfer information from the msg to the commandline. + The @tokens are the same as for templates, and in addition you can + use two other @tokens: +

+

+ @path The GOLDPATH, including a trailing backslash. + @file The full filename of the message file (GOLDED.MSG) + that will be written to disk before the utility is + called. + @tmpfile The full filename of a temporary message file + (GEDTMPxx.xxx) that will be written to disk before the + utility is called. +

+

+ Examples: +

+

+ EXTERNUTIL 1 c:\4dos\4dos.com /c c:\crypt\encrypt.bat @file + EXTERNUTIL 2 c:\4dos\4dos.com /c c:\crypt\decrypt.bat @file +

+

+ To call a defined external utility, you must assign a key to it. + There are 24 new keyboard commands you can use in GOLDKEYS.CFG for + this purpose: +

+

+ ExternUtilNN +

+

+ Where NN is in the range 01 to 24 _with_ leading zero. Examples: +

+

+ F11 ExternUtil01 + F12 ExternUtil02 +

+

+ Then if you press F11, you would call external utility number 1 + and so on. The ExternUtilNN keywords ONLY work in reader mode, not + in the internal editor or any other place. +

+

+ HOW IT WORKS: +

+

+ 1. Just before the external utility is called, GoldED+ writes the + current message text to the GOLDED.MSG file in the GOLDPATH. + The file is written as a textfile with each line CR-LF + terminated. The content is exactly as you see it on the + screen, which means that kludges are only included if you have + enabled kludge viewing. If the -NoKeepCtrl option is used, + kludges, tearline and origin are stripped before the file is + written. If the token @tmpfile is used, a temporary file named + GEDTMPxx.xxx (where xx.xxx is something unique) is created + with exactly the same content as @file. +

+

+ 2. GoldED+ clears the screen and then calls the utility. +

+

+ 3. The utility can now load and process the @file and/or + @tmpfile, or do anything else you want. It doesn't have to + have anything to do with the current msg. You could call a + spreadsheet, a game, whatever. But I think this feature will + mainly be used for utilities that process the @file. If the + utility processes the @file, it could write the changes back + to the @file. +

+

+ 4. After returning from the utility, GoldED+ reloads the @file and + displays it just as if it was the current message. For + example, if your utility was a decrypter and the msg was + encrypted, you would now see the decrypted msg. Neat eh? :-) +

+

+ 5. If you want to make the reloaded text permanent (save it in + the msg), you can use the Change Msg function and immediately + choose "Save Message" from the Editing menu (if enabled with + EDITMENU Yes). This is in fact the method you could use if you + wanted to EN-crypt a msg (however, it is easier to use the + method which involves the EDITSAVEUTIL keyword). +

+

+ The QUOTESPACING feature can interfere with encoded msgs that + include the '>' character at the beginning of lines (often seen in + uuencoded msgs), by automatically inserting blank lines before and + after the lines with '>'. I have therefore changed the + quotespacing default from YES to NO. Be sure to check if you have + a different setting if you are using an older edition of the + advanced configuration files. +

+

+ If the string "-----BEGIN PGP MESSAGE-----" is found as the first + 27 characters in a reloaded message, GoldED+ will automatically add + the FSC-0073 kludge "^aENC: PGP" to indicate that the message is + encrypted. This kludge may be used by some software to set up + alternative routing for encrypted mail which would otherwise be + bounced if sent through normal channels. +

+

+ See the "Using PGP as an External Utility" chapter for batchfile + examples and instructions on how to use this new feature with PGP. +

+

+ !!! IMPORTANT !!! From FidoNet Policy 4.07 (chapter 2.1.4): +

+

+ "[..] Therefore, encrypted and/or commercial traffic that is + routed without the express permission of all the links in the + delivery system constitutes annoying behavior." +

+

+ So be careful with this feature! +

+

+ TIP: You can use the EXTERNUTIL feature to setup keys to view or + print an attached fax. Use something like this in GOLDED.CFG: +

+

+ EXTERNUTIL 11 c:\zfax\zfax.com pf @subject ; print fax + EXTERNUTIL 12 c:\zfax\zfax.com vf @subject ; view fax +

+

+ And this in GOLDKEYS.CFG: +

+

+ @F11 ExternUtil11 ; Press Alt-F11 to print the fax + @F12 ExternUtil12 ; Press Alt-F12 to view the fax +

+

+ Or choose your own key assignments and fax view/print utils. +

+

+ Note that this assumes that the fax file is listed in the subject + line like an attached file. +

+

+ NOTE: If you're running GoldED+/386 and try to use a Win32 program + as an EXTERNUTIL, you might get the error "This program cannot be + run in DOS mode". You can work around this by calling the Win32 + program via the shell. For example if this call fails: +

+

+ EXTERNUTIL 1 c:\utl\mywin32.exe @file +

+

+ Replace it with: +

+

+ EXTERNUTIL 1 command.com /c c:\utl\mywin32.exe @file +

+

+ Then it should work. If not, try using full path to command.com. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EZYCOMMSGBASE <path> + +

+ Defines the base path for the Ezycom msgbase. If not set, AREAFILE + Ezycom will set it. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EZYCOMUSERBASE <path> + +

+ Defines the base path for the Ezycom userbase. If not set, + AREAFILE Ezycom will set it. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + EZYCOMUSERNO <userno> + +

+ (0) +

+

+ Defines the lastread set used in the Ezycom message base. +

+ + + + <YES/NO> + + + + This keyword controls statusline appearance in the + + + If set to + + + + + + Mail reader. + + + + , + + + + + + + + + + + + + + + + + FIDOHWMARKS <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will use the echomail "highwater mark" (1.MSG) + to determine if a message is "sent" or "unsent" in *.MSG areas. +

+

+ NOTE: Some older echomail processors do not update the highwater + mark in a way that GoldED+ can recognize. If all messages appear to + marked "Uns", even after the mail has been scanned out, try + turning off this keyword. +

+ + + + FIDOLASTREAD <file> + +

+ (LASTREAD) +

+

+ Defines the filename of the *.MSG lastread files. DO NOT specify a + path. +

+ + + + FIDOMSGTYPE <Opus/FTS1> + +

+ (Opus) +

+

+ This keyword defines the default format of Fido *.MSG files. It is + only used by some AREAFILE's when reading external area + configuration files, where the preferred format is unknown. +

+

+ The FTS1 (FTS-0001.012 and later) format uses zone/point fields, + where the Opus format uses date/time stamps. When set to Opus + format, GoldED+ interprets the date/time stamps as DOS-style + bitmapped date/time. +

+ + + + FIDONULLFIX <yes/no> + +

+ (no) +

+

+ If set to YES, GoldED+ will replace NUL chars with LF chars in the + msg body when reading a Fido *.MSG file. This is slower of course, + but not noticably on fast machines. +

+

+ This option was created to enable GoldED+ users to read msgs that + were created/handled by brain-dead programs (I don't have names, + sorry) which are not obeying our primary technical standard: + FTS-0001. FTS-1 states that a NUL terminates the msg body. But + sometimes msgs are encountered which have a NUL as the first char + in the msg body or perhaps in other places, thereby causing GoldED+ + to show a blank or cut-off msg. In some Pascal-based readers, such + as FM, these msgs can be read anyway, because in Pascal a NUL does + not terminate a string like in C/C++. +

+

+ NOTE: Even if the new FIDONULLFIX keyword is disabled, GoldED+ will + still fix a NUL if it is the _first_ character in the msg body. + This probably fixes most of these buggy msgs without the overhead + of checking the entire msg. +

+ + + + FIDOUSERLIST <file> + +

+ Path and filename of a FIDOUSER.LST file. +

+

+ This file is expected to be sorted in ascending alphabetical order + using plain ASCII case-insensitive sort. Each line in the list is + expected to be 60 characters plus a CR and a LF, or in other words + records of 62 bytes each. If the list is produced by a nodelist + compiler, everything should be okay, but be careful if you have + edited the file manually. Note that a FIDOUSER.LST file only + supports a name lookup (to get the address). +

+ + + + FIDOUSERNO <userno> + +

+ (0) +

+

+ This is an index into the FIDOLASTREAD file. Each user occupies 2 + bytes in the lastread file. +

+ + + + FILEALIAS <alias> <filename> + +

+ Used to define short alias names for filenames. If you regularly + write msgs to different files in different paths, this feature is + very useful, and reduces the risk of typing wrong. +

+

+ Example: +

+

+ FILEALIAS DKB R:\DKBBS\DKBBS +

+

+ With this file alias, you can simply write "DKB" at the filename + prompt, and the long filename will be used. +

+ + + + FILELISTPAGEBAR <yes/no> + +

+ (yes) +

+

+ Enables or disables a pagebar (scrollbar) in the file attach list + function. +

+ + + + FORCETEMPLATE <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will popup a template selection menu when you + start writing a new msg or reply. If you have both TEMPLATE(s) and + FORCETEMPLATE in a Random System group, you can tell GoldED+ to use + the random template(s) by hitting ESC instead of selecting from + the menu. +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + FORMFEEDSEPARATOR <yes/no> + +

+ (no) +

+

+ Used when saving messages to file. If enabled, it inserts a Form + Feed (12d) character after each message. +

+ + + + FRQEXT <.ext> + +

+ With this keyword you can add extra known filename extensions for + the filerequest function. The following extensions are already + known by default, and need not be defined (duplicate definitions + are ignored): +

+

+ .ARC .ARJ .DOC .EXE .GIF .LHA .LZH .JPG .PAK .PNG .RAR .RUN .SDA + .SDN .TXT .ZIP .ZOO +

+

+ Each extension _must_ have the leading dot. +

+

+ Example: FRQEXT .XYZ +

+ + + + FRQNODEMAP <to-node> <from-node> + +

+ This keyword is used for the file request feature (Ctrl-F). It + allows you to define mappings from a nodenumber used in a file + announcement to another nodenumber. This is useful in the cases + where a multi-line system announces files using their primary + nodenumber, which may be a regular V34 modem number, but they also + have an ISDN number, which you would prefer to use instead. + Examples: +

+

+ // change-to: from: + FRQNODEMAP 2:236/99 2:236/100 + FRQNODEMAP 2:236/1043 2:236/43 +

+

+ So, if I saw a file announcement from 2:236/100, and requested + some files, the request would automatically be addressed to + 2:236/99. +

+ + + + FRQOPTIONS <options> + +

+ (FromTop) +

+

+ Defines options for the file request function: +

+

+ Sort Sort the list of files alphabetically. + FromTop Scan the message from the top of the message. + NotFromTop Scan the message from the top of the screen. + NoFiles Don't list the file FILES if no files were found. + NoWazooMsg Don't save the request message. + Fast Bypass the header edit and save the msg immediately. +

+

+ By default, the "FromTop" option is enabled. If you often request + files from very long announcement messages, you might find it very + useful to set the "NotFromTop" option. +

+

+ The "NoFiles" option was added because if no filenames are found + in a message, the file request function defaults to listing the + magic name FILES instead of complaining that no files were found. +

+

+ If the FRQWAZOO keyword is enabled, the default behaviour is to + save the request message with the FRQ attribute stripped. Use the + "NoWazooMsg" option if you don't want the request message. +

+

+ Use the "Fast" option if you find that you almost never change the + destination of the file request message anyway. If you enable this + option, remember that you can always go over to the netmail area + and change the file request message before it is sent. +

+

+ The UseFlowFile option enables a feature which was default in + 2.50, but which I have been informed is problematic for modern + mailers in some setups. The default is now to ONLY create/update + the .REQ file and NOT also touch/create a .?LO flowfile. +

+ + + + FRQWAZOO <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will create WaZOO .REQ files instead of file + request messages. You must define an OUTBOUNDPATH if you enable + this feature. +

+ + + + GEDHANDSHAKE <yes/no> + +

+ (yes) +

+

+ If this switch set to yes GoldEd displays handshake char in + statusline. If you annoyed with this feature you could hide this + character by setting this option to no. +

+ + + + GERMANKEYBOARD <yes/no> + +

+ (autodetect) +

+

+ This option is meanful for w32 version only. Due to right Alt key + required to enter some native characters in german version of + Windows it could be defined to yes for this. +

+ + + + GOLDBASEPATH <path> + +

+ Specifies the directory where GoldED+ can find the Goldbase msgbase + files. +

+ + + + GOLDBASESYSPATH <path> + +

+ Specifies the directory where GoldED+ can find the NETMAIL.DAT and + ECHOMAIL.DAT files of the Goldbase msgbase. If not specified, the + GOLDBASEPATH is used. +

+ + + + GOLDBASEUSERNO <userno> + +

+ (0) +

+

+ Specifies the lastread set used in the Goldbase message base. +

+ + + + GOLDPATH <path> + +

+ This is the path where GoldED+ finds all it's control files. It is + not necessary to define this, unless you have special needs. The + GOLDPATH defaults to directory where the GOLDED.CFG file was + found. +

+ + + + GROUP <groupname> + +

+ Starts a Random System group. See the Random System chapter for + details. +

+ + + + HIGHLIGHTUNREAD <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ updates (increases) the "timesread" field in + each message that you read. If set to NO, it doesn't touch the + message. The YES setting causes a slight performance decrease, + because the header of each message has to be read, the timesread + field updated and the header written back to disk. The update + happens immediately after the message is displayed, so you may not + notice it at all. A message is only updated if the timesread field + contains the value 0 (zero). +

+

+ This keyword only works in the following msgbase formats: Fido + (*.MSG), Hudson, Goldbase, JAM, Squish, Ezycom and AdeptXBBS. In + Squish and Ezycom, there is no timesread field, but I have annexed + a reserved message attribute (in Squish, 0x00080000, now called + MSGSEEN; in Ezycom, extattr 0x80) for the purpose of marking a + message as read at least once. The other formats (PCBoard, + WildCat) have no timesread field, but they have reserved fields or + attributes which *could* be used. +

+ + + + HUDSONPATH <path> + +

+ Specifies the directory where GoldED+ can find the Hudson msgbase + files. +

+ + + + HUDSONSIZEWARN <size in bytes> + +

+ (16000000) +

+

+ When the Hudson MSGTXT.BBS file exceeds this size, GoldED+ starts + to warn that the msgbase is getting dangerously close to the + structural limit (which is 16MB for the MSGTXT.BBS file). With + this keyword you can raise or lower the warning size in case you + think the default is too low or too high. +

+ + + + HUDSONSYSPATH <path> + +

+ Specifies the directory where GoldED+ can find the NETMAIL.BBS and + ECHOMAIL.BBS files of the Hudson msgbase. If not specified, the + HUDSONPATH is used. +

+ + + + HUDSONUSERNO <userno> + +

+ (0) +

+

+ Specifies the lastread set used in the Hudson message base. +

+ + + + IGNORECHARSET <yes/no> + +

+ (no) +

+

+ If set to yes then GoldEd ignores CHRS kludges in messages thus + you will be able to switch codepage in messages with inappropriate + charset. +

+ + + + IMPORTBEGIN <text> + +

+ ("=== Cut ===") +

+

+ This keyword, together with IMPORTEND, defines some text to add in + the beginning and end of an imported text file in the internal + editor. If only IMPORTBEGIN is defined, the text is also used for + the IMPORTEND. The <text> may be enclosed in quotes ("") if + leading or trailing spaces are needed. The quotes are stripped. +

+

+ The replacement token "@file" can be used in the <text>. It will + be replaced with the import filename as entered. +

+

+ Example: +

+

+ IMPORTBEGIN === Cut Begin: @file === + IMPORTEND === Cut End === +

+ + + + IMPORTEND <text> + +

+ (same as IMPORTBEGIN) +

+

+ See IMPORTBEGIN. +

+ + + + INBOUNDPATH <path> + +

+ (defaults to GOLDPATH) +

+

+ The inbound path is currently only used with the file request + feature (the READfilerequest command, <Ctrl-F>). If you use this + feature, GoldED+ will put the file descriptions into a FILES.BBS in + the inbound path, ready for when the requested files are moved to + the correct file areas. +

+ + + + INCLUDE + + + + + + + + This tells the configuration file reader to stop reading the current + configuration file, and start reading the file specifyed as an + extra configuration source, then resume reading the previous + configuration file. + + + The + + + Mail reader and nodelist compiler. + + + + + + INCLUDENODES <addressmask> + +

+ You can define up to 50 different addressmasks to be included from + the compiled nodelists. This is only used in conjunction with the + EXCLUDENODES keyword to include otherwise EXcluded nodes. This + keyword is only used by GoldNODE. +

+ + + + INPUTFILE <filename> + +

+ (*) +

+

+ Defines the default name in the internal editor file import + function. +

+

+ GoldED+ can automatically uuencode and apply a base64 encoding to + the files during importing them into the internal editor. +

+

+ NOTE: This is a very simple implementation of encoders. It cannot + split large files over several messages. The file mode number 644 + is hard-coded and has nothing to do with the actual file mode. +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + INTENSECOLORS <yes/no> + +

+ (no) +

+

+ GoldED+ is capable of switching off the "blink" color, and thereby + enabling the use of bright background (paper) colors. Enable this + keyword, and try out one of the intense color setup examples. +

+ + + + INTERNETADDRESS <internet-address> + +

+ Specifies your Internet address. This must be the address only, no + name. The INTERNETADDRESS and USERNAME will be combined to a + standard "From: internetaddresss (username)" headerline when you + write e-mail or articles. +

+

+ Example: +

+

+ USERNAME Odinn Sorensen + INTERNETADDRESS odinn@ibm.net +

+

+ Produces the RFC line: +

+

+ From: odinn@ibm.net (Odinn Sorensen) +

+ + + + INTERNETDOMAIN <domainname> + +

+ (username%domain.net) +

+

+ Defines the domain-part of outgouing Message-ID's. If you don't + know your full domain, leave it as default, which should work just + fine. +

+ + + + INTERNETGATE [gatename<,>]<address> + +

+ Defines the local Internet gate you use when sending netmail to + Internet users. This option is activated when you write an + Internet address in the TO: field in the header display. GoldED+ + detects the Internet address by looking for the '@' character. If + detected, GoldED+ puts the gate address from INTERNETGATE in the + TO: address field. If you have defined the optional gate name + (typically UUCP), GoldED+ also replaces the typed Internet address + with the gate name and puts the Internet address in a TO: line in + the message body. Some gate software accepts the Internet address + directly in the header, while other software may need the special + (UUCP) name and a separate TO: line. Examples: +

+

+ INTERNETGATE UUCP, 1:105/42 ; Standard, with gate name + INTERNETGATE 2:230/9316 ; My uplink runs GIGO software +

+

+ This keyword can be used globally in GOLDED.CFG, if you only ever + use one gate, or in GROUP's for specific areas in GOLDRAND.CFG if + you have multiple netmail areas and regularly use more than one + gate. +

+

+ NOTE: If you enable the INTERNETRFCBODY keyword, you should always + use the gatename UUCP, because otherwise the gateway software may + send duplicate copies (carbon copies) of your e-mails. +

+ + + + INTERNETLOOKUP <yes/no> + +

+ (no) +

+

+ If set to Yes, GoldED+ will check the systemname in the nodelist + when doing a lookup and if the systemname looks like an Internet + address (contains an '@' char), the msg will be addressed to that + Internet address using the INTERNETGATE name/address if defined. +

+

+ For example, let's say there was something like this in the + nodelist: +

+

+ ,999,somebody@somewhere,Whereever,Some_Body,... +

+

+ And this in my GOLDED.CFG: +

+

+ INTERNETLOOKUP Yes + INTERNETGATE 2:230/9316 +

+

+ Then if I did a lookup of "Some Body" and selected the entry with + the Internet address, GoldED+ would make a msg looking like this: +

+

+ -------------------------------------- + From : odinn@winboss.dk 2:236/77 + To : somebody@somewhere 2:230/9316 + Subj : whatever + -------------------------------------- +

+

+ Or if my gate was defined as "INTERNETGATE UUCP 2:230/9316": +

+

+ -------------------------------------- + From : odinn@winboss.dk 2:236/77 + To : UUCP 2:230/9316 + Subj : whatever + -------------------------------------- + To: somebody@somewhere +

+

+ So what's the use of all this? It allows you to make a + nodelist-style list of users with Internet addresses and use it + with GoldED+ so that you can do a lookup of normal names instead of + trying to remember strange Internet addresses. Of course something + similar could be done using the ADDRESSMACRO's, but with the + nodelist approach, you could build a "network" of users which have + offline Internet access via FTN-gate software and distribute the + nodelist for automatic processing. +

+ + + + INTERNETMSGID <yes/no> + +

+ (no) +

+

+ Specifies whether the FTN MSGID kludge should contain an RFC1036 + compatible Message-ID or the normal FTS-9 format. Note that using + the RFC1036 format in MSGID breaks the FTS-9 (version 001) + specification, so please don't use this feature in FidoNet netmail + or echomail. As a safeguard, GoldED+ will only use the RFC1036 + format in areas specifically marked as e-mail or newsgroups, using + the SOUPEMAIL and SOUPNEWSRCFILE keywords or using the Email and + News area types with the AREADEF keyword, even when INTERNETMSGID + is set to YES globally. +

+ + + + INTERNETREPLY <yes/no> + +

+ (yes) +

+

+ When INTERNETREPLY is enabled, GoldED+ always uses the FSC-35 + REPLYADDR/REPLYTO kludges to gate replies to msgs from Internet + correctly. If disabled, GoldED+ only uses the FSC-35 method if the + Internet address is too large to fit in the max-35-character TO: + header field. Some gate software requires that the FSC-35 method + is used, while other software accepts Internet addresses directly + in the header. +

+ + + + INTERNETRFCBODY <yes/no> + +

+ (no) +

+

+ Tells GoldED+ whether to look for and process RFC headerlines at + the top of the message body, before the first empty line. Also + tells GoldED+ to insert its own RFC headerlines at the top of the + message body instead of as kludge lines. This option should only + be used when receiving Internet mail as QWK packets where the RFC + headerlines are usually found at the top of the messages, or when + sending Internet mail via FTN packet to a gateway running GIGO. + GIGO does not recognize RFC header in kludges, but it does + recognize them at the top of the messages, if it is properly + configured (with lines of "Allow_Xxx:" in GIGO's HEADERS.CFG, + where Xxx are the RFC headerlines the gate administrator wants to + allow). +

+ + + + INVALIDATE <type> <"findstring"> <"replacestring"> + +

+ This is used to invalidate (change) certain control strings in + quoted text. Use this in conjunction with old versions of D'Bridge + or other software that chokes on control strings in quoted text. + As an added bonus feature, if the tearline or origin is + invalidated to a null string (""), they will not be quoted at all. +

+

+ The <type> can be one of the following: +

+

+ Tearline Invalidate tearline ("---"). + Origin Invalidate origin (" * Origin: "). + Seenby Invalidate SEEN-BY's. +

+

+ By default, the following invalidations are used: +

+

+ INVALIDATE Tearline "---" "-+-" + INVALIDATE Origin " * Origin: " " + Origin: " + INVALIDATE Seenby "SEEN-BY" "SEEN+BY" +

+

+ If you want to disable invalidation entirely, use this: +

+

+ INVALIDATE Tearline "---" "---" + INVALIDATE Origin " * Origin: " " * Origin: " + INVALIDATE Seenby "SEEN-BY" "SEEN-BY" +

+

+ The defined INVALIDATEs are also used during importing a file when + editing a mail in the internal message editor. +

+ + + + JAMHARDDELETE <yes/no> + +

+ (no) +

+

+ The default setting makes GoldED+ conform to the JAMAPI specs when + deleting msgs in JAM msgbases. This means that deleted msgs are + only marked as such in the message header, not in the index. As a + result, GoldED+ will find and display the deleted msgs until you + run a message pack utility to physically remove the deleted msgs. +

+

+ If JAMHARDDELETE is set to Yes, GoldED+ will zap the reference to + the message in the index when deleting msgs. This way the deleted + msgs will not show up again later. The drawback of this approach + is that it is hard to undelete msgs, and may break other software + which assume 100% to-the-letter conformance to the specs. Note + however, that the hard-delete method is transparent to normal use + of JAM msgbases. Probably the only software that might break are + undelete utilities. +

+

+ For the techies and programmers, the hard-delete method is simply + setting both UserCRC and HdrOffset in the index to 0xFFFFFFFF + instead of only the UserCRC. According to the JAMAPI specs, a + value of 0xFFFFFFFF in HdrOffset means that "there is no + corresponding message header". Sounds remarkably like a deleted + msg, right? :-) +

+ + + + JAMPATH <path> + +

+ (defaults to the HUDSONPATH) +

+

+ Defines the path where GoldED+ can access the NETMAIL/ECHOMAIL.JAM + files, which are used by mail processors to find and scan out mail + written by users. +

+

+ GoldED+ can handle enviroment variables correctly in paths + specified in connection with this keyword. For example, if a path + is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in + AUTOEXEC.BAT (or whatever), then GoldED+ translates the path to + C:\POINT\path\name. + NOTE: The translation is done at config compile time, so if you + change the environment variable and haven't changed anything else + that would cause GoldED+ to recompile it's config, you must force + it with the -F or -FF command parameter. +

+ + + + KEYBCLEAR <yes/no> + +

+ (no) +

+

+ Tells GoldED+ whether or not to clear the keyboard buffer on + startup. This also clears KEYBSTACK or commandline key stuffing. + In older versions of GoldED+, it was necessary to enable this + keyword if you had renamed GOLDED.EXE to DBEDIT.EXE. This version + detects the .EXE renaming and automatically enables KEYBCLEAR, + regardless of the configuration setting. +

+ + + + KEYBDEFAULTS <yes/no> + +

+ (yes) +

+

+ GoldED+ defines a default keyboard configuration setup internally. + The keys can be reconfigured in the GOLDKEYS.CFG file. By default, + the internal keyboard setup is active always, redefinable with the + definitions in GOLDKEYS.CFG. But in some cases it can be + preferrable that the internal keyboard setup is turned off, so + that only the keys in GOLDKEYS.CFG are active. If you want this, + set KEYBDEFAULTS to NO. +

+ + + + KEYBEXT <yes/no> + +

+ (detect) +

+

+ If enabled, GoldED+ will use extended bios calls to read the + keyboard. With the extended keyboard, you can use keys like + <Alt-Left>, <Alt-Home> and other extended keys. If you don't have + an extended keyboard, don't despair - using a few neat tricks, I + have made it possible to use some of the extended keys even with a + non-extended keyboard. +

+ + + + KEYBMODE <poll/block> + +

+ (poll) +

+

+ If this option is set to Poll, GoldED+ switches its keyboard + handling code from "blocking" to "polling" mode. This enables + GoldED+ to provide a continuously running statusline clock, + automatic internal editor autosave, timeout exit and screensaver. + If set to Block, the timeout exit and screensaver are disabled, + and the clock and autosave are dependent on key presses. +

+

+ In order to minimize waste of CPU resources in keyboard polling + mode, GoldED+ automatically detects DESQview, Windows and OS/2 and + releases timeslices during the keyboard poll. +

+ +KEYBSTACK <keystring> +

+ With this keyword, you can "stack" keys in the keyboard buffer. + The KEYBSTACK can be overridden by commandline keystacking, which + uses the same syntax. +

+

+ The <keystring> can be a mixture of the following: +

+

+ ^Char Ctrl-key (^Letter). + ~Char Ctrl-key (~Letter). (Use this with 4DOS!). + @Key Alt-key (@Number or @Letter). + Char Literal character. + "String" String, enclosed in double quotes. + 'String' String, enclosed in single quotes. + Number Keyboard scan code (decimal). + ! Clear keyboard buffer. +

+

+ Whitespace (space and tab) is ignored, except in quoted strings. +

+

+ See the chapter for more info. +

+ + + + KLUDGE <kludge-definition> + +

+ The definition may optionally be enclosed in quotes. A definition + must be enclosed in quotes if it contains leading or trailing + spaces. The KLUDGE tells GoldED+ which kludges it should consider + as "known" in addition to the built-in known kludges. +

+

+ Here are a bunch of examples, most of which are kludges generated + by the GIGO Internet gateway software: +

+

+ KLUDGE " " ; For wrapped kludges + KLUDGE "Content-Type:" + KLUDGE "Date:" + KLUDGE "From:" + KLUDGE "In-Reply-To:" + KLUDGE "Message-Id:" + KLUDGE "Mime-Version:" + KLUDGE "Organization:" + KLUDGE "Newsgroups:" + KLUDGE "Received:" + KLUDGE "Reply-To:" + KLUDGE "Sender:" + KLUDGE "Subject:" + KLUDGE "To:" + KLUDGE "Errors-To:" + KLUDGE "FTN-From:" ; X-FTN-From: + KLUDGE "ORIGREF:" ; Gated? + KLUDGE "ORIGID:" ; Gated? + KLUDGE "RFC-" ; Seen in NET_DEV +

+

+ The kludges defined with KLUDGE are not case-sensitive, but when + GoldED+ looks for the kludges, it matches to the exact length. This + means that for example "RFC-" will match all kludges beginning + with that string. +

+

+ The ASCII 1 kludge char should not be included in the definition + string, but GoldED+ can handle it if you do. +

+ + + + KLUDGECHRS <yes/no> + +

+ (yes) +

+

+ If set to YES, GoldED+ uses the "^aCHRS" kludge instead of the + "^aCHARSET" kludge when appropriate. +

+ + + + LOADLANGUAGE <file> + +

+ If defined, this keyword will load a language definition file. +

+

+ This feature can be used to load a small set of national language + definitions in national areas, an english set in international + areas, etc. Typically this would be used to load the definitions + of the date/time strings for use in the template and the + Msg/From/To/Subj strings in the header display. +

+

+ In the ADVANCED archive, a set of GEDLNG*.CFG files are provided, + which are designed for use with LOADLANGUAGE. Please note that + there is also a @loadlanguage template token. This way you can + choose to load a language file from the template, or by using the + Random System. The template token takes precedence over the + LOADLANGUAGE in the Random System, but if both are defined, both + will be loaded. +

+

+ This keyword can be used globally and in Random System groups, but + it is probably not very useful when used globally. +

+ + + + LOGFILE <file> + +

+ (GOLDED.LOG) +

+

+ Defines the name of the GoldED+ logfile. You should not change the + default. +

+ + + + LOGFORMAT <fd,max,bink,qbbs,db> + +

+ (fd) +

+

+ Defines the log format GoldED+ should use when writing to the + logfile. +

+ + + + LOOKUPECHO <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will use nodelist lookup when entering the TO: + name in msgs in echomail areas. +

+

+ GoldED+ *won't* lookup the name if it exactly matches the current + WHOTO - text. This is a feature, because a lookup of "All" is not + very useful. :-) +

+ + + + LOOKUPLOCAL <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will use nodelist lookup when entering the TO: + name in msgs in local areas. +

+

+ GoldED+ *won't* lookup the name if it exactly matches the current + WHOTO - text. This is a feature, because a lookup of "All" is not + very useful. :-) +

+ + + + LOOKUPNET <yes/no> + +

+ (yes) +

+

+ If enabled, GoldED+ will use nodelist lookup when entering the TO: + name in msgs in netmail areas. +

+ + + + LOOKUPUSERBASE <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will attempt to find a matching username in the + user database if a to-name with wildcards is entered in echo or + local areas. +

+

+ The userbase lookup feature is not new, but a need arose for an + option to turn off the lookup. I decided to let the default be to + disable the lookup. Previously the lookup was always enabled. +

+ + + + MAILINGLIST <echoid> <senderaddress> [contribution address] + +

+ Defines one or more mailing lists. When importing e-mail from a + SOUP packet, GoldED+ will look at the Internet address in the + "Sender" header and if it matches one of the MAILINGLIST's, the + e-mail will be tossed to the defined area. Note that GoldED+ + supports only participation in, not hosting of mailing lists. The + contribution address is the destination Internet address for mail + you write to the mailing list - the address is typically given to + you when you subscribe to a list. If the contribution address is + not specified, the senderaddress is assumed. +

+ + + + MAILTOSS <echoid> <contribution-address> <pattern> + +

+ This is acutally the same as MAILINGLIST in disguise with the + parameters recorded and it also enables the full set of pattern + matching. The <pattern> can be written exactly as if in the prompt + for the advanced search feature. +

+

+ Any number of MAILTOSS lines can be given for a particular list, + if there is for some reason no single way to identify the list. +

+

+ When determining the contribution address, the first MAILTOSS + (or MAILINGLIST) that matches the echoid is chosen. +

+

+ MAILTOSS and MAILINGLIST can both be used at the same time and for + the same lists. MAILINGLIST is always the faster, because it looks + only at specific headerlines. MAILTOSS uses much more complex + pattern matching and can even match based on message body content. +

+ + + + MAPPATH <server filespec> <local filespec> + +

+ This keyword is used to map paths, for example if you have + different drive letters on a server machine and a workstation. You + might have your FidoNet mailer and mail processor setup to run + with the server drive letter (C:), but run GoldED+ from a + workstation where that drive is mapped to a different letter (J:). + If you use AREAFILE's to get the area configuration for GoldED+, + you need to use MAPPATH to map the server drive letter to the + workstation equivalent. +

+

+ Another case might be that you have a setup with DOS-style paths + and want to run the Linux version with the same GoldED+ setup. You + can then use MAPPATH to map the DOS drive-based paths to Unix + style paths. +

+

+ Examples: +

+

+ MAPPATH C: J: + MAPPATH C:\ /mnt/dos/c/ +

+

+ NOTE: You don't have to worry about backslash/forwardslash in this + case - they are always mapped automatically to the correct type + for the operating system. +

+ + + + MEMBER <echoid> + +

+ Defines Random System group members. See the Random System chapter + for details. +

+ + + + MENUDROPMSG <yes/no> + +

+ (no) +

+

+ Defines the default selection in the "Drop This Msg?" menu. +

+ + + + MENUMARKED <marked/current/previous/default> + +

+ (default) +

+

+ Specifies the position of the selection bar in the Marked/Current + menu. +

+

+ Marked Set selector to Marked. + Current Set selector to Current. + Previous Set selector to previously selection. + Default Set selector to Marked if there are marked msgs. +

+

+ Note that older versions (before 2.50) used the equivalent of the + "previous" setting. +

+ + + + MOUSE <yes/no> + +

+ (no) +

+

+ The mouse support in GoldED+ is currently not functional, so this + keyword is ignored. +

+ + + + MSGLISTDATE <written/arrived/received/no> + +

+ (written) +

+

+ Can be used globally and in groups. This keyword specifies the + default date shown in the right column in the message list. If + "no" is specified, the date column is removed and the space used + to widen the other columns. Personally I prefer to see the + "arrived" date, which is why I implemented this feature. +

+

+ The key command LISTtoggledate (Ctrl-D) toggles between them. +

+

+ Note that the "arrived" date doubles as the "processed" date for + messages that are written locally and scanned out from your + messagebase. +

+

+ Not all messagebase formats supports all three dates. The table + below shows which messagebase supports which dates: +

+

+ Written Arrived Received + JAM X X X + *.MSG X X + Squish X X + Ezycom X X + Hudson X + Goldbase X + PCBoard X +

+

+ If a date is not supported, "n/a" (for "not available") is shown + instead. +

+ + + + MSGLISTFAST <yes/no> + +

+ (yes) +

+

+ The message lister can operate in two ways, fast or slow. In the + fast mode, only the message headers are loaded for the list + information. Depending on the msgbase format and message type, + some information may not be quite the same when presented in the + lister because information which is gathered from kludges or other + control information in the message text will be missing. Most of + the time this may not be a problem, so if you want speed, chose + the fast mode (default). +

+

+ The slow mode loads and fully interprets the content of each + message before the message list is presented. The slowness is most + noticable when entering the lister and when paging up and down. + You may want to use the slow mode for areas with Internet + newsgroups and e-mail, where GoldED+ uses the "From" kludge to get + the real name of the message writer. +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + MSGLISTFIRST <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ automatically starts the message lister when + entering an area. +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + MSGLISTHEADER <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ shows the header of the current message when + you scroll the bar up and down. This is how it worked in previous + versions. If disabled, GoldED+ does not show the header and instead + uses the screen space to show more messages. By eliminating the + header display, it is also much faster at scrolling the list. +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + MSGLISTPAGEBAR <yes/no> + +

+ (yes) +

+

+ Enables or disables a pagebar (scrollbar) in the message list. +

+ + + + MSGLISTVIEWSUBJ <yes/no> + +

+ (yes) +

+

+ If enabled, GoldED+ will display the full subject in the bottom + border of the list window. Note that this feature slows down + scrolling a bit. +

+ + + + MSGLISTWIDESUBJ <yes/no> + +

+ (no) +

+

+ If enabled, the Subject column is made wider by removing the To + column. This is especially useful in gated Internet newsgroups, + where the To name is always "All". +

+

+ You can toggle between wide and short subject with Ctrl-B + (keycommand LISTtogglewidesubj). +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + NAMESFILE <file> + +

+ (NAMES.FD) +

+

+ GoldED+ supports the "address macro" file supported by FrontDoor + and Maximus. If no path is specified, the file is first searched + for in the path from the "FD" environment variable and then the + GOLDPATH, if the FD variable failed. +

+

+ The address macros are added *after* those defined with the + ADDRESSMACRO keyword (if any) (see this for details on the + format). +

+ + + + NETNAME + +

dummy text

+ + + + NICKNAME <your pseudo> + +

+ Defines the nick name (pseudo) for the current USERNAME. Can be + used globally and in random system groups. + +

+ + + + NODELIST <file> [zone/addr] + +

+ Here you define up to 255 nodelists that are used by GoldED+ and the + companion nodelist compiler GoldNODE. The nodelists must generally + be in the standard "St.Louis" nodelist format, but they can also + contain FrontDoor/Version7 style Boss/Point extensions. The + default zone is defined by the first ADDRESS or AKA, but can be + overridden by adding the zone number or a full address after the + filename. GoldED+ currently needs it's own special index files to + use the nodelists. These index files are created by GoldNODE. +

+

+ <file> Nodelist file. If the extension is .999 or a + wildcard (".*"), the newest file with a numeric + extension is used. + [zone/addr] Default zone or address for the nodelist (if no + zone info is present in the list itself). +

+

+ See also the USERLIST keyword, and the Nodelist Browsing chapter. +

+

+ NOTE: If you have nodelists with duplicate some of each others + nodes, the nodelist with the newest or most correct entries should + be placed LAST, and you should use the -D (remove duplicates) + option with GoldNODE. +

+ + + + NODELISTWARN <yes/no> + +

+ (yes) +

+

+ If set to YES, GoldED+ will warn you during startup if one or more + nodelists are missing. Use NO to disable the warning if it bothers + you or you delete/pack your nodelists when the nodelists are + compiled. +

+

+ NOTE: GoldED+ can work fine with lookups etc. without nodelists as + long as it can access its own indexes (GOLDNODE.GX?). Only the + extra details will be missing. +

+ + + + NODEPATH <path> + +

+ This is where GoldED+ and GoldNODE finds the nodelist files and + indexes. +

+ + + + NODEPATHFD <path> + +

+ Path where GoldED+ can find the FrontDoor nodelist index files. +

+ + + + NODEPATHIM <path> + +

+ Path to the InterMail nodelist index files. This is actually just + an alias name of the NODEPATHFD keyword, since InterMail and + FrontDoor uses the same nodelist index files. +

+ + + + NODEPATHV7 <path> + +

+ Path where GoldED+ can find the Version 7 nodelist index files. +

+

+ NOTE: For the Version 7 nodelist index support, GoldED+ *requires* + that the files SYSOP.NDX, NODEX.NDX and NODEX.DAT are present. + None of these files may be missing and no other filenames are + supported. Multiple sets of index files are not supported. +

+ + + + NODEV7FLAGS <flag> <value> + +

+ The Version 7 nodelist index does not by default define any + nodelist flags except the CM flag. Unfortunately the V7 index does + not point to the actual nodelist, it only has some bits which are + marked "reserved" in the specifications. The NODEV7FLAGS keyword + allows you to define the meaning of each of these bits. +

+

+ The <value> field can be a number or a bit number. Allowed numbers + are: 32, 64, 128, 256, 512, 1024, 2048, 8192 and 16384. Allowed + bit numbers are: b5, b6, b7, b8, b9, b10, b11, b13 and b14. +

+

+ Example: +

+

+ NODEV7FLAGS MO b5 + NODEV7FLAGS LO b6 + NODEV7FLAGS MN b7 + NODEV7FLAGS NC b8 + NODEV7FLAGS ZEC b9 + NODEV7FLAGS REC b10 + NODEV7FLAGS NEC b11 + NODEV7FLAGS XA b13 + NODEV7FLAGS XX b14 +

+

+ See also the NODEV7MODEM keyword for other nodelist flags. +

+

+ The nodelist flag bits in the index files are put in by your + Version 7 nodelist compiler. You must make sure that the nodelist + flag definitions in your nodelist compiler setup match those in + your GoldED+ setup. +

+ + + + NODEV7MODEM <type> <value> + +

+ The Version 7 nodelist index does not by default define any + nodelist modem type flags. Unfortunately the V7 index does not + point to the actual nodelist, it only has some bits which are + marked "reserved" in the specifications. The NODEV7MODEM keyword + allows you to define the meaning of each of these bits. +

+

+ The <value> field can be a number or a bit number. Allowed numbers + are: 1, 2, 4, 8, 16, 32, 64 and 128. Allowed bit numbers are: b0, + b1, b2, b3, b4, b5, b6 and b7. +

+

+ Example: +

+

+ NODEV7MODEM VFC b0 + NODEV7MODEM HST b1 + NODEV7MODEM V34T b2 + NODEV7MODEM V32B b3 + NODEV7MODEM V34 b4 + NODEV7MODEM V42B b5 + NODEV7MODEM ZYX b6 + NODEV7MODEM ISDN b7 +

+

+ See also the NODEV7FLAGS keyword for other nodelist flags. +

+

+ The modem type bits in the index files are put in by your Version + 7 nodelist compiler. You must make sure that the modem type + definitions in your nodelist compiler setup match those in your + GoldED+ setup. +

+ + + + ORGANIZATION <text> + +

+ Specifies the content of the RFC Organization header for Internet + messages. +

+ + + + ORIGIN <"string"> + +

+ You can define many different origins for use in GoldED+. You can + select one of the defined origins from the Origin selection menu + (the READchangeorigin keyword), which is also available from the + EDITMENU and the EDITSAVEMENU. +

+

+ Leading and/or trailing spaces can be added by enclosing the + origin string in quotes. +

+

+ This keyword can be used globally and in a Random System group. +

+

+ NOTE: Origins defined in the Random System will always override + the global origins defined with this keyword, except when they are + selected from the EDITSAVEMENU. +

+ + + + OUTBOUNDPATH <path> + +

+ Defines a Binkley-style outbound path. Currently only used for + WaZOO .REQ file requests (see FRQWAZOO). This should be the name + of your primary outbound without extension. +

+ + + + OUTPUTFILE <file> + +

+ This is the default name of the file written using the + READwritemsg command. +

+

+ This keyword can be used globally and in a Random System group. +

+ + + + PCBOARDPATH <path> + +

+ Defines the default path where GoldED+ should look for the PCBoard + setup files if it can't find the PCBOARD environment variable. +

+ + + + PCBOARDUSERNO <userno> + +

+ (0) +

+

+ Specifies the lastread set used in the PCBoard message base. +

+ + + + PERSONALMAIL <startup,allnames> + +

+ Specifies options regarding the personal mail scan feature. None + of them are enabled by default. +

+

+ If the "startup" option is used, GoldED+ scans for personal mail + while doing the startup mail scan. +

+

+ If the "allnames" option is used, GoldED+ scans for mail to all the + USERNAME's instead of only the first. The default is not to scan + for personal mail at startup and to scan only for the first name. + This is faster. +

+

+ Example: +

+

+ PERSONALMAIL Startup, AllNames +

+

+ The example makes GoldED+ scan for personal mail to all your + USERNAME's at startup. +

+ + + + PLAY <filename.ext/beepnoise> + +

+ See the EVENT keyword for a definition of the PLAY parameters. + You may specify +

+ Bugs: At least one +

+ This keyword can be used globally and in a Random System group. +

+ + + + PRINTDEVICE <devicename> + +

+ (PRN) +

+

+ Defines the name of the device used for printing. PRN is the + default, but LPTx can also be used. Printers on COMx ports may + also work, but this has not been tested. +

+

+ Devices are opened in Write-Only text mode. The function has been + successfully tested to work with two popular peer-to-peer network + packages. +

+

+ You should NOT use a filename as devicename. Use the filename + option in the Write menu instead. +

+ + + + PRINTFORMFEED <yes/no> + +

+ (yes) +

+

+ Used when printing messages. If enabled, it prints a Form Feed + (12d) character after each message. +

+ + + + PRINTINIT <printstring> + +

+ This keyword defines the command string sent to your printer to + initialize it before the actual printing. +

+

+ The <printstring> can contain items like these: +

+

+ $Hex A hexadecimal string. + #Decimal A decimal (integer) number. + "String" Text string, enclosed in double quotes. + 'String' Text string, enclosed in single quotes. + Other chars Ignored. +

+ + + + PRINTLENGTH <lines> + +

+ (60) +

+

+ Defines the number of lines per page for printing. A formfeed is + printed when every time PRINTLENGTH lines have been printed. +

+ + + + PRINTMARGIN <characters> + +

+ (80) +

+

+ The right margin to use in printed messages. +

+ + + + PRINTRESET <printstring> + +

+ This keyword defines the command string sent to your printer to + reset it after printing. +

+

+ <printstring> See the PRINTINIT keyword. +

+ + + + QUOTEBLANK <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will put the QUOTESTRING on blank lines in the + quote. Otherwise blank lines are left blank in quotes. +

+ + + + QUOTEBUFFILE <filename> + +

+ If used, it sets the default filename for the quotebuffer. If no + path is specified, the GOLDPATH is used. +

+

+ This keyword can be used globally and in Random System groups. +

+

+ NOTE: If this keyword is used in globally (in GOLDED.CFG), it + effectively disables the automatically named quotebuffers, as + described in the chapter about the QUOTEBUFMODE keyword. +

+ + + + QUOTEBUFMODE <ask/append/overwrite> + +

+ (ask) +

+

+ Specifies what GoldED+ should do, if the quotebuffer file exists + already. +

+

+ Ask A menu asks you to select append/overwrite/skip. + Append Always append, no asking. + Overwrite Always overwrite, no asking. +

+

+ The "always overwrite" mode is not very useful I guess, but it's + there if you need it. +

+

+ The quotebuffer feature automatically creates special filenames + for the buffer file, using these guidelines: +

+

+ FORMAT FILENAME LOCATION + Fido GOLDED.QBF In the directory with the *.MSG's. + Hudson GOLDHxxx.QBF In the HUDSONPATH. + Squish filename.QBF Where the Squish area is. + Ezycom GLDxxxxx.QBF In the EZYCOMMSGPATH. + JAM filename.QBF Where the JAM area is. + Goldbase GOLDGxxx.QBF In the GOLDBASEPATH. + PCBoard filename.QBF Where the PCBoard area is. +

+

+ Note that they all have extension .QBF so that you can easily find + them. +

+ + + + QUOTECHARS ["]<chars>["] + +

+ Defines up to 10 chars to recognize in addition to '>' as quote + string chars. This is most useful in gated Internet newsgroups, + where chars such as '|', ':' and ';' are sometimes used instead of + the '>'. +

+

+ This keyword can be used globally and in Random System groups. +

+

+ Example: +

+

+ Group Internet: + Member alt.*, comp.*, net.email + Quotechars "|:;" + Username odinn@winboss.dk + EndGroup +

+

+ The example is similar to the one I use myself (net.email is a + local netmail area where I import my gated e-mail from + winboss.dk). The username is my actual Internet address. +

+

+ Note that using additional quotechars such as '|' and ':' may + cause odd results when quoting in the cases when they are actually + NOT used in a message as quotechars. Consider for example quoting + a smiley :-) +

+ + + + QUOTECTRL <Tearline,Origin,yes/no> + +

+ Specifies if you want quote tearline and/or origin in your + messages. +

+

+ This keyword can be used in random system groups. +

+ + + + QUOTEMARGIN <chars> + +

+ (70) +

+

+ The margin to which quotes are wrapped. A negative value means + that the negative value is added to the DISPMARGIN (not + recommended). +

+ + + + QUOTESPACING <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will automatically add blank lines before and + after a block of quoted text, if none are present already. This + improves the readability of some messages. +

+ + + + QUOTESTOPS + + + + + + + + If one of characters defined by this keyword found before quotechar + then line will be not treated as quote. + + + + + + + + + + QUOTESTRING <quotespec> + +

+ (" FL> ") +

+

+ With this keyword you define how you want the quotestring to look + in your quoted replies. +

+

+ The <quotespec> can contain these characters: +

+

+ F Replaced with the first letter of the first name. + M Replaced with the letters of the middle names. + L Replaced with the first letter of the last name. + > Required quote-char. + Spaces Cosmetics. +

+

+ Other characters are allowed but *not* recommended. +

+

+ This keyword can be used globally and in Random System Groups. +

+ + + + QUOTEWRAPHARD <yes/no> + +

+ (yes) +

+

+ This keyword controls behaviour of quoted text (wrap or reflow). +

+ + + + QWKBADMSGS <echoid> + +

+ Specifies the area where messages in unknown conferences are put. + If you get messages tossed here by accident, you must move them + manually to the correct area. If the badmsgs area is not defined, + the messages will silently disappear. Messages tossed to the + badmsgs area will have the control line "AREA:<bbsid>_<confno>" at + the top of the message. +

+ + + + QWKCONFMAP <bbsid> ["]<confname>["] <echoid> + +

+ Defines the mapping between the BBSID and conference names in the + QWK packets and the echoid name of the conference as required by + GoldED+. You MUST define a mapping for every conference that you + subscribe to. If you don't, the messages will be tossed to the + area defined by QWKBADMSGS or disappear. The <bbsid> is the name + listed on line 5 in CONTROL.DAT after the comma. The <confname> is + the conference names listed on line 13 and on alternate lines + onwards in CONTROL.DAT. If a conference name contains embedded + spaces, the <confname> must be enclosed in double quotes, like + this: "Main Board". The area <echoid> must be already defined + either in an AREAFILE or using the AREADEF or AREA keywords. +

+ + + + QWKEXPORTPATH <path> + +

+ Path where outgoing QWK reply files (BBSID.MSG) can be placed. +

+ + + + QWKIMPORTPATH <path> + +

+ Path where incoming QWK packet files (CONTROL.DAT and + MESSAGES.DAT) can be found. +

+ + + + QWKOPTIONS <bbsid> <options> + +

+ The <bbsid> is the BBSID (same as the name of the QWK packet) for + which the options will be active. The <options> can be any or a + combination of the following, separated by commas or spaces: +

+

+ KLUDGES/NOKLUDGES: Defaults to NOKLUDGES. Specifies whether or not + to include the FidoNet-style kludges at the top of messages when + exporting to QWK. NOTE: Unless you enable this option, GoldED+ will + *not* include kludges in your QWK packets. You should check if the + BBS supports kludges in QWK packets. If it does, please enable + this option. +

+

+ MIXCASE/NOMIXCASE: Defaults to NOMIXCASE. Specifies whether or not + the BBS allows mixed upper/lower case in the QWK message headers. + The default is to uppercase the TO and FROM header fields when + exporting to QWK packets. +

+

+ RECEIPT/NORECEIPT: Defaults to NORECEIPT. Specifies whether or not + the BBS supports return receipt requests (RRQ). If the RECEIPT + option is enabled, GoldED+ will insert "RRR" at the front of the + subject field if the RRQ attribute is set on your messages, when + exporting to QWK packets. +

+ + + + QWKREPLYLINKER <cmd> + +

+ Commandline for a replylinker program to call after QWK import. +

+ + + + QWKTOSSLOG <file> + +

+ Name of a file where GoldED+ puts the echoids of each area where + articles have been imported. The tosslog file is intended to be + used with a replylinker. If no path is given, it defaults to the + GOLDPATH. +

+ + + + RA2USERSBBS <yes/no> + +

+ (detect) +

+

+ GoldED+ supports the two different formats of the Hudson USERS.BBS + file. With this keyword you can tell GoldED+ which format to use. +

+

+ If set to YES, the RA2 format is used. Otherwise if the it is set + to NO, the Hudson format is used. +

+

+ If this keyword is NOT used, GoldED+ tries to detect the format by + looking at the size of the USERS.BBS file and comparing this to + the record sizes of the RA2 and Hudson formats. +

+

+ If the size matches one and not the other, the format is detected + to be of the matching type. +

+

+ If the size matches both (which is quite normal), GoldED+ looks for + the RA environment variable and if found, in the RA config files + for the RA version. +

+

+ If the size does not match either of them (indicating a possibly + damaged userfile), GoldED+ exits with an error message and writes + in the log with details of the problem and an advise to run a + userbase packing utility. +

+

+ If used, this keyword should be placed in the configuration file + _after_ any AREAFILE keyword. +

+ + + + RCVDISABLESCFM <yes/no> + +

+ (yes) + + If this keyword defined to "no" then GoldEd will recognize RRq + (receipt request) and/or CFM (confirmation) flag on messages with + RCV (received) flag set. After that RRq and CFM flags will be + resetted. It is useful if your netmail tracker sets RCV flag + before you actually read messages. + chapter, + , + , + , + +

+ + + + REGISTERKEY + +

+ + + + REGISTERNAME + +

+ These keywords do nothing and won't do anything in the future. + They were used when GoldED+ was a Shareware product. +

+ + + + REM + +

+ This keyword ignores everything behind it. This is useful to + comment a single line out. +

+ + + + REPLYLINK <chain/direct> + +

+ Defaults to "direct" for JAM and "chain" for everything else. +

+

+ If set to "direct", GoldED+ will link your reply directly to the + original message. If set to "chain", it will link to the last + message in the reply chain. The default ("chain") is how GoldED+ + has done it in all previous versions. +

+

+ The advantage of the "direct" linking method is that you can + easily find the the original message the reply was for. Unless of + course you have later re-linked using a chain-linking replylinker + utility. I can recommend the utility SQLINK by Serge Terekhov. + SQLINK links Squish areas using the MSGID/REPLY kludges and makes + direct links instead of chain-linking on the subject line like + most other replylinkers do. There are probably also similar + replylinkers for other msgbase formats, I just don't know them. +

+ + + + REPLYLINKLIST <fast/full> + +

+ (fast) +

+

+ When there is more than one reply to a msg in a JAM or Squish + area, GoldED+ pops up a list of the replies. This keyword affects + the contents of the list. +

+

+ In the "fast" mode, the list data is based solely on what can be + found by reading the message header, which is quite fast. + Unfortunately some software does not (or cannot) fill the header + with the correct origination address. In that case, set this + keyword to "full", which makes GoldED+ read and scan each message + for control data to get the origination address. That can be very + slow. +

+ + + + ROBOTNAME <name> + +

+ A "robot" is a program on the Boss or Uplink system which responds + automatically to netmail messages. Usually the robot links or + unlinks echomail areas or distributed files. +

+

+ The following ROBOTNAME's are defined by default: +

+

+ AreaFix, AreaMgr, FileFix, AreaLink, AllFix, Raid, GEcho. +

+

+ If you write a netmail message where the TO: name is one of the + robot names, GoldED+ will ignore any template definition, and give + you a blank msg (possibly with a tearline) to edit. +

+ + + + SCREENBLANKER <seconds> [BLACK] + +

+ (180) +

+

+ If non-zero, GoldED+ will blank the screen after the defined number + of seconds, and put a small moving window up instead. Hitting any + key (including shiftkeys) will return the screen to normal. If + zero, no blanking is done. +

+

+ If the additional parameter "BLACK" is given, GoldED+ will switch + the screen completely black instead of showing its own animated + screenblanker. This is useful if you have a monitor with + powersaving-features. +

+

+ Example: +

+

+ SCREENBLANKER 300 BLACK +

+

+ NOTE: This feature only works if KEYBMODE is set to "poll". +

+ + + + SCREENMAXCOL <columns> + +

+ (0) +

+

+ On some systems, GoldED+ may no detect the correct display size. + With this keyword you can force a specific size. If zero, + autodetect is used. +

+ + + + SCREENMAXROW <rows> + +

+ (0) +

+

+ On some systems, GoldED+ may not detect the correct display size. + With this keyword you can force a specific size. If zero, + autodetect is used. +

+ + + + SCREENPALETTE <reg> <value> OR <reg> (red green blue) + +

+ You can change the color palette used in GoldED+. The palette has + 16 color registers, corresponding to the 16 colors from black (0) + to intense white (15). By changing the values in the palette + registers, it is possible to make any of the 16 colors a + completely different color. You can even make the background + colors intense, without using the intense color feature. There are + 64 different colors to chose from. +

+

+ To configure the palette colors in GoldED+, the SCREENPALETTE + keyword is used. There are two different syntaxes: +

+

+ SCREENPALETTE <reg> <value> + SCREENPALETTE <reg> (red green blue) +

+

+ So you can either compose the color value using separate red, + green, blue components, or directly use a precalculated value. The + red/green/blue values can only be in the range 0-3. +

+

+ These are the original palette values: +

+

+ SCREENPALETTE 0 (0 0 0) + SCREENPALETTE 1 (0 0 2) + SCREENPALETTE 2 (0 2 0) + SCREENPALETTE 3 (0 2 2) + SCREENPALETTE 4 (2 0 0) + SCREENPALETTE 5 (2 0 2) + SCREENPALETTE 6 (2 2 0) + SCREENPALETTE 7 (2 2 2) + SCREENPALETTE 8 (1 1 1) + SCREENPALETTE 9 (1 1 3) + SCREENPALETTE 10 (1 3 1) + SCREENPALETTE 11 (1 3 3) + SCREENPALETTE 12 (3 1 1) + SCREENPALETTE 13 (3 1 3) + SCREENPALETTE 14 (3 3 0) + SCREENPALETTE 15 (3 3 3) +

+

+ Copy these lines into your GOLDED.CFG and start experimenting! :-) +

+

+ If you have written a program to edit the palette and write a + GoldED+ palette setup file, please don't keep it a secret! :-) +

+ + + + SCREENSHADOWS <yes/no> + +

+ (yes) +

+

+ If enabled, all relevant windows and menus in GoldED+ will have + shadows. +

+ + + + SCREENSIZE <mode> + +

+ (Auto) +

+

+ Use this to force GoldED+ to use either 25 lines, 43/50 lines on + EGA/VGA, or even special videomodes supported by your SuperVGA + adapter (modes like 132x44, 100x40 or 80x60). +

+

+ The <mode> can be one of the following: +

+

+ Auto Use detected size. + 25 Switch to 25 lines. + 28 Switch to 28 lines. + 4350 Switch to 43/50 lines. + Mode <NN> Switch to videomode NN (a hexadecimal value). +

+

+ Please check your video adapter manual carefully before trying out + the Mode option. SELECTING A WRONG MODE CAN DAMAGE YOUR MONITOR!!! +

+

+ The Mode option is ignored in the W32 and OS/2 version. +

+ + + + SCREENUSEBIOS <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will use standard BIOS calls for screen + updates. This is VERY slow, and should only be used if really + needed. Normally GoldED+ uses direct screen writes. +

+

+ This feature is only interpreted in the DOS version. +

+ + + + SEARCHFOR ["]<string|string|..>["] + +

+ Defines a set of search strings, separated by the '|' character. + The search set defined here is the default when using the Alt-F/Z + search functions or the marking system. +

+

+ The '|' character works like an OR operator. That is, the search + is successful if one OR more of the strings are matched. The '&' + character is used as the logical AND operator. +

+

+ Please refer to appropriate section in user's guide for more + information. +

+

+ Older versions used the ';' semicolon character as a separator, + but that conflicts with the config reader which treats the + semicolon in a special way. The semicolon is still accepted as + separator char like '|', but if semicolons are used, you MUST + enclose the search strings with quotes or the config reader will + treat the first semicolon as the start of a comment. +

+

+ Examples: +

+

+ SEARCHFOR string1 + SEARCHFOR string1|string2|stringx + SEARCHFOR "string1;string2;stringx" + SEARCHFOR "string 1"|string2&stringx +

+

+ This keyword can be used globally and in Random System groups. +

+ + + + SEMAPHORE <type> <file> + +

+ This keyword defines "semaphore" files, for use with other mailer + and/or mail processing software. +

+

+ The <type> can be one of the following: +

+

+ NETSCAN Empty netmail scan file (for D'Bridge/FD). + ECHOSCAN Empty echomail scan file (for D'Bridge). + EXPORTLIST Echoid-list of your new messages. + IMPORTLIST Echoid-list of new imported messages. +

+

+ The semaphore files are placed in the AREAPATH, if no path is + specified. +

+

+ See the example .CFG files for typical semaphore filenames. +

+

+ NOTE: You should not set SEMAPHORE EXPORTLIST to + %JAMPATH%\ECHOMAIL.JAM. This is incorrect and probably may cause + your mail processor to malfunction. Use the JAMPATH keyword + instead. +

+

+ GoldED+ can handle enviroment variables correctly in paths + specified in connection with this keyword. For example, if a path + is defined as %MAIL%\path\name, and SET MAIL=C:\POINT is in + AUTOEXEC.BAT (or whatever), then GoldED+ translates the path to + C:\POINT\path\name. +

+

+ NOTE: The translation is done at config compile time, so if you + change the environment variable and haven't changed anything else + that would cause GoldED+ to recompile it's config, you must force + it with the -F or -FF command parameter. +

+

+ In addition, GoldED+ itself can watch for some semaphore files and + execute the appropiate function if it is in the arealist screen. + This can be useful if you have a multitasking system and you want + to "tell" GoldED+ that there is new mail in some areas and GoldED+ + should update its display correctly. +

+

+ In detail, there are +

+

+ EXITNOW <file> Quit immediately. + SCANALL <file> Scan all areas + SCANNETMAIL <file> Scan all netmail areas + SCANTHIS <file> Scan the areas listed in the file + PMSCANALL <file> PM-scan all areas + PMSCANNETMAIL <file> PM-scan all netmail areas + PMSCANTHIS <file> PM-scan the areas listed in the file + QWKIMPORT <file> Import QWK packets + QWKEXPORT <file> Export to QWK + SOUPIMPORT <file> Import SOUP packets + SOUPEXPORT <file> Export to SOUP + IDLETIME <seconds> Number of seconds between checks +

+

+ If SEMAPHORE IDLETIME is defined and non-zero, then GoldED+ will + check this list of semaphore files when the user has not pressed a + key in the specified number of seconds. The semaphores are only + checked when the arealist screen is active. If a semaphore file is + found, the file is deleted and then the action is performed. If no + path is given for the files, the GOLDPATH is assumed. +

+

+ Example: +

+

+ SEMAPHORE SCANALL SCANALL.NOW + SEMAPHORE IDLETIME 30 +

+

+ This causes GoldED+ to check every 30 seconds for the SCANALL.NOW + file in the GOLDPATH, and scan all areas if it's found. +

+ + + + SERIALNO + +

+ Everything mentioned above about REGISTERKEY and REGISTERNAME + applied to this keyword. +

+ +SHAREMODE <yes/no/mode#> +

+ (yes) +

+

+ If enabled, GoldED+ opens all files in a SHARE.EXE compatible mode. +

+

+ The default share-mode is "Share Deny None", but another may be + specified directly if you give the mode number as the keyword + parameter (decimal). +

+

+ It is normally not necessary to change the default. +

+ + + + SOUNDPATH <path> + +

+ (defaults to the GOLDPATH) +

+

+ Tells GoldED+ where to find the sound files for the PLAY and EVENT + keywords. +

+ + + + SOUPBADMSGS <echoid> + +

+ Specifies the area where "bad messages" from SOUP packets can be + tossed. It should be an echomail or newsgroup area. +

+ + + + SOUPEMAIL <echoid> + +

+ Specifies the area where Internet e-mails can be tossed. It must + be a netmail or e-mail area. +

+ + + + SOUPEXPORTMARGIN <margin> + +

+ (76) +

+

+ This is the margin that GoldED+ will hard-wrap to when exporting to + SOUP packets. If you're getting complaints that your lines are too + long, you may want to set this to 70 or 60. +

+

+ NOTE: You should NOT enable EDITHARDTERM in email and newsgroups + that are exported to SOUP. If you do, your messages will probably + be exported with short line "droppings" after the wrapping margin. +

+ + + + SOUPEXPORTPATH <path> + +

+ Path where outgoing SOUP reply packet files (REPLIES and + GOLD*.MSG) can be placed. +

+ + + + SOUPIMPORTPATH <path> + +

+ Path where the incoming SOUP packet files (AREAS and *.MSG) can be + found. +

+ + + + SOUPNEWSRCFILE <file> + +

+ Name with full path of the NEWSRC file which lists the newsgroups + you are connected to. GoldED+ uses the list to mark the matching + areas as newsgroups. These will then be scanned for outgoing mail + when starting a SOUP export. +

+ + + + SOUPREPLYLINKER <cmd> + +

+ Commandline for a replylinker program to call after SOUP import. +

+ + + + SOUPREPLYTO <internet-address> + +

+ Internet-Address other users should use when they respond to your + mails (Reply-To Headerline). +

+ + + + SOUPTOSSLOG <file> + +

+ Name of a file where GoldED+ puts the echoids (newsgroup names) of + each area where articles have been imported. The tosslog file is + intended to be used with a replylinker. If no path is given, it + defaults to the GOLDPATH. +

+ + + + SQUISHDIRECT <yes/no> + +

+ (no) +

+

+ If enabled, then in Squish areas, if the DIR (direct) attribute is + set on a message, GoldED+ will automatically set both the CRA + (crash) and HLD (hold) attributes when saving the message. +

+

+ According to the Squish Developers Kit, this is the way to tell + SquishMail that a message should be routed direct, because + SquishMail does not recognize the FLAGS kludge where the DIR + attribute is normally found. This keyword should probably only be + used with SquishMail (the mail processor) and then only when used + with Binkley or other so-called "static" mailers. DON'T use it + with FrontDoor! +

+ + + + SQUISHSCAN <api/quick> + +

+ (quick) +

+

+ Specfies whether to use a quick scanning method which only looks + in the .SQI files. This will normally work fine, but may fail + slightly in obscure cases, especially when used with Squish 1.0x + or programs using the old version of the MSGAPI. If you suspect + problems, try to set this keyword to "api", which tells GoldED+ to + look in the .SQD file for an exact count of active msgs in the + .SQI file. +

+

+ NOTE: GoldED+ does NOT use the original MSGAPI by Scott Dudley. + Since version 2.50, a completely rewritten implementation is used. +

+ + + + SQUISHUSERNO <index> + +

+ (0) +

+

+ This sets the lastread index number for the Squish *.SQL lastread + files. Lowest number is 0 (zero), highest is (in theory) 65534. +

+

+ If used, this disables the use of USER.BBS to find the index + number, and will in effect also stop GoldED+ from creating USER.BBS + or any new entries in it (useful in a single-user point system). + If a Squish msgbase is shared between several users, and you don't + want to have a USER.BBS (recommended in such a case), each user + must have a unique SQUISHUSERNO in their GOLDED/GOLDAREA.CFG. +

+ + + + SQUISHUSERPATH <path>[file] + +

+ This keyword defines the path where GoldED+ can find and use/create + your USER.BBS file, which is used in connection with the Squish + area lastreads. You can also specify the exact filename if not + USER.BBS. +

+

+ If this path or filename is not defined, GoldED+ will instead take + the one specified with AREAFILE Squish or AREAFILE Maximus + (whichever comes first), or failing that, use the MAXIMUS or + SQUISH environment variables. If even that fails, the AREAPATH or + GOLDPATH is used. If AREAFILE Maximus is used, GoldED+ gets the + filename from MAX.PRM. +

+ + + + STATUSLINECLOCK <yes/no> + +

+ (yes) +

+

+ If enabled, GoldED+ will display a clock in HH:MM:SS format in the + right side of the statusline. +

+

+ You can redefine the clock format with the language keyword + ST_STATUSLINETIMEFMT in GOLDLANG.CFG. See the Language Definition + chapter to details about the date/time codes you can use. +

+

+ NOTE: The clock will only run continuously if KEYBMODE is set to + "poll". +

+ + + + STATUSLINEHELP <yes/no/nologo> + +

+ (no) +

+

+ If set to YES, GoldED+ will replace the "logo" in the left side of + the statusline with a text saying "F1 Help". This is for use in + "point package" setups where the user may be a complete novice, + maybe even to computers, and who needs to be guided to the help + screens. The "F1 Help" text is configurable with the + ST_STATUSLINEHELP language keyword (put it in GOLDLANG.CFG). +

+

+ If set to NO, GoldED+ will display it's logo (name and version) in + the left side of the statusline. +

+

+ If set to NOLOGO, GoldED+ will not display anything in the left + side. The middle part is extended to fill the space on the left + side. +

+ + + + STYLECODES <yes/hide/no> + +

+ (hide) +

+

+ If enabled (yes or hide), GoldED+ will highlight text surrounded by + one of the following characters in a different color: '*' for bold + text, '/' for italic text, '_' for underlined text and '#' for + reversed text. These are commonly used "stylecodes" which add + emphasis to the text, without making it harder to read. Examples: + *This* will be shown in bold color, /this/ in italic color and + _this_ in underlined color. It is also possible to combine styles, + such as */this/*, in bolditalic color. +

+

+ The differ in yes and hide is that hide strips surrounding + stylecodes. +

+

+ Described values are specific to -asa. Official vesions starting + at 3.00beta3 has bug in implementation which causes GoldEd to + ignore this keyword. Realization of this keyword in -asa versions + compatible with official versions prior to 3.00beta3. +

+

+ To define the highlight colors, use COLOR STYLECODE. See the color + chapter for details. +

+ + + + STYLECODEPUNCT <"charlist"> + +

+ (!\"$%&()+,.:;<=>@[\]^`{|}~) + + + + STYLECODESTOPS <"charlist"> + +

+ ("") +

+

+ The STYLECODEPUNCT keyword specifies all the characters that + punctuates words. The stylecode line parser scans forward until it + meets one of these characters and then looks back to see if it + found a word with stylecodes around it. +

+

+ The STYLECODESTOPS keyword specifies characters which, if found + within the word to be highlighted, causes the highlight to be + cancelled. +

+

+ These keywords were added to allow users to experiment with the + characters for punctuation and stop for stylecode sequences. This + is mostly to illustrate the point that it is almost impossible to + make stylecodes work in every case you want without getting a lot + of false highlights too. Please keep in mind that stylecodes are, + and always will be, a primitive and very error-prone method for + adding highlights to message text. The defaults are: +

+

+ STYLECODEPUNCT !\"$%&()+,.:;<=>@[\]^`{|}~ + STYLECODESTOPS +

+

+ Note that the double-quote (") must have the backslash (\) in + front of it - the sequence (\") is translated to a single ("). +

+ + + + TAGLINE <string or filename> + +

+ Defines one or more taglines. A tagline collection filename can be + specified if prepended with an '@' character, like this: TAGLINE + @TAGLINE.LST. If a tagline collection file is used, GoldED+ will + create an index file for it the first time it is used or any time + the file is edited. The index file has the same name, but + extension ".SDX". The index file is an array of 32-bit long + integers, containing the offset of each line in the tagline + collection file. +

+

+ This keyword can be used globally and in a Random System group. +

+

+ Taglines defined in the Random System *always* overrides the + default global taglines defined with this keyword. +

+ + + + TAGLINECHAR <char> + +

+ ('.') +

+

+ Defines the character GoldED+ uses when putting a tagline in your + message. The default is '.'. You should not change this default. + GoldED+ itself only recognizes taglines with '.' or '_' + (underscore). +

+ + + + TAGLINESUPPORT <yes/no> + +

+ (yes) +

+

+ Allows you to turn off the internal tagline support, in case it + turns out to be too buggy or if you want to use one of the many + good external tagline utilties out there instead. +

+ + + + TASKTITLE <string> + +

+ (@longpid) +

+

+ Sets window title in Win32 and OS/2 versions, ignored in other. +

+ + + + TEARLINE <string> + +

+ (@longpid @version) +

+

+ Here you can define your default tearline. The tearline can be up + to 76 chars long (excluding the leading "--- "), but beware that + policies (such as FidoNet ECHOPOL1) may set a significantly lower + limit (around 30). +

+

+ This keyword can be used globally and in a Random System group. +

+

+ Tearlines defined in the Random System *always* overrides the + default tearline defined with this keyword. +

+

+ If your tearline does not contain at least the string "GoldED" or + "GED", GoldED+ will automatically insert it's PID kludge. See also + description of USEPID keyword. +

+ + + + TEMPLATE <file> ["desc"] [match-address] + +

+ (GOLDED.TPL) +

+

+ You can define many different template files. The templates can be + switched using the READchangetemplate (Ctrl-T) popup menu or the + EDITMENU. +

+

+ The optional "desc" can be used to give the templates more + meaningful names like "International template" instead of + non-obvious names like "GOLDED.TPL". If a description is used, it + must appear before the match-address. It must always be enclosed + in quotes, even if it is only one word. +

+

+ The match-address is an address mask (wildcards allowed) which can + be used to tell GoldED+ to select that template if the destination + address on a message you write matches the match-address. The + matching will only take place if the TEMPLATEMATCH keyword has + been enabled. +

+

+ This keyword can be used globally and in a Random System group. In + Random System groups, only the <file> parameter can be used. +

+

+ Templates defined in Random System groups always override the + globally defined templates, except when selected from the EDITMENU + or when automatic template matching is in effect. +

+

+ To override the automatic template matching, start by selecting a + template manually using the READchangetemplate (Ctrl-T) command or + the EDITMENU. +

+

+ Currently only one match-address per template can be specified, + but you can specify several TEMPLATE keywords for the same file. +

+

+ Example: +

+

+ // Use DANSK.TPL for messages to Danish nodes/points. + TEMPLATE DANSK.TPL "Danish" 2:23/* + TEMPLATE DANSK.TPL "Danish" 2:234/* + TEMPLATE DANSK.TPL "Danish" 2:235/* + TEMPLATE DANSK.TPL "Danish" 2:236/* + TEMPLATE DANSK.TPL "Danish" 2:237/* + TEMPLATE DANSK.TPL "Danish" 2:238/* +

+

+ // Use INTERNET.TPL for messages to the WinBoss gateway + TEMPLATE INTERNET.TPL "Internet" 2:230/9316 +

+

+ // Use ENGLISH.TPL for messages to everywhere else + TEMPLATE ENGLISH.TPL "English" * +

+ + + + TEMPLATEMATCH <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will select a template which matches the + destination address on messages that you write. This keyword can + be used globally or in random system groups. +

+ + + + TEMPLATEPATH <path> + +

+ (defaults to the GOLDPATH) +

+

+ Defines the default path for msg templates. Use this if you want + to place templates in a path separate from the GOLDPATH. +

+ + + + TEMPPATH <path> + +

+ Defines the directory where temporary files are placed by GoldED+ + and GoldNODE. +

+

+ This path should *NOT* point to a RAM disk or other volatile + media! +

+

+ GoldNODE uses this path to store a temporary file which can become + as large as the largest index file (GOLDNODE.GXN), so again, don't + point it to a small RAM disk. If GoldNODE cannot find a TEMPPATH, + it will use the NODEPATH instead. +

+ +TIMEOUT <seconds> +

+ (0) +

+

+ Similar to the screen blanking (SCREENBLANKER) feature, GoldED+ can + auto-exit after a specified period of time. Useful if you are in a + hurry (or didn't get enough sleep last night ;-), and run GoldED+ + from your mailer shell. The timeout value can be overridden with + the -T commandline option. +

+

+ NOTE: This feature only works if KEYBMODE is set to "poll". +

+ + + + TIMEOUTSAVEMSG <yes/no> + +

+ (yes) +

+

+ If set to YES, GoldED+ behaves as usual: It saves the (perhaps + partially written) msg text in the internal editor to the msgbase + and exits. If set to NO, GoldED+ will save the msg text in + GOLDED.MSG just as if EDITAUTOSAVE function was in use and the + power went out. Next time you started GoldED+ and entered a msg, it + would detect the "lost" msg and ask you if it should be continued. +

+ + + + TITLESTATUS <yes/no> + +

+ (yes) +

+

+ If enabled then brief status will be added to title. (Win32 and + OS/2 versions only) +

+ + + + TWITMODE <mode> + +

+ (Blank) +

+

+ In GoldED+ you can define several "Twit" names, addresses or + subjects. With this keyword you can specify the action taken when + a Twit message is encountered. +

+

+ The <mode> can be one of the following: +

+

+ Show Show twit messages. + Blank Blank twit messages. + Skip Skip twit messages, unless to your USERNAME's. + Ignore Skip twit messages, always. + Kill Deletes twit messages, *without* confirmation! +

+

+ This keyword can be used globally and in a Random System group. +

+ + + + TWITNAME <name/address> + +

+ With this keyword, you can specify "Twit" names and/or addresses. + When a Twit name/address is detected, the TWITMODE setting will + determine the action taken. +

+ + + + TWITSUBJ <"string"> + +

+ With this keyword, you can specify "Twit" subjects. When a Twit + subject is detected, the TWITMODE setting will determine the + action taken. The subject string is searched in the entire subject + text, so you can specify a partial twit subject. Twit subjects are + limited to maximum 35 characters. +

+ + + + TWITTO <yes/no> + +

+ (no) +

+

+ If enabled, GoldED+ will check both from- and to-names when + checking for twitnames. By default only the from-names are + checked. +

+

+ This is a global keyword and won't work as intended if used in a + random system group. +

+ + + + UNPACKER + +

+ Added ability to READ packed messagebases. You need to add PKD + attribute to such echo definition and specify UNPACKER for the + extension defined. You should pack all files from the single + messagebase to the archive with the same name. For *.msg areas you + should add the directory as well. When entering to the archived area + UNPACKER will be executed to unpack files to TEMPPATH. On exit, all + files will be deleted. + + New UNPACKER keyword have the following syntax: + + UNPACKER >extension< > + + + + USEAREA <yes/no> + +

+ (yes) +

+

+ If set to no then GoldEd will not recognize + + + + USECHARSET <yes/no> + +

+ (yes) +

+

+ If set to no then GoldEd will not generate @CHRS and @CHARSET + kludges. +

+ + + + USEFLAGS <yes/no> + +

+ (yes) +

+

+ If enabled, GoldED+ inserts the FLAGS kludge for certain extended + attributes, as defined in FSC-0053 by Joaquim H. Homrighausen, and + supported by FrontDoor, D'Bridge, IMail and other modern software. + GoldED+ uses FLAGS to emulate the Hold and Freq attributes which + are not defined in the Hudson message format. +

+ + + + USEFWD <yes/no/ask> + +

+ (yes) +

+

+ If enabled, GoldED+ inserts the FSC-0092 kludges introduced by the + author of FleetStreet, Michael Hohner. These are +

+

+ FWDFROM The original From-Name + FWDORIG The original From-Aka + FWDTO The original TO-Field + FWDDEST The original TO-aka (only in netmails) + FWDSUBJ The original subject + FWDAREA The original areatag + FWDMSGID The original MSGID (useful for reply-linking) +

+

+ When forwarding, GoldED+ now adds these kludges, unless the + original message already contains them, in which case they are + preserved. When doing a normal reply (Alt-Q or Alt-R) to a message + with the FWD kludges, GoldED+ replies to the forwarder. To reply to + the from-name in the forwarded message, use the comment-reply + function (Alt-G). If the message contains the FWDAREA kludge, you + can reply to the forwarder in the original area (Alt-N) or reply + to the from-name in the original area (Alt-B). Note that it is not + possible to reply to the to-name of a message with the FWD + kludges, and it is also not possible to reply to the to-name of + the forwarded message (the FWDTO name). +

+ + + + USEINTL <type> + +

+ (yes) +

+

+ The INTL kludge is normally only inserted in netmail messages, if + the origination zone is different from the destination zone (the + "Auto" setting), but on systems with many AKA's in the mailer, it + might be useful/necessary to add it ALWAYS (the "Yes" setting). + The "No" option should never be used. +

+

+ The <type> can be one of the following: +

+

+ Auto Only insert in inter-zone netmail. + Yes Always insert. Recommended and default. + No Never insert. +

+ + + + USEMSGID <yes/no> + +

+ (yes) +

+

+ If enabled, the MSGID kludge is inserted in netmail and echomail, + and the REPLY kludge is inserted when replying to a msg with a + MSGID. +

+

+ The MSGID kludge is defined in FidoNet document FTS-9. +

+ + + + USEPID <yes/no> + +

+ (no if GoldEd mentioned in tearline, yes otherwise) +

+

+ If disabled then @PID kludge will not be used in your messages + regardless of tearline contents. +

+ + + + USERLIST <file> [zone/addr] + +

+ In addition to normal nodelist support, GoldED+ also supports the + "FIDOUSER.LST" style userlist format. The default zone is defined + by the first ADDRESS or AKA, but can be overridden by adding the + zone number or a full address after the filename. +

+

+ <file> Userlist file in FIDOUSER.LST format. + [zone/addr] Default address for the userlist (if no zone info + is present). +

+ + + + USERLISTFILE <file> + +

+ (GOLDED.LST) +

+

+ GoldED+ can generate a list of all users in the current area. This + keyword defines the default name of the FIDOUSER.LST style + userlist output file generated with the READmakeuserlist command. +

+ + + + USERNAME <name>[[,]< >address] + +

+ You can define many different names/aliases. When GoldED+ finds an + un-received message to one of your USERNAME's, it is marked as + received. Useful if you use alias names in some conferences. It is + possible to change the current name using the READchangeusername + popup menu. +

+

+ For msgbase formats with an associated user database, GoldED+ uses + the *first* defined USERNAME to look in the user database for + which lastread record to use. If your name is not found, it is + added and a new lastread record created. +

+

+ Example: +

+

+ USERNAME Odinn Sorensen, 2:236/77.999 +

+

+ This keyword can be used globally and in a Random System group. +

+ + + + USETZUTC <yes/no> + +

+ (no) +

+

+ Activates usage of TZUTC kludge in your messages. You should + properly setup timezone information in your OS. For example, + in DOS you should set environment variable TZ to something + like this: +

+

+ TZ=MSK-3MSD,M3.5.0/02:00,M10.5.0/03:00 +

+

+ This line valid for Moscow, Russia. +

+

+ This option could be used in random system groups. +

+ + + + UUDECODEPATH <path> + +

+ Specifies the path where files are placed when using the uudecode + feature. Files are placed in current directory if a path is not + specified. +

+

+ The specified path *must* exist ! +

+ + + + VIEWHIDDEN <yes/no> + +

+ (no) +

+

+ Hidden lines are "unknown" kludge lines. If enabled, hidden lines + will be displayed (in a different color) when reading msgs. +

+

+ A hidden line is defined as a line which has the FidoNet kludge + char (^a, ASCII 1) as the first char and is not on the list of + internally or user defined known kludges. +

+

+ This keyword can be used globally and in a Random System group. +

+

+ IMPORTANT NOTE: +

+

+ In some conferences the hidden lines are used to give witty + comment "between the lines" in the plain text, but generally it is + considered a bad practice and should be avoided because it may + cause severe technical problems if a witty comment in a hidden + line happens to match a (perhaps experimentally) defined kludge + somewhere. It should also be noted that hidden lines are not kept + in their original places when used in the JAM msgbase. This is due + to the way the JAM specification stores FidoNet kludges. +

+ + + + VIEWKLUDGE <yes/no> + +

+ (no) +

+

+ If enabled, known kludge lines will be displayed (in a different + color) when reading msgs. +

+

+ Known kludges are those defined internally in GoldED+ plus those + defined with the KLUDGE keyword. +

+

+ This keyword can be used globally and in a Random System group. +

+ + + + VIEWQUOTE <yes/no> + +

+ (yes) +

+

+ This is an experimental feature. It is similar to the VIEWHIDDEN + and VIEWKLUDGE keywords, but for quoted text. I implemented it + because I was annoyed with the excessive quoting often seen in + Internet newsgroups. When this keyword is set to NO, GoldED+ + attempts to trim down the quotes so that only the first line of + each quote block is shown. It is not always successful, sometimes + the result is not so useful. +

+

+ A key command has been added to supplement this feature: + READtogglequote. Suggested key assignment: Ctrl-V. Example: +

+

+ ^V READtogglequote +

+

+ Try it out if you are annoyed with excessive quotes. +

+

+ This keyword can be used globally and in a Random System group. +

+ + + + WHOTO <name> + +

+ This name is inserted in the TO: name field, when entering new + messages (not replies) in echomail or local areas. +

+

+ This keyword can be used globally and in a Random System group. +

+ + + + WILDCATUSERNO <userno> + +

+ Defines the lastread set used in the WildCat! 4.x message base. +

+ + + + WRITETEMPLATE + +

+ + + + XLATCHARSET <importid> <exportid> <file> + +

+ This keyword defines character set translation table files. +

+

+ <importid> Charset import identifier. + <exportid> Charset export identifier. + <file> Charset translation table file. +

+

+ See the Character Translation chapter for details. +

+ + + + XLATESCSET <import> <export> <escfile> + +

+ This keyword defines escape sequence translation table files. +

+

+ <importid> Escset import identifier. + <exportid> Escset export identifier. + <file> Escape sequence translation table file. +

+

+ See the Character Translation chapter for details. +

+ + + + XLATEXPORT <charsetid> + +

+ Defines the export charset for your messages. See the Character + Translation chapter for details. +

+

+ This keyword can be used globally and in a Random System group. +

+

+ It can also be used in templates (the @xlatexport token). +

+ + + + XLATIMPORT <charsetid> + +

+ (IBMPC) +

+

+ Defines the local charset for your machine. See the Character + Translation chapter for details. +

+

+ This keyword can be used globally and in a Random System group. +

+ + + + XLATLOCALSET <charsetid> + +

+ (IBMPC) +

+

+ Use this keyword to specify the actual physical charset in effect + for text screen display. This was previously the hardcoded value + IBMPC, corresponding to the IBM codepage 437 (or the nordic + edition 865). +

+

+ NOTE: All charset translation files must translate from and to the + charset identified with the XLATLOCALSET keyword! +

+ + + + XLATPATH <path> + +

+ This is the path where GoldED+ tries to find the XLATCHARSET and + XLATESCSET files. +

+ + + + ZONEGATING <yes/no/ask> + +

+ (ask) +

+

+ When writing a netmail message to a destination in another zone, + you can either send the message directly (No) or via the local + ZoneGate (Yes). You can also be consulted each time (Ask). GoldED+ + won't ask if Cra or Hld attribute is set. +

+

+ + + + + + + Obsolete Keywords + +

+This is a list of keywords which were used in various older versions. +These keywords are now obsolete, either because they have been renamed +or replaced, or if they no longer have any function. Most of the +keywords are still active and remapped to the new names. +

+

+To check if you have obsolete keywords in your setup, run GoldED+ with +the -F -D commandline parameters. Then if you get a number of "Unknown +keyword" warnings, you should replace the old keywords with the new +ones or remove them. +

+

+ Old keyword: New keyword: +

+

+ AREAAUTOFREQ AREAFREQTO + AREABADMSGS SOUPBADMSGS + AREASORT AREALISTSORT + ASSIGNTO MEMBER + AUTOATTACH EDITAUTOATTACH + BLANKTIME SCREENBLANKER + BOARDNOS (removed) + CCATTRIB ATTRIBSCC + CCLIST CARBONCOPYLIST + CFMATTRIB ATTRIBSCFM + CHANGEDATE EDITCHANGEDATE + CHANGEPROMPT (removed) + CHARSET XLATCHARSET + CLEARKEYS (removed) + COLOUR COLOR + COMMENTNOISE BEEPCOMMENT + COOKIEFILE (removed) + CRLFTERM EDITCRLFTERM + DELORIG ASKDELORIG + DISPMSGLIST MSGLISTFIRST + DISPMSGLISTFAST MSGLISTFAST + DISPSTYLECODES STYLECODES + DOSSWAP (removed) + ECHOATTRIB ATTRIBSECHO + ECHOINFO CTRLINFOECHO + EDITMARGIN (removed) + EDITORVERSION (removed) + ELIMSNOW (removed) + ESCSET XLATESCSET + EXCLAREA AREAEXCL + EXPORTCHARSET XLATEXPORT + EXTKEYS (removed) + FIDOLASTREADNO FIDOUSERNO + FIELDCLEAR EDITFIELDCLEAR + FILECHECK (removed) + FILECHECKALL (removed) + FREEAREA (removed) + FREETEAR (removed) + GOLDEDCFM CONFIRMFILE + GOLDEDLOG LOGFILE + GOLDEDLST USERLISTFILE + GOLDEDMSG EDITORFILE + GOLDEDNAM NAMESFILE + GOLDEDPRN OUTPUTFILE + GOLDHELP (no longer documented) + GOLDKEYS (no longer documented) + GOLDLANG (no longer documented) + GOLDRAND (no longer documented) + GOLDXLAT (no longer documented) + HARDLINE EDITHARDLINE + HARDLINES EDITHARDLINES + HWMARKS (removed) + INCLAREA AREAINCL + INTERNALEDITOR EDITINTERNAL + LASTREAD FIDOLASTREAD + LASTREADUSER FIDOUSERNO + LISTWRAP (removed) + LOCALATTRIB ATTRIBSLOCAL + LOCALCHARSET XLATIMPORT + LOCALHIGHLIGHT (removed) + LOCALINFO CTRLINFOLOCAL + LOCALNOISE (removed) + MAPDRIVE MAPPATH + MATCHAKA AKAMATCH + MAXCOLS SCREENMAXCOL + MAXMSGSIZE (removed) + EDITMSGSIZE (removed) + MAXROWS SCREENMAXROW + MIXCASE EDITMIXCASE + MULTIQBBS (removed) + NETATTRIB ATTRIBSNET + NETINFO CTRLINFONET + NETTEAR CTRLINFONET performs similar function + NEXTAREA AREANEXT + NEXTMSGS (removed) + NODELISTPAGEBAR (removed) + NOISEFACTOR (removed) + OVERLAY (removed) + OVERLAYEMS (removed) + OVERLAYEXT (removed) + PAGEBAR (removed) + QBBSINCRESCAN (removed) + QBBSPATH HUDSONPATH + QBBSREBUILD (removed) + QBBSSCAN (removed) + QMSGPATH HUDSONPATH + REALMSGNO (removed) + REBUILD (removed) + RENAREA AREARENAME + REPLYRE EDITREPLYRE + RIGHTMARGIN DISPMARGIN + SAVEMENU EDITSAVEMENU + SAVETIME EDITAUTOSAVE + SAYBIBI (removed) + SCANAREA AREASCAN + SCREENELIMSNOW (removed) + SCREENUSEANSI (removed) + SHADOWS (removed) + SHARE SHAREMODE + SHOWTWITS TWITMODE + SIGNALFILE SEMAPHORE + SOUNDDEVICE (removed) + SPACEQUOTES (removed) + SPELLCHECKER EDITSPELLCHECK + STACKKEYS KEYBSTACK + STARTECHO AREASTART + SWAPALL (removed) + SYSOP USERNAME + TABSIZE DISPTABSIZE + TAGLINEFILE (removed) + TIMESLICE (removed) + TIMEZONEOFFSET USETZUTC performs similar function + UNDELETELINES EDITUNDELETE + USEBIOS SCREENUSEBIOS + XPLIST CROSSPOSTLIST +

+

+ + + + + + Location Dependent Configuration Keywords + +

+The following configuration keywords are location dependent and should +be placed in a particular order in the configuration file(s). Keywords +that are *not* listed can be placed anywhere you want. +

+

+The keywords are listed in groups of those that depend on each other. +They are listed in the recommended order within each group. The order +between the groups is not important, with one noted exception. +

+

+Name/Address/Areas: + USERNAME + ADDRESS + AKA + ATTRIBSNET Specifies default attributes for AREAFILE etc. + ATTRIBSECHO As above. + ATTRIBSLOCAL As above. + FIDOMSGTYPE + PCBOARDPATH Recommended if you use PCBoard. + MAPPATH + AREARENAME Rename occurs before AREAEXCL/INCL. + AREAEXCL + AREAINCL + AREAISEMAIL + AREAISNEWS + AREAPATH Default path for the AREAFILE's. + AREAFILE + RA2USERSBBS Overrides AREAFILE RemoteAccess. + AREADESC Add description and more to some AREAFILE's. + AREA Overrides areas in AREAFILE's. + AREADEF As above. +

+

+Paths: + GOLDPATH + TEMPPATH MUST be in GOLDED.CFG. Used only by GoldNODE. +

+

+Nodelists: MUST be below ADDRESS/AKA and ONLY in GOLDED.CFG! + NODEPATH + NODELIST + USERLIST + EXCLUDENODES Remember to replace "ALL" with '*'. + INCLUDENODES As above. +

+

+Colors: + INTENSECOLORS Selects a default intense colorset if enabled. + COLORSET Selects a default colorset. + COLOR +

+

+External utils: + EXTERNOPTIONS + EXTERNUTIL +

+

+Character translation: + XLATPATH + XLATCHARSET + XLATESCSET +

+

+Random System: + GROUP Starts a group. + MEMBER Defines areas that are members of the group. + <Group Items> See the Random System chapter for a list. + ENDGROUP Ends a group. +

+

+ + + +Message Attributes Reference +

+This is a list and description of all message attributes that are +supported by GoldED+ in the keywords that accept attribute settings or +can be displayed in the header. +

+

+A/S Archive/sent. +ARQ Audit request. +ATT File attached. +CFM Confirmation receipt requested. +COV Fax cover letter. +CRA Crash - high priority mail. +DEL Deleted. +DIR Direct. Don't route this message. +FAX Fax image attached. +FRQ File request. +GRP Group message. +HIR Fax hi-resolution image. +HLD Hold for pickup. +HUB Host- or Hub-route message. +IMM Immediate - Send message NOW! +K/S Kill/sent. Delete message automatically after it is sent. +KFS Kill/file/sent. Delete attached files after they are sent. +LET Fax letterhead. +LOC Local. Message was written on your system. +LOK Lock. Prevents send/delete/purge/editing. +ORP Orphan. Could not be sent because destination node is unknown. +PKD Packed. Used in area definitions to unpack before using. +PRN Msg has been printed. Specific for Squish (bitvalue 00040000h). +PVT Private. Message may only be read by the addressee and author. +R/O Read only. Used in area definitions to prevent writing. +RCV Received. Read by the addressee. +RRC Return receipt. +RRQ Return receipt requested. +RSV FTS-1 reserved (unused) attribute. +SIG Fax signature. +SNT Sent. Message has been sent or exported from the msgbase. +TFS Truncate/file/sent. Truncate files to zero length when sent. +TRS Transit. Message passing through, not for you. +UNS Unsent message. +URQ Update file request. +XMA Xmail. Attach does not conform to the ARCmail 0.60 standard. +ZON Zonegate. Route through zonegate if possible. +

+

+ + + +Area Configuration +

+GoldED offers a wide variety of methods for defining message areas. +You can define each area manually in the GOLDED.CFG file (or an +INCLUDE'ed GOLDAREA.CFG file), or you can tell GoldED+ to read the area +setup files of many popular BBS/mailer/mail processor packages. +

+

+For manual definition of areas, use the AREA or AREADEF (recommened) +keywords. +

+

+For external area configuration, the general syntax for the AREAFILE +keyword is: +

+

+ AREAFILE <programname> [path or filename(s)] [-options] +

+

+Available options: +

+

+-S<sortspec> +

+

+ If you are *not* using the global AREALISTSORT keyword for sorting + all the areas, you can sort the areas of each AREAFILE separately. + See the AREALISTSORT keyword for the definition of <sortspec>. +

+

+If no path is specified, the appropriate environment variable or the +AREAPATH is used to find the files. +

+

+The <programname> can be one of the following: +

+ + + AdeptXBBS + +

+ Reads the AdeptXBBS configuration files. +

+

+ Looks for the ADEPTXBBS environment variable. +

+ + + + AreasBBS + +

+ GoldED+ is can handle a wide variety of AREAS.BBS type files. It + can read and distinguish between the old CONFMAIL style with paths + for *.MSG areas, the Hudson/Goldbase style with board numbers, the + Squish style with "$basename" and the JAM style with "!basename". +

+

+ The disadvantage of using an AREAS.BBS is that there are no area + descriptions. The echoid is used as description instead. However, + GoldED+ will use any text behind a semicolon on definition lines as + description. This may or may not be compatible with mail + processors, so be careful. A better solution may be to use the + AREAFILE Echolist to add descriptions from a separate file. +

+

+ One or more AREAS.BBS files may be specified on the same line. +

+ + + + Concord + +

+ Support is planned but not yet implemented. +

+ + + + Crashmail + +

+ Reads the CrashMail II configuration file. +

+ + + + D'Bridge + +

+ Reads the DBRIDGE.AA1/.AA2 files (for version 1.30) or the + DBRIDGE.ADF of the later versions. +

+

+ Looks for the "DBRIDGE" and "DB" environment variables. +

+ + + + Dutchie + +

+ Reads the DUTCHIE.ARE file. +

+

+ Looks for the "DUTCHIE" environment variable. +

+ + + + Echolist + +

+ Reads a simple ascii-text file containing an echolist in this + format: +

+

+ <echoid> <description> +

+

+ or DZ-format (requires -DZ switch): +

+

+ [Status], Tag, Comment, Moderator's Name, Address,[Flags] +

+

+ This feature adds descriptions to already existing areas in + GoldED+. Example: +

+

+ AREAFILE AreasBBS AREAS.BBS + AREAFILE EchoList ECHOLIST.TXT + AREAFILE EchoList echo5020.lst -dz +

+

+ Descriptions for unknown echoids are ignored. Blank lines and + lines beginning with characters which are illegal in echoids (such + as ';') are also ignored. +

+

+ Additional switch -SqaFix could be used to read echolist and groups + from SqaFix configuration file: +

+

+ AREAFILE Squish C:\SQUISH\ + AREAFILE EchoList C:\SQUISH\SQAFIX.CFG -SqaFix +

+ + + + Ezycom + +

+ Reads CONFIG.EZY and MESSAGES.EZY. Supports Ezycom 1.02 and 1.10g, + but not 1.01. +

+

+ Looks for the "EZY" and "TASK" environment variables. +

+ + + + FastEcho + +

+ Reads the FASTECHO.CFG file. Supports version 1.10 up to 1.46. +

+

+ Looks for the "FASTECHO" environment variable. +

+ + + + Fidoconfig + +

+ Reads fidoconfig (used in Husky Project software). Supports + version 0.15. Used parser is more powerful than original from + fidoconfig, due to it strictly follows specification from proposal + and implements all features from there. Additionaly it implements + groups not described in proposal but used in in library. +

+

+ Looks for the "FIDOCONFIG" environment variable. +

+ + + + FidoPCB + +

+ Reads FIDOPCB.CFG. Supports version 1.x. +

+

+ Looks for the "FIDOPCB" environment variable. +

+ + + + FMail + +

+ Reads FMAIL.CFG and FMAIL.AR. Supports versions 0.92, 0.98, 1.0g, + and 1.20. +

+

+ Looks for the "FMAIL" environment variable. +

+ + + + FrontDoor + +

+ Reads the SETUP.FD/FD.SYS and FOLDER.FD/FOLDER.SYS files. If you + want the real echoid's attached to the areas, you will also need + to supply the filename of the relevant AREAS.BBS file(s). Supports + versions 1.99c and 2.xx. +

+

+ Looks for the "FD" environment variable. +

+ + + + GEcho + +

+ Reads SETUP.GE and AREAFILE.GE. Supports versions 1.00, 1.02, + 1.10, 1.11 and 1.20. +

+

+ Looks for the "GE" environment variable. +

+ + + + IMAIL + +

+ Reads the IMAIL.CF and IMAIL.AR files. Supports version 1.60, + 1.7x and 1.8x. +

+

+ Looks for the "IMAIL" environment variable. +

+ + + + InterMail + +

+ Reads the FD.SYS/IMSYS.CFG and FOLDER.CFG/IMFOLDER.CFG files. + Supports version 2.26 and newer. +

+

+ Looks for the "IM" environment variable. +

+ + + + LoraBBS + +

+ Reads the CONFIG.DAT and SYSMSG.DAT files. Supports version 2.33, + 2.40 and possibly others. +

+

+ Looks for the "LORA" and "LORABBS" environment variables. +

+ + + + Maximus + +

+ Reads the MAX.PRM and AREA.DAT or MAREA.DAT files. Compatible (or + should be) with both the old (1.xx) and (2.xx) and new (3.xx) + formats. If your AREA.DAT is named differently, you must supply + the correct filename. +

+

+ Looks for the "MAXIMUS" environment variable. +

+ + + + ME2 + +

+ Reads the old ME2 editor AREADESC.ME2 file and AREAS.BBS file(s). + You must supply the names of both files. +

+ + + + Opus + +

+ Reads the Opus 1.1x SYSTEM??.DAT files or the Opus 1.7x SYSMSG.DAT + file. +

+

+ Looks for the "OPUS" environment variable. +

+ + + + ParToss + +

+ Reads the ParToss configuration file. +

+ + + + PCBoard + +

+ Reads the PCBOARD.DAT, CNAMES.@@@ and CNAMES.ADD files. Supports + version 14.x and 15.x, up to and including 15.22. Note that, + depending on the version, echoid's may not be read from this + format. If the echoid is not available, the description is used as + echoid, after conversion to uppercase and spaces to underscores. +

+

+ Looks for the "PCBOARD" environment variable. +

+ + + + Portal + +

+ Reads the PORTAL*.CFG and PORTAL.ARE files. +

+

+ Looks for the "POPCMDLINE" environment variable. +

+ + + + ProBoard + +

+ Reads MSGAREAS.PB. Supports version 2.0. +

+

+ Looks for the "PB" environment variable. +

+ + + + QEcho + +

+ Reads /etc/qecho/AreaList. Supports version patched by Eugene + Sorochinsky for JAM messae base support. +

+ + + + QFront + +

+ Reads QORIGIN.DAT and QECHOS.DAT. Supports version 1.13b. +

+

+ Looks for the "QFRONT" environment variable. +

+ + + + QuickBBS + +

+ Reads the CONFIG.BBS or QUICKCFG.DAT and MSGCFG.DAT files. To get + the real echoid's, you must also supply the filename of the + relevant AREAS.BBS. +

+

+ Looks for the "QUICKBBS" and "QBBS" environment variables. +

+ + + + RaEcho + +

+ Reads AREAS.RAE. Supports version 1.00 and 1.01. +

+

+ Looks for the "RAECHO" environment variable. +

+ + + + RemoteAccess + +

+ Reads the MESSAGES.RA file. To get the real echoid's, you must + also supply the filename of the relevant AREAS.BBS. Supports + versions 0.xx, 1.xx, 2.0x and 2.5x. +

+

+ Looks for the "RA" environment variable. +

+ + + + Squish + +

+ Reads SQUISH.CFG and AREAS.BBS (if used). Supports version 1.0x + and 1.1x. The "Include <filename>" feature of Squish 1.10 is also + supported. +

+

+ The optional /G switch specifies the default group of the imported + areas, i.e. /g=G or /g=#103. +

+

+ Looks for the "SQUISH" and "MAXIMUS" environment variables. +

+ + + + SuperBBS + +

+ Reads CONFIG.BBS, SCONFIG.BBS and BOARDS.BBS. Supports version + 1.16 and 1.17. +

+

+ Looks for the "SUPERBBS" and "SBBS" environment variables. +

+ + + + timEd + +

+ Reads TIMED.CFG and any included file. Also reads the + configuration from other mail software defined in TIMED.CFG. +

+

+ Looks for the "TIMED" environment variable. +

+ + + + Termail + +

+ This is for the Terminate Mail system (Termail). GoldED+ does + currently only support Termail 4.00 und 5.xx style .CFG-files. +

+

+ Reads TM.CFG and any AREAFILE (an AREAS.BBS type file) defined + there. +

+

+ NOTE: If you use this, you must start GoldED+ in the Termail + directory, because the standard TM configuration files use + relative paths. +

+

+ Looks for the "TM" environment variable. +

+ + + + TosScan + +

+ Reads the FD.SYS/SETUP.FD and AREAFILE.FD files. Supports version + 1.00 and FrontDoor 1.99c and 2.xx. +

+

+ Looks for the "FD" environment variable. +

+ + + + WaterGate + +

+ Reads the WTRCFG.TDB and AREABASE.TDB files. Supports version + 0.93. +

+ + + + WMail + +

+ Reads the WMAIL.PRM and AREAS.PRM files. Supports version 2.2. +

+

+ Looks for the "WMAIL" environment variable. +

+ + + + XMail + +

+ Reads the AREAS.XM file. Supports version 1.00. +

+

+ Looks for the "XM" environment variable. +

+ + + + +The Random System +

+With the Random System, you can define area-specific sets of origins, +tearlines, templates, usernames and many other items. If +more than one item of each type is specified, a random one is picked - +a Random System. This is a very useful feature when (for example) +participating in conferences with different languages. +

+

+The Random System is built on the idea of "groups". A group is a +collection of "items", belonging to the group. You can assign one or +more echomail areas, designated by their echoid's to a group. Groups +can also be specified for just a single echo, and DOS/4DOS-style +wildcards can be used to simplify the assignment of echoes with common +strings in their name, such as *.DK, SIG.* and so on. In this way, you +could for example setup one group for all national echoes, another for +special local echoes, a third for international echoes etc. +

+ + + Defining Groups + +

+The general syntax of a group definition is: +

+

+GROUP <id>[:] + ; items go here + [Member <id list>] +ENDGROUP +

+

+The Group <id> can be one of three things: +

+

+1. A group letter or #number, matching the group letters or numbers + used in the AREAFILE's of D'Bridge, GEcho, IMAIL, TosScan and many + others. To use this feature, you need to enable the AREAFILEGROUPS + keyword. +

+

+2. An individual echoid or echoid mask (wildcards can be used). The + items are then simply defined below the Group line. +

+

+3. A group label, terminated by a colon (:). The group items are + defined below the Group line. Echoes are assigned to the group by + adding one or more Member statements. +

+

+You can't assign a group to another group. It will not harm, but it +also won't work :-) +

+

+The order of groups is very important. GoldED+ scans the groups from +the top down. This means that the most general groups must be placed +at the bottom and exceptions (individual areas for example) must be +placed at the top. +

+ + + + Defining Random Items + +

+The random items are defined much like in the main GoldED+ +configuration file. +

+

+If more than one of each item is defined within a group, those items +will be picked randomly (hence the name "Random System"), while GoldED+ +collects items when entering an area. +

+

+ Random Item Keywords: , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + , + . +

+

+See the Configuration Keyword Reference chapter for details about each +keyword. +

+ + + + Random System Example + +

+Below is an example of how a Random System could be setup. Note how +the letter group 'D' goes first, followed by the explicit group +definitions for the NERDS and FOO echoes. Then comes the more general +groups (those with Label:'s), where the echoes are assigned with one +or more Member statements. At last there is the catch-all "Group *", +which works as the default group. +

+

+=== Cut, GOLDRAND.CFG === +

+

+Group NERDS ; For the NERDS echo. + Origin "I am a Nerd. Take me to your Loser!" +

+

+Group FOO ; This group is *only* for the FOO echo. + Tearline FooED @rev + Origin "Foo-ing my day away" +

+

+Group FooEchoes: + Member *FOO* ; Use wildcards to catch any other foo echo. + Tearline FooED @rev + Origin "This is a Foo-lish origin" +

+

+Group FidoNet: + Member NET_DEV, WORLDPOL, INTERCOOK + Member GREEN.029, C_ECHO, C_PLUSPLUS + Origin "Fight-O-Net? Good name..." + Template FIDONET.TPL + Whoto Everyone +

+

+Group SigNet: + Member SIG.* ; The wildcard is VERY handy here ;-) + Origin "To SIG or not to SIG..." + Template SIGNET.TPL +

+

+Group D ; Letter D for Danish echoes. + Template DANSK.TPL +

+

+Group * ; This is default group + Origin "Yet another forgotten echo" +

+

+=== Uncut === +

+

+See the example GOLDRAND.CFG in the ADVANCED archive for a real-life +setup similar to the one I use myself. +

+ + + + + + + The Color Configuration + +

+Color configuration in GoldED+ is a bit complicated, and you probably +have to experiment quite a bit, if you want make your own setup. For +your convenience, I have added a number of example color setups, +provided by some of my many good users. I suggest you try them all and +use the one that suits you best, perhaps tuning it a bit to your +taste. +

+

+The COLOR keyword uses the following syntax: +

+ + + COLOR <window> <part> <colors> + +

+ <window> AREA, ASK, BACKGROUND, BRAG, HEADER, HELP, INFO, MENU, + READER, SHADOW, STATUS. +

+

+ <part> BLOCK, BORDER, BTYPE, EDIT, HIDDEN, HIGHLIGHT, INPUT, + KLUDGE, NOSELECT, ORIGIN, QUOTE, SELECTOR, TEARLINE, + TITLE, WINDOW. +

+

+The <colors> are composed of [blinking] <ink> [on <paper>]. +

+

+ <ink> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey, + DGrey, LBlue, LGreen, LCyan, LRed, LMagenta, Yellow, + White. +

+

+ <paper> Black, Blue, Green, Cyan, Red, Magenta, Brown, LGrey. +

+

+For monochrome setups we instead have: +

+

+ <ink> Normal, Highlight, Reverse, Underline. +

+

+The SHADOW color does not need a <part>, because it is global. +

+

+The paper color always defaults to Black if not specified. +

+

+If <part> is "BTYPE", the <color> is a value in the range 0-3, which +defines the type of lines used when drawing menus and windows: +

+

+BTYPE 0 is single horizontal and single vertical lines. +BTYPE 1 is double horizontal and double vertical lines. +BTYPE 2 is single horizontal and double vertical lines. +BTYPE 3 is double horizontal and single vertical lines. +

+

+The default border type is always BTYPE 0. +

+

+The following is a description of the different window parts: +

+ + + + Various general color items + +

+ SHADOW Shadow below windows and menus. + STATUS WINDOW Status line at the bottom. + BACKGROUND WINDOW Background for the startup window. + BACKGROUND BORDER Overscan color (currently DOS only). +

+

+ <anything> PAGEBAR Pagebar (scrollbar). +

+

+ The PAGEBAR color specifially sets the color of the pagebars + (scrollbars) in GoldED+. A pagebar color can currently be set for + AREA, READER and MENU. Note that BORDER will set both the BORDER and + PAGEBAR colors, so remember to place the PAGEBAR color below the + BORDER color. +

+ + + + Startup screen / logo window + +

+ BRAG WINDOW The Copyright window. + BRAG BORDER Lines around the Copyright window. + BRAG TITLE The logo text. + BRAG HIGHLIGHT The inner logo lines. + BRAG BLOCK The outer logo lines. + BRAG BTYPE Copyright window border type. +

+ + + + Area Selection Menu + +

+ AREA WINDOW Descriptions, the top line (inc. search). + AREA BORDER Lines. + AREA TITLE Titles on the border. + AREA SELECTOR Selection bar. + AREA HIGHLIGHT The color for the area marks. + AREA BTYPE Window border type. +

+ + + + Message Header + +

+ HEADER WINDOW Header text. + HEADER BORDER Lines. + HEADER TITLE Titles on the border. + HEADER INPUT Message number input field. + HEADER EDIT Header input fields. + HEADER HIGHLIGHT Marks. + HEADER BTYPE Window border type. + HEADER FROM Header From field. + HEADER TO Header To field. + HEADER SUBJECT Header Subject field. +

+

+ The FROM/TO/SUBJECT colors supplement the HEADER WINDOW color. Note + that WINDOW will also set the FROM/TO/SUBJECT colors, so remember to + place the new colors below it. +

+ + + + Message Text + +

+ READER WINDOW Normal message text. + READER BORDER The Pagebar. + READER QUOTE (Odd) Quoted lines. + READER QUOTE2 (Even) Quoted lines. + READER CURSOR Character at cursor pos. (int. editor). + READER KLUDHIDD Kludges and hidden lines. + READER TEARORIG Tearline and Origin. + READER BLOCK Block color (internal editor). + READER BTYPE Window border type. + READER HIGHLIGHT Search highlight in the message text. + READER KLUDGE Known kludges. + READER HIDDEN Hidden lines. (Unknown kludges). + READER SIGNATURE Internet-Style signatures ("-- "). + READER TAGLINE Taglines. (Only the one just above tearline). + READER TEARLINE Tearline. + READER ORIGIN Origin. +

+

+ The KLUDGE/HIDDEN colors replaces the old KLUDHIDD color. Note that + KLUDHIDD will set both the KLUDGE and HIDDEN colors, so remember to + place the new colors below it if you keep the old definition. +

+

+ The TAGLINE color is the color of taglines. GoldED+ detects a tagline + if it starts with "..." or "___" and is just above the tearline or + origin. +

+

+ The TEARLINE/ORIGIN colors replaces the old TEARORIG color. Note + that TEARORIG will set both the TEARLINE and ORIGIN colors, so + remember to place the new colors below it if you keep the old + definition. +

+ + + + Miscellaneous Smaller Menus + +

+ ASK WINDOW Menu items. + ASK BORDER Lines. + ASK TITLE Menu title. + ASK SELECTOR Selection bar. + ASK NOSELECT Non-selectable menu items. + ASK HIGHLIGHT Hotkeys. + ASK BTYPE Window border type. +

+ + + + Miscellaneous Larger Menus (Browser Windows) + +

+ MENU WINDOW Menu items. + MENU BORDER Lines. + MENU TITLE Menu title. + MENU SELECTOR Selection bar. + MENU NOSELECT Non-selectable menu items. + MENU HIGHLIGHT Hotkeys/marks. + MENU UNREAD When a msg is unread. + MENU UNREADHIGH Additional highlight of to/from. + MENU UNSENT When a msg is unsent. + MENU UNSENTHIGH Additional highlight of to/from. +

+ + + + Help Screens + +

+ HELP WINDOW Help text. + HELP BORDER Lines. + HELP SELECTOR Current keyword. + HELP HIGHLIGHT Other keywords. + HELP BTYPE Window border type. +

+ + + + Pop Up Information Windows + +

+ INFO WINDOW Window text. + INFO BORDER Lines. + INFO TITLE Info title. + INFO BTYPE Window border type. +

+ + + + Stylecodes + +

+ STYLECODE ALL All stylecodes at once. + STYLECODE B *Bold* + STYLECODE I /Italic/ + STYLECODE BI /*BoldItalic*/ + STYLECODE U _Underline_ + STYLECODE BU _*BoldUnderline*_ + STYLECODE IU /_ItalicUnderline_/ + STYLECODE BIU _/*BoldItalicUnderline*/_ + STYLECODE R #Reverse# + STYLECODE RB *#ReverseBold#* + STYLECODE RI /#ReverseItalic#/ + STYLECODE RBI /*#ReverseBoldItalic#*/ + STYLECODE RU _#ReverseUnderline_# + STYLECODE RBU _*#ReverseBoldUnderline#*_ + STYLECODE RIU _/#ReverseItalicUnderline#/_ + STYLECODE RBIU _/*#ReverseItalicUnderline#*/_ +

+

+ Note that stylecode color definitions must be placed below COLOR + READER WINDOW, because it overrides the COLOR STYLECODE definitions. +

+

+See the GEDCOL*.CFG and GEDMON*.CFG files for examples of color +configuration. +

+ + + + + + + The Message Template + +

+The message template gives you a ready-made skeleton for writing your +messages in the editor. The template is one of GoldED+'s many strong +features. With this, you can eliminate the tedious typing of greetings +etc etc. GoldED+ also provides a number of replacement strings, +"tokens", to dynamically add message specific information to the +template. +

+

+As in the configuration file, a semicolon (;) first on the line makes +the line a comment. Any other line is put into the editor file, after +token expansion. Tokens are not case sensitive. +

+

+The following is a list of the tokens available: +

+ + + Conditional tokens + +

+ (these are replaced with a null string) +

+

+@changed Line is only inserted in Changed msgs (from others). +@comment Line is only inserted in Reply-Comments. +@echo Line is only inserted in Echomail. +@forward Line is only inserted in Forwarded messages. +@local Line is only inserted in Local messages. +@moderator Line is only inserted if substring "moderator" appeared in + from line. +@moved Line is only inserted in Reply-Moved messages. +@net Line is only inserted in Netmail. +@new Line is only inserted in New messages (not replies). +@position Specifies the starting line for the editor cursor. +@quotebuf Line is only inserted in Quotebuffered msgs. +@quoted Line is only inserted in Quoted replies. +@reply Line is only inserted in Non-Quoted Replies. +

+ + + + Insert tokens + +

+ (anything else on the line is ignored) +

+

+@attrib <attributes> - Adds specific message attributes. +@include <filename> - Inserts the file. +@forcefrom <"from"> - sets message FROM: field, even if non-empty + (see @setfrom) +@forcesubj <"subject"> - sets message SUBJ: field, even if non-empty + (see @setsubj) +@forceto <"to"> - sets message TO: field, even if non-empty + (see @setto) +@loadlanguage Loads a partial language config file. +@message Inserts the original message (in Forward & Change). +@quote Inserts a quote of the original message. +@random [random.txt] - Inserts random text. +@setfrom <"from"> - Sets the message FROM: field. +@setsubj <"subject"> - Sets the message SUBJ: field. +@setto <"to"> - Sets the message TO: field. +@xlatexport <charset> - Sets the export charset. +

+ + + + Replacement tokens + +

+ (replaced with message specific data): +

+

+@c3daddr Current user 3D (boss) address. +@caddr Current user address. +@cdate Current date. +@cdesc Current area description. +@cecho Current echoid. +@cfname Current user first name. +@clname Current user last name. +@cname Current user name. +@cpseudo Current pseudonym given by NICKNAME keyword, or @cfname. +@ctime Current time. +@ctzoffset Current timezone offset (if available and enabled). +@d3daddr Destination 3D (boss) address. +@daddr Destination address. +@dfname Destination first name. +@dlname Destination last name. +@dname Destination name. +@dpseudo Destination pseudonym (see addressbook), or @dfname. +@f3daddr Current from 3D (boss) address. +@faddr Current from address. +@ffname Current from first name. +@flname Current from last name. +@fname Current from name. +@fpseudo Current from pseudonym (see addressbook), or @ffname. +@longpid Long program id. "GoldED", "GoldED/2" or "GoldED/386". +@o3daddr Original 3D (boss) address. +@oaddr Original address. +@odate Original date. +@odesc Original area description if moved, else current. +@oecho Original echoid if moved, otherwise current. +@ofname Original first name. +@ofrom Original RFC "From" headerline. +@olname Original last name. +@omessageid Original RFC "Message-ID" headerline. +@omsgid Original MSGID kludge content. +@oname Original name. +@opseudo Original pseudonym (see addressbook), or @ofname. +@origin The current global or Random System origin. +@os2slash "/2" if running GoldED+/2. Empty otherwise. +@osslash same as above. +@otime Original time. +@otzoffset Original timezone offset (if available and enabled). +@oto Original RFC "To" headerline. +@pid Short program id. "GED", "GED/2" or "GED386". +@pseudo pseudonym (see addressbook), or @tfname. +@rev The revision number (in the form mmdd). +@serialno Emptiness. +@subject The message subject line. +@t3daddr Destination to 3D (boss) address. +@taddr Destination to address. +@tagline The current global or Random System tagline. +@tearline The current global or Random System tearline. +@tfname Destination to first name. +@tlname Destination to last name. +@tname Destination to name. +@tpseudo Destination to pseudonym (see addressbook), or @tfname. +@ver The simple version number (in the form x.yy) +@version The complete release version number of GoldED+. +@_caddr Current user address (fixed width: 19 chars). +@_cname Current user name (fixed width: 34 chars). +@_daddr Destination address (fixed width: 19 chars). +@_dname Destination name (fixed width: 34 chars). +@_oaddr Original address (fixed width: 19 chars). +@_oname Original name (fixed width: 34 chars). +@_taddr Destination to address (fixed width: 19 chars). +@_tname Destination to name (fixed width: 34 chars). +

+

+Tokens dealing with names may optionally have two parameters (each +parameter enclosed in curve brackets): your name and opponent name, +destination name additionally accepts third parameter - WhoTo name. +Here is example on how this feature could be used: +

+

+ @oname{I}{You} wrote to @dname{me}{you}{everyone}: +

+

+The template text begins at the first non-comment line. +

+

+See the included GOLDED.TPL for example usage. +

+

+If you need to put some text which contains one of these tokens into a +template file, use an extra '@' in front of the token. +

+

+Example: +

+

+ Internet: somebody@veryhot.com +

+

+would produce +

+

+ Internet: somebody2.51yhot.com (because @ver is a token) +

+

+so write it like this instead: +

+

+ Internet: somebody@@veryhot.com +

+

+The double '@' will then be translated to a single, and token +translation skips past the @token. +

+ + + + + + + The Online Help System + +

+GoldED has a built-in context sensitive help system, tied to the <F1> +key (one of the very few keys that cannot be reconfigured). It +contains a complete keyboard reference and help for most situations. +It is current not as complete or sophisticated as I'd like it myself, +but this may be improved in future versions. +

+

+You can completely redefine the help screens if you wish - the +GOLDHELP.CFG file is a plain ASCII text file which contains all help +definitions. The help file is split into several help categories. Here +is an example of a couple of defined help categories: +

+

+ *B 1,Help Category 1 + help text help text help text + help text help text help text + *P + help text help text help text + help text help text help text + *E +

+

+ *B 2,Help Category 2 + help text help text help text + help text help text help text + *P + help text help text help text + help text help text help text + See also: ^Help Category 1^ + *E +

+

+The "*B" indicator specifies the beginning of a help category. The +format is "*B helpcatnumber[,helpcatname]". In GoldED+ the help +categories are numbered 1000-9999, split into more or less logical +groups. See the help file for assignments. There should be only one +space between the "*B" and the help category number. The help category +name is only required for cross-references. If there are no +cross-references to that help category, then you can leave the +helpcatname parameter out. +

+

+The "*P" indicator specifies a page break and is optional. You may +have as many page breaks as you'd like. The "*E" indicator specifies +the end of the help category. The "*B", "*P", and "*E" indicators must +all begin in the first column. These indicators and the help category +name are case insensitive (can be in lowercase, uppercase, or mixed). +

+

+In the definition of Help Category 2, you will notice the +crossreference to Help Category 1. All cross-referencing is done by +embedding the cross- reference category name (not number) inside +carats (^). If you need to display a carat inside the help file, use a +double carat (^^). +

+

+Any text contained outside of the "*B" and "*E" is treated as +comments. If an "*E" is not found, then the end-of-file will be +treated as an "*E". +

+

+Not all of the help categories in this help file are actually used in +the current version of GoldED+. The ones not used are empty, except for +a two-line "header". +

+

+The usable dimensions of the help window are 60 columns by 16 lines. +In the help file there is a model of the actual window. +

+ + + + + + Character Translation + +

+GoldED implements several different proposals for character +translation in imported and exported messages: +

+ + + FSC-0050 "Charset Identifier" + +

+ by Thomas Sundblom. + + + + FSC-0051 "I51" + +

+ by Thomas Gradin. + + + + FSC-0054 "CHARSET proposal" + +

+ by Duncan McNutt. + + + + No FSC "Composed Characters" + +

+ by Andre van de Wijdeven. +

+

+FSC-0050 is currently known to be implemented in the OPMED 3.xx +message editor, and in Opus 1.7x. It uses the same identifier as +FSC-0054 (a ^aCHARSET kludge), but is a lot simpler (but not +necessarily better). +

+

+The "I51" and "CHARSET" proposals are in the process of being merged +to one proposal, which should combine the advantages of both. They are +both based on using the LATIN-1 (also known as ISO 8859-1) character +set for extended ASCII. The LATIN-1 set is the same set used by +Windows 3.xx, Amiga and many other non-PC computers. In addition to +LATIN-1, I51 defines a set of so-called escape sequences for +characters not found in the LATIN-1 set. +

+

+"Composed Characters" became quite popular in Holland, but the author +decided to drop his proposal because it relied on escape sequences +using the so called "soft-cr" (141d, 8Dh) character. GoldED+ will +continue to support Composed as long as it seems necessary. +

+

+If you want to know more about the details, I suggest you read the +proposals or contact the authors. +

+

+GoldED currently supports two types of translation tables, the *.ESC +files and the *.CHS files. +

+ + + + The ESC translation tables + +

+The *.ESC files are used for import translation of the escape +sequences defined in I51 and Composed Characters. +

+

+In the ESC files, the semicolon is used for comments. The *first* +non-comment line defines the charset the escape code are mapped TO. +This is normally IBMPC, and should not be changed. Any other +non-comment line is treated as an escape sequence definition with this +syntax: +

+

+ <esc1><esc2><space><map chars>[; comment/description] +

+

+Leading spaces are *not* allowed in ESC files. <esc1> and <esc2> are +the two characters that define the escape sequence. <space> is ignored +and can be used to make the table look better. <map chars> defines the +local representation of the escape sequence, up to three characters. +Normally you would only map to one extended ascii character. The map +chars can be either the characters themselves, or decimal or +hexadecimal numbers of the form "\d<dec>" or "\x<hex>" (like in the C +programming language). +

+ + + + The CHS translation tables + +

+The *.CHS files are used for import and export translation of the +CHARSET type character sets, and export of I51 and Composed escape +sequences. +

+

+The CHS files uses the format of the raw text files provided in the +CHARSET3.ZIP example implementation of FSC-0054. Study some of the +files provided if you want to know how to define them. +

+

+The two keywords XLATESCSET and XLATCHARSET are used to define which +files belong to what import and export set. You can define more than +one import and export set for each file. +

+

+The keyword XLATIMPORT defines which charset you have on your own +machine - this would normally be "IBMPC". It can be useful to change +this (using the Random System) in areas where another character set +than IBMPC is the dominant (like Amiga or MacIntosh, whatever). +

+

+The keyword XLATEXPORT defines the charset your messages should be +exported to, if any. +

+

+Confused? Yeah, I know - this is a confusing subject, and my +implementation and documentation is not perfect. Normally you will not +have to worry about it. Turn it off completely if you don't understand +it. +

+ + + + + + + Keyboard Command Reference + +

+Most of the GoldED+ keyboard commands can be reached with just one +keystroke. To ease operation for experienced users of other message +editors, GoldED+ comes with several sets of keys for each of the +keyboard commands - direct non-shifted keys, Alt/Ctrl-keys and +function keys. Many of these key assignments will be familiar for +users of Msged, Msged/Q, ME2 and FM. +

+

+The following is a list of all keyboard commands, sorted by type and +alphabetically, using the format +

+

+ <command> <short description> +

+

+This list is also available in the context-sensitive help system on +the <F1> key. +

+

+It is possible to almost completely redefine the keyboard - this in +done in the GOLDKEYS.CFG file, which also handles macro definition +(see later). +

+ + + Arealist Commands + +

+AREAabort Abort the arealist. +AREAaskexit Exit GoldED+, prompt for final decision. +AREAboardnos Toggle sequential areas vs. board numbers. +AREAcatchup Point the lastread pointer to the last message + in the current area. +AREAdosshell Shell to DOS. +AREAdropmsgmarks Unmark all msgs in selected areas. +AREAgotofirst Move selection bar to first area. +AREAgotolast Move selection bar to last area. +AREAgotonext Move selection bar to next area. +AREAgotoprev Move selection bar to previous area. +AREAheat Heat highwatermarks. +AREAjump Move selection bar to next marked area. +AREAjumpnextmatch Move selection bar to next matching area. +AREAquitnow Exit immediately, no questions asked. +AREAscan Scan areas. +AREAscanpm Scan areas for personal mail. +AREAselect Enter the reader for the selected area. +AREAselectmarks Select which set of area marks should be used. +AREAsoundkill Stops currently played sound file. +AREAtoggle Toggle mark on the selected area. +AREAtouchnetscan Touches the SEMAPHORE NETSCAN file. +AREAwritegoldlast Write a fresh copy of GOLDLAST.LST +AREAzap Zap highwatermarks. +

+ + + + Internal Editor Commands + +

+EDITabort Abort editing this message - ask first. +EDITanchor Set a block "anchor" on the current line. +EDITaskexit Exit from GoldED+ - ask first. +EDITblockdown Extend block area one line down. +EDITblockend Extend block area to the end of line. +EDITblockhome Extend block area to the beginning of line. +EDITblockleft Extend block area one character left. +EDITblockpgup Extend block area one screen up. +EDITblockpgdn Extend block area one screen down. +EDITblockright Extend block area one character right. +EDITblockup Extend block area one line up. +EDITcleardeletebuf Clears the undelete buffer. +EDITclearpastebuf Clears the cut'n'paste buffer. +EDITcopy Copies the block to the cut'n'paste buffer. +EDITcopyabovechar Inserts character same as in the same position + in previous line. +EDITcut Cut the block to the cut'n'paste buffer. +EDITdelchar Delete the char at the cursor position. +EDITdelete Delete the block. +EDITdeleteeol Delete from cursor position to end of line. +EDITdelleft Delete the char to the left of the cursor. +EDITdelline Delete the current line. (Copied to the +EDITdelltword Delete the word to the left of the cursor. +EDITdelrtword Delete the word to the right of the cursor. +EDITdosshell Shell to DOS. +EDITdupline Duplicates the current line. +EDITexitmsg Drop this message - NO ASKING! DANGEROUS! +EDITexporttext Exports the current block to a file. +EDITgobegline Move cursor to beginning of line. +EDITgobotline Move cursor to the bottom line in the display. +EDITgobotmsg Move cursor to the last line in the message. +EDITgodown Move cursor down to next line. +EDITgoeol Move cursor to the end of the line. +EDITgoleft Move cursor one position left. +EDITgopgdn Move cursor one page of lines down. +EDITgopgup Move cursor one page of lines up. +EDITgoright Move cursor one position right. +EDITgotopline Move cursor to the top line in the display. +EDITgotopmsg Move cursor to the first line in the message. +EDITgoup Move cursor up to the previous line. +EDITgowordleft Move cursor to the previous word. +EDITgowordright Move cursor to the next word. +EDITheader Edit the message header, attributes etc. +EDITimportquotebuf Imports the current quote buffer. +EDITimporttext Import text file into this message. +EDITkillquotes (ignored) +EDITloadfile Load the message file saved with EDITsavefile. +EDITlookupcursor Lookup name/node at cursor position. +EDITlookupdest Lookup TO: node. +EDITlookuporig Lookup FROM: node. +EDITnewline Terminate paragraph and/or add a new line. +EDITpaste Paste a previously cut block at the cursor. +EDITquitnow Quit GoldED+ immediately - no asking. +EDITreflow Reflows the current text or quote paragraph. +EDITsavefile Saves the current message as a file. +EDITsavemsg Save this message. +EDITsoundkill Stops currently played sound flie. +EDITspellcheck Calls an external spell checker for the msg. +EDITtab Add spaces to the next tab-stop. +EDITtabreverse Remove spaces to the prev tab-stop. +EDITtogglecase Toggle the case of the cursor character. +EDITtoggleinsert Toggle insert mode. +EDITtolower Change the cursor character to lowercase. +EDITtoupper Change the cursor character to uppercase. +EDITundelete Undelete previously deleted lines. +EDITzapquotebelow Deletes quotes below. +

+ + + + File Selection Commands + +

+FILEabort Abort file selection. +FILEaskexit Exit GoldED+ - ask first. +FILEdosshell Shell to DOS. +FILEgotofirst Go to first file. +FILEgotolast Go to last file. +FILEgotonext Go to next file. +FILEgotoprev Go to previous file. +FILEmark Mark file. +FILEmarkall Mark all files. +FILEquitnow Quit GoldED+ immediately. +FILEselect Select the marked file(s). +FILEtogglemark Toggle file mark. +FILEunmark Unmark file. +FILEunmarkall Unmark all files. +

+ + + + Message Lister Commands + +

+LISTabort Abort message lister. +LISTaskexit Exit GoldED+ - ask first. +LISTdosshell Shell to DOS. +LISTgotobookmark Go to BookMark message. +LISTgotofirst Go to first message. +LISTgotolast Go to last message. +LISTgotonext Go to next message. +LISTgotoprev Go to previous message. +LISTmarkingoptions Marking menu. +LISTquitnow Quit GoldED+ immediately. +LISTselect Go to reader at the selected message. +LISTtogglebookmark Toggle BookMark on the selected message. +LISTtoggledate Toggle date column content. +LISTtogglemark Toggle Mark on the selected message. +LISTtogglewidesubj Toggle between wide and short subject. +

+ + + + Nodelist Browser Commands + +

+NODEabort Abort nodelist browsing. +NODEaskexit Exit GoldED+ - ask first. +NODEdosshell Shell to DOS. +NODEgotofirst Go to first node. +NODEgotolast Go to last node. +NODEgotonext Go to next node. +NODEgotoprev Go to previous node. +NODEquitnow Quit GoldED+ immediately. +NODEselect Select node. +

+ + + + Message Reader Commands + +

+READaddressbookadd Add current/marked mail writer(s) to + addressbook. Ask first. +READaskexit Exit GoldED+, prompt for final decision. +READchangeaka Change default AKA address for current area. +READchangeattrs Change the attributes of the current message. +READchangemsg Change current message. +READchangeorigin Change default origin for the current area. +READchangetagline Change default tagline. +READchangetemplate Change default template. +READchangeusername Change default username. +READchangexlatimport Change default import charset. +READcommentmsg Comment-Reply to message. (Reply to TO name). +READcopymoveforward Enter the Copy/Move/Forward function menu. +READdecreasemargin Decrease message margin. For test purposes. +READdeletemsg Delete current/marked message(s). Ask first. +READdosshell Shell to DOS. +READfidorenumber Renumber Fido/Opus *.MSG files. +READfilerequest Generate a filerequest from the current msg. +READfindall Find string(s) in message header and text. +READfindheader Find string(s) in message header. +READgotobookmark Go to the "BookMark" message. +READgotofirstmsg Go to the first message in the area. +READgotolastmsg Go to the last message in the area. +READgotomsgno Go to a specific message number. +READgotonextarea Go directly to the next area. +READgotonextmsg Go to the next message. +READgotonextunread Go to the next unread message. +READgotoprevarea Go directly to the previous area. +READgotoprevmsg Go to the previous message. +READgotoprevunread Go to the previous unread message. +READgotoreplies Choose from the next messages in the replylink. +READgotoreply1st Go to the first reply to this message. +READgotoreplynext Go to the next reply to this message. +READgotoreplyprev Go to the parent message in the replylink. +READincreasemargin Increase message margin. For test purposes. +READlookupdest Lookup TO: node. +READlookuporig Lookup FROM: node. +READmakeuserlist Generate FIDOUSER.LST of users in the area. +READmakepathreport Added "path report" feature. The output file + can be processed by a RDDT (Route Diagram + Drawing Tool) utility. +READmarkingoptions Enter the marking menu. +READmessagelist Enter the message lister. +READmovecommentmsg Comment-Reply in another area. +READmovequotemsg Quote-Reply in another area. +READmsgcontinue Page down or go to next message. +READmsgend Display last part of current message. +READmsghome Display first part of current message. +READmsglinedown Scroll message display. +READmsglineup Scroll message display. +READmsgpgdn Page message display. +READmsgpgup Page message display. +READnewarea Enter the area selection screen. +READnewmsg Start a new message. +READquitnow Exit GoldED+ immediately, no questions asked. +READquotebuf Append quote of the msg to the quotebuffer. +READquotemsg Quote-Reply to message. (Reply to FROM name). +READreplymsg Reply to the current message, without quoting. +READsearch Launches the search engine. +READsoundkill Stops currently played sound file. +READthreadtree Enter the Message Threading lister. +READtogglebookmark Toggle a "BookMark" on the current message. +READtogglehexdump Toggle hexdump mode. For debugging purposes. +READtogglehiddklud Toggle display of Hidden and Kludge lines. +READtogglehidden Toggle display of Hidden lines. +READtogglekludge Toggle display of Kludge lines. +READtogglemark Toggle a message mark on the current message. +READtogglemarkread Toggle "Read Marked" mode. +READtogglepagebar Toggle the "PageBar" feature. +READtogglequote Toggle display of quoted lines. Experimental. +READtogglerot13 Toggle ROT13 encryption for the current msg. +READtogglerealmsgno Toggle between seq. or real message numbers. +READtogglestyles Toggle Disable/Show/Show+Strip of STYLECODES. +READtoggletwits Toggle Twit display - Show/Blank/Skip/Ignore. +READtouchnetscan Touches the SEMAPHORE NETSCAN file. +READtouchsemaphore Popup touch a manually entered semaphore file. +READuserbase Launches the addressbook. +READuudecode UUdecodes the current message. +READwritemsg Write message(s) to file or printer. +

+ + + + Key Undefine Commands + +

+AREAundefine +EDITundefine +FILEundefine +LISTundefine +NODEundefine +READundefine +

+

+The undefine commands can used to undefine any of the built-in default +keyboard definitions. +

+

+See the Key Reference below for a list of the key symbols you can use +in keyboard redefinition. +

+ + + + +Macros and Keystacking +

+GoldED has a simple keyboard macro facility, which you can use to +automate certain common operations. In addition, a "keystacking" +facility allows you to create simple automatic macros on the fly. +

+

+The macro definition syntax is modelled after the syntax used in the +QEdit text editor: +

+

+ <assignment-key> Macro <commands or keys> + <assignment-key> AreaMacro <commands or keys> + <assignment-key> EditMacro <commands or keys> + <assignment-key> FileMacro <commands or keys> + <assignment-key> ListMacro <commands or keys> + <assignment-key> NodeMacro <commands or keys> + <assignment-key> ReadMacro <commands or keys> +

+

+Macros are defined in the GOLDKEYS.CFG file, where you can also find +several examples. +

+

+By using the word "Auto" as <assignment-key>, you can even define a +special macro which will be automatically executed when you start +GoldED. +

+

+Keystacking is a special form of auto-macros. You simply specify a +bunch of keys to be "stacked" in the (special internal) keyboard +buffer for sequential execution. +

+

+You can either specify a default set of keystacking in the .CFG +configuration file, or override any default keystacking by typing the +keystack definitions at the GoldED+ commandline or the GEDCMD +environment variable. +

+

+See the Key Reference chapter for a list of the key symbols you can +use in macros and keystacking. +

+

+ + + + + + Key Reference + +

+Below is the list of key symbols recognized by GoldED+ for +keyboard/macro definition and keystacking. +

+

+Unshifted function keys +

+

+ F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 +

+

+Shift-function keys +

+

+ #F1 #F2 #F3 #F4 #F5 #F6 #F7 #F8 #F9 #F10 #F11 #F12 +

+

+Alt-function keys +

+

+ @F1 @F2 @F3 @F4 @F5 @F6 @F7 @F8 @F9 @F10 @F11 @F12 +

+

+Ctrl-function keys +

+

+ ^F1 ^F2 ^F3 ^F4 ^F5 ^F6 ^F7 ^F8 ^F9 ^F10 ^F11 ^F12 +

+

+Alt-Numbers +

+

+ @0 @1 @2 @3 @4 @5 @6 @7 @8 @9 +

+

+Alt-Letters +

+

+ @A @B @C @D @E @F @G @H @I @J @K @L @M + @N @O @P @Q @R @S @T @U @V @W @X @Y @Z +

+

+Ctrl-Letters +

+

+ ^A ^B ^C ^D ^E ^F ^G ^H ^I ^J ^K ^L ^M + ^N ^O ^P ^Q ^R ^S ^T ^U ^V ^W ^X ^Y ^Z +

+

+Insert/Delete +

+

+ Ins ^Ins @Ins + Del ^Del @Del +

+

+Home/End +

+

+ Home ^Home @Home + End ^End @End +

+

+Page up/down +

+

+ PgUp ^PgUp @PgUp + PgDn ^PgDn @PgDn +

+

+Cursor left/right +

+

+ Left ^Left @Left + Right ^Right @Right +

+

+Cursor up/down +

+

+ Up ^Up @Up + Down ^Down @Down +

+

+Misc other keys +

+

+ Esc ^Grey* Key5 Space Tab #Tab @Tab BackSpace ^BackSpace + @BackSpace Enter ^Enter @Enter +

+

+Note that some of the Alt-keys, especially the cursor-related keys and +the F11/F12 keys, are "extended" keys normally only available on +systems with an extended keyboard bios. However, GoldED+ uses a few +tricks to make some the extended keys available on non-extended +systems. +

+ + + + + + Language Definition + +

+GoldED allows you to almost completely redefine the language dependent +text in the program. +

+

+The language dependent text in GoldED+ is defined in the plain ASCII +text GOLDLANG.CFG file. +

+

+See the example language file for the actual method and format of +language redefinition. +

+

+If you are planning to translate the text in GoldED+, you should also +look into the definition of the help screens. +

+

+You do not need permission from the author before announcing or +distributing your own modified language files. +

+ + + Date/Time Substitution Codes + +

+A few of the language texts can contain special date/time substitution +codes. The keywords for those are: MS_DateTimeFmt, MS_DateFmt, +MS_TimeFmt and ST_StatuslineTimeFmt. +

+

+Here are the valid substitution codes: +

+

+ %a Abbreviated weekday name (Mon, Tue, Wed, ...). + %A Full weekday name (Monday, Tuesday, Wednesday, ...). + %b Abbreviated month name (Jan, Feb, Mar, ...). + %B Full month name (January, February, March, ...). + %d Day of month (01-31). + %e Day of month, with leading space for single digits (1-31). + %E Day of month (1-31). + %H Hour (00-23) (24-hour clock). + %I Hour (01-12) (12-hour clock). + %j Day of the year (001-366). + %m Month (01-12). + %M Minute (00-59). + %p AM or PM according to 12-hour clock. + %S Second (00-59). + %U Week number (00-52) where sunday is first day of the week. + %w Weekday (0-6) where 0 is sunday. + %W Week number (01-53) where monday is first day of the week. + %y Year without century (00-99). + %Y Year with century. + %% Character '%'. +

+

+The %a, %A, %b and %B codes substitute to the current language setup +loaded using the LOADLANGUAGE keyword. +

+

+*** NOTE *** +

+

+In the continuing development of GoldED+, it is impossible to +completely maintain backward compatibility of the language format or +the text defined there. New features may add and/or obsolete some +definitions, or may change the format of others. +

+

+The existing language file may contain definitions which are already +obsolete, but which I haven't had time to search for and remove, as +well as there may be some texts in GoldED+ which are not yet definable. +All this will of course be corrected in future versions. If you find +inconsistencies, please report them, because I may have overlooked +them. +

+ + + + + + + Message Kludge Lines + +

+Kludge lines are special control lines, that begin with a ^a (ASCII 1) +as the first character of the line, followed by a unique identifying +name and the relevant control information. +

+

+GoldED is aware of a lot of these kludges, and supports a number of +them, if you want to have them inserted in your messages. +

+

+Some kludges are useless junk and more or less commercials for this +and that software, but a few are useful for miscellaneous purposes. In +the following, I will list (some of) the known and supported kludges, +and a short description of what they are used for. +

+ + + ACUPDATE: + +

+ This kludge is a feature of Squish 1.10: Message Broadcast + Modify/Delete. Read the docs for Squish 1.10 for details. +

+ + + + AREA:<echoname> + +

+ This is not really a kludge, and it doesn't begin with a ^a, but I + included it on the kludge list because it sometimes turned up in + echomail areas where it should have been stripped off by the mail + tosser. +

+ + + + CC: <name> <address> + +

+ When GoldED+ produces carbon copies, it adds to each message a full + list of the persons who get a copy. One version of this list is + hidden behind the CC: kludge. +

+ + + + CHARSET:<charset identifier> + +

+ Proposed in FSC-0050 and FSC-0054, this kludge is an attempt to + find a solution to the problem of the high-bit characters (like + the IBM PC vs Amiga vs Mac etc. national chars) in messages. + GoldED+ can recognize, use and generate this kludge. +

+ + + + CHRC:<font change id> + +

+ Proposed in FSC-0054, this is a kludge for changing fonts, + underlining and other stuff. +

+ + + + CHRS:<charset identifier> + +

+ Alternative FSC-0054 version of the CHARSET kludge. +

+ + + + DESTADDR:<destaddress> + +

+ This one is not proposed anywhere, but it looks like it gives the + address of the intended recipient. GoldED+ takes the address for + the dest field. +

+ + + + DOMAIN <destdomain> <destaddress> <origdomain> <origaddress> + +

+ Proposed in FSC-0038, this tries to solve the problem of mail + crossing domain boundaries. GoldED+ takes both addresses. +

+ + + + EID:<crc16> <stamp> [replycrc16] <replystamp> + +

+ Proposed in FSC-0031, this is used for dupe checking and reply + linking. The EID is today generally considered as garbage, but a + lot of older mail processors such as QMail still generate it. +

+ + + + ENC: + +

+ Signifies that the message contains encrypted data. GoldED+ will + add this kludge if it detects that the message has been encrypted + with PGP. +

+ + + + EOT: + +

+ End Of Text. See SOT. +

+ + + + FLAGS <special attributes> + +

+ Proposed in FSC-0053, this is a special netmail kludge used by the + FrontDoor and D'Bridge mailers and the IMail mail processor. It + provides extra attributes not found among the standard attributes + in the normal message/packet headers. GoldED+ uses and generates + this kludge, if you set the attributes. +

+ + + + FMPT <from point> + +

+ Defined in FTS-0001, this tells the point number of the + originator. Netmail only. GoldED+ can generate this line. +

+ + + + FWDAREA <original area> + +

+ FSC-0092: The original area in forwards. See + USEFWD and FSC-0092 for a more detailed + description. +

+ + + + FWDDEST <aka> + +

+ FSC-0092: The original To: address in forwards. + See USEFWD and FSC-0092 for a more detailed + description. +

+ + + + FWDFROM <name> + +

+ FSC-0092: The original From: name in forwards. + See USEFWD and FSC-0092 for a more detailed + description. +

+ + + + FWDMSGID <aka serial#> + +

+ FSC-0092: The original MSGID in forwards. + See USEFWD and FSC-0092 for a more detailed + description. +

+ + + + FWDORIG <aka> + +

+ FSC-0092: The original from-aka in forwards. See + USEFWD and FSC-0092 for a more detailed + description. +

+ + + + FWDSUBJ <original subject> + +

+ FSC-0092: The original subject in forwards. See + USEFWD and FSC-0092 for a more detailed + description. +

+ + + + FWDTO <name> + +

+ FSC-0092: The original To: field in forwards. See + USEFWD and FSC-0092 for a more detailed + description. +

+ + + + GATECHK:<???> + +

+ Some sort of gating kludge? Don't know what it's for. +

+ + + + GIF:<filename> + +

+ Invented by Henk Wever and used in his + Dutchie software. The filename (which does not have an + extension) indicates a GIF picture of the author of the + message. +

+ + + + GROUP:<echoname> + +

+ I think this one comes from stray Groupmail messages. Similar to the + AREA kludge. +

+ + + + I51 (no parameters) + +

+ Proposed in FSC-0051, this indicates that the message text + conforms to the ISO-8859-1 (LATIN-1) + character set, and may contain certain escape codes. The + ISO-8859-1 set is used in Amiga and + Windows 3.xx. GoldED+ can recognize, use and + generate this kludge. +

+ + + + INTL <destaddress> <origaddress> + +

+ Defined in FTS-0001, this one solves the problem of + crossing zone boundaries. Netmail only. GoldED+ can + generate this line. +

+ + + + MSGID: <origaddress> <serialno> + +

+ Defined in FTS-0009, this is a method for unique + identification of a message. It can be used for dupe checking and + replylinking. GoldED+ can generate this line. +

+ + + + MSGTO: <destaddress> + +

+ This one is not proposed anywhere, but it looks like it gives the + address of the intended recipient. GoldED+ takes the + address for the dest field. +

+ + + + Original: <Carbon copy, original name> + +

+ Generated by the FrontDoor FM editor when it + produces carbon copies. +

+ + + + PATH: <list of nodes> + +

+ Defined in FTS-0004, this is a valuable tool for finding + dupe links and other structural faults in the net structures. + Unfortunately the list of nodes is 2D (net/node), and this creates + problems when exporting echomail across zones. +

+ + + + PTH: <list of nodes> + +

+ Not yet a FSC (or is it?), this is a 5D-version of the + PATH kludge, which sticks to the top of the msg. +

+ + + + PID: <identifier> <version> [serialno] + +

+ Proposed in FSC-0046, this takes a stab at the tearline + abuse, and puts safe information about the first mail processing + software in the line. This could be message editors, mail scanners and + other stuff. +

+ + + + Realname: <Name> + +

+ This kludge was probably born in Russia because of some software was + not able to properly handle non-ASCII characters in + the header lines. Name should be written in national codepage. + Otherwise I don't see any reason for this kludge. I don't know any + software that generate this kludge. +

+ + + + RFD: <id> + +

+ Received For Distribution. A kludge inserted by one of the file + announcement programs. +

+ + + + REPLY: <replyaddress> <replyserialno> + +

+ Defined in FTS-0009, this is the MSGID + counterpart. When replying to a message with a MSGID, the + MSGID of the original is renamed to REPLY. +

+ + + + RID:<stuff> + +

+ Unknown kludge which looks suspiciously like the EID. +

+ + + + ROUTE <list of nodes and points> + +

+ Specifies route path. Currently supported by Unimail and + S\Tosser. +

+ + + + SEEN-BY: <list of nodes> + +

+ Defined in FTS-0004, this is a tool for finding dupe links + and other structural faults in the net structures. Depending on the + mail tosser, the seen-by's may or may not have a preceding ^a + character. Unfortunately the list of nodes is 2D (net/node), and this + can create problems when exporting echomail across zones. +

+ + + + SN:<serialno> + +

+ Serial number inserted by the Dutchie message editor. +

+ + + + SOT: + +

+ Start Of Text. See EOT. +

+ + + + SPLIT: + +

+ Defined in FSC-0047. A method for splitting large msgs so + that some mail processors don't choke on them. +

+ + + + TCL1:, TCL2: <long hex string> + +

+ Old obsolete swedish dupecheck/replylink kludge. +

+ + + + TID: + +

+ Tosser ID. Similar to the PID, but specifically + for mail processors. +

+ + + + TOPT <to point> + +

+ Defined in FTS-0001, this tells the point number of the + destination. Netmail only. GoldED+ can generate this line. +

+ + + + TZ <offset from UTC> + +

+ Specifies the time to add to the header time to get the + UTC (Universal Time Coordinated) time. Generated by newer + versions of the TrackMail netmail processor. +

+ + + + TZUTC + +

+ See TZ. GoldED+ can generate this line. +

+ + + + Via: <netmail tossing info> + +

+ Routed netmail messages usually gets a Via line for each node + it passes through. This can be used for tracing faults in the netmail + routing structure. +

+ + + + XID:<stuff> + +

+ Unknown kludge which looks suspiciously like the EID. +

+ + + + + + + +