This section of the specification describes the basic data types that mayappear as an element"s nội dung or an attribute"s value.
Bạn đang xem: The singhalese hand
For introductory information about reading the HTML DTD, please consult theSGML tutorial.
6.1 Case information
Each attribute definition includes information about the case-sensitivity of its values. The case information is presentedwith the following keys:
CSThe value is case-sensitive (i.e., user agents interpret "a" and "A"differently).CIThe value is case-insensitive (i.e., user agents interpret "a" & "A" asthe same).CNThe value is not subject to lớn case changes, e.g., because it is a number or acharacter from the document character set.CAThe element or attribute definition itself gives case information.CTConsult the type definition for details about case-sensitivity.If an attribute value is a list, the keys apply to every value in the list,unless otherwise indicated.
6.2 SGML basic types
The document type definition specifies thesyntax of HTML element nội dung and attribute values using SGML tokens (e.g.,PCDATA, CDATA, NAME, ID, etc.). See
6.3 Text strings
A number of attributes ( %Text; in the DTD) take text that is meant tobe "human readable". For introductory information about attributes, pleaseconsult the tutorial discussion ofattributes.
6.4 URIs
This specification uses the term URI as defined in
Note that URIs include URLs (as defined in
Relative URIs are resolved lớn full URIs using a base URI.
URIs are represented in the DTD by the parameter entity %URI;.
URIs in general are case-sensitive. There may be URIs, or parts of URIs, where casedoesn"t matter (e.g., machine names), but identifying these may not be easy.Users should always consider that URIs are case-sensitive (to be on the safeside).
Please consult the appendix for information about non-ASCII characters in URI attributevalues.
6.5 Colors
The attribute value type "color" (%Color;) refers to màu sắc definitions asspecified in
| Black = "#000000" | Green = "#008000" | ||
| Silver = "#C0C0C0" | Lime = "#00FF00" | ||
| Gray = "#808080" | Olive = "#808000" | ||
| White = "#FFFFFF" | Yellow = "#FFFF00" | ||
| Maroon = "#800000" | Navy = "#000080" | ||
| Red = "#FF0000" | Blue = "#0000FF" | ||
| Purple = "#800080" | Teal = "#008080" | ||
| Fuchsia = "#FF00FF" | Aqua = "#00FFFF" |
Thus, the color values "#800080" & "Purple" both refer to lớn the colorpurple.
6.5.1 Notes on using colors
Although colors can showroom significant amounts of information to documents andmake them more readable, please consider the following guidelines whenincluding color in your documents:
Don"t use màu sắc combinations that cause problems for people with colorblindness in its various forms.If you use a background image or phối the background color, then be sure toset the various text colors as well.When practical, adopt common conventions khổng lồ minimize user confusion.6.6 Lengths
HTML specifies three types of length values for attributes:
Length values are case-neutral.
6.7 content types (MIMEtypes)
Note. A "media type" (defined in
This type is represented in the DTD by %ContentType;.
Content types are case-insensitive.
Examples of nội dung types include "text/html", "image/png", "image/gif","video/mpeg", "audio/basic", "text/tcl", "text/javascript", and"text/vbscript". For the current danh sách of registered MIME types, please consult
Note. The content type "text/css", while not currently registered with IANA, should be usedwhen the linked resource is a
6.8 Language codes
The value of attributes whose type is a language code ( %LanguageCode in the DTD) refers khổng lồ a language code as specified by
Language codes are case-insensitive.
6.9 Character encodings
The "charset" attributes (%Charset in the DTD) refer to lớn a character encoding as described in thesection on character encodings. Valuesmust be strings (e.g., "euc-jp") from the IANA registry (see
Names of character encodings are case-insensitive.
User agents must follow the steps mix out in the section on specifying character encodings in orderto determine the character encoding of an external resource.
6.10 Singlecharacters
Certain attributes hotline for a single character from the document character set. These attributes takethe %Character type in the DTD.
Single characters may be specified with character references (e.g., "&").
Xem thêm: Tổng Hợp Stt Bị Bỏ Rơi, Cap Đừng Buồn Vì Ai Đó Bỏ Rơi Bạn, 999+ Stt Tâm Trạng Bị Bỏ Rơi Hay Nhất
6.11 Dates andtimes
The format is:
YYYY-MM-DDThh:mm:ssTZDwhere: YYYY = four-digit year mm = two-digit month (01=January, etc.) DD = two-digit day of month (01 through 31) hh = two digits of hour (00 through 23) (am/pm NOT allowed) mm = two digits of minute (00 through 59) ss = two digits of second (00 through 59) TZD = time zone designatorThe time zone designator is one of:
Zindicates UTC (Coordinated Universal Time). The "Z" must be uppercase.+hh:mmindicates that the time is a local time which is hh hours andmm minutes ahead of UTC.-hh:mmindicates that the time is a local time which is hh hours andmm minutes behind UTC.Exactly the components shown here must be present, with exactly thispunctuation. Note that the "T" appears literally in the string (itmust be uppercase), lớn indicate the beginning of the time element, as specifiedin
If a generating application does not know the time to the second, it may usethe value "00" for the seconds (and minutes and hours if necessary).
6.12 liên kết types
Authors may use the following recognized linktypes, listed here with their conventional interpretations. In theDTD, %LinkTypes refers to lớn aspace-separated danh mục of liên kết types. Trắng space characters are not permittedwithin links types.
These liên kết types are case-insensitive, i.e., "Alternate" has the samemeaning as "alternate".
User agents, search engines, etc. May interpret these links types in avariety of ways. For example, user agents may provide access khổng lồ linkeddocuments through a navigation bar.
Authors may wish to define additional linktypes not described in this specification. If they vì so, theyshould use a profile to cite theconventions used to define the link types. Please see the profile attribute of the HEAD element for moredetails.
For further discussions about liên kết types, please consult the section on liên kết in HTML documents.
6.13 Mediadescriptors
The following is a danh sách of recognized media descriptors ( %MediaDesc in the DTD).
screenIntended for non-paged computer screens.ttyIntended for truyền thông using a fixed-pitch character grid, such as teletypes,terminals, or portable devices with limited display capabilities.tvIntended for television-type devices (low resolution, color, limitedscrollability).projectionIntended for projectors.handheldIntended for handheld devices (small screen, monochrome, bitmappedgraphics, limited bandwidth).printIntended for paged, opaque material and for documents viewed on screen inprint preview mode.brailleIntended for braille tactile feedback devices.auralIntended for speech synthesizers.allSuitable for all devices.Future versions of HTML may introduce new values & may allow parameterizedvalues. Khổng lồ facilitate the introduction of these extensions, conforming useragents must be able to lớn parse the truyền thông media attribute value as follows:
The value is a comma-separated các mục of entries. For example,media="screen, 3d-glasses, print & resolution > 90dpi"is mapped to:
"screen""3d-glasses""print và resolution > 90dpi"Each entry is truncated just before the first character that isn"t a USASCII letter Script data ( %Script; in the DTD) can be the nội dung of the SCRIPT element & the value ofintrinsic sự kiện attributes. Useragents must not evaluate script data as HTML markup but instead must pass it onas data to a script engine. The case-sensitivity of script data depends on thescripting language. Please note that script data that is element content may not contain character references, but script data that isthe value of an attribute may contain them. The appendix provides furtherinformation about specifying non-HTML data. Style sheet data (%StyleSheet; in theDTD) can be the content of the STYLE element and the value of the style attribute. User agents must not evaluate style data as HTMLmarkup. The case-sensitivity of style data depends on the stylesheet language. Please chú ý that style sheet data that is element content may not contain character references, but style sheet datathat is the value of an attribute may contain them. The appendix providesfurther information about specifying non-HTML data. Except for the reserved names listed below, frame target names (%FrameTarget; in the DTD) mustbegin with an alphabetic character (a-zA-Z). User agents should ignore allother target names. The following target names are reserved và have specialmeanings.6.14 Script data
6.15 Style sheet data
6.16 Frame targetnames
