Build a markup language for your own ASP website system

Author：Eve Cole Update Time：2009-06-25 17:32:25

As a dynamic website, it is inevitable to encounter the problem of online editing of articles during the construction process. HTML provides a textarea tag, but that doesn't actually solve this problem because the textarea is plain text. Unless you use HTML tags when inputting, you will get a plate of text with no structure from beginning to end when outputting. In WEB design, building a WYSIWYG online editor through DHTML solves this problem very well.

But what you see is not the only solution. While surfing the Internet, the author found that the online editors of some portal websites are very unique. It is not a WYSIWYG (but provides a preview function), but a textarea text field, but it does not support HTML markup language. Instead, it has its own set of markup language.

Figure 1

Figure 2

The author feels that it is very smooth to use and summarizes its advantages as follows:

First, it does not have many tags, is very simple compared to HTML, and can automatically generate paragraphs by pressing Enter, which is easily accepted by ordinary users. The author believes that if Chinese tags are used, it can be accepted by more domestic users.

Second, compared to WYSIWYG editors, users can better control the structure of their articles and generate less garbled code.

Third, the visibility is much better than HTML, and it is even better with the preview function.

Fourth, it is safer because its own markup language does not support scripting.

After some thinking and practice by the author, I now disclose the method of building this own markup language:

First, we determine a simple and necessary set of markup language for our website. When determining, omit some unnecessary items. In my case, the markup language I decided on for my website was as follows:

[image]URL of image[/image]
[Title]Text content[/Title]
[Subtitle]Text content[/subtitle] (added considering that users may be segmented)
[bold]Text content[/bold]
[italics]Text content[/italics]
[link]website[/link]

Then, provide a certain mechanism to allow the browser to understand our tags. So, how to let the browser understand the tags we determine? On the page where the content is displayed, we need to write a program to translate all our tags into standards HTML tags, but the HTML code entered by the user must be filtered out before.

Step one: filter HTML code.

This is actually very simple, just replace all "<" tags with "<" and all ">" with ">". This is achieved in ASP through the following statement:

Content=replace(content,"<","<")

Content=replace(content,">",">")

(In the above code, content is a variable that stores the content we want to display. If it appears below, it means the same meaning.)

Step 2: Translate our markup to HTML

This is relatively complicated, because it is not just a matter of replacing all [tags with < and] with > and then translating the Chinese (such as pictures) into English (such as IMG). There are two reasons:

1 is the content in our markup, which needs to be processed differently according to different classifications:

The first type is directly displayed to the user, such as:

[Title]Text[/Title]

At this time, you only need to translate the tag into the corresponding English. For example, the above tag is translated into <h1>text</h1>.

The second category is not directly presented to the user, such as:

[Picture]Picture URL[/Picture]

At this time, the content "image URL" in the middle of the tag is just the URL we want to display. In HTML, it is the SRC attribute of the <IMG> tag, and this tag does not need an ending tag in HTML. So the result of direct translation is yes Wrong.

The third category is directly presented and simultaneously used as an attribute, such as:

[link]website[/link]

2. Not all places with item tags need to be translated. For example, sometimes users need to use the symbols "[" and symbols "]" to express their content. At this time, if such tags are translated as "<" and ">" are definitely not in line with the user's wishes.

After analyzing the problems that arise, the author will provide a reference for ideas for writing programs and a reference program below.

Since different tags require different translation methods, different tags must be translated one by one.

For any single tag, it may appear multiple times in an article, or it may not appear once. The program should first check the start tag of a certain tag from beginning to end (for example, if "Picture]Picture Address[/Picture]" is " [Picture]"), once it is checked, then start checking the end mark from that position. If it is also checked, it means that this is the mark we want; if the end mark is not checked, then it means that it is not what we want. markup, but only the content displayed by the user themselves. After checking, the tags are translated into HTML tags, and the content in the tags are processed differently according to different types. After finishing, the checking continues from the position of the end tag until the end of the article.

In actual writing, the idea of recursion needs to be used. The following is a sample program for translating the tag [picture]picture address[/picture].

Function TranslateImg(Str)
Start=instr(str, "[picture]") 'Check the starting position of the mark If start=0 then exit function 'The starting position is 0, which means there is no such mark, then the program ends End=instr(start, str,"[/ Picture]" 'Check the position of the end mark that appears after the start position. If end=0 then exit function 'The position of the end mark is 0, which means there is no end mark and the program ends MidStr=mid(str, start+4, end- start-4) 'Mark the content in the middle ReplaceStr=mid(str, start, end-start+5) 'Mark the content in the middle with a mark as the content to be replaced Str=replace(instr, ReplaceStr,"<img src= ”&MidStr&”>”) 'Translate markup to HTML
TranslateImg Str 'Execute this function recursively
End Function

Through the above analysis, I believe readers can build a set of "MyHTML" markup language for their own websites through their own analysis.

In actual development, there are still some issues that need to be overcome, such as: processing of mark nesting; whether to translate before submitting the user to the database or when the user browses the article and call it out from the database; to provide users with some automatic The button with the mark is inserted to facilitate the user's operation experience. This article is only for the purpose of attracting readers' appreciation.