rfc1896.ps

中、英文RFC文档大全打包下载完全版 .

%%Page: 8 8
%%PageResources: (atend)
SS
0 0 25 11 798 1100 300 SM
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
0 0 0 fC
225 269 207 (RFC 1896) 207 SB
858 269 684 (text/enriched MIME Content-type) 684 SB
1881 269 294 (February 1996) 294 SB
225 2917 372 (Resnick & Walker) 372 SB
1079 2917 276 (Informational) 276 SB
2006 2917 127 ([Page ) 127 SB
2133 2917 25 (8) 25 SB
2158 2917 17 (]) 17 SB
225 377 1935 (Within the scope of an "in", the first line following each CRLF is indented, and subsequent lines) 1935 SB
225 435 715 (remain flush to the running margin.) 715 SB
225 543 1939 (Whether or not text is justified by default \(that is, whether the default environment is "flushleft",) 1939 SB
225 601 1817 ("flushright", or "flushboth"\) is unspecified, and depends on the preferences of the user, the) 1817 SB
225 659 1856 (capabilities of the local software and hardware, and the nature of the character set in use. On) 1856 SB
225 717 1899 (systems where full justification is considered undesirable, the "flushboth" environment may be) 1899 SB
225 775 1946 (identical to the default environment. Note that full justification should never be performed inside) 1946 SB
225 833 1825 (of "center", "flushleft", "flushright", or "nofill" environments. Note also that for some non-) 1825 SB
225 891 1516 (ASCII character sets, full justification may be fundamentally inappropriate.) 1516 SB
225 999 1653 (Note that [RFC-1563] defined two additional indentation commands, "Indent" and) 1653 SB
225 1057 1845 ("IndentRight". These commands did not force a line break, and therefore their behavior was) 1845 SB
225 1115 1719 (unpredictable since they depended on the margins and character sizes that a particular) 1719 SB
225 1173 1925 (implementation used. Therefore, their use is deprecated and they should be ignored just as other) 1925 SB
225 1231 511 (unrecognized commands.) 511 SB
32 0 0 58 58 0 0 0 56 /Times-Bold /font29 ANSIFont font
225 1337 504 (Markup Commands) 504 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1460 1834 (Commands in this section, unlike the other text/enriched commands are declarative markup) 1834 SB
225 1518 1934 (commands. Text/enriched is not intended as a full markup language, but instead as a simple way) 1934 SB
225 1576 1944 (to represent common formatting commands. Therefore, markup commands are purposely kept to) 1944 SB
225 1634 1737 (a minimum. It is only because each was deemed so prevalent or necessary in an e-mail) 1737 SB
225 1692 1414 (environment that these particular commands have been included at all.) 1414 SB
32 0 0 50 50 0 0 0 48 /Times-Bold /font29 ANSIFont font
375 1798 169 (Excerpt) 169 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
525 1861 1635 (causes the affected text to be interpreted as a textual excerpt from another source,) 1635 SB
525 1919 1567 (probably a message being responded to. Typically this will be displayed using) 1567 SB
525 1977 1599 (indentation and an alternate font, or by indenting lines and preceding them with) 1599 SB
525 2035 1504 ("> ", but such decisions are up to the implementation. Note that as with the) 1504 SB
525 2093 1602 (justification commands, the excerpt command implicitly begins and ends with a) 1602 SB
525 2151 1614 (line break if one is not already there. Nested "excerpt" commands are acceptable) 1614 SB
525 2209 1612 (and should be interpreted as meaning that the excerpted text was excerpted from) 1612 SB
525 2267 1544 (yet another source. Again, this can be displayed using additional indentation,) 1544 SB
525 2325 405 (different colors, etc.) 405 SB
525 2441 1573 (Optionally, the "excerpt" command can take a parameter by using the "param") 1573 SB
525 2499 1564 (command. The format of the data is unspecified, but it is intended to uniquely) 1564 SB
525 2557 1499 (identify the text from which the excerpt is taken. With this information, an) 1499 SB
525 2615 1587 (implementation should be able to uniquely identify the source of any particular) 1587 SB
525 2673 1535 (excerpt, especially if two or more excerpts in the message are from the same) 1535 SB
525 2731 1425 (source, and display it in some way that makes this apparent to the user.) 1425 SB
1 #C
statusdict begin /manualfeed false store end
EJ RS
%%PageTrailer
%%PageResources: font Times-Bold
%%+ font Times-Roman
%%Page: 9 9
%%PageResources: (atend)
SS
0 0 25 11 798 1100 300 SM
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
0 0 0 fC
225 269 207 (RFC 1896) 207 SB
858 269 684 (text/enriched MIME Content-type) 684 SB
1881 269 294 (February 1996) 294 SB
225 2917 372 (Resnick & Walker) 372 SB
1079 2917 276 (Informational) 276 SB
2006 2917 127 ([Page ) 127 SB
2133 2917 25 (9) 25 SB
2158 2917 17 (]) 17 SB
32 0 0 50 50 0 0 0 48 /Times-Bold /font29 ANSIFont font
375 375 111 (Lang) 111 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
525 438 1572 (causes the affected text to be interpreted as belonging to a particular language.) 1572 SB
525 496 1609 (This is most useful when two different languages use the same character set, but) 1609 SB
525 554 1483 (may require a different font or formatting depending on the language. For) 1483 SB
525 612 1503 (instance, Chinese and Japanese share similar character glyphs, and in some) 1503 SB
525 670 1550 (character sets like UNICODE share common code points, but it is considered) 1550 SB
525 728 1563 (very important that different fonts be used for the two languages, especially if) 1563 SB
525 786 1618 (they appear together, so that meaning is not lost. Also, language information can) 1618 SB
525 844 1556 (be used to allow for fancier text handling, like spell checking or hyphenation.) 1556 SB
525 960 1536 (The "lang" command requires a parameter using the "param" command. The) 1536 SB
525 1018 1584 (parameter data can be any of the language tags specified in [RFC-1766], "Tags) 1584 SB
525 1076 1629 (for the Identification of Languages". These tags are the two letter language codes) 1629 SB
525 1134 1443 (taken from [ISO-639] or can be other language codes that are registered) 1443 SB
525 1192 1601 (according to the instructions in the Langauge Tags RFC. Consult that memo for) 1601 SB
525 1250 400 (further information.) 400 SB
32 0 0 58 58 0 0 0 56 /Times-Bold /font29 ANSIFont font
225 1356 1216 (Balancing and Nesting of Formatting Commands) 1216 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1479 1843 (Pairs of formatting commands must be properly balanced and nested. Thus, a proper way to) 1843 SB
225 1537 319 (describe text in ) 319 SB
32 0 0 50 50 0 0 0 45 /Times-BoldItalic /font30 ANSIFont font
544 1537 224 (bold italics) 224 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
768 1537 60 ( is:) 60 SB
32 0 0 42 42 0 0 0 33 /Courier /font0 ANSIFont font
375 1643 950 (<bold><italic>the-text</italic></bold>) 950 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1729 292 (or, alternately,) 292 SB
32 0 0 42 42 0 0 0 33 /Courier /font0 ANSIFont font
375 1835 950 (<italic><bold>the-text</bold></italic>) 950 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1921 1101 (but, in particular, the following is illegal text/enriched:) 1101 SB
32 0 0 42 42 0 0 0 33 /Courier /font0 ANSIFont font
375 2027 950 (<bold><italic>the-text</bold></italic>) 950 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 2113 1870 (The nesting requirement for formatting commands imposes a slightly higher burden upon the) 1870 SB
225 2171 1764 (composers of text/enriched bodies, but potentially simplifies text/enriched displayers by) 1764 SB
225 2229 1927 (allowing them to be stack-based. The main goal of text/enriched is to be simple enough to make) 1927 SB
225 2287 1940 (multifont, formatted email widely readable, so that those with the capability of sending it will be) 1940 SB
225 2345 1950 (able to do so with confidence. Thus slightly increased complexity in the composing software was) 1950 SB
225 2403 1849 (deemed a reasonable tradeoff for simplified reading software. Nonetheless, implementors of) 1849 SB
225 2461 1731 (text/enriched readers are encouraged to follow the general Internet guidelines of being) 1731 SB
225 2519 1949 (conservative in what you send and liberal in what you accept. Those implementations that can do) 1949 SB
225 2577 1599 (so are encouraged to deal reasonably with improperly nested text/enriched data.) 1599 SB
1 #C
statusdict begin /manualfeed false store end
EJ RS
%%PageTrailer
%%PageResources: font Courier
%%+ font Times-Bold
%%+ font Times-BoldItalic
%%+ font Times-Roman
%%Page: 10 10
%%PageResources: (atend)
SS
0 0 25 11 798 1100 300 SM
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
0 0 0 fC
225 269 207 (RFC 1896) 207 SB
858 269 684 (text/enriched MIME Content-type) 684 SB
1881 269 294 (February 1996) 294 SB
225 2917 372 (Resnick & Walker) 372 SB
1079 2917 276 (Informational) 276 SB
1981 2917 127 ([Page ) 127 SB
2108 2917 50 (10) 50 SB
2158 2917 17 (]) 17 SB
32 0 0 58 58 0 0 0 56 /Times-Bold /font29 ANSIFont font
225 375 905 (Unrecognized formatting commands) 905 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 498 1943 (Implementations must regard any unrecognized formatting command as "no-op" commands, that) 1943 SB
225 556 1897 (is, as commands having no effect, thus facilitating future extensions to "text/enriched". Private) 1897 SB
225 614 1826 (extensions may be defined using formatting commands that begin with "X-", by analogy to) 1826 SB
225 672 662 (Internet mail header field names.) 662 SB
225 780 1908 (In order to formally define extended commands, a new Internet document should be published.) 1908 SB
32 0 0 67 67 0 0 0 65 /Times-Bold /font29 ANSIFont font
225 886 1005 (White Space in Text/enriched Data) 1005 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1020 1831 (No special behavior is required for the SPACE or TAB \(HT\) character. It is recommended,) 1831 SB
225 1078 1851 (however, that, at least when fixed-width fonts are in use, the common semantics of the TAB) 1851 SB
225 1136 1872 (\(HT\) character should be observed, namely that it moves to the next column position that is a) 1872 SB
225 1194 1919 (multiple of 8. \(In other words, if a TAB \(HT\) occurs in column n, where the leftmost column is) 1919 SB
225 1252 1924 (column 0, then that TAB \(HT\) should be replaced by 8-\(n mod 8\) SPACE characters.\) It should) 1924 SB
225 1310 1831 (also be noted that some mail gateways are notorious for losing \(or, less commonly, adding\)) 1831 SB
225 1368 1892 (white space at the end of lines, so reliance on SPACE or TAB characters at the end of a line is) 1892 SB
225 1426 373 (not recommended.) 373 SB
32 0 0 67 67 0 0 0 65 /Times-Bold /font29 ANSIFont font
225 1532 1190 (Initial State of a text/enriched interpreter) 1190 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1666 1903 (Text/enriched is assumed to begin with filled text in a variable-width font in a normal typeface) 1903 SB
225 1724 1947 (and a size that is average for the current display and user. The left and right margins are assumed) 1947 SB
225 1782 1466 (to be maximal, that is, at the leftmost and rightmost acceptable positions.) 1466 SB
32 0 0 67 67 0 0 0 65 /Times-Bold /font29 ANSIFont font
225 1888 741 (Non-ASCII character sets) 741 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 2022 1891 (One of the great benefits of MIME is the ability to use different varieties of non-ASCII text in) 1891 SB
225 2080 1914 (messages. To use non-ASCII text in a message, normally a charset parameter is specified in the) 1914 SB
225 2138 1934 (Content-type line that indicates the character set being used. For purposes of this RFC, any legal) 1934 SB
225 2196 1882 (MIME charset parameter can be used with the text/enriched Content-type. However, there are) 1882 SB
225 2254 1908 (two difficulties that arise with regard to the text/enriched Content-type when non-ASCII text is) 1908 SB
225 2312 1857 (desired. The first problem involves difficulties that occur when the user wishes to create text) 1857 SB
225 2370 1823 (which would normally require multiple non-ASCII character sets in the same text/enriched) 1823 SB
225 2428 1920 (message. The second problem is an ambiguity that arises because of the text/enriched use of the) 1920 SB
225 2486 783 ("<" character in formatting commands.) 783 SB
32 0 0 58 58 0 0 0 56 /Times-Bold /font29 ANSIFont font
225 2592 1011 (Using multiple non-ASCII character sets) 1011 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 2715 1834 (Normally, if a user wishes to produce text which contains characters from entirely different) 1834 SB
225 2773 1886 (character sets within the same MIME message \(for example, using Russian Cyrillic characters) 1886 SB
1 #C
statusdict begin /manualfeed false store end
EJ RS
%%PageTrailer
%%PageResources: font Times-Bold
%%+ font Times-Roman
%%Page: 11 11
%%PageResources: (atend)
SS
0 0 25 11 798 1100 300 SM
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
0 0 0 fC
225 269 207 (RFC 1896) 207 SB
858 269 684 (text/enriched MIME Content-type) 684 SB
1881 269 294 (February 1996) 294 SB
225 2917 372 (Resnick & Walker) 372 SB
1079 2917 276 (Informational) 276 SB
1981 2917 127 ([Page ) 127 SB
2108 2917 50 (11) 50 SB
2158 2917 17 (]) 17 SB
225 377 1917 (from ISO 8859-5 and Hebrew characters from ISO 8859-8\), a multipart message is used. Every) 1917 SB
225 435 1947 (time a new character set is desired, a new MIME body part is started with different character sets) 1947 SB