[MS-OXRTFEX]: Rich Text Format (RTF) Extensions Algorithm. Intellectual Property Rights Notice for Open Specifications Documentation

Transcription

1 [MS-OXRTFEX]: Intllctual Proprty Rights Notic for Opn Spcifications Documntation Tchnical Documntation. Microsoft publishs Opn Spcifications documntation ( this documntation ) for protocols, fil formats, data portability, computr languags, and standards support. Additionally, ovrviw documnts covr intr-protocol rlationships and intractions. Copyrights. This documntation is covrd by Microsoft copyrights. Rgardlss of any othr trms that ar containd in th trms of us for th Microsoft wbsit that hosts this documntation, you can mak copis of it in ordr to dvlop implmntations of th tchnologis that ar dscribd in this documntation and can distribut portions of it in your implmntations that us ths tchnologis or in your documntation as ncssary to proprly documnt th implmntation. You can also distribut in your implmntation, with or without modification, any schmas, IDLs, or cod sampls that ar includd in th documntation. This prmission also applis to any documnts that ar rfrncd in th Opn Spcifications documntation. No Trad Scrts. Microsoft dos not claim any trad scrt rights in this documntation. Patnts. Microsoft has patnts that might covr your implmntations of th tchnologis dscribd in th Opn Spcifications documntation. Nithr this notic nor Microsoft's dlivry of this documntation grants any licnss undr thos patnts or any othr Microsoft patnts. Howvr, a givn Opn Spcifications documnt might b covrd by th Microsoft Opn Spcifications Promis or th Microsoft Community Promis. If you would prfr a writtn licns, or if th tchnologis dscribd in this documntation ar not covrd by th Opn Spcifications Promis or Community Promis, as applicabl, patnt licnss ar availabl by contacting iplg@microsoft.com. Tradmarks. Th nams of companis and products containd in this documntation might b covrd by tradmarks or similar intllctual proprty rights. This notic dos not grant any licnss undr thos rights. For a list of Microsoft tradmarks, visit Fictitious Nams. Th xampl companis, organizations, products, domain nams, mail addrsss, logos, popl, placs, and vnts that ar dpictd in this documntation ar fictitious. No association with any ral company, organization, product, domain nam, mail addrss, logo, prson, plac, or vnt is intndd or should b infrrd. Rsrvation of Rights. All othr rights ar rsrvd, and this notic dos not grant any rights othr than as spcifically dscribd abov, whthr by implication, stoppl, or othrwis. Tools. Th Opn Spcifications documntation dos not rquir th us of Microsoft programming tools or programming nvironmnts in ordr for you to dvlop an implmntation. If you hav accss to Microsoft programming tools and nvironmnts, you ar fr to tak advantag of thm. Crtain Opn Spcifications documnts ar intndd for us in conjunction with publicly availabl standards spcifications and ntwork programming art and, as such, assum that th radr ithr is familiar with th aformntiond matrial or has immdiat accss to it. 1 / 33

2 Rvision Summary Dat Rvision History Rvision Class Commnts 4/4/ Nw Initial Availability. 4/25/ Minor Rvisd and updatd proprty nams and othr tchnical contnt. 6/27/ Major Initial Rlas. 8/6/ Minor Updatd rfrncs to rflct dat of initial rlas. 9/3/ Minor Rvisd and ditd tchnical contnt. 12/3/ Minor Updatd IP notic. 3/4/ Minor Rvisd and ditd tchnical contnt. 4/10/ Major Updatd tchnical contnt and applicabl product rlass. 7/15/ Major Rvisd and ditd for tchnical contnt. 11/4/ Editorial Rvisd and ditd th tchnical contnt. 2/10/ Non Vrsion rlas 5/5/ Minor Updatd th tchnical contnt. 8/4/ Minor Clarifid th maning of th tchnical contnt. 11/3/ Non 3/18/ Non No changs to th maning, languag, or formatting of th tchnical contnt. No changs to th maning, languag, or formatting of th tchnical contnt. 8/5/ Major Significantly changd th tchnical contnt. 10/7/ Non No changs to th maning, languag, or formatting of th tchnical contnt. 1/20/ Major Significantly changd th tchnical contnt. 4/27/ Major Significantly changd th tchnical contnt. 7/16/ Non No changs to th maning, languag, or formatting of th tchnical contnt. 10/8/ Major Significantly changd th tchnical contnt. 2/11/ Non 7/26/ Non 11/18/ Non 2/10/ Non No changs to th maning, languag, or formatting of th tchnical contnt. No changs to th maning, languag, or formatting of th tchnical contnt. No changs to th maning, languag, or formatting of th tchnical contnt. No changs to th maning, languag, or formatting of th tchnical contnt. 4/30/ Minor Clarifid th maning of th tchnical contnt. 2 / 33

3 Dat Rvision History Rvision Class Commnts 7/31/ Major Significantly changd th tchnical contnt. 10/30/ Minor Clarifid th maning of th tchnical contnt. 3/16/ Major Significantly changd th tchnical contnt. 5/26/ Non 9/14/ Non 6/13/ Non 9/14/ Non No changs to th maning, languag, or formatting of th tchnical contnt. No changs to th maning, languag, or formatting of th tchnical contnt. No changs to th maning, languag, or formatting of th tchnical contnt. No changs to th maning, languag, or formatting of th tchnical contnt. 3 / 33

4 Tabl of Contnts 1 Introduction Glossary Rfrncs Normativ Rfrncs Informativ Rfrncs Ovrviw HTML/Plain Txt Encapsulation Attachmnt and RTF Intgration Rlationship to Protocols and Othr Algorithms Applicability Statmnt Standards Assignmnts Algorithm Dtails Encapsulating RTF Writr Algorithm Dtails Abstract Data Modl Initialization Procssing Ruls HTML and Plain Txt Spcific Encapsulation Syntax FROMTEXT Control Word FROMHTML Control Word HTMLRTF Toggl Control Word HTMLTAG Dstination Group HTMLTagParamtr HTML Fragmnt CONTENT HTML Fragmnt MHTMLTAG Dstination Group HTMLBASE Control Word Encoding HTML into RTF Encoding Plain Txt into RTF D-Encapsulating RTF Radr Algorithm Dtails Abstract Data Modl Initialization Procssing Ruls Rcognizing RTF Containing Encapsulation Extracting Encapsulatd HTML from RTF Extracting Original Plain Txt from RTF Attachmnt and RTF Intgration Algorithm Exampls Encapsulating HTML into RTF Intgrating Sampl Attachmnts and RTF Scurity Scurity Considrations for Implmntrs Indx of Scurity Paramtrs Appndix A: Product Bhavior Chang Tracking Indx / 33

5 1 Introduction Th is an xtnsion to RTF, as dscribd in [MSFT-RTF], that is usd to ncod mta information from (or about) th original format (HTML or plain txt) within RTF. Sctions 1.6 and 2 of this spcification ar normativ. All othr sctions and xampls in this spcification ar informativ. 1.1 Glossary This documnt uss th following trms: Attachmnt objct: A st of proprtis that rprsnts a fil, Mssag objct, or structurd storag that is attachd to a Mssag objct and is visibl through th attachmnts tabl for a Mssag objct. attachmnts tabl: A Tabl objct whos rows rprsnt th Attachmnt objcts that ar attachd to a Mssag objct. Augmntd Backus-Naur Form (ABNF): A modifid vrsion of Backus-Naur Form (BNF), commonly usd by Intrnt spcifications. ABNF notation balancs compactnss and simplicity with rasonabl rprsntational powr. ABNF diffrs from standard BNF in its dfinitions and uss of naming ruls, rptition, altrnativs, ordr-indpndnc, and valu rangs. For mor information, s [RFC5234]. charactr st: A mapping btwn th charactrs of a writtn languag and th valus that ar usd to rprsnt thos charactrs to a computr. cod pag: An ordrd st of charactrs of a spcific script in which a numrical indx (cod-point valu) is associatd with ach charactr. Cod pags ar a mans of providing support for charactr sts and kyboard layouts usd in diffrnt countris. Dvics such as th display and kyboard can b configurd to us a spcific cod pag and to switch from on cod pag (such as th Unitd Stats) to anothr (such as Portugal) at th usr's rqust. d-ncapsulating RTF radr: A Rich Txt Format (RTF) radr, as dscribd in [MSFT-RTF], that rcognizs if an input RTF documnt contains ncapsulatd HTML or plain txt, and xtracts and rndrs th original HTML or plain txt instad of th ncapsulating RTF contnt. ncapsulating RTF writr: A Rich Txt Format (RTF) writr, as dscribd in [MSFT-RTF], that producs an RTF documnt as a rsult of format convrsion from othr formats, such as plain txt or HTML, and also stors th original documnt in a form that allows for subsqunt rtrival. ncapsulation: A procss of ncoding on documnt in anothr documnt in a way that allows th first documnt to b r-cratd in a form that is narly idntical to its original form. format convrsion: A procss that convrts a txt documnt from on txt format, such as Rich Txt Format (RTF), HTML, or plain txt, to anothr txt format. Th rsult of txt convrsion is typically a nw documnt that is an approximat rndring of th sam information. Hyprtxt Markup Languag (HTML): An application of th Standard Gnralizd Markup Languag (SGML) that uss tags to mark lmnts in a documnt, as dscribd in [HTML]. mssag body: Th main mssag txt of an mail mssag. A fw proprtis of a Mssag objct rprsnt its mssag body, with on proprty containing th txt itslf and othrs dfining its cod pag and its rlationship to altrnativ body formats. 5 / 33

6 Mssag objct: A st of proprtis that rprsnts an mail mssag, appointmnt, contact, or othr typ of prsonal-information-managmnt objct. In addition to its own proprtis, a Mssag objct contains rcipint proprtis that rprsnt th addrsss to which it is addrssd, and an attachmnts tabl that rprsnts any fils and othr Mssag objcts that ar attachd to it. MIME Encapsulation of Aggrgat HTML Documnts (MHTML): A MIME-ncapsulatd HTML documnt, as dscribd in [RFC2557]. plain txt: Txt that dos not hav markup. S also plain txt mssag body. rmot opration (ROP): An opration that is invokd against a srvr. Each ROP rprsnts an action, such as dlt, snd, or qury. A ROP is containd in a ROP buffr for transmission ovr th wir. rndring position: A location in a Rich Txt Format (RTF) documnt whr an attachmnt is placd visually. Rich Txt Format (RTF): Txt with formatting as dscribd in [MSFT-RTF]. ROP rqust: S ROP rqust buffr. Unicod: A charactr ncoding standard dvlopd by th Unicod Consortium that rprsnts almost all of th writtn languags of th world. Th Unicod standard [UNICODE5.0.0/2007] provids thr forms (UTF-8, UTF-16, and UTF-32) and svn schms (UTF-8, UTF-16, UTF-16 BE, UTF-16 LE, UTF-32, UTF-32 LE, and UTF-32 BE). Uniform Rsourc Locator (URL): A string of charactrs in a standardizd format that idntifis a documnt or rsourc on th World Wid Wb. Th format is as spcifid in [RFC1738]. MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: Ths trms (in all caps) ar usd as dfind in [RFC2119]. All statmnts of optional bhavior us ithr MAY, SHOULD, or SHOULD NOT. 1.2 Rfrncs Links to a documnt in th Microsoft Opn Spcifications library point to th corrct sction in th most rcntly publishd vrsion of th rfrncd documnt. Howvr, bcaus individual documnts in th library ar not updatd at th sam tim, th sction numbrs in th documnts may not match. You can confirm th corrct sction numbring by chcking th Errata Normativ Rfrncs W conduct frqunt survys of th normativ rfrncs to assur thir continud availability. If you hav any issu with finding a normativ rfrnc, plas contact dochlp@microsoft.com. W will assist you in finding th rlvant information. [HTML] World Wid Wb Consortium, "HTML 4.01 Spcification", Dcmbr 1999, [MS-DTYP] Microsoft Corporation, "Windows Data Typs". [MS-OXCMSG] Microsoft Corporation, "Mssag and Attachmnt Objct Protocol". [MSFT-RTF] Microsoft Corporation, "Rich Txt Format (RTF) Spcification", vrsion 1.9.1, March 2008, [RFC2119] Bradnr, S., "Ky words for us in RFCs to Indicat Rquirmnt Lvls", BCP 14, RFC 2119, March 1997, 6 / 33

7 [RFC5234] Crockr, D., Ed., and Ovrll, P., "Augmntd BNF for Syntax Spcifications: ABNF", STD 68, RFC 5234, January 2008, Informativ Rfrncs [MS-OXBBODY] Microsoft Corporation, "Bst Body Rtrival Algorithm". [MS-OXCDATA] Microsoft Corporation, "Data Structurs". [MS-OXCFOLD] Microsoft Corporation, "Foldr Objct Protocol". [MS-OXCFXICS] Microsoft Corporation, "Bulk Data Transfr Protocol". [MS-OXCROPS] Microsoft Corporation, "Rmot Oprations (ROP) List and Encoding Protocol". [MS-OXRTFCP] Microsoft Corporation, "Rich Txt Format (RTF) Comprssion Algorithm". 1.3 Ovrviw can transmit txt in diffrnt txt formats, including Hyprtxt Markup Languag (HTML), RTF, and plain txt. Various softwar componnts can impos diffrnt txt format rquirmnts for contnt to b stord or displayd to th usr, and txt format convrsion might b ncssary to comply with ths rquirmnts. For xampl, an -mail clint might b configurd to compos -mail in HTML, RTF, or plain txt, and support dynamically changing formats during composition. Gnral format convrsion can introduc noticabl (and unwantd) changs in contnt formatting. Thrfor, it is imprativ not only to aim for high-fidlity convrsions to RTF, but also to find a mchanism to rcovr th contnt in its original format. This algorithm is usd to ncod mta information from (or about) th original format (HTML or plain txt) within RTF, so that if convrsion back to th original form is ncssary, it can b vry clos to th original contnt HTML/Plain Txt Encapsulation Encapsulation and d-ncapsulation can introduc changs in th contnt of th original documnt, as long as such changs do not affct th rndring of th documnt in its original format. For xampl, it is allowabl to introduc, rmov, or chang insignificant whitspac in HTML and/or to normaliz txt lin ndings to us carriag rturn/lin fd pairs (CRLFs). Two softwar rols can b idntifid in rspct to this ncapsulation format: 1. Encapsulating RTF writr: Th RTF writr, as dscribd in [MSFT-RTF], that convrts contnt from HTML or plain txt format to RTF and prsrvs th original form of th contnt in an RTF documnt by using th ncapsulation format spcifid by this algorithm. 2. D-ncapsulating RTF radr: Th RTF radr, as dscribd in [MSFT-RTF], that convrts contnt from RTF back to HTML or plain txt format, by rcognizing that an RTF documnt contains ncapsulatd HTML or plain txt contnt and xtracting such contnt (instad of prforming a gnral format convrsion from RTF to HTML or plain txt format). This algorithm dos not spcify a gnral format convrsion procss btwn HTML (or plain txt) and RTF. Such a convrsion procss can b a propritary and oftn approximat mapping btwn RTF formatting faturs, as dscribd in [MSFT-RTF], and HTML formatting faturs, as dscribd in [HTML]. For xampl, th HTML cod fragmnt "<B>tst</B>" could b convrtd to "{\b tst}". Th ncapsulation of original contnt is orthogonal to a format convrsion procss and can b combind with any such format convrsion. An RTF radr can choos to ignor th ncapsulation within an RTF documnt and trat such a documnt as a pur RTF documnt. Thrfor, th RTF documnt that contains th ncapsulatd 7 / 33

8 original contnt nds to also contain an adquat RTF rndring of th original HTML or plain txt documnt. Th implmntr dtrmins th richnss of th convrsion from th original contnt format to RTF Attachmnt and RTF Intgration clints that support RTF can support rndring attachmnts, imags, and fil attachmnt icons inlin with mssag body txt. This algorithm dfins how to idntify and spcify which objct to rndr at a givn position within an RTF documnt. This algorithm dos not spcify how to gnrat th visual rprsntation of an attachmnt. If a clint dos not implmnt this portion of th algorithm, rlationships btwn th attachmnt position and associatd txt within a documnt might b ambiguous. For xampl, if a documnt introducs an attachmnt with th txt "th contnt in th following fil:", th xpctation is that th fil attachmnt icon will appar adjacnt to th introductory txt. Howvr, if this algorithm is not implmntd, th fil attachmnt icon might not appar nar th associatd txt, making th association ambiguous if thr ar multipl attachmnts involvd. 1.4 Rlationship to Protocols and Othr Algorithms This is an xtnsion to RTF, as dscribd in [MSFT-RTF]. For concptual background information and ovrviws of th rlationships and intractions btwn this and othr protocols, s [MS-OXPROTO]. 1.5 Applicability Statmnt This algorithm is applicabl to any clint or srvr that supports RTF. A clint can us this algorithm to stor or rtriv HTML or plain txt that is ncapsulatd in RTF. D-ncapsulating th original HTML or plain txt from th RTF documnt nabls th clint to rndr contnt with highr fidlity than might b achivd by convrting th contnt from RTF back to HTML or plain txt format. Attachmnt and RTF intgration, as dscribd in sction 2.1, is ncssary to adquatly rndr RTF mssag bodis. Th rintgration is important to providing an accurat placmnt of inlin imags, attachmnt icons, and othr objcts. 1.6 Standards Assignmnts Non. 8 / 33

9 2 Algorithm Dtails 2.1 Encapsulating RTF Writr Algorithm Dtails Encapsulation nabls storag of th HTML or plain txt contnt of a documnt in th body of anothr RTF documnt. <1> Encapsulation lvrags nativ RTF such that an RTF radr can rndr th RTF rprsntation of th documnt without any indication of mbddd contnt and, whn dncapsulatd, th HTML and plain txt will diffr only minimally from th original HTML or plain txt contnt. To ncapsulat HTML or plain txt documnt contnt insid an RTF documnt, th RTF writr uss two xtnsibility faturs of RTF, as dscribd in [MSFT-RTF]: 1. RTF control words unknown to an RTF radr hav to b ignord by th RTF radr. Th HTML/plain txt ncapsulation format spcifid by this algorithm dfins nw RTF control words, as spcifid in sction RTF control words ar dscribd in [MSFT-RTF]. 2. Ignorabl RTF dstinations (that is, RTF groups that start with "{\*\<dstination-nam>" and nd with "}") hav to b skippd (not rndrd in any form) by any RTF radr that dos not rcogniz th <dstination-nam>. Th HTML/plain txt ncapsulation format spcifid by this algorithm dfins nw RTF dstinations for ncapsulating original or rwrittn HTML markup, as spcifid in sction 2.1. An implmntr of this algorithm has to hav a good undrstanding of RTF, as spcifid in [MSFT- RTF], and HTML, as spcifid in [HTML], to crat RTF contnt that sufficintly rprsnts th original HTML or plain txt contnt, and to ncapsulat plain txt or HTML in such RTF Abstract Data Modl Non Initialization Non Procssing Ruls HTML and Plain Txt Spcific Encapsulation Syntax Encapsulation uss svral control words to fully ncapsulat HTML and plain txt in RTF. This sction spcifis th Augmntd Backus-Naur Form (ABNF) grammar format, as spcifid in [RFC5234], for thos tokns and includs information about ach tokn FROMTEXT Control Word Th FROMTEXT control word spcifis that th RTF documnt was producd from plain txt. ; \fromtxt FROMTEXT = %x5c f.6d This control word MUST appar bfor th \fonttbl control word and aftr th \rtf1 control word, as spcifid in [MSFT-RTF]. For additional rstrictions rgarding placmnt of this control word, s sction / 33

10 FROMHTML Control Word Th FROMHTML control word spcifis that th RTF documnt contains ncapsulatd HTML txt.<2> ; \fromhtml1 FROMHTML = %x5c f.6d d.6c "1" This control word MUST b \fromhtml1. Any othr form, such as \fromhtml or \fromhtml0, will not b considrd ncapsulatd. This control word MUST appar bfor th \fonttbl control word and aftr th \rtf1 control word, as spcifid in [MSFT-RTF]. For additional rstrictions rgarding placmnt of this control word, s sction HTMLRTF Toggl Control Word Th HTMLRTF control word idntifis fragmnts of RTF that wr not in th original HTML contnt.<3> ; \htmlrtf or \htmlrtf1 or \htmlrtf0 HTMLRTF = %x5c d.6c ["0" / "1"] This control word is usd to mark rgions of th RTF contnt that ar th rsult of approximat format convrsion and wr not part of th original HTML contnt. This control word complis with th smantics spcifid in [MSFT-RTF] rgarding toggl control words. Thrfor, \htmlrtf and \htmlrtf1 both rprsnt nabling th control word. Control word Stat Dscription \htmlrtf \htmlrtf1 BEGIN Th d-ncapsulating RTF radr MUST NOT copy any subsqunt txt and control words in th RTF contnt until th stat is disabld. \htmlrtf0 END This control word disabls an arlir instanc of \htmlrtf or \htmlrtf1, thrby allowing th d-ncapsulating RTF radr to valuat subsqunt txt and control words in th RTF contnt. A d-ncapsulating RTF radr MUST support th HTMLRTF control word within nstd groups. Th stat of th HTMLRTF control word MUST transfr whn ntring groups and b rstord whn xiting groups, as spcifid in [MSFT-RTF]. This xampl shows how stats ar modifid whn nstd via groups using bold, whr \b nabls bold and \b0 disabls bold: "\b bold { bold \b0 non-bold } bold \b0 non-bold non-bold { non-bold \b bold } non-bold" HTMLTAG Dstination Group Th HTMLTAG dstination group ncapsulats HTML fragmnts that cannot b dirctly rprsntd in RTF.<4> ; \*\htmltag[htmltagparamtr][content] HTMLTAG = %x5c.2a.5c d.6c [HTMLTagParamtr] [CONTENT] HTMLTagParamtr = *3DIGIT ; A spac MUST b usd to sparat th CONTENT HTML fragmnt ; from th HTMLTagParamtr HTML fragmnt if th txt 10 / 33

11 ; starts with a DIGIT, or if th HTMLTagParamtr HTML fragmnt ; is omittd. CONTENT = [SP] *VCHAR For xampl, "<FONT fac="symbol">" would b spcifid in th CONTENT HTML fragmnt as follows: "\*\htmltag148 <FONT fac="symbol">" HTMLTagParamtr HTML Fragmnt Th HTMLTagParamtr HTML fragmnt is a WORD ([MS-DTYP]) valu comprisd of th flags spcifid in this sction: Dstination, TagTyp, and othr flags. This fragmnt SHOULD NOT<5> b mittd, xcpt as spcifid in sction Although th HTMLTagParamtr HTML fragmnt is dfind in trms of bitmasks, it appars in this spcification as a dcimal valu. Dstination Flag Th Dstination flag dfins whr th HTML contnt was locatd rlativ to th <HTML>, <HEAD>, and <BODY> lmnts. Th following tabl spcifis th valus for th Dstination flag. Nam Valu Dscription INBODY 0x0000 Th corrsponding fragmnt of original HTML SHOULD appar insid of a <BODY> HTML lmnt. INHEAD 0x0001 Th corrsponding fragmnt of original HTML SHOULD appar insid of a <HEAD> HTML lmnt. INHTML 0x0002 Th corrsponding fragmnt of original HTML SHOULD appar insid of an <HTML> HTML lmnt. OUTHTML 0x0003 Th corrsponding fragmnt of original HTML SHOULD appar outsid of an <HTML> HTML lmnt. TagTyp Flag Th TagTyp flag dfins th typ of HTML contnt that is stord in th CONTENT HTML fragmnt in an \*\htmltag dstination group. Th following tabl spcifis th valus for th TagTyp flag. Nam Valu Dscription TEXT 0x0000 This group ncapsulats a txt fragmnt rathr than any HTML tags. HTML 0x0010 This group ncapsulats th <HTML> HTML lmnt. HEAD 0x0020 This group ncapsulats th <HEAD> HTML lmnt. BODY 0x0030 This group ncapsulats th <BODY> HTML lmnt. P 0x0040 This group ncapsulats th <P> HTML lmnt. STARTP 0x0050 This group ncapsulats an HTML tag that starts a paragraph othr than th <P> HTML lmnt. ENDP 0x0060 This group ncapsulats an HTML tag that nds a paragraph othr than th <P> HTML lmnt. BR 0x0070 This group ncapsulats th <BR> HTML lmnt. PRE 0x0080 This group ncapsulats th <PRE> HTML lmnt. 11 / 33

12 Nam Valu Dscription FONT 0x0090 This group ncapsulats th <FONT> HTML lmnt. HEADER 0x00A0 This group ncapsulats hading HTML tags such as <H1>, <H2>, and so on. TITLE 0x00B0 This group ncapsulats th <TITLE> HTML lmnt. PLAIN 0x00C0 This group ncapsulats th <PLAIN> HTML lmnt. RESERVED1 0x00D0 Rsrvd, MUST b ignord. RESERVED2 0x00E0 Rsrvd, MUST b ignord. UNK 0x00F0 This group ncapsulats any othr HTML tag. Th following tabl spcifis th valus for th Othr flags fild. Nam Valu Dscription INPAR 0x0004 Th corrsponding fragmnt of th original HTML SHOULD appar insid a paragraph HTML lmnt. CLOSE 0x0008 This is a closing tag. MHTML 0x0100 This group ncapsulats MIME Encapsulation of Aggrgat HTML Documnts (MHTML); that is, an HTML tag with a rwritabl URL paramtr. For mor dtails about th MHTMLTAG dstination group, s sction CONTENT HTML Fragmnt Th CONTENT HTML fragmnt in an HTMLTAG dstination group contains parts of original HTML markup or othr txt that ar not duplicatd or significantly transformd in RTF contnt, such as HTML tags, txt that might includ HTML charactr rfrncs, and HTML commnts.<6> It is possibl that som txt in th CONTENT HTML fragmnt will nd to b scapd or convrtd to RTF control words to produc propr RTF. Th following tabl spcifis valid RTF scap tokns and control words that can b usd in th CONTENT HTML fragmnt. A d-ncapsulating RTF radr MAY<7> fail to xtract th original HTML whn othr RTF control words ar includd in th CONTENT HTML fragmnt. RTF scap tokns and control words \par \tab Corrsponding HTML txt %x0d.0a (OCTET squnc CRLF) %x09 (OCTET form for th horizontal tab charactr) \{ %x7b (OCTET form for {) \} %x7d (OCTET form for }) \\ %x5c (OCTET form for rvrs solidus '\') \lquot \rquot \ldblquot " " (Unicod valu U+2018) " " (Unicod valu U+2019) " " (Unicod valu U+201C) 12 / 33

13 RTF scap tokns and control words \rdblquot \bullt \ndash \mdash Corrsponding HTML txt " " (Unicod valu U+201D) " " (Unicod valu U+2022) " " (Unicod valu U+2013) " " (Unicod valu U+2014) \~ " " (non-braking spac) \_ \'HH \u[-]nnnnn " " ( soft hyphn) %xhh (OCTET with th hxadcimal valu of HH) "&#xhhhh;" whr: NNNNN is a positiv intgr xprssd in dcimal digits -NNNNN is a ngativ intgr xprssd in dcimal digits HHHH is th hxadcimal quivalnt of NNNNN or -NNNNN \uc No visual rprsntation in HTML MHTMLTAG Dstination Group Th MHTMLTAG dstination group is usd to ncapsulat an HTML tag with a rwritabl URL paramtr. ;\*\mhtmltag[htmltagparamtr][content] MHTMLTAG = %x5c.2a.5c.6d d.6c [HTMLTagParamtr] [CONTENT] This RTF dstination MAY b usd in RTF markd with th \fromhtml1 control word.<8> Th MHTMLTAG dstination group has an optional numric HTMLTagParamtr HTML fragmnt. Th valus and format of th numric paramtr ar idntical to th numric paramtr in th HTMLTAG dstination group, as spcifid in sction This RTF control word SHOULD b skippd on d-ncapsulation and SHOULD NOT b writtn whn ncapsulating HTMLBASE Control Word Th HTMLBASE control word indicats a location of a rwrittn Uniform Rsourc Locator (URL) insid a MHTMLTAG dstination group. ; \htmlbas HTMLBASE = %x5c d.6c This RTF control word SHOULD b skippd on d-ncapsulation and SHOULD NOT b writtn whn ncapsulating. This is bcaus th HTMLBASE control word can appar only insid an MHTMLTAG dstination group, which is to b ignord, as spcifid in sction / 33

14 Encoding HTML into RTF Th translation btwn HTML and RTF is not spcifid by this algorithm and is implmntationdpndnt. To mit RTF-ncapsulatd HTML, implmntrs MAY<9> do th following: Produc a valid RTF documnt, as spcifid by [MSFT-RTF]. Emit a FROMHTML control word in th RTF hadr aftr th \rtf1 control word to indicat that ncapsulatd HTML is includd in th RTF documnt. Spcify a dfault cod pag for txt runs in RTF by using th \ansicpgn kyword, as spcifid in [MSFT-RTF]. Emit a font tabl to dfin fonts usd in RTF. Spcify charactr st information for ach font whn ncssary, as spcifid in [MSFT-RTF]. Produc a singl mpty HTMLTAG dstination group with th Dstination flag st to INBODY and th TagTyp flag st to P ({\*\htmltag64}) bfor any shard visibl txt in a gnratd RTF documnt (for xampl, immdiatly following th RTF hadr, as spcifid in [MSFT-RTF]).<10> Us an HTMLTAG dstination group to prsrv any contnt of th original HTML documnt that dos not hav dirct rprsntation in RTF (such as HTML tags, txt with HTML charactr rfrncs, HTML commnts, or insignificant whitspac). Produc an HTMLTagParamtr HTML fragmnt in any HTMLTAG dstination control word (xcpt th {\*\htmltag64} mpty dstination group).<11> Any txt insid an HTMLTAG dstination group can b ncodd by a dfault RTF cod pag, as spcifid in [MSFT-RTF]. Any txt that cannot b rprsntd by using a dfault RTF cod pag without data loss can b ncodd by using \un control words. Us HTMLRTF control words to supprss d-ncapsulation of any RTF contnt that is not part of th original HTML contnt. In particular, any mittd RTF control words that chang charactrformatting proprtis, such as \f, \fs, \b, or \i, can<12> b xplicitly supprssd by th HTMLRTF control word. Any corrsponding original HTML contnt can b ncapsulatd in HTMLTAG dstination groups, as spcifid in sction Produc txt in a cod pag that corrsponds to th currnt font for ach txt run, or in a dfault RTF cod pag if no currnt font is slctd for a txt run (outsid of an HTMLTAG dstination group, and whn not supprssd by an HTMLRTF control word). Any charactrs that cannot b rprsntd in a slctd cod pag can b ncodd by using th \un control word Encoding Plain Txt into RTF Th translation btwn plain txt and RTF is not spcifid by this algorithm and is implmntation dpndnt. Implmntrs MUST produc a valid RTF documnt, as spcifid by [MSFT-RTF]. Implmntrs MUST mit a FROMTEXT control word in th RTF hadr, aftr th \rtf1 control word, to indicat that RTF was producd from plain txt. Implmntrs SHOULD spcify a dfault cod pag for txt runs in RTF by using th \ansicpgn control word, as spcifid in [MSFT-RTF]. Implmntrs can mit a font tabl to dfin fonts usd in RTF. Implmntrs SHOULD spcify charst information for ach font whn ncssary, as spcifid in [MSFT-RTF]. Implmntrs MUST NOT us HTMLTAG dstination groups or th FROMHTML control word in RTF contnt markd with th FROMTEXT control word. All txtual contnt MUST b rprsntd dirctly in RTF. Implmntrs SHOULD produc txt in a cod pag that corrsponds to th currnt font for ach txt run, or in a dfault RTF cod pag if no currnt font is slctd for a txt run. Any charactrs that cannot b rprsntd in a slctd cod pag SHOULD b ncodd by using th \un control word. Any rsulting charactrs that ar not allowd or hav a spcial maning in RTF 14 / 33

15 syntax MUST b scapd, as spcifid in [MSFT-RTF]. Any lin-nding charactr squnc (such as CRLF, CR, or LF) MUST b convrtd to RTF as \par or \lin RTF control words. Implmntrs can add othr formatting RTF control words that do not hav txtual rprsntation (for xampl, to improv th prsntation quality of th rsulting RTF). 2.2 D-Encapsulating RTF Radr Algorithm Dtails D-ncapsulation nabls prviously ncapsulatd HTML and plain txt contnt to b xtractd and rndrd as HTML and plain txt instad of th ncapsulating RTF contnt. Aftr d-ncapsulation, th HTML and plain txt diffr only minimally from th original HTML or plain txt contnt Abstract Data Modl This sction dscribs a concptual modl of possibl data organization that an implmntation maintains to participat in this algorithm. Th dscribd organization is providd to facilitat th xplanation of how th algorithm bhavs. This documnt dos not mandat that implmntations adhr to this modl as long as thir xtrnal bhavior is consistnt with that dscribd in this documnt. To proprly intgrat attachmnts with th RTF body, a clint rquirs: A list of attachmnts. A position array that stors th \objattph locations built from th RTF body. Th \objattph control word is spcifid in [MSFT-RTF]. Ths structurs ar ncssary to combin th attachmnts from th Mssag objct with th RTF body Initialization Th list of attachmnts MUST b sortd by th valu of th PidTagRndringPosition proprty ([MS-OXCMSG] sction ), in ascnding ordr. Sorting th list of attachmnts can b accomplishd whn qurying th contnts from th attachmnts tabl, or from an in-mmory list of attachmnts at som latr point. Th position array MUST b clard, making th siz of th array zro Procssing Ruls Rcognizing RTF Containing Encapsulation Bfor th d-ncapsulating RTF radr tris to rcogniz th ncapsulation, th radr SHOULD<13> nsur that th documnt has a valid RTF documnt hading according to [MSFT-RTF] (that is, it starts with th charactr squnc "{\rtf1"). Th d-ncapsulating RTF radr SHOULD<14> inspct no mor than th first 10 RTF tokns (that is, bgin group marks and control words) in th input RTF documnt, in squnc, starting from th bginning of th RTF documnt. If on of th control words is th FROMHTML control word, th dncapsulating RTF radr SHOULD conclud that th RTF documnt contains an ncapsulatd HTML documnt and stop furthr inspction. If on of th control words is th FROMTEXT control word, th d-ncapsulating RTF radr SHOULD conclud that th RTF documnt was producd from a plain txt documnt and stop furthr inspction. During th inspction, th d-ncapsulating RTF radr SHOULD conclud that thr is no ncapsulatd contnt and that this is a normal (pur) RTF documnt if any of th following conditions ar tru: 15 / 33

16 Thr ar any RTF tokns bsids th bgin group mark "{" or a control word within th first 10 tokns. Thr is no FROMHTML or FROMTEXT control word within th first 10 tokns Extracting Encapsulatd HTML from RTF Th d-ncapsulating RTF radr MUST pars th RTF documnt as spcifid in [MSFT-RTF]. Bfor attmpting d-ncapsulation, th radr MUST first rcogniz th ncapsulatd contnt, as spcifid in sction To b abl to corrctly convrt txt insid RTF, th d-ncapsulating RTF radr SHOULD procss control words and othr information in RTF that affct th intrprtation of txt runs in RTF and a cod pag of such txt runs. For mor dtails about control words and txt runs, s [MSFT-RTF]. In particular, th d-ncapsulating RTF radr SHOULD us th dfault cod pag, as spcifid in th RTF hadr, and it SHOULD us th cod pag information, as spcifid for ach font in a font tabl. It also SHOULD track changs to th currnt font and us th appropriat cod pag for th currntly slctd font. Th d-ncapsulating RTF radr MUST skip othr parts of th RTF hadr, as spcifid in [MSFT-RTF]. If th d-ncapsulating RTF radr ncountrs an HTMLTAG dstination group, it SHOULD ignor any HTMLTagParamtr HTML fragmnts in an HTMLTAG control word. Any CONTENT HTML fragmnts insid HTMLTAG dstination groups MUST b copid to a dstination HTML documnt, as follows: Any RTF scaps and RTF control words that rprsnt Unicod charactrs, as spcifid in sction , MUST b convrtd to appropriat txt and such txt MUST b copid to th targt HTML documnt. RTF scaps SHOULD b unscapd and th rsulting byts intrprtd in a dfault RTF cod pag, as spcifid in [MSFT-RTF]. Unicod charactrs producd from Unicod scaps (\un control word) and othr control words SHOULD b intrprtd as Unicod charactrs. Any othr RTF control words within a CONTENT HTML fragmnt insid an HTMLTAG dstination group SHOULD b ignord. Any rmaining txt within a CONTENT HTML fragmnt insid an HTMLTAG dstination group MUST b copid to th targt HTML documnt. To intrprt such txt, th d-ncapsulating RTF radr MUST us th dfault RTF cod pag, as spcifid in th RTF hadr. For mor dtails about cod pag support, s [MSFT-RTF]. Outsid of an HTMLTAG dstination group, th d-ncapsulating RTF radr MUST do th following: Ignor and skip any txt and RTF control words that ar supprssd by any HTMLRTF control word othr than th \fn control word. Th d-ncapsulating RTF radr SHOULD track th currnt font vn whn th corrsponding \fn control word is insid of a fragmnt that is disabld with an HTMLRTF control word. Ignor and skip any standard RTF dstination groups that do not produc visibl txt (such as \colortbl groups), xcpt for th \fonttbl group. Th d-ncapsulating RTF radr SHOULD procss a font tabl group and at last rmmbr th cod pag that corrsponds to ach font. Ignor any ignorabl dstination groups (that is, groups that start with "\*") othr than th HTMLTAG dstination group. Copy th rmaining contnt to th targt HTML documnt as follows: Any RTF scaps and RTF kywords that rprsnt Unicod charactrs MUST b convrtd to appropriat txt, and such txt MUST b copid to th targt HTML documnt. For a complt list and syntax of such scaps and control words, s [MSFT-RTF]. RTF scaps SHOULD b unscapd and th rsulting byts intrprtd in a cod pag that corrsponds to th currnt 16 / 33

17 font. Unicod charactrs producd from Unicod scaps (\un control word) and othr control words SHOULD b intrprtd as Unicod charactrs. Any \par and \lin RTF control words MUST b convrtd to CRLF and such CRLF squncs MUST b copid to th targt HTML documnt. Any \tab RTF control words MUST b convrtd to th horizontal tab (%x09) charactr, and such charactrs MUST b copid to th targt HTML documnt. Any othr RTF control words SHOULD b ignord. Any rmaining txt MUST b copid to th targt HTML documnt. Txt SHOULD b intrprtd in a cod pag that corrsponds to th currntly slctd font Extracting Original Plain Txt from RTF Th d-ncapsulating RTF radr MUST pars th RTF documnt as spcifid in [MSFT-RTF]. Bfor trying d-ncapsulation, it MUST first rcogniz th ncapsulatd contnt, as spcifid in sction To b abl to corrctly convrt txt insid RTF, th d-ncapsulating RTF radr SHOULD procss control words and othr information in RTF that affct th intrprtation of txt runs in RTF and a cod pag of such txt runs. For mor dtails about cod pag support, s [MSFT-RTF]. In particular, th d-ncapsulating RTF radr SHOULD us th dfault cod pag, as spcifid in th RTF hadr, and it SHOULD us th cod pag information, as spcifid for ach font in a font tabl. It SHOULD also track changs of a currnt font by following RTF txt, and us th appropriat cod pag for th currntly slctd font. Th d-ncapsulating RTF radr MUST skip othr parts of th RTF hadr, as spcifid in [MSFT-RTF]. Th d-ncapsulating RTF radr MUST xamin ach control tokn, translat it to its txtual quivalnt, and mit it to th output stram. Any RTF formatting control words that do not hav a txtual rprsntation MUST b ignord. Individual txtual charactrs can b scapd by RTF and ths SHOULD b convrtd to thir charactr quivalnts and mittd to th output stram (for xampl: "\{"," \}", "\\", and "\'HH"). Aftr unscaping, th rsulting byts SHOULD b intrprtd in a cod pag that corrsponds to th currntly slctd font. Unicod charactrs producd from Unicod scaps (\un control word) and othr control words SHOULD b intrprtd as Unicod charactrs. Th \par and \lin RTF control words SHOULD b translatd to CRLF and mittd to th output stram. Th \tab control word SHOULD b translatd to th horizontal tab (%x09) charactr, and such charactr SHOULD b mittd to th output stram. Any rmaining txt MUST b copid to th targt plain txt documnt. Txt SHOULD b intrprtd in a cod pag that corrsponds to th currntly slctd font Attachmnt and RTF Intgration To intgrat Attachmnt objcts into an RTF body, th list of Attachmnt objcts to intgrat MUST b rtrivd from th attachmnts tabl, as spcifid in [MS-OXCMSG] sction Th attachmnt list MUST only includ thos Attachmnt objcts that hav a PidTagAttachmntHiddn proprty ([MS-OXCMSG] sction ) whos valu is qual to FALSE (0x00) or non-xistnt, and a PidTagRndringPosition proprty ([MS-OXCMSG] sction ) whos valu is not qual to 0xFFFFFFFF. Whn th RTF radr is parsing RTF and it ncountrs an \objattph control word, it SHOULD add a nw instanc to th position array. Th position array stors th location in th data stram whr th 17 / 33

18 objct blongs. This location can b rprsntd as th numbr of charactrs from th bginning of th rndrd contnt. Aftr th RTF radr has finishd parsing th ntir RTF contnt and populating th position array, sufficint information is availabl to complt th intgration procss. Th numbr of valus in th position array SHOULD b compard to th numbr of valus in th attachmnts list (rtrivd from th attachmnts tabl). If th numbr of valus dos not match, th RTF radr ignors th locations spcifid in th position array and uss th data providd in th attachmnt list. This can b accomplishd by mptying th position array. Any xtra attachmnts SHOULD b insrtd at th nd of th rndrd RTF, or MAY<15> b insrtd using th rndring position stord in th PidTagRndringPosition proprty ([MS-OXCMSG] sction ) of th attachmnt. Th attachmnt list and th position array SHOULD b numratd in lock stp. For ach instanc, if a valu xists in th position array, th location spcifid in th position array SHOULD b usd as th insrt location. Th nxt stp is to prpar th attachmnt for insrtion. Th prparations ncssary for insrtion of an objct will vary dpnding on th RTF radr. For mor information, an implmntr should consult th documntation associatd with thir RTF radr. Aftr it is prpard, th location spcifid for th Attachmnt objct SHOULD b slctd. If th location in th position array is gratr than th numbr of rndrd charactrs in th body, th insrt<16> location is st to th nd of th rndrd RTF body. That location is thn rplacd with th prpard Attachmnt objct. At this point, th insrtion is complt, and th RTF radr movs to th nxt attachmnt in squntial ordr, and to th nxt ntry in th position array. As spcifid arlir in this sction, if thr ar not sufficint instancs in th position array, any rmaining attachmnts in th attachmnts list SHOULD b appndd to th nd of th RTF body, or MAY<17> b insrtd using th rndring position stord in th PidTagRndringPosition proprty of th attachmnt. If thr ar xtra valus in th position array, RTF radrs SHOULD simply ignor rndring thm, as spcifid in [MSFT-RTF]. For an xampl of attachmnt intgration, s sction / 33

19 3 Algorithm Exampls 3.1 Encapsulating HTML into RTF Having th following sourc HTML contnt: <HTML><had> <styl> <!-- /* Styl Dfinitions */ p.msonormal, li.msonormal {font-family:arial;} --> </styl> <!-- This is a HTML commnt. Thr is a horizontal tab (%x09) charactr bfor th commnt, and som nw lins insid th commnt. --> </had> <body> <p class="msonormal">not th lin brak insid a P tag. <b>this is bold txt</b> </p> <p class="msonormal"> This is a normal txt with a charactr rfrncs: < <br> charactrs that hav spcial maning in RTF: {}\<br> </p> <ol> <li class="msonormal">this is a list itm </ol> </body> </HTML> An ncapsulating RTF writr can (by conforming to this algorithm) produc th following RTF: {\rtf1\ansi\ansicpg1251\fromhtml1 \dff0 {\fonttbl {\f0\fmodrn Courir Nw;}{\f1\fswiss Arial;}{\f2\fswiss\fcharst0 Arial;}} {\colortbl\rd0\grn0\blu0;\rd0\grn0\blu255;} {\*\htmltag64} \uc1\pard\plain\dftab360 \f0\fs24 {\*\htmltag <HTML><had>\par <styl>\par <!--\par /* Styl Dfinitions */\par p.msonormal, li.msonormal \{font-family:arial;\}\par -->\par </styl>\par \tab <!-- This is a HTML commnt.\par Thr is a horizontal tab (%x09) charactr bfor th commnt, \par and som nw lins insid th commnt. -->\par </had>\par <body>\par <p\par class="msonormal">} {\htmlrtf \f1 \htmlrtf0 Not th lin brak insid a P tag. {\*\htmltag <b>}{\htmlrtf \b \htmlrtf0 This is a bold txt{\*\htmltag </b>}} \htmlrtf\par\htmlrtf0} \htmlrtf \par \htmlrtf0 {\*\htmltag </p>\par <p class="msonormal">\par} {\htmlrtf \f1 \htmlrtf0 This is a normal txt with a charactr rfrncs: {\*\htmltag }\htmlrtf \'a0\htmlrtf0 {\*\htmltag <}\htmlrtf <\htmlrtf0 {\*\htmltag }\htmlrtf {\f2\'a8}\htmlrtf0{\*\htmltag <br>\par}\htmlrtf\lin\htmlrtf0 charactrs which hav spcial maning in RTF: \{\}\\{\*\htmltag <br>\par}\htmlrtf\lin\htmlrtf0\htmlrtf\par\htmlrtf0} {\*\htmltag </p>\par <ol>\par 19 / 33

20 <li class="msonormal">}{\htmlrtf {{\*\pn\pnlvlbody\pndc\pnstart1\pnindnt360{\pntxta.}}\li360\fi-360{\pntxt 1.\tab} \f1 \htmlrtf0 This is a list itm}\htmlrtf\par\htmlrtf0} {\*\htmltag \par </ol>\par </body>\par </HTML>\par }} A d-ncapsulating RTF radr can rcovr th original HTML documnt from th RTF xampl in this sction by conforming to this algorithm. 3.2 Intgrating Sampl Attachmnts and RTF A usr has just rcivd a pic of -mail that thy would lik to opn and rad. Th following is a dscription of what a clint might do to accomplish th usr's intntions and th rsponss that a srvr might rturn. Th usr opns th Mssag objct by using th RopOpnMssag rmot opration (ROP) ([MS- OXCROPS] sction ) for an -mail mssag that just arrivd. It was snt with th mssag ID and foldr ID dscribd in th following tabl. Proprty nam Proprty ID Data typ Data PidTagFoldrId ([MS-OXCFOLD] sction ) 0x6748 PtypIntgr64 ([MS-OXCDATA] sction ) 0xBFE7F PidTagMid ([MS-OXCFXICS] sction ) 0x674A PtypIntgr64 0x95D Th body proprtis ar rtrivd to dtrmin which body format is appropriat to load, as dscribd in [MS-OXBBODY]. Th clint snds a RopGtProprtisSpcific ROP rqust ([MS-OXCROPS] sction ) and th srvr rsponds with th information dscribd in th following tabl. Prop rty nam P r o p rt y I D Da ta typ D at a Valu PidT agrt fins ync ([MS - OXC MSG] scti on ) 0 x 0 E 1 F Pty pb ool a n ([M S- OX CD AT A] sc tio n x Tru 20 / 33

21 21 / 33 Prop rty nam P r o p rt y I D Da ta typ D at a Valu ) PidT agbo dy ([MS - OXC MSG] scti on ) 0 x Pty pe rro rc od ([M S- OX CD AT A] sc tio n ) 0x NotEnoughMmory PidT agbo dyht ml ([MS - OXC MSG] scti on ) 0 x Pty pe rro rc od 0x f NotFound PidT agrt fco mpr ss d ([MS - OXC MSG] scti on ) 0 x Pty pbi na ry ([M S- OX CD AT A] sc tio n ) 26 1 By t s C 5A B3 {\rtf1\ansi\ansicpg1252\dff0\dflang1033{\fonttbl{\f0\fswiss\fcharst0 Arial;}}<CR><LF>{\*\gnrator<SP>Richd20<SP> ;}\viwkind4\uc1\pa rd\f0\fs20<sp>this<sp>is<sp>a<sp>tst<sp>mail.\par<cr><lf>\objattph\'20\pa r<cr><lf>\par{\*\optional<sp>with<sp>an<sp>optional<sp>lin\par}<cr><lf>l ts<sp>hav<sp>anothr<sp>attachmnt\par<cr><lf>\objattph\'20\par<cr><lf> \par<cr><lf>adding<sp>a<sp>pictur\par<cr><lf>\objattph\'20\par<cr><lf>}

22 Prop rty nam P r o p rt y I D Da ta typ D at a Valu B A F8 0B 60 6E 0E F 01 F7 02 A4 03 E A C0 73 B D 0A 80 9D A 22 / 33

23 Prop rty nam P r o p rt y I D Da ta typ D at a Valu 09 B0 09 F B1 1A 52 0D E D E C E E 01 D0 13 A C B 0B A 34 0C B 03 0B 23 / 33

24 Prop rty nam P r o p rt y I D Da ta typ D at a Valu B A D C E 0A A2 0A 81 6F A 12 A C 27 AF 0C A B F E5 24 / 33

25 Prop rty nam P r o p rt y I D Da ta typ D at a Valu F A D A 6C 0B A A2 11 E1 4C E9 10 F A 51 6F 1A FB D F / 33

26 Prop rty nam P r o p rt y I D Da ta typ D at a Valu 8A 0A 80 A B D E0 5E B 53 1D DF 20 A2 7D Basd on th srvr rsponss, th propr body to load is th valu of th PidTagRtfComprssd proprty. Th PidTagRtfComprssd proprty is stord in a packd format; by using th RTF Comprssion Algorithm, as dscribd in [MS-OXRTFCP], th contnt is dcodd and th raw RTF is as follows: {\rtf1\ansi\ansicpg1252\dff0\dflang1033{\fonttbl{\f0\fswiss\fcharst0 Arial;}}<CR><LF>{\*\gnrator<SP>Richd20<SP> ;}\viwkind4\uc1\pard\f0\fs20<SP>Thi s<sp>is<sp>a<sp>tst<sp>mail.\par<cr><lf>\objattph\'20\par<cr><lf>\par{\*\optional<sp>with<sp>an<sp>optional<sp>lin\ par}<cr><lf>lts<sp>hav<sp>anothr<sp>attachmnt\par<cr><lf>\objattph\'20\par<cr><lf>\par<cr ><LF>Adding<SP>a<SP>pictur\par<CR><LF>\objattph\'20\par<CR><LF>} This algorithm is thn usd to dtrmin whthr th RTF is ncapsulatd by xamining th RTF tokns bfor th font tabl dstination. Bcaus th FROMHTML and FROMTEXT control words ar not found in th RTF hadr, th contnts ar not ncapsulatd. As th body is loadd and th RTF radr parss th RTF, th rndr position of ach \objattph tokn is calculatd and stord in an array similar to that which is dscribd in th following tabl. 26 / 33

27 Position array Not Thr is an optional dstination (\optional) that is not undrstood by th RTF radr. This affcts th rndrd tokn locations, as th contnts "with an optional lin < CRLF >" ar not rndrd. Whn th body parsing is complt and th xistnc of placholdr tokns is rcordd, th attachmnts from th mssag ar loadd. Th following ROP rqusts ar transmittd to th srvr: Th RopGtAttachmntTabl ROP ([MS-OXCROPS] sction ). Th RopStColumns ROP ([MS-OXCROPS] sction ), which rqusts th PidTagAttachNumbr ([MS-OXCMSG] sction ), PidTagAttachMthod ([MS-OXCMSG] sction ), PidTagRndringPosition ([MS-OXCMSG] sction ), PidTagAttachLongFilnam ([MS-OXCMSG] sction ), and PidTagAttachmntHiddn ([MS-OXCMSG] sction ) proprtis. Th RopQuryRows ROP ([MS-OXCROPS] sction ). Th rspons buffr from th RopQuryRows ROP contains thr rows, as dscribd in th following thr tabls. Row 1 Proprty nam Proprty ID Data typ Data Valu PidTagAttachNumbr 0x0E21 PtypIntgr32 ([MS-OXCDATA] sction ) 0x PidTagAttachMthod 0x3705 PtypIntgr32 0x afbyvalu PidTagRndringPosition 0x370B PtypIntgr32 0x PidTagAttachLongFilnam 0x3707 PtypString ([MS- OXCDATA] sction ) C 00 6C 00 6F F C E "hlloworld.txt" PidTagAttachmntHiddn 0x7FFE PtypBoolan 0x0000 FALSE Row 2 Proprty nam Proprty ID Data typ Data Valu PidTagAttachNumbr 0x0E21 PtypIntgr32 0x PidTagAttachMthod 0x3705 PtypIntgr32 0x afbyvalu PidTagRndringPosition 0x370B PtypIntgr32 0x PidTagAttachLongFilnam 0x3707 PtypString C 00 6C 00 6F F C "hlloworld.doc" 27 / 33

28 Proprty nam Proprty ID Data typ Data Valu E F PidTagAttachmntHiddn 0x7FFE PtypBoolan 0x0000 FALSE Row 3 Proprty nam Proprty ID Data typ Data Valu PidTagAttachNumbr 0x0E21 PtypIntgr32 0x PidTagAttachMthod 0x3705 PtypIntgr32 0x afol PidTagRndringPosition 0x370B PtypIntgr32 0x A 100 PidTagAttachLongFilnam 0x3707 PtypString "PBrush" PidTagAttachmntHiddn 0x7FFE PtypBoolan 0x0000 FALSE Bcaus th attachmnts ar alrady ordrd corrctly by rndring position, thy do not nd to b rordrd. Bcaus th attachmnt list is thr ntris long, and th prviously constructd position array is also thr ntris long, th insrtion positions com from th position array. This rsults in rplacing th scond and third attachmnts at diffrnt positions than thos st in th valu of th PidTagRndringPosition proprty. Spcifically, th scond attachmnt ("hlloworld.doc") will rplac position 54, not 76, and th third attachmnt will rplac position 74, not 100. Looping ovr th stord objattph positions in th position array, ach attachmnt is prpard for insrtion. Th first attachmnt ("hlloworld.txt") rplacs rndrd charactr position 22. Th scond attachmnt ("hlloworld.doc") rplacs th rndrd charactr position 54. Finally, th last attachmnt ("PBrush") rplacs th rndrd charactr position 74. Bcaus thr ar no additional attachmnts, th intgration is complt. 28 / 33