Tickets :: Comment on [#8160] bad mime viewer on rtf may be due to base64 encoding

* Your Email Address
* Spam protection	Enter the letters below: .__ . ..__. __.. \| \\|\/\|[__](__ \| \|__/\| \|\| \|.__)\|___
Comment	>> This one does not work > >> --=_431d1cd1bf52dffeb4eb3d03f4030979 > >> Content-Transfer-Encoding: base64 > >> Content-Type: text/rtf; charset="UTF-8"; > >> name="UTF-8''D%C3%A9cret SCD 85-694 en 2009.rtf"; > >> Content-Disposition: attachment; > >> filename="UTF-8''D%C3%A9cret SCD 85-694 en 2009.rtf"; > > > > FWIW, this is incorrect encoding under RFC 2184. But this has > nothing to do with the below issue: > > > >> And one is encoded in base 64 > >> > >> and it produces: > >> {\rtf1\ansi\ansicpg1252\uc1 > >> \deff0\deflang1036\deflangfe1036{\fonttbl{\f0\froman\fcharset0\fprq2{\\panose 02020603050405020304}Times New Roman;}{\f2\fmodern\fcharset0\fprq1{\\panose >> 02070309020205020404}Courier > >> New;} > >> {\f3\froman\fcharset2\fprq2{\\panose > >> 05050102010706020507}Symbol;}{\f14\fnil\fcharset2\fprq2{\\panose > >> 05000000000000000000}Wingdings;}{\f27\fswiss\fcharset0\fprq2{\*\panose > >> 020b0604030504040204}Tahoma;}{\f28\froman\fcharset238\fprq2 Times New > >> Roman CE;} > > > > That's exactly what is expected. That is the contents of the > text/rtf file. IMP/Horde does not have any specific RTF conversion > viewer, so it will display the raw contents of the text file. > >
Attachment
Watch this ticket