As I found when playing around with the MAILTO this morning, you need a machine that supports Japanese within Outlook (this is typically a Japanese OS installed). The following does not work on an English machine but it does when running Japanese OS:
<a href="mailto:?Content-type:ISO-2022-JP&Context-Language=ja&subject=%E9%9B%BB%E5%AD%90%E3%83%A1%E3%83%BC%E3%83%AB&body=%E9%9B%BB%E5%AD%90%E3%83%A1%E3%83%BC%E3%83%AB";>Japanese mailto</a> >On Fri, 12 Mar 2004 08:56:26 -0500 Rick Evans <[EMAIL PROTECTED]> wrote. >I went round and round trying to get mailto attachments to work and it >turns out that there just is not a whole lot that the MAILTO tag >supports. The link I sent has links to the official documents at >Microsoft of what they support and then they link to the original RFC >document. I found a full explanation of the mail headers at: > > http://www.faqs.org/rfcs/rfc3282.html > >This document had a link to the document you need at the bottom, which >explains how to send non-ASCII text in a body: > > http://www.faqs.org/rfcs/rfc2047.html > >I am checking with a friend of mine who is Japanese to see how to do >this exactly. > >On Thursday, March 11, 2004, at 09:58 PM, Susan Henshaw wrote: > >> >> Went down that path too, by adding: >> Mailto:?Content-type:text/html&body=mailbody >> >> That did nothing to help. >> >> I also tried: >> <A lang="jp" href="mailto:sameoldstuff";> >> >> No amount of google-searching has offered any other tips either. A >> frustrating kind of problem. >> >> Cheers, >> Sue >> >> >> On 3/11/04 9:20 PM, "Richard O. Hammer" <[EMAIL PROTECTED]> wrote: >> >>> Susan Henshaw wrote: >>>> The Japanese characters are in the body of the mail, not in the email >>>> address. >>> >>> Yes. Sorry I didn't pick that up at first. I've got another link, to >>> a document which seems relevant as I understand your problem now. >>> "The mailto URL scheme" <http://ftp.isi.edu/in-notes/rfc2368.txt> >>> >>> From scanning that RFC it is not clear to me that you can use >>> Japanese characters, even if encoded, in that place. >>> >>> But if you can I guess this problem would come up: You are creating a >>> generic, very simple email message, so probably the programs which >>> handle it assume you are working with the default character set, which >>> would be ASCII or something like it. If you create a message in which >>> the body has a different character set then you have to specify that >>> charset in the headers of the email message, so the mail client knows >>> how to decode the characters, and you have not done that, although >>> maybe you could by using the mailto protocol to set a Content-type >>> heading. >>> >>> Rich Hammer >>> >>> >>> _______________________________________________ >>> Juglist mailing list >>> [EMAIL PROTECTED] >>> http://trijug.org/mailman/listinfo/juglist_trijug.org >> >> >> _______________________________________________ >> Juglist mailing list >> [EMAIL PROTECTED] >> http://trijug.org/mailman/listinfo/juglist_trijug.org >> >> > >Rick Evans >http://www.bhaktivani.com >http://www.mergingcurrents.com > > >_______________________________________________ >Juglist mailing list >[EMAIL PROTECTED] >http://trijug.org/mailman/listinfo/juglist_trijug.org _______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
