Knowledge of web standards — enriching tags in paragraphs


If you have started to use web standards step by step in your work with how difficult can Web standards be? This content will let you further understand the details of the paragraphs. If you’re just ready to start, it doesn’t matter. You can read “start with P, step by step”, and then read this article.
  Last night I decided to give up inserting CSS content at this time and continue to go deep into XHTML content. Maybe you will find XHTML far less interesting than CSS. Yes, it is. CSS can change countless visible possibilities. XHTML is just for machines and programs. But in fact, XHTML is much more important than CSS. We all know that the function of the web page itself is to carry information, data and knowledge, which we temporarily call “content”. The first element of the website is content. A web page without content may not be called a web page, but if you put a pile of content together without tags to distinguish paragraphs, key points, references, etc., the content will be crowded together and can’t be read. Even if you are a master of CSS and let you beautify it in a pile of documents without XHTML tags, you can’t start. Yes, content needs XHTML to distinguish content and give CSS a place to play. If content is the viscera and soul and CSS is the flesh, XHTML is the bone.  

XHTML is so important that we certainly can’t waste time. Now let’s introduce the tags that can be used in paragraphs one by one. (you should pay attention to this sentence: “tags used in paragraphs”, which means that these tags are not block level tags. They are inline tags.) the first thing to introduce is to emphasize Tags – strong and em. Why introduce two tags at a time? Because both labels have an emphasis. Same emphasis, so why waste two labels? Although they all have the meaning of emphasis, the intensity of emphasis is different. Strong a little more than em. If EM is “emphasis” and “attention” in Chinese vocabulary, then strong is “repeated emphasis” and “special attention”. Of course, emphasis labels can not be abused in the text. Rational use will highlight the key contents of the article. Then the general emphasis can be em. if it needs special emphasis, then strong.  

Some friends may say that the difference between strong and EM is that the content in strong is displayed in bold and the content in EM is displayed in italics. This statement is wrong because the two tags themselves do not have style attributes. There are some style tags in HTML tags, such as < b > < I > < U >, and style tags are not recommended in XHTML. The content in strong we see in the browser is displayed in bold, which is only the browser’s preset style for labels. This does not mean that strong is bold. If the browser no longer provides preset styles one day, there will be no styles in strong. So is em. Interested friends can refer to the article “semantics has nothing to do with style”.  

Now we all like to use abbreviations to express specific things or events. The advantage of this is to convey information conveniently and quickly, rather than typing so long words every time, especially for repeated words. So what XHTML tags should be used for acronyms? This is another introduction to the two tags – abbr and acronym. The general purpose of the two labels is the same, but there are still differences in details. For example, the function of < abbr > < / abbr > is to indicate that the content in the label is abbreviated. The function of < acronym > < / acronym > is to indicate that the content in the label is an acronym. You have noticed that I used EM emphasis for “acronyms”. Generally speaking, acronym is more commonly used in English than abbr, but the opposite is true in Chinese. Because there is no acronym in Chinese. There may be acronyms, but there are few. For example: the people’s Republic of China, referred to as China; The National People’s Congress, or NPC for short; These are not acronyms. I think ABR should be used when Chinese idioms appear in the text. Of course, only this label is not enough, because only knowing that it is an acronym is not enough, at least give a detailed name. Therefore, when using these two tags, a title attribute should be added. The correct way of writing should be like this< acronym   title=”European   Computer   Manufacturers   Association”>ECMA</acronym>;< abbr   Title = “gradually deepen or improve according to certain steps.” > step by step < / abbr > the content in the title will not be directly displayed on the browser. The suspension prompt will appear only after the mouse moves to that position. Of course, the general abbreviation label is only used when the abbreviation appears for the first time, and it can not be used if it appears again in the article in the future.  

Are there any acronyms in your document? Do you give complete vocabulary of acronyms? If you apply it quickly, it will make your documents more popular. If you want your documents to be popular, your documents must be polite. Maybe a friend will say: you’re going crazy. How can you be polite?   In fact, documents do need to be polite. For example, when you quote someone else’s reference, book or magazine, are they marked out? Yes, that’s what we’re talking about here. Respect others. For example, when I need to recommend an article from others, I need to deal with it like this: < A   Href = “…” > < cite > the title of the recommended article < cite > < / a > you have noticed that there is also a cite tag in the a tag. Of course, if you need to quote a sentence or a paragraph of text, this label is not suitable. This label only indicates the title and name of the literature. This label is a bit similar to the contents of the bibliography of references at the back of our books, and it is also a bit like a footnote. Of course, the cite tag can be handled like this. As for the tags that need to quote a sentence or paragraph, we will introduce them later.  

For our industry, the probability of code appearing in documents is really too high. So how to distinguish the code from the content in the document must need a specific label. Here is the most commonly used and simple code tag. The function of this tag is only to deal with some short code. It is not suitable for a large number of codes that need to be branched and indented. For some codes as shown in this article, the tag code is more suitable. If you are interested, you can open the source code of this article. About how to deal with a large amount of code, please look forward to future articles.  

I would also like to remind you that reading this article does not play any role. It is the most important to apply what you see to your work. As long as you are applying, you will be further away from success. Let’s work together, come on  

Recommended Today

The selector returned by ngrx store createselector performs one-step debugging of fetching logic

Test source code: import { Component } from ‘@angular/core’; import { createSelector } from ‘@ngrx/store’; export interface State { counter1: number; counter2: number; } export const selectCounter1 = (state: State) => state.counter1; export const selectCounter2 = (state: State) => state.counter2; export const selectTotal = createSelector( selectCounter1, selectCounter2, (counter1, counter2) => counter1 + counter2 ); // […]