[ Pobierz całość w formacie PDF ]

closest parent block element to define the base direction of the block.
When a block element that does not have a dir attribute is transformed to the
style of an inline element by a style sheet, the resulting presentation should be
equivalent, in terms of bidirectional formatting, to the formatting obtained by explicitly
adding a dir attribute (assigned the inherited value) to the transformed element.
24 Dec 1999 18:26 88
Paragraphs, Lines, and Phrases
9 Text
Contents
1. White space . . . . . . . . . . . . . . . 89
.
2. Structured text . . . . . . . . . . . . . . . 90
.
1. Phrase elements: EM, STRONG, DFN, CODE, SAMP, KBD, VAR, CITE, ABBR,
and ACRONYM . . . . . . . . . . . . . . 90
.
2. Quotations: The BLOCKQUOTE and Q elements . . . . . . 92
.
Rendering quotations . . . . . . . . . . . 93
.
3. Subscripts and superscripts: the SUB and SUP elements . . . . 94
.
3. Lines and Paragraphs . . . . . . . . . . . . . 94
.
1. Paragraphs: the P element . . . . . . . . . . . 95
.
2. Controlling line breaks . . . . . . . . . . . . 95
.
Forcing a line break: the BR element . . . . . . . 96
.
Prohibiting a line break . . . . . . . . . . . 96
.
3. Hyphenation . . . . . . . . . . . . . . 96
.
4. Preformatted text: The PRE element . . . . . . . . . 97
.
5. Visual rendering of paragraphs . . . . . . . . . . 98
.
4. Marking document changes: The INS and DEL elements . . . . . 99
.
The following sections discuss issues surrounding the structuring of text. Elements
that present text [p.195] (alignment elements, font elements, style sheets, etc.) are
discussed elsewhere in the specification. For information about characters, please
consult the section on the document character set. [p.41]
9.1 White space
The document character set [p.41] includes a wide variety of white space characters.
Many of these are typographic elements used in some applications to produce
particular visual spacing effects. In HTML, only the following characters are defined
as white space characters:
ASCII space ( )
ASCII tab ( )
ASCII form feed ( )
Zero-width space (​)
Line breaks [p.95] are also white space characters. Note that although 

and 
 are defined in [ISO10646] [p.353] to unambiguously separate lines
and paragraphs, respectively, these do not constitute line breaks in HTML, nor does
this specification include them in the more general category of white space
characters.
89 24 Dec 1999 18:26
Paragraphs, Lines, and Phrases
This specification does not indicate the behavior, rendering or otherwise, of space
characters other than those explicitly identified here as white space characters. For
this reason, authors should use appropriate elements and styles to achieve visual
formatting effects that involve white space, rather than space characters.
For all HTML elements except PRE, sequences of white space separate "words"
(we use the term "word" here to mean "sequences of non-white space characters").
When formatting text, user agents should identify these words and lay them out
according to the conventions of the particular written language (script) and target
medium.
This layout may involve putting space between words (called inter-word space),
but conventions for inter-word space vary from script to script. For example, in Latin
scripts, inter-word space is typically rendered as an ASCII space ( ), while
in Thai it is a zero-width word separator (​). In Japanese and Chinese,
inter-word space is not typically rendered at all.
Note that a sequence of white spaces between words in the source document may
result in an entirely different rendered inter-word spacing (except in the case of the
PRE element). In particular, user agents should collapse input white space
sequences when producing output inter-word space. This can and should be done
even in the absence of language information (from the lang attribute, the HTTP
"Content-Language" header field (see [RFC2616] [p.354] , section 14.12), user
agent settings, etc.).
The PRE element is used for preformatted text [p.97] , where white space is
significant.
In order to avoid problems with SGML line break rules [p.335] and inconsistencies
among extant implementations, authors should not rely on user agents to render
white space immediately after a start tag or immediately before an end tag. Thus,
authors, and in particular authoring tools, should write:
We offer free technical support for subscribers.
and not:
We offer free technical support for subscribers. [ Pobierz całość w formacie PDF ]

  • zanotowane.pl
  • doc.pisz.pl
  • pdf.pisz.pl
  • supermarket.pev.pl

    •