Jonathan Osuch wrote:
I don't know if that would work. The problem is that when Fractint reads a PAR, the double character combination would have to be there or the slash/ back-slash would be misinterpreted.
I have tried several combinations of special and other characters to see what all would happen. The results are interesting and varied. Here are two examples that explain the majority of what will happen. The following produces two lines of comment: COMMENT=_FractInt_$version$.$patch$_\\\\\\$_$\\/_PASSES=t |....,....1....,....2....,....3....,....4 ---|----------------------------------------- 1 | FractInt 2004.3 \\\\\$ 2 | PASSES=t | The following produces four lines of comment: COMMENT=_FractInt_$version$.$patch$_\\\\\\$_$\\/\__\\/_PASSES=t//// |....,....1....,....2....,....3....,....4 ---|----------------------------------------- 1 | FractInt 2004.3 \\\\\$ 2 |_ \ 3 | PASSES=t 4 | | What is odd, when the back-slash is followed by multiple special characters, only the back-slash will be considered regular text until two other special characters are put together. Then only the first one of the other special characters will be shown in the comments.
The space character having to be represented by an underscore seems to be an enigma. Maybe Tim can shed some light on this.
It appears that the parser for the SSTOOLS.INI will treat the space character as the delimiter for the end of the COMMENT parameter, instead of looking for a typical line-feed or carriage-return character. So the underscore has to be used to show a space in an actual comment. Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/