rfc1896.ps

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

225 493 1883 (specified in the charset parameter of the Content-type line. However, using multiple character) 1883 SB
225 551 1807 (sets this way in text/enriched messages introduces problems. Since a change in the charset) 1807 SB
225 609 1890 (parameter requires a new part, text/enriched formatting commands used in the first part would) 1890 SB
225 667 1865 (not be able to apply to text that occurs in subsequent parts. It is not possible for text/enriched) 1865 SB
225 725 1352 (formatting commands to apply across MIME body part boundaries.) 1352 SB
225 833 1867 ([RFC-1341] attempted to get around this problem in the now obsolete text/richtext format by) 1867 SB
225 891 1881 (introducing different character set formatting commands like "iso-8859-5" and "us-ascii". But) 1881 SB
225 949 1941 (this, or even a more general solution along the same lines, is still undesirable: It is common for a) 1941 SB
225 1007 1850 (MIME application to decide, for example, what character font resources or character lookup) 1850 SB
225 1065 1928 (tables it will require based on the information provided by the charset parameter of the Content-) 1928 SB
225 1123 1926 (type line, before it even begins to interpret or display the data in that body part. By allowing the) 1926 SB
225 1181 1853 (text/enriched interpreter to subsequently change the character set, perhaps to one completely) 1853 SB
225 1239 1849 (different from the charset specified in the Content-type line \(with potentially much different) 1849 SB
225 1297 1926 (resource requirements\), too much burden would be placed on the text/enriched interpreter itself.) 1926 SB
225 1405 1874 (Therefore, if multiple types of non-ASCII characters are desired in a text/enriched document,) 1874 SB
225 1463 967 (one of the following two methods must be used:) 967 SB
375 1571 38 (1.) 38 SB
450 1571 1632 (For cases where the different types of non-ASCII text can be limited to their own) 1632 SB
450 1629 1675 (paragraphs with distinct formatting, a multipart message can be used with each part) 1675 SB
450 1687 1653 (having a Content-Type of text/enriched and a different charset parameter. The one) 1653 SB
450 1745 1649 (caveat to using this method is that each new part must start in the initial state for a) 1649 SB
450 1803 1638 (text/enriched document. That means that all of the text/enriched commands in the) 1638 SB
450 1861 1625 (preceding part must be properly balanced with ending commands before the next) 1625 SB
450 1919 1688 (text/enriched part begins. Also, each text/enriched part must begin a new paragraph.) 1688 SB
375 2027 38 (2.) 38 SB
450 2027 1698 (If different types of non-ASCII text are to appear in the same line or paragraph, or if) 1698 SB
450 2085 1603 (text/enriched formatting \(e.g. margins, typeface, justification\) is required across) 1603 SB
450 2143 1688 (several different types of non-ASCII text, a single text/enriched body part should be) 1688 SB
450 2201 1635 (used with a character set specified that contains all of the required characters. For) 1635 SB
450 2259 1712 (example, a charset parameter of "UNICODE-1-1-UTF-7" as specified in [RFC-1642]) 1712 SB
450 2317 1538 (could be used for such purposes. Not only does UNICODE contain all of the) 1538 SB
450 2375 1601 (characters that can be represented in all of the other registered ISO 8859 MIME) 1601 SB
450 2433 1676 (character sets, but UTF-7 is fully compatible with other aspects of the text/enriched) 1676 SB
450 2491 1530 (standard, including the use of the "<" character referred to below. Any other) 1530 SB
450 2549 1631 (character sets that are specified for use in MIME which contain different types of) 1631 SB
450 2607 1025 (non-ASCII text can also be used in these instances.) 1025 SB
1 #C
statusdict begin /manualfeed false store end
EJ RS
%%PageTrailer
%%PageResources: font Times-Roman
%%Page: 12 12
%%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 (12) 50 SB
2158 2917 17 (]) 17 SB
32 0 0 58 58 0 0 0 56 /Times-Bold /font29 ANSIFont font
225 375 1238 (Use of the "<" character in formatting commands) 1238 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 498 1918 (If the character set specified by the charset parameter on the Content-type line is anything other) 1918 SB
225 556 1729 (than "US-ASCII", this means that the text being described by text/enriched formatting) 1729 SB
225 614 1844 (commands is in a non-ASCII character set. However, the commands themselves are still the) 1844 SB
225 672 1893 (same ASCII commands that are defined in this document. This creates an ambiguity only with) 1893 SB
225 730 1948 (reference to the "<" character, the octet with numeric value 60. In single byte character sets, such) 1948 SB
225 788 1898 (as the ISO-8859 family, this is not a problem; the octet 60 can be quoted by including it twice,) 1898 SB
225 846 1757 (just as for ASCII. The problem is more complicated, however, in the case of multi-byte) 1757 SB
225 904 1823 (character sets, where the octet 60 might appear at any point in the byte sequence for any of) 1823 SB
225 962 369 (several characters.) 369 SB
225 1070 1767 (In practice, however, most multi-byte character sets address this problem internally. For) 1767 SB
225 1128 1886 (example, the UNICODE character sets can use the UTF-7 encoding which preserves all of the) 1886 SB
225 1186 1932 (important ASCII characters in their single byte form. The ISO-2022 family of character sets can) 1932 SB
225 1244 1784 (use certain character sequences to switch back into ASCII at any moment. Therefore it is) 1784 SB
225 1302 1923 (specified that, before text/enriched formatting commands, the prevailing character set should be) 1923 SB
225 1360 1930 ("switched back" into ASCII, and that only those characters which would be interpreted as "<" in) 1930 SB
225 1418 1354 (plain text should be interpreted as token delimiters in text/enriched.) 1354 SB
225 1526 1893 (The question of what to do for hypothetical future character sets that do not subsume ASCII is) 1893 SB
225 1584 561 (not addressed in this memo.) 561 SB
32 0 0 67 67 0 0 0 65 /Times-Bold /font29 ANSIFont font
225 1690 1032 (Minimal text/enriched conformance) 1032 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1824 1882 (A minimal text/enriched implementation is one that converts "<<" to "<", removes everything) 1882 SB
225 1882 1862 (between a <param> command and the next balancing </param> command, removes all other) 1862 SB
225 1940 1666 (formatting commands \(all text enclosed in angle brackets\), and, outside of <nofill>) 1666 SB
225 1998 1929 (environments, converts any series of n CRLFs to n-1 CRLFs, and converts any lone CRLF pairs) 1929 SB
225 2056 221 (to SPACE.) 221 SB
32 0 0 67 67 0 0 0 65 /Times-Bold /font29 ANSIFont font
225 2162 683 (Notes for Implementors) 683 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 2296 1863 (It is recognized that implementors of future mail systems will want rich text functionality far) 1863 SB
225 2354 1797 (beyond that currently defined for text/enriched. The intent of text/enriched is to provide a) 1797 SB
225 2412 1912 (common format for expressing that functionality in a form in which much of it, at least, will be) 1912 SB
225 2470 1821 (understood by interoperating software. Thus, in particular, software with a richer notion of) 1821 SB
225 2528 1876 (formatted text than text/enriched can still use text/enriched as its basic representation, but can) 1876 SB
225 2586 1858 (extend it with new formatting commands and by hiding information specific to that software) 1858 SB
225 2644 1826 (system in text/enriched <param> constructs. As such systems evolve, it is expected that the) 1826 SB
225 2702 1760 (definition of text/enriched will be further refined by future published specifications, but) 1760 SB
1 #C
statusdict begin /manualfeed false store end
EJ RS
%%PageTrailer
%%PageResources: font Times-Bold
%%+ font Times-Roman
%%Page: 13 13
%%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 (13) 50 SB
2158 2917 17 (]) 17 SB
225 377 1838 (text/enriched as defined here provides a platform on which evolutionary refinements can be) 1838 SB
225 435 126 (based.) 126 SB
225 543 1943 (An expected common way that sophisticated mail programs will generate text/enriched data is as) 1943 SB
225 601 1872 (part of a multipart/alternative construct. For example, a mail agent that can generate enriched) 1872 SB
225 659 1890 (mail in ODA format can generate that mail in a more widely interoperable form by generating) 1890 SB
225 717 1201 (both text/enriched and ODA versions of the same data, e.g.:) 1201 SB
32 0 0 42 42 0 0 0 33 /Courier /font0 ANSIFont font
375 823 1225 (Content-type: multipart/alternative; boundary=foo) 1225 SB
375 907 125 (--foo) 125 SB
375 949 675 (Content-type: text/enriched) 675 SB
375 1033 775 ([text/enriched version of data]) 775 SB
375 1075 875 (--foo Content-type: application/oda) 875 SB
375 1159 525 ([ODA version of data]) 525 SB
375 1201 175 (--foo--) 175 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1337 1839 (If such a message is read using a MIME-conformant mail reader that understands ODA, the) 1839 SB
225 1395 1672 (ODA version will be displayed; otherwise, the text/enriched version will be shown.) 1672 SB
225 1503 1803 (In some environments, it might be impossible to combine certain text/enriched formatting) 1803 SB
225 1561 1903 (commands, whereas in others they might be combined easily. For example, the combination of) 1903 SB
225 1619 716 (<bold> and <italic> might produce ) 716 SB
32 0 0 50 50 0 0 0 45 /Times-BoldItalic /font30 ANSIFont font
941 1619 224 (bold italics) 224 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
1165 1619 904 ( on systems that support such fonts, but there) 904 SB
225 1677 1925 (exist systems that can make text bold or italicized, but not both. In such cases, the most recently) 1925 SB
225 1735 1454 (issued \(innermost\) recognized formatting command should be preferred.) 1454 SB
225 1843 1865 (One of the major goals in the design of text/enriched was to make it so simple that even text-) 1865 SB
225 1901 1868 (only mailers will implement enriched-to- plain-text translators, thus increasing the likelihood) 1868 SB
225 1959 1832 (that enriched text will become "safe" to use very widely. To demonstrate this simplicity, an) 1832 SB
225 2017 1899 (extremely simple C program that converts text/enriched input into plain text output is included) 1899 SB
225 2075 311 (in Appendix A.) 311 SB
32 0 0 67 67 0 0 0 65 /Times-Bold /font29 ANSIFont font
225 2181 777 (Extensions to text/enriched) 777 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 2315 1950 (It is expected that various mail system authors will desire extensions to text/enriched. The simple) 1950 SB
225 2373 1869 (syntax of text/enriched, and the specification that unrecognized formatting commands should) 1869 SB
225 2431 1206 (simply be ignored, are intended to promote such extensions.) 1206 SB
32 0 0 67 67 0 0 0 65 /Times-Bold /font29 ANSIFont font
225 2537 357 (An Example) 357 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 2671 1400 (Putting all this together, the following "text/enriched" body fragment:) 1400 SB
32 0 0 42 42 0 0 0 33 /Courier /font0 ANSIFont font
375 2777 1125 (From: Nathaniel Borenstein <[e-mail]>) 1125 SB
375 2819 800 (To: Ned Freed <[e-mail]>) 800 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: 14 14
%%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 (14) 50 SB
2158 2917 17 (]) 17 SB
32 0 0 42 42 0 0 0 33 /Courier /font0 ANSIFont font
375 375 675 (Content-type: text/enriched) 675 SB
375 459 1325 (<bold>Now</bold> is the time for <italic>all</italic>) 1325 SB
375 501 200 (good men) 200 SB
375 543 900 (<smaller>\(and <<women>\)</smaller> to) 900 SB
375 585 625 (<ignoreme>come</ignoreme>) 625 SB
375 669 475 (to the aid of their) 475 SB
375 795 1000 (<color><param>red</param>beloved</color>) 1000 SB
375 837 200 (country.) 200 SB
375 921 275 (By the way,) 275 SB
375 963 1350 (I think that <paraindent><param>left</param><<smaller>) 1350 SB
375 1047 900 (</paraindent>should REALLY be called) 900 SB
375 1131 1325 (<paraindent><param>left</param><<tinier></paraindent>) 1325 SB
375 1173 675 (and that I am always right.) 675 SB
375 1257 250 (-- the end) 250 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
225 1409 1939 (represents the following formatted text \(which will, no doubt, look somewhat cryptic in the text-) 1939 SB
225 1467 630 (only version of this document\):) 630 SB
32 0 0 50 50 0 0 0 48 /Times-Bold /font29 ANSIFont font
375 1573 97 (Now) 97 SB
32 0 0 50 50 0 0 0 45 /Times-Roman /font32 ANSIFont font
472 1576 307 ( is the time for ) 307 SB
32 0 0 50 50 0 0 0