Sender: SpiritRain Fairy Rain Ridiculous 2006, message area: ANSI Title: Activity Board, Method of Reducing Signature Files by@sayuri@seeYou Sending site: Sun and Moon Guanghua January 12, 2007 02:44:24 Friday, site mail This is my previous experience. I wrote it down and shared it with everyone. I hope everyone can summarize it again. Event viewing or signature files are generally done using auxiliary software, such as the commonly used Duluo BU and my commonly used ANSIEdit, etc. This version can be downloaded from www.bbs.nju.edu.cn. Then copy it to the bbs. If you do this often, you may encounter a problem, that is After copying it to bbs, I find that it cannot be displayed normally or the webmaster tells you that the viewing version of your event is too long. No. I can accept it. What should I do if I encounter this situation? There are still ways. So far, I have only encountered it. An event version cannot be modified to meet the requirements of the site. 1. After transferring from the software to bbs, first press the Esc key and then press the c key to preview the ansi effect. Don't use the publishing method to see the effect, which is a waste of time and people will reply to the article immediately. matter 2. If the preview is normal, it will not be normal after publishing. This happens when posting articles or letters. Original One reason is that there are extra spaces at the end of each line in your ansi work. Note that every The end of a line depends on whether there is a cross-car key, not whether there are no characters following it. The effect of spaces is The extension of the recent background color. These spaces will not jump to the next line to display when browsing. After publishing, due to the way bbs handles it, it will display too many extra blank lines in one line. Automatically displayed on the next line, so there is a problem The solution is to find that it cannot be displayed normally. Press shift e to modify the article and use the End key to jump to each line. Check to see if there are any extra spaces at the end. If there are, use the left delete key to delete them. It’s worth noting. The thing is, you can't delete too much because some of the space keys may be what you use to fill in the background color. Let's explore the body size yourself. It's relatively simple. 3. The preview is a mess. I found that the code is very messy. That’s because some lines of your code are too long. Copy them. When I went up, it had already automatically wrapped. At this time a. You need to first find out which ones automatically break a line. If they were copied from Big Radish, etc., then you Pay attention to the lines starting with *[0;1;33;40m, etc. Generally, each line starts like this. Below it The line that starts with this is either the line that starts with this or the line break above it. I usually check it after seeing it. Check it out. I'll press OK here and then Esc c to preview and see if the line in question is in The preview that starts here will show a blank line here, so you know the position of the mouse. b. Start modifying it after finding it. How to delete unnecessary control characters is described below. c. Generally, I modify the first problem area next to the previous one, and after modifying it, I find that it has been corrected. Immediately ctl w to save and then make changes. If you find that you made a mistake, usually ctl w and then select a not to save. Go in and modify it later 4 If the code exceeds 257, it cannot be placed on one line in the signature file. If the description file exceeds 150 Then it is an unqualified product. What you can do at this time is to streamline the code. A. Delete Delete several symbols a. It is simply a redundant symbol. For example, *[30;40m is followed by some of the above stuff. This is This is a redundant thing because it is impossible to see this character displayed. This situation occurs. The reason is usually the ansi software. Maybe you accidentally set it up like this in the software. And this is impossible to find without looking at the source code and thinking carefully. b. Delete redundant control codes. These codes are purely redundant. For example, there are no characters after them. But use *[0;1;37;40m, this 37 is redundant. There are many similar examples. Take a look for yourself. Bar B. Root replacement! Use *[m instead of *[0;1m, and for example, *[m*[37;40m will have one less element than *[0;1;37;40m characters. This is very useful at critical times. C. Technique! This is used at very critical times, such as the ID version of the activity above. There is one line in a line that cannot be put down in one line even after exhausting the previous methods. Some characters and control symbols. At this time, I considered using two lines to put its control symbols. The specific method is to put the first color control character beyond the 150th line at the end of the above line. Note that it is best to use the End key to jump to the end of this end. And if the front part of this line only changes the background color and no characters appear, then You can also put the color and effect control characters of the first appearing character on the top line, for example This is how I made the activity board on the ID board, and only in this way can I just satisfy 148 people. Characters, for example: 1234567890 This is an example Example of two colors The following is written above. Take a look to see if the two have exactly the same effect. 1234567890 This is an example Example of two colors Source: 日月光华 bbs.fudan.edu.cn [From: SpiritRain]